PJSIP extensions become Unreachable

FreePBX
1

Hi,

I’ve a Freepbx Distro (last version) installed on a VM in a cloud.
Freepbx 14 Current Asterisk Version: 13.22.0

I’ve 5 different locations (branch) with phones connected to this Cloud PBX.

Regularly (twice a week), I’ve all phones even from the same location that become Unreachable.
I need to reboot the PBX to make them reachable again. It is very unpleasant for me and my client (business environnement).

This morning, before reboot the PBX, I copy the log file :

[2019-05-14 07:52:45] VERBOSE[17894] res_pjsip/pjsip_configuration.c: Endpoint 105 is now Unreachable
[2019-05-14 07:52:45] VERBOSE[17894] res_pjsip/pjsip_options.c: Contact 105/sip:[email protected]:61100 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:52:56] VERBOSE[23518] res_pjsip/pjsip_configuration.c: Endpoint 104 is now Unreachable
[2019-05-14 07:52:56] VERBOSE[23518] res_pjsip/pjsip_options.c: Contact 104/sip:[email protected]:61134 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:10] VERBOSE[17894] res_pjsip/pjsip_configuration.c: Endpoint 108 is now Unreachable
[2019-05-14 07:53:10] VERBOSE[17894] res_pjsip/pjsip_options.c: Contact 108/sip:[email protected]:61128 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:15] VERBOSE[17894] res_pjsip/pjsip_configuration.c: Endpoint 100 is now Unreachable
[2019-05-14 07:53:15] VERBOSE[17894] res_pjsip/pjsip_options.c: Contact 100/sip:[email protected]:61089 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:15] VERBOSE[10652] res_pjsip/pjsip_configuration.c: Endpoint 103 is now Unreachable
[2019-05-14 07:53:15] VERBOSE[10652] res_pjsip/pjsip_options.c: Contact 103/sip:[email protected]:61143 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:22] VERBOSE[1969] res_pjsip/pjsip_configuration.c: Endpoint 101 is now Unreachable
[2019-05-14 07:53:22] VERBOSE[1969] res_pjsip/pjsip_options.c: Contact 101/sip:[email protected]:61132 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:29] VERBOSE[23518] res_pjsip/pjsip_configuration.c: Endpoint 102 is now Unreachable
[2019-05-14 07:53:29] VERBOSE[23518] res_pjsip/pjsip_options.c: Contact 102/sip:[email protected]:8782 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:38] VERBOSE[1969] res_pjsip/pjsip_configuration.c: Endpoint 107 is now Unreachable
[2019-05-14 07:53:38] VERBOSE[1969] res_pjsip/pjsip_options.c: Contact 107/sip:[email protected]:61130 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:53:38] VERBOSE[23518] res_pjsip/pjsip_configuration.c: Endpoint 106 is now Unreachable
[2019-05-14 07:53:38] VERBOSE[23518] res_pjsip/pjsip_options.c: Contact 106/sip:[email protected]:61142 is now Unreachable. RTT: 0.000 msec
[2019-05-14 07:54:13] VERBOSE[23518] res_pjsip/pjsip_options.c: Contact 100/sip:[email protected]:61089 has been deleted
[2019-05-14 07:54:13] VERBOSE[23518] res_pjsip/pjsip_options.c: Contact 101/sip:[email protected]:61132 has been deleted
[2019-05-14 07:54:13] VERBOSE[17894] res_pjsip/pjsip_options.c: Contact 102/sip:[email protected]:8782 has been deleted
[2019-05-14 07:54:13] VERBOSE[10652] res_pjsip/pjsip_options.c: Contact 105/sip:[email protected]:61100 has been deleted
[2019-05-14 07:54:13] VERBOSE[1969] res_pjsip/pjsip_options.c: Contact 106/sip:[email protected]:61142 has been deleted
[2019-05-14 07:54:13] VERBOSE[23518] res_pjsip/pjsip_options.c: Contact 107/sip:[email protected]:61130 has been deleted
[2019-05-14 07:54:19] VERBOSE[17894] res_pjsip/pjsip_options.c: Contact 103/sip:[email protected]:61143 has been deleted
[2019-05-14 07:54:19] VERBOSE[10652] res_pjsip/pjsip_options.c: Contact 104/sip:[email protected]:61134 has been deleted
[2019-05-14 07:54:19] VERBOSE[1969] res_pjsip/pjsip_options.c: Contact 108/sip:[email protected]:61128 has been deleted

Any Idea???

Thanks,

2

92.184.125.209 shows as Orange Mobile; see http://whois.domaintools.com/92.184.125.209 .

Is that correct (connected via LTE router or similar)? If so, you are likely behind double or triple NAT, which could cause problems when the public IP address changes. Post details of network setup.

Also, does only this one location have trouble? If not, when trouble occurs, is only one location affected? Do you observe a public IP address change (after the reboot, peer address is different)? May this be related to your firewall setup (new address may be blocked)? Phone make/model? If not using SIP UDP, provide details.

3

You are right Stewart. Only this location is connected through a LTE router and only this location have trouble. Phones are Yealink T46 / T42.

If I put a sip registration expire to 60 seconds on phones, could it resolves this kind of trouble ?

4

It might, and it’s easy enough to try. Also, set Max Contacts for these extensions to e.g. 5. Otherwise, the ‘new’ registration (from a changed IP address) will be rejected if the old one has not yet expired.

However, this is a complex network setup and there are often situations where frequent retries cause trouble, by preventing ‘poisoned’ NAT associations from timing out. Also, any hardware or software firewalls at the server end may be contributing to the problem.

In tough cases, there is no substitute for examining the network behavior during the outage to understand what is going wrong. This may take a while; possibly it can be done on a weekend or in early morning hours when the business is closed, if you are lucky enough to have the problem occur at such times.

1 Like
5

Thank you Stewart, I try this and give you an answer.
Edit : it was the LTE Network and routeur wich causes those problems.
10 SIP had local SIP port 5060. The routeur didn’t handle correctly the NAT rules. At each REGISTER a phone send to the PBX, it opens a new NAT port. It was a DLINK AC1200 LTE ROUTER.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.