VoiceBlue Next replied: 406 Not Acceptable

[coopcsc]

Hi,
I have 3CX V16.0.5.619 version with "2N VoiceBlue Next" GSM gateway with last firmware.
All perfectly works for some years but now I receive this error when I call a number and "outbound rules" route the call to GSM gateway:

SIP Server/Call Manager ID: 12294
Call or Registration to 3357987900@(Ln.10001@GSM) has failed. 10.0.0.43 replied: 406 Not Acceptable; from IP:10.0.0.43:5060

I tried to reboot 3CX and "VoiceBlue Next" but not work. I never change any settings on both.

Thank you very much in advance for your help.

Regards,
Davide

 

[leejor]

You will need to determine if the 406 reply is coming from the gateway itself (incorrect number format?), or, as a result of a message from the GSM provider (does the SIM work when put into a phone, and the same number called?). Does the gateway have a syslog available to use for troubleshooting?

Is it just calls to a specific number, that fail?

 

[cobaltit]

As this is VoiceBlue replying to 3CX and not 3CX replying to VoiceBlue you need to talk to VoiceBlue to figure out why.

 

[coopcsc]

Hi,
I missed to say that I test VoiceBlue and with VoiceBlue webgui I can call any number.
And incoming calls all works perfectly as before.

 

[leejor]

Are there logs available (syslog, Telnet, GUI), in the gateway, that can perhaps explain the 406 Not Acceptable message? Does setting the 3CX Activity Log to Verbose, offer additional information. Incompatible Codec perhaps? Was there an update done, on 3CX, or the gateway?

 

[coopcsc]

this is the log and I changed real phone number with 3333333333

16:39:40.61 -->SIP 10.0.0.41:5060 (5060)
"INVITE sip:[email protected]:5060;user=phone;phone-context=10001 SI..."
"Via: SIP/2.0/UDP 10.0.0.41:5060;branch=z9hG4bK-524287-1---ac4668599942..."
"Max-Forwards: 70"
"Contact: <sip:[email protected]:5060>"
"To: <sip:[email protected]:5060;user=phone;phone-context=10001>"
"From: "David"<sip:[email protected]:5060;user=phone;phone-cont..."
"Call-ID: hYCv1WBSSf06EEesm1q_MA.."
"CSeq: 1 INVITE"
"Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY,..."
"Content-Type: application/sdp"
"Supported: replaces, timer"
"Content-Length: 271"
""
"v=0"
"o=3cxPS 53452210176 231525580801 IN IP4 10.0.0.41"
"s=3cxPS Audio call"
"c=IN IP4 10.0.0.41"
"t=0 0"
"m=audio 7868 RTP/AVP 0 8 9 3 101"
"a=rtpmap:0 PCMU/8000"
"a=rtpmap:8 PCMA/8000"
"a=rtpmap:9 G722/8000"
"a=rtpmap:3 GSM/8000"
"a=rtpmap:101 telephone-event/8000"
"a=sendrecv"
16:39:40.61 <++SIP 10.0.0.41:5060 (5060)
"SIP/2.0 406 Not Acceptable"
"Max-Forwards: 70"
"Via: SIP/2.0/UDP 10.0.0.41:5060;branch=z9hG4bK-524287-1---ac4668599942..."
"From: "David" <sip:[email protected]:5060;user=phone;phone-con..."
"To: <sip:[email protected]:5060;user=phone;phone-context=10001>"
"Call-ID: hYCv1WBSSf06EEesm1q_MA.."
"CSeq: 1 INVITE"
"Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY,..."
"Supported: replaces, timer"
"Allow: INVITE,BYE,ACK,CANCEL,OPTIONS,REFER,NOTIFY"
"Content-Length: 0"
""
16:39:40.62 -->SIP 10.0.0.41:5060 (5060)
"ACK sip:[email protected]:5060;user=phone;phone-context=10001 SIP/2..."
"Via: SIP/2.0/UDP 10.0.0.41:5060;branch=z9hG4bK-524287-1---ac4668599942..."
"Max-Forwards: 70"
"To: <sip:[email protected]:5060;user=phone;phone-context=10001>"
"From: "David"<sip:[email protected]:5060;user=phone;phone-cont..."
"Call-ID: hYCv1WBSSf06EEesm1q_MA.."
"CSeq: 1 ACK"
"Content-Length: 0"
""

 

[leejor]

Was there anything after that? It shows and INVITE, and an ACK, but nothing indicating why the call ended.

 

[coopcsc]

not any alse

 

[leejor]

Sorry, missed the "SIP/2.0 406 Not Acceptable" at 16:39:40.61 , in the first part.

 

[leejor]

I'm wondering if it has something to do with the Media Description, or perhaps Codec choice?

https://www.3cx.com/blog/voip-howto/sdp-voip2/

 

[coopcsc]

Hi, how I can verify, test and correct that problem?

 

[JohnS_3CX]

Hi,

Since this is not a supported device, you can either get help from the manufacturer or if you are familiar with SIP you can try to analyze with wireshark.

Meanwhile, you can also check the 2N logs to see perhaps why it replied. Generally the 406 means that the device received a request that it does not accept, but the SIP trace might not make that clear, which means the 2N logs might have some extra information.

If all else fails, you can backup its config, and reset it and start from scratch to set it up