SIP trunk stops working every circa 30 min (and needs restart)

[jaalsa]

Hello:

I have a generic SIP trunk setup (with Telefónica FTTH, in Spain) which works fine until it stops working. Then I have to disable/enable it and starts working for the same amount of time.

I have put together some Wireshark captures of the relevant events with some descriptions added. I hope it is useful to know what is going on an how to solve it. The capture has been made in the same machine 3CX PBX (ver 16.0.7.1078) is installed (10.7.1.35). The is no NAT, the access to the provider's SIP server (10.31.255.134) is through a specific VLAN and routes received by RIP. In the firewall all is allowed to/from this interface.



Plase, let me know if you know more details.

Thanks!

 

[leejor]

First of all I question why the trunk is registering every minute. Is that something you've manually set? It seems excessive, and many providers tend to frown on registrations happening that often. Have you contacted the provider to see if they have any insight?

You say you disable, then re-enable the "tunnel", which tunnel are you talking about?

Was this working previously, then began having issues, or a new install?

 

[jaalsa]

Hi,

Thanks for the answer.

The re-register time is the default for a generic trunk: 180.

It re-registers every minute because the provider seems to ask for that:

If set my re-register time to 3600 (for example) the same happens.

I have not contacted the provider about this. I'm not sure they will anwer because altough they let the users do this and they are ok with it, they don't provide official support. It is like a perk that comes with this residential connection. I've seen in these forums users using the same service but without this issue.

Anyway, during this "re-register every 70 s" phase everything works ok (see final comment).

By disable and enable the "tunnel" I meant the trunk. My mistake.

New install, never used it before.

I'm no expert, but what concerns me is that the trunk stops working when 3CX sends the register message with "remove 1 binding" comment. It seems that at this point is like the 3CX de-registers from ISPs SIP (thus the 403 forbidden I guess).

Thanks again!

 

[NickD_3CX]

First, to avoid these kind of issues, we recommend using a Supported 3CX SIP Trunk provider.
You generally won't have these problems, but if you do, 3CX Partners and support should be in a much better position to help you.

On your case, something that seems strange is the 200 OK with the 3 bindings towards the end of the screenshot you sent. That usually means that your provider is seeing 3 different registrations.

The only other advice I could give is check that the DID numbers in 3CX are entered exactly in the same format as the provider is sending them.