3cx 488 Not acceptable error from VOIP.MS.

[tspjoker]

just let you guys know that if your encrypted sip traffic press"yes. then you will getting 3cx 488 Not acceptable error from VOIP.MS.
better put as "No" as default. but idk why I am getting error...lol

 

[YiannisH_3CX]

Hi @tspjoker

Its not enough to enable the setting in the Voip.ms side only. There is also configuration that needs to be done in the 3CX side as well but we never tested this so I cannot share any details. You are probably sending something to Voip.ms that is not compatible with their encryption requirements that is why you are getting a 488.
Since we haven't tested this and we do not support it I would suggest not enabling on the Voip.ms side either to avoid any compatibility issues.

 

[tspjoker]

Hi @tspjoker

Its not enough to enable the setting in the Voip.ms side only. There is also configuration that needs to be done in the 3CX side as well but we never tested this so I cannot share any details. You are probably sending something to Voip.ms that is not compatible with their encryption requirements that is why you are getting a 488.
Since we haven't tested this and we do not support it I would suggest not enabling on the Voip.ms side either to avoid any compatibility issues.

but this is what exactly they want me to do.???
https://wiki.voip.ms/article/Call_Encryption_-_TLS/SRTP#Configuration_on_SIP_Client
and as soon as i enable this getting error message

 

[cobaltit]

Did you read the entire article or read what @YiannisH_3CX posted? That setting turns on encrypted traffic on the voip.ms side of things. Then it says this:

That means you have to enable encryption on the 3CX side. As mentioned, 3CX has not tested this so you are better off leaving it off.

 

[YiannisH_3CX]

but this is what exactly they want me to do.???
https://wiki.voip.ms/article/Call_Encryption_-_TLS/SRTP#Configuration_on_SIP_Client
and as soon as i enable this getting error message

Since we have not tested this our implementation may not be compatible with the implementation of Voip.ms which might be causing your issues. Even if the trunks are registered using TLS calls might still fail for any number of reasons.