Skip to content
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

Open
ShineYangGod opened this issue Nov 24, 2022 · 13 comments
Open

[Bug]: Crash occurs when using TCP to register sip number #219

ShineYangGod opened this issue Nov 24, 2022 · 13 comments
Labels

Comments

@ShineYangGod
Copy link

Context

I crashed when registering a sip number using the TCP [protocol]
log.txt

General information

  • Device: iPhone 12
  • OS:iOS
  • Version of the App:
  • Version of the SDK:5.0.50

Expected behaviour

You can register successfully

To Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Additional context

Add any other context about the problem here.

SDK logs URL

No response

@Viish
Copy link
Member

Viish commented Nov 24, 2022

Hi,

First of all please update to latest release (5.1.71). 5.0.X SDK isn't supported anymore.
Then if issue still happens please attach the stack trace.

Cheers,

@ShineYangGod
Copy link
Author

Hello, I have updated to 5.1.71, but a Drop frame appears when sending a message because we are waiting for reference frame

@Viish
Copy link
Member

Viish commented Nov 25, 2022

Sorry but I don't understand your issue.
Can you be more explicit and attach logs?

@ShineYangGod
Copy link
Author

截屏2022-11-25 16 09 51

How can I get the remote domain name instead of the ip address, because the address that the remote device calls is actually a domain name?For example this test.homecity365.com

@ShineYangGod
Copy link
Author

When I send a message, there seems to be a loop problem, and I have been unable to send it successfully
log.txt

@Viish
Copy link
Member

Viish commented Nov 25, 2022

Please enable debug logs, only warnings and error don't help much in this case.

@ShineYangGod
Copy link
Author

log.txt
截屏2022-11-25 17 26 43
I have enabled the log, and the receiver here should be the same as the domain name sent by the sender. Why is the IP address resolved?

@Viish
Copy link
Member

Viish commented Nov 25, 2022

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).

@ShineYangGod
Copy link
Author

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

@Viish
Copy link
Member

Viish commented Nov 25, 2022

If headers are wrong for SIP packets you receive, it's probably your proxy server that doesn't do it's job properly.
Are you using Asterisk?

@ShineYangGod
Copy link
Author

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?
Our Android also uses the sdk, and the Android sdk gets the domain name

@ShineYangGod
Copy link
Author

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?

@ShineYangGod
Copy link
Author

Hello, I am using the linphone SDK, when I answer the call and turn on the video, there will be a thread problem, I hope it can be resolved
截屏2023-01-12 15 55 39

The version I am using is 5.1.71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants