-
Notifications
You must be signed in to change notification settings - Fork 704
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
ESP not responding to OPTIONS during registration process (AUD-5034) #1111
Comments
Hi @davidedigesualdo , Our SIP client usually replies with "200 OK" to the 'OPTIONS' message, but not during registration process. Maybe you could turn off the 'OPTIONS' message on the PBX ? In addition, we also support configuring the 'OPTIONS' message on client side here. The other thing is why the 'OPTIONS' message is sent before the registration is replied. Maybe you can try to use TCP/TLS to registration to the server. br. |
Hi @ahhfzhang, Unfortunately the PBX is a public service which is not directly managed by me. I've already notified the PBX customer service, but they cannot switch off the OPTIONS during the registration process. Moreover, the RFC 3261 (SIP: Session Initiation Protocol) doesn't prevent the UAS to send an OPTIONS message to the UA during the registration process, so the correct behaviour should be the UA to answer to the OPTIONS message. I've tried to use TCP connection, and the behaviour is the same. |
Hi, |
+1, the same problem with public voip provider, it works great on fritzbox voip device, but not with public providers :( |
Environment
Problem Description
I tried to build and run the example code under "examples/protocols/voip". Codec and streams initializations are ok.
When the SIP client tries to register to the SIP PBX (Asterisk), the PBX replies with "Auth requested". Then the SIP client sends authenticated registration message, and the SIP PBX replies with an OPTIONS message. The client doesn't reply, but restarts the loop of registration.
Expected Behavior
Into the "Allow" string the SIP client sends "OPTIONS", so it should implement "OPTIONS" methods.
The expecteed behaviour is the SIP client replies with "200 OK" to the options message, so the PBX sends "200 OK" to the REGISTER message and the registration process is complete.
Actual Behavior
The SIP client doesn't reply to the PBX OPTIONS message and restarts the registration process again and again.
Debug Logs
Suggestions
It would be great if you can add the possibility to customize the allowed methods in the SIP client configuration, so that a developer can enable/disable the supported methods.
The text was updated successfully, but these errors were encountered: