- Joined
- Aug 19, 2017
- Messages
- 1
- Reaction score
- 0
G'day!
We're just starting experiencing an odd problem; for only a few of our extensions, calls to them are failing with error code 406. I haven't been able to identify any common reason why they'd be failing, yet other extensions would work fine. It occurs when the extension is dialed directly from another 3CX user, or when they are dialed from an outside line.
I'm seeing the following in the logs on a failed call:
I've captured a packet trace to compare a successful call against an unsuccessful call, but I'm not seeing anything that's different. 406 tends to mean there's a problem with the method in the SIP message header, correct?
Any insight on where to investigate next would be greatly appreciated. Any further details that I can provide please let me know.
Thanks!
-Matt
We're just starting experiencing an odd problem; for only a few of our extensions, calls to them are failing with error code 406. I haven't been able to identify any common reason why they'd be failing, yet other extensions would work fine. It occurs when the extension is dialed directly from another 3CX user, or when they are dialed from an outside line.
I'm seeing the following in the logs on a failed call:
Code:
08/18/2017 5:24:53 PM - Call to T:Extn:5034@[Dev:sip:[email protected]:50195;transport=TCP;rinstance=1-5671967b34114fb19534e30ad6373e6f;ob] from L:1733.1[Extn:5025] failed, cause: Cause: 406 Not Acceptable/INVITE from 127.0.0.1:5080
08/18/2017 5:24:53 PM - [CM503003]: Call(C:1733): Call to <sip:[email protected]:5060> has failed; Cause: 406 Not Acceptable/INVITE from 127.0.0.1:5080
I've captured a packet trace to compare a successful call against an unsuccessful call, but I'm not seeing anything that's different. 406 tends to mean there's a problem with the method in the SIP message header, correct?
Any insight on where to investigate next would be greatly appreciated. Any further details that I can provide please let me know.
Thanks!
-Matt