Solved Server Error/No Ports

[c.holloway]

Recently we've been seeing an error in our version 15 instances both when receiving incoming calls and when placing outbound calls. The issue is intermittent and I currently only have an example of a call coming in to a ring group that failed to call all members of the group due to this error. I have attached what I pulled from the logs, reordered top down and with IP addresses changed.

The error, to me, suggests an RTP issue but I could be totally wrong about that.

 

[craigreilly]

This log file doesn’t show much - I see 101 is not registered and another extension is Busy.
Not sure how many phones in the ring group- if Pbx is local or cloud based, etc.
lots of things could be wrong.
Did anything get changed recently?
Firewall checker ok?
Calls to individual extensions on?
What does log say on failed outbound calls?

 

[c.holloway]

There are 6 phones in the ring group. I'm not particularly concerned with the extensions that weren't registered or busy. Those are normal things I know how to address.

Recently they were updated to SP5 and I moved them from using custom templates to using the standard template from 3CX. (The custom template was to set up the outbound proxy settings on the phone so I didn't have to manually set it on each phone)

I believe the firewall checker fails the full cone NAT test. However, this has always been the case and the issue is pretty recent.

We've experienced the error on calls to other extensions, particularly this same call when 103 tried to transfer the received call to another DN. I can update the ticket with those logs if you think it will be helpful but they're no more descriptive than the logs already attached. The call is terminated with the cause 500 Server Error/No Ports/INVITE from ~~SBCWANIP~~:5094

 

[YiannisH_3CX]

Hello @c.holloway

The only other time i have seen this error was when UDP was switching to TCP but to figure out what is causing this in your case you will need a trace of an affected call and the PBX logs in verbose logging level. With that in mind i would recommend creating a ticket with our support department so they can have a look at the PBX logs and determine the cause of the issue. Make sure you pass the firewall checker first though.

 

[c.holloway]

YiannisH,

I turned up verbose debugging and I'm finding that on the calls that fail, the GSM codec is being negotiated for some reason, even though its not utilized anywhere in my config and to my knowledge the Yealink t42 doesn't even support it. I imagine this is what is causing our problems so i'm currently pursuing how/why this codec is being negotiated. I'll post back if/when I find more.

 

[YiannisH_3CX]

Make sure that the codecs you are looking at are not between the provider and the PBX. The PBX and the phone could be using a different codec for audio.

 

[c.holloway]

Update:

I changed the external call codec preference as described in this post: https://www.3cx.com/community/threads/codec-order.48537/

This was the only place in the system or on the phones themselves that GSM was referenced at all. Changing the codec order here to have GSM at the end and G711ulaw and g729 as the first and second codec preferred for external calls SEEMS to have fixed it. I've made this change for two clients and so far it hasn't reoccurred. I'll post back if we go a few more days without a reoccurance

 

[YiannisH_3CX]

Thank you for the update. Let us know if you face any more issues.

 

[c.holloway]

It's been a couple weeks without a repeat of the issue. I think we can consider this one closed

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for the update.