Asterisk 13.23.1 PJSIP not responding to REGISTER


#1

The two servers, one production and one pre-production, that I have running Asterisk 13.23.1, both are FreePBX distros. Preproduction is running FreePBX 13.0.195.17, and Production server is on FreePBX 13.0.195.19. Once I perform fwconsole stop and fwconsole restart, everything responds again for a couple days, but it’s ongoing.

Chan_SIP extensions appear to register just fine. PJSIP listening on 5012 (I have a few other older asterisk servers listening on 5012 with no issues), Chan_SIP on 5060.


Connected to Asterisk 13.23.1 currently running on reachos (pid = 14317)

<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---20f3dc2a560ba11a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 2 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0

[2019-02-25 14:17:23] WARNING[14436]: chan_sip.c:4068 retrans_pkt: Retransmission timeout reached on transmission 355958421-562915274-1482916698 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---67864e52b1ec7e56;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 3 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---67864e52b1ec7e56;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 3 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0

<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---67864e52b1ec7e56;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 3 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---67864e52b1ec7e56;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 3 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0

[2019-02-25 14:17:56] WARNING[14436]: chan_sip.c:4127 retrans_pkt: Timeout on 945895384-1803212978-175066909 on non-critical invite transaction.
<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---67864e52b1ec7e56;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 3 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:32187 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---67864e52b1ec7e56;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 3 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0

<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


[2019-02-25 14:19:07] WARNING[14436]: chan_sip.c:4127 retrans_pkt: Timeout on 2094243888-420594577-1057614692 on non-critical invite transaction.
<--- Received SIP request (572 bytes) from UDP:50.x.x.x:32955 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.68:64956;branch=z9hG4bK-524287-1---ea01fd4c42be4d08;rport
Max-Forwards: 70
Contact: <sip:105@192.168.2.68:64956;rinstance=5a88f7d556450d0a>
To: "105"<sip:105@pbx.domain.com:5012>
From: "105"<sip:105@pbx.domain.com:5012>;tag=93254a06
Call-ID: 95788ZTg3ZGU1MGJjMTBmYmU4MGE1YjU5ZTYyMzI3OGNmMjU
CSeq: 23 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (572 bytes) from UDP:50.x.x.x:32955 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.68:64956;branch=z9hG4bK-524287-1---ea01fd4c42be4d08;rport
Max-Forwards: 70
Contact: <sip:105@192.168.2.68:64956;rinstance=5a88f7d556450d0a>
To: "105"<sip:105@pbx.domain.com:5012>
From: "105"<sip:105@pbx.domain.com:5012>;tag=93254a06
Call-ID: 95788ZTg3ZGU1MGJjMTBmYmU4MGE1YjU5ZTYyMzI3OGNmMjU
CSeq: 23 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23879 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ca85c41b0debc40a;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 4 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (572 bytes) from UDP:50.x.x.x:32955 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.68:64956;branch=z9hG4bK-524287-1---ea01fd4c42be4d08;rport
Max-Forwards: 70
Contact: <sip:105@192.168.2.68:64956;rinstance=5a88f7d556450d0a>
To: "105"<sip:105@pbx.domain.com:5012>
From: "105"<sip:105@pbx.domain.com:5012>;tag=93254a06
Call-ID: 95788ZTg3ZGU1MGJjMTBmYmU4MGE1YjU5ZTYyMzI3OGNmMjU
CSeq: 23 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (572 bytes) from UDP:50.x.x.x:32955 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.68:64956;branch=z9hG4bK-524287-1---ea01fd4c42be4d08;rport
Max-Forwards: 70
Contact: <sip:105@192.168.2.68:64956;rinstance=5a88f7d556450d0a>
To: "105"<sip:105@pbx.domain.com:5012>
From: "105"<sip:105@pbx.domain.com:5012>;tag=93254a06
Call-ID: 95788ZTg3ZGU1MGJjMTBmYmU4MGE1YjU5ZTYyMzI3OGNmMjU
CSeq: 23 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (572 bytes) from UDP:50.x.x.x:32955 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.68:64956;branch=z9hG4bK-524287-1---ea01fd4c42be4d08;rport
Max-Forwards: 70
Contact: <sip:105@192.168.2.68:64956;rinstance=5a88f7d556450d0a>
To: "105"<sip:105@pbx.domain.com:5012>
From: "105"<sip:105@pbx.domain.com:5012>;tag=93254a06
Call-ID: 95788ZTg3ZGU1MGJjMTBmYmU4MGE1YjU5ZTYyMzI3OGNmMjU
CSeq: 23 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0

<--- Received SIP request (569 bytes) from UDP:50.x.x.x:55823 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---ec66500bc69eca1e;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 5 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


[2019-02-25 14:21:45] WARNING[14436]: chan_sip.c:4127 retrans_pkt: Timeout on 1040071899-747190983-835245942 on non-critical invite transaction.
<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0

<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:45276 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---d1a842357ed0e47f;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 6 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


[2019-02-25 14:25:39] NOTICE[14436][C-000001a5]: chan_sip.c:26363 handle_request_invite: Failed to authenticate device <sip:902test@66.x.x.x>;tag=1896631551
[2019-02-25 14:26:11] WARNING[14436]: chan_sip.c:4068 retrans_pkt: Retransmission timeout reached on transmission 1747592391-892573254-1494611247 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32000ms with no response
[2019-02-25 14:27:30] WARNING[14436]: chan_sip.c:4127 retrans_pkt: Timeout on 626881974-1608086183-1802696570 on non-critical invite transaction.
[2019-02-25 14:27:54] WARNING[14436]: chan_sip.c:4127 retrans_pkt: Timeout on 18307468-1404386089-948246300 on non-critical invite transaction.
[2019-02-25 14:28:44] NOTICE[14436][C-000001a8]: chan_sip.c:26363 handle_request_invite: Failed to authenticate device 1001<sip:1001@66.x.x.x>;tag=e3eb3747
<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


<--- Received SIP request (569 bytes) from UDP:50.x.x.x:23598 --->
REGISTER sip:pbx.domain.com:5012 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.109:56739;branch=z9hG4bK-524287-1---99ac2a38d3d56470;rport
Max-Forwards: 70
Contact: <sip:109@192.168.2.109:56739;rinstance=f9bdef6c5ab23d31>
To: "109"<sip:109@pbx.domain.com:5012>
From: "109"<sip:109@pbx.domain.com:5012>;tag=1751b83d
Call-ID: 95788ZTU1ZjViZmI1OGUyMzY2YzdmYzdmM2U3ODhiZmM2MTc
CSeq: 7 REGISTER
Expires: 3600
Allow: OPTIONS, SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO
User-Agent: Bria Teams release 5.4.1 stamp 95788
Content-Length: 0


[2019-02-25 14:31:19] WARNING[14436]: chan_sip.c:4127 retrans_pkt: Timeout on 764955014-2075939591-1628180171 on non-critical invite transaction.
[2019-02-25 14:35:29] NOTICE[14436][C-000001aa]: chan_sip.c:26363 handle_request_invite: Failed to authenticate device <sip:3000zxc@66.x.x.x>;tag=478595384
[2019-02-25 14:36:01] WARNING[14436]: chan_sip.c:4068 retrans_pkt: Retransmission timeout reached on transmission 112162139-1818502002-828079957 for seqno 2 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 31999ms with no response
reachos*CLI>

The only other thing unique about these two servers is that they both have bria teams endpoints and I have android and apple push services allowed through iptables (and other than that, the client sites my office IP, and my pstn turnking provider, nothing else is allowed on 5060), eg:

#Allow Bria Teams push servers
#push.softphone.com
-A INPUT -p tcp -m tcp -s push.softphone.com --dport 5060 -j ACCEPT
-A INPUT -p udp -m udp -s push.softphone.com --dport 5060 -j ACCEPT
-A INPUT -p tcp -m tcp -s push.softphone.com --dport 5012 -j ACCEPT
-A INPUT -p udp -m udp -s push.softphone.com --dport 5012 -j ACCEPT

#2

You’re not replying to the REGISTER properly. You’re never sending a 401 Unauthorized challenge nor are you sending a 200 OK to the register if you’re not authing with a user/password but just IP.

Basically, since Asterisk isn’t replying properly the Bria servers keep re-transmitting and re-attempting to REGISTER. Show your config for this endpoint.


#3

Hey @BlazeStudios. The server starts responding as soon as I fwconsole restart. I started monitoring the server in top and noted when this started happening node running command /www/html… (gets cut off, but I didn’t think to run ps aux|grep node at the time); I uninstalled a bunch of modules dependent upon nodejs and reinstalled nodejs. So far, the main issue has not reoccurred.

Further issues masked by the issue at large exists with individual endpoints, but its looking to me like NAT issue at this point.


#4

Hi @bittrekker
What will happen if you execute pjsip reload from Asterisk console?
We need to locate whether the issue is related to PJSIP channel driver or not.

Broa should not be the case - it is a very stable software having good interoperability with Asterisk in a number of installations


#5

Hi @Pentium-5, Thanks for the tip; since the utilization issues resolved it hasn’t come up again (node on one server, disabled modules that used nodejs and uninstalled and reinstalled nodejs, and on the other one, java memory usage at 100% via iSymphonyServerV3, resolution similar to the node server issue: https://community.freepbx.org/t/disable-java-to-prevent-high-memory-usage/25601).

It’s very odd that I could still register Chan_SIP. If this does come up again, I’ll try pjsip reload.


#6

@Pentium-5

Spoke too soon, pjsip stopped responding to register again.

I tried pjsip reload from the asterisk console, but it said No such command ‘pjsip reload’.

Went back to top, since that seemed to be a good lead last time. Now fail2ban is hogging cpu.

26420 root 20 0 1222m 9420 2364 S 110.0% 0.4 5:08.05 fail2ban-server

This is insane. The memory issue causing this behavior makes sense, but I’m quite confused by the cpu time causing this issue.


#7

Turn off fail2ban, does the issue stop?


#8

@BlazeStudios Yes, stopping the fail2ban service stops the CPU usage.
For now I’ve also set it to not start on reboot
chkconfig fail2ban off

I’ve tried turning it back on a couple times, it immediately shoots up to 110-120% cpu, I’ve never seen fail2ban server do this.

Server hasn’t stopped responding since I stopped the service.

The other server is continuing to have issues. Stops responding to REGISTER. Monitoring top, intermittently mysqld and cron max out cpu, haven’t gotten to the bottom of them yet.

cron log
tail -f /var/log/cron

Mar  2 11:51:11 bsaw crond[1034]: (asterisk.old) ORPHAN (no passwd entry)
Mar  2 11:51:11 bsaw crond[1034]: (asterisk) RELOAD (/var/spool/cron/asterisk)
Mar  2 11:51:11 bsaw CROND[5099]: (asterisk) CMD ([ -x /var/lib/asterisk/bin/schedtc.php ] && /var/lib/asterisk/bin/schedtc.php)
Mar  2 11:51:11 bsaw CROND[5100]: (asterisk) CMD (/usr/sbin/fwconsole pms wu_alert > /dev/null 2>&1)
Mar  2 11:51:11 bsaw CROND[5101]: (asterisk) CMD (/var/lib/asterisk/bin/pagepro-scheduler.php 2>&1 >/dev/null)
Mar  2 11:51:11 bsaw CROND[5102]: (asterisk) CMD ([ -x /var/www/html/admin/modules/dashboard/scheduler.php ] && /var/www/html/admin/modules/dashboard/scheduler.php > /dev/null 2>&1)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5120]: (asterisk) LIST (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5122]: (asterisk) LIST (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5124]: (asterisk) LIST (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5125]: (asterisk) REPLACE (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5127]: (asterisk) LIST (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5129]: (asterisk) LIST (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5131]: (asterisk) LIST (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5132]: (asterisk) REPLACE (asterisk)
Mar  2 11:51:11 bsaw /usr/bin/crontab[5134]: (asterisk) LIST (asterisk)

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  906 mysql     20   0 4231m  44m 3272 S 163.5  3.1  46741:06 mysqld
18775 asterisk  20   0 5103m  37m  10m S 12.3  2.7 116:42.35 asterisk
 3033 asterisk  20   0 1269m 284m 1616 S  2.0 20.1 455:16.61 letschat
