Extension unreachable / reachable


(Luca) #1

Hello,

I have one extension on my freepbx who become unreachable and instantly become reachable :

freepbx*CLI>
– Removed contact ‘sip:12@172.16.2.4:5060’ from AOR ‘12’ due to request
== Contact 12/sip:12@172.16.2.4:5060 has been deleted
== Endpoint 12 is now Unreachable
– Added contact ‘sip:12@172.16.2.4:5060’ to AOR ‘12’ with expiration of 3600 seconds
== Endpoint 12 is now Reachable
– Contact 12/sip:12@172.16.2.4:5060 is now Reachable. RTT: 40.226 msec
– Removed contact ‘sip:12@172.16.2.4:5060’ from AOR ‘12’ due to request
== Contact 12/sip:12@172.16.2.4:5060 has been deleted
== Endpoint 12 is now Unreachable
– Added contact ‘sip:12@172.16.2.4:5060’ to AOR ‘12’ with expiration of 3600 seconds
== Endpoint 12 is now Reachable
– Contact 12/sip:12@172.16.2.4:5060 is now Reachable. RTT: 46.113 msec
– Removed contact ‘sip:12@172.16.2.4:5060’ from AOR ‘12’ due to request
== Contact 12/sip:12@172.16.2.4:5060 has been deleted
== Endpoint 12 is now Unreachable
– Added contact ‘sip:12@172.16.2.4:5060’ to AOR ‘12’ with expiration of 3600 seconds
== Endpoint 12 is now Reachable
– Contact 12/sip:12@172.16.2.4:5060 is now Reachable. RTT: 55.394 msec

how can i fix this problem ?

Thanks for your reply :slight_smile:


(Dave Burgess) #2

This is a new one for me. Do you have any idea what is requesting the extension be deleted?


(Tom Ray) #3

The extension isn’t being deleted. The registered contact to the AOR is being deleted. This is classic NAT/networking issues.


(Joshua C. Colp) #4

It happens as a result of the device itself requesting the registration to be removed.

I’d suggest providing a SIP trace (pjsip set logger on) to show the actual traffic going on. As well - what is the device that is registering to this extension?


(Luca) #5

Hello,

There is the result of : pjsip set logger on

<— Transmitting SIP request (417 bytes) to UDP:172.16.2.4:5060 —>
OPTIONS sip:12@172.16.2.4:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.124.11:5060;rport;branch=z9hG4bKPj35ab618c-b431-4bd6-b610-365cd955985b
From: sip:12@192.168.124.11;tag=ed185835-4d62-4335-a638-5dc3c88031f4
To: sip:12@172.16.2.4
Contact: sip:12@192.168.124.11:5060
Call-ID: 2fdaf8d2-143d-435c-821c-b0d12aa4963f
CSeq: 65178 OPTIONS
Max-Forwards: 70
User-Agent: FPBX-14.0.8.4(13.26.0)
Content-Length: 0

<— Received SIP response (486 bytes) from UDP:172.16.2.4:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.124.11:5060;rport=5060;branch=z9hG4bKPj35ab618c-b431-4bd6-b610-365cd955985b
From: sip:12@192.168.124.11;tag=ed185835-4d62-4335-a638-5dc3c88031f4
To: sip:12@172.16.2.4;tag=1755428817
Call-ID: 2fdaf8d2-143d-435c-821c-b0d12aa4963f
CSeq: 65178 OPTIONS
Supported: replaces, path, timer
User-Agent: Grandstream GXP2170 1.0.9.69
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Length: 0

The device is a grandstream gxp2170

Thanks for your reply
Luca


(Joshua C. Colp) #6

That’s a single successful result for qualifying. It doesn’t show the REGISTERs - which will likely show the Grandstream asking for the registration to be removed.


(system) closed #7

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