I've been working on a registration issue across 5 different servers where the trunk shows registered in the dashboard however the system is not able to take calls and when checking with the SIP provider it shows the trunk as not registered. To be clear this is partially an issue with the SIP provider as they are accepting the DNS registration on the second attempt and then their system will not resolve the IP, the call becomes unroutable and their system give a 404 error.
Order of events:
3CX sends registration as normal
Within milliseconds 3CX sends a second registration using DNS name instead of IP
Trunk provider gives 401 Unauthorized response
3CX sends 2nd registration with DNS name
Trunk provider gives 200 OK response
Registration examples below:
Normal contact - sip:[email protected]:5060
DNS contact - sip:[email protected].3cx.us
Any thoughts on this? I can't reproduce as the behavior is random across 3 different servers. A reboot or registration refresh resolves the issue. For 3 or the 5 servers the problem has not come back. 2 servers continue to do this randomly. How can I stop 3CX from sending DNS name in the contact field?
Order of events:
3CX sends registration as normal
Within milliseconds 3CX sends a second registration using DNS name instead of IP
Trunk provider gives 401 Unauthorized response
3CX sends 2nd registration with DNS name
Trunk provider gives 200 OK response
Registration examples below:
Normal contact - sip:[email protected]:5060
DNS contact - sip:[email protected].3cx.us
Any thoughts on this? I can't reproduce as the behavior is random across 3 different servers. A reboot or registration refresh resolves the issue. For 3 or the 5 servers the problem has not come back. 2 servers continue to do this randomly. How can I stop 3CX from sending DNS name in the contact field?