20723 root      20   0  389m  56m 2068 S  1.7  4.0  15:45.25 fop2_server

#9

So not a resource issue. I tried connecting my bria to it, no reply. I connected Chan_SIP, and it connected just fine. restart services, everything back up again.

netstat shows asterisk is listening on the port that I assigned to pjsip.
Again, no reply to REGISTER:

pjsip set logger on
<--- Received SIP request (981 bytes) from UDP:35.x.x.x:5060 --->
REGISTER sip:host.domain:5012;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 10.22.40.159:5060;branch=z9hG4bK-524287-1---7d69e03545198e7e;rport
Max-Forwards: 70
Contact: <sip:423-45a962ea7dd0e0556b5bfd36a9cf2d3d@10.22.40.159:5060;transport=UDP>;+sip.instance="<urn:uuid:ea6089fe-1273-5343-911d-a1ef69bc5812>";reg-id=1;expires=1800
To: <sip:423@host.domain:5012;transport=UDP>
From: <sip:423@host.domain:5012>;tag=279c4b43
Call-ID: Vd_s0zf7vPr3zLFk7l1OyQ..@10.128.0.3
CSeq: 322 REGISTER
Expires: 1800
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, MESSAGE, OPTIONS, PRACK, REGISTER, UPDATE
User-Agent: CounterPath Bria Push Server 2.1.0 (18667)
Authorization: Digest username="423",realm="asterisk",nonce="1551682454/12250fa1dbb133547ce9e49c43b2237b",uri="sip:host.domain:5012;transport=UDP",response="cf8503fc4f36486c56e990312bae3331",cnonce="dff541009a5af0fc085415c9aba8cd4c",nc=00000002,qop=auth,algorithm=md5,opaque="763007f575d36d53"
Content-Length: 0

#10

I’m not aware of any filed issues for this, and certainly haven’t heard of such things. It may be environment specific. You can follow the wiki[1][2] to collect information and file an issue[3].

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
[2] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock
[3] https://issues.asterisk.org/jira


#11

Not sure what this log entry below means. I’ll submit my logs to an issues ticket

[2019-03-04 08:58:16] DEBUG[28686] res_pjsip/pjsip_distributor.c: Could not find matching transaction for Request msg REGISTER/cseq=7 (rdata0x7f03a505a1c8)
[2019-03-04 08:58:16] DEBUG[28686] res_pjsip/pjsip_distributor.c: Taskprocessor overload alert: Ignoring 'Request msg REGISTER/cseq=7 (rdata0x7f03a505a1c8)'.

#12

That means your system seems to be overloaded, so PJSIP is ignoring new requests so that it doesn’t add to the overload[1]. In a future version this will become configurable[2] so that if you really want, you can disable or limit what triggers it. You’d need to look at the logs and over all what is going on to see why it is overloaded. As well by overloaded I mean that Asterisk can’t service its queued tasks fast enough, so the queue is just growing and growing and growing.

The chan_sip module doesn’t have this functionality, and due to the way it is architected it does not contribute to overloads as much and can throttle things by way of not servicing network traffic as fast.

[1] https://blogs.asterisk.org/2016/07/13/asterisk-task-processor-queue-size-warnings/
[2] https://gerrit.asterisk.org/c/asterisk/+/11002


#13

Thank you so much for your assistance, I thought I had the utilization issue resolved. I’ll open another ticket with my hosting provider.