-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Crash occurs when using TCP to register sip number #219
Comments
Hi, First of all please update to latest release (5.1.71). 5.0.X SDK isn't supported anymore. Cheers, |
Hello, I have updated to 5.1.71, but a Drop frame appears when sending a message because we are waiting for reference frame |
Sorry but I don't understand your issue. |
When I send a message, there seems to be a loop problem, and I have been unable to send it successfully |
Please enable debug logs, only warnings and error don't help much in this case. |
log.txt |
FROM and TO header for sent SIP MESSAGEs are set by the app. So if there is an issue with those headers check that your app is setting them properly or that you don't answer to a message that was sent with such header (common issue with Asterisk for example). |
When I get the address of the caller on the answering call page, it is also wrong. It is also the ip address obtained, not the domain name. The correct one should be the domain name |
If headers are wrong for SIP packets you receive, it's probably your proxy server that doesn't do it's job properly. |
I consulted the operation and maintenance engineer, but I don't know what the header you are talking about is? Can you describe it more clearly? |
Hello, is it possible to register multiple sip numbers at one time? We have a scenario where multiple sip numbers need to be registered at one time. I used a loop to register multiple sip numbers, but when I send a message, the port used to send the message is always the port of the last sip number. I have incoming What's the matter with the sip number and port? |
Context
I crashed when registering a sip number using the TCP [protocol]
log.txt
General information
Expected behaviour
You can register successfully
To Reproduce
Additional context
Add any other context about the problem here.
SDK logs URL
No response
The text was updated successfully, but these errors were encountered: