Incoming Calls not working


(Ali Abbas) #1

Hello everyone, I have configured a freepbx on my local pc, i’m receiving some issue with inbound calls. I can make outgoing calls but incoming call are not working. Please check log below. Thanks

CSeq: 102 OPTIONS
Call-ID: 623235955284d74d5c4986a67b069f43@192.168.108.176:5060
Contact: <sip:203@192.168.108.18:5060>
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER
Supported: replaces,100rel
User-Agent: PolycomVVX-VVX_300-UA/5.9.0.9373
Accept-Language: en
Accept: application/sdp,text/plain,message/sipfrag,application/dialog-info+xml
Accept-Encoding: identity
Supported: 100rel,replaces,norefersub,sdp-anat
Content-Length: 0

<------------->
[2020-09-09 15:39:36] VERBOSE[11852] chan_sip.c: --- (15 headers 0 lines) ---
[2020-09-09 15:39:36] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '623235955284d74d5c4986a67b069f43@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c: Reliably Transmitting (NAT) to 64.136.174.30:5060:
OPTIONS sip:64.136.174.30 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK268ee13f;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as79c7a785
To: <sip:64.136.174.30>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 0302102d2afdbfb401d93b79735e5cab@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:39:39 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c: Reliably Transmitting (NAT) to 64.136.173.31:5060:
OPTIONS sip:64.136.173.31 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK0586950d;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as41281f1f
To: <sip:64.136.173.31>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 410c5eed47ea923863325e253b56599e@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:39:39 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:64.136.174.30:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK268ee13f;rport=60387
To: <sip:64.136.174.30>
From: "Unknown" <sip:Unknown@192.168.108.176:5060>;tag=as79c7a785
Call-ID: 0302102d2afdbfb401d93b79735e5cab@192.168.108.176:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c: --- (7 headers 0 lines) ---
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '0302102d2afdbfb401d93b79735e5cab@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:64.136.173.31:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK0586950d;rport=60387
To: <sip:64.136.173.31>
From: "Unknown" <sip:Unknown@192.168.108.176:5060>;tag=as41281f1f
Call-ID: 410c5eed47ea923863325e253b56599e@192.168.108.176:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c: --- (7 headers 0 lines) ---
[2020-09-09 15:39:39] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '410c5eed47ea923863325e253b56599e@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:39:46] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->

<------------->
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->
REGISTER sip:192.168.108.176:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.51:62277;branch=z9hG4bK-d8754z-0909000d8d075001-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>
To: "Admin"<sip:301@192.168.108.176:5060>
From: "Admin"<sip:301@192.168.108.176:5060>;tag=077ef416
Call-ID: OTg1YTg2NDQxMDg4MDMyODc2N2JlY2Y3OWMzNTI1MjM.
CSeq: 49 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Supported: replaces
User-Agent: 3CXPhone 6.0.26523.0
Authorization: Digest username="301",realm="asterisk",nonce="7a1243a3",uri="sip:192.168.108.176:5060",response="4a374277a36dfe70b99d1c06ea5cbf45",algorithm=MD5
Content-Length: 0

<------------->
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: --- (14 headers 0 lines) ---
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Sending to 192.168.108.51:62277 (NAT)
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Sending to 192.168.108.51:62277 (NAT)
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.108.51:62277 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.108.51:62277;branch=z9hG4bK-d8754z-0909000d8d075001-1---d8754z-;received=192.168.108.51;rport=62277
From: "Admin"<sip:301@192.168.108.176:5060>;tag=077ef416
To: "Admin"<sip:301@192.168.108.176:5060>;tag=as4939d827
Call-ID: OTg1YTg2NDQxMDg4MDMyODc2N2JlY2Y3OWMzNTI1MjM.
CSeq: 49 REGISTER
Server: FPBX-14.0.13.34(13.32.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="7a78072c"
Content-Length: 0

<------------>
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Scheduling destruction of SIP dialog 'OTg1YTg2NDQxMDg4MDMyODc2N2JlY2Y3OWMzNTI1MjM.' in 32000 ms (Method: REGISTER)
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->
REGISTER sip:192.168.108.176:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.51:62277;branch=z9hG4bK-d8754z-8b530f4b1b2c0000-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>
To: "Admin"<sip:301@192.168.108.176:5060>
From: "Admin"<sip:301@192.168.108.176:5060>;tag=077ef416
Call-ID: OTg1YTg2NDQxMDg4MDMyODc2N2JlY2Y3OWMzNTI1MjM.
CSeq: 50 REGISTER
Expires: 120
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Supported: replaces
User-Agent: 3CXPhone 6.0.26523.0
Authorization: Digest username="301",realm="asterisk",nonce="7a78072c",uri="sip:192.168.108.176:5060",response="5ae6a898cd5c645b01ee3f28d88314b3",algorithm=MD5
Content-Length: 0

<------------->
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: --- (14 headers 0 lines) ---
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Sending to 192.168.108.51:62277 (no NAT)
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Reliably Transmitting (no NAT) to 192.168.108.51:62277:
OPTIONS sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK589aafe5
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as5741b6dc
To: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 1def8e957f825378099d8bff2fda15f9@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:39:47 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.108.51:62277 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.51:62277;branch=z9hG4bK-d8754z-8b530f4b1b2c0000-1---d8754z-;received=192.168.108.51;rport=62277
From: "Admin"<sip:301@192.168.108.176:5060>;tag=077ef416
To: "Admin"<sip:301@192.168.108.176:5060>;tag=as4939d827
Call-ID: OTg1YTg2NDQxMDg4MDMyODc2N2JlY2Y3OWMzNTI1MjM.
CSeq: 50 REGISTER
Server: FPBX-14.0.13.34(13.32.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 120
Contact: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>;expires=120
Date: Wed, 09 Sep 2020 10:39:47 GMT
Content-Length: 0

<------------>
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Scheduling destruction of SIP dialog 'OTg1YTg2NDQxMDg4MDMyODc2N2JlY2Y3OWMzNTI1MjM.' in 32000 ms (Method: REGISTER)
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK589aafe5
Contact: <sip:192.168.108.51:62277>
To: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>;tag=e84fd330
From: "Unknown"<sip:Unknown@192.168.108.176>;tag=as5741b6dc
Call-ID: 1def8e957f825378099d8bff2fda15f9@192.168.108.176:5060
CSeq: 102 OPTIONS
Accept: application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Supported: replaces
Allow-Events: presence, message-summary, tunnel-info
Content-Length: 0

<------------->
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: --- (13 headers 0 lines) ---
[2020-09-09 15:39:47] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '1def8e957f825378099d8bff2fda15f9@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:39:58] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:58562 --->

<------------->
[2020-09-09 15:40:00] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '_K5eVJx6y0AUmqX5mwlKIw..' Method: REGISTER
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c: Reliably Transmitting (no NAT) to 192.168.108.13:5060:
OPTIONS sip:204@192.168.108.13:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK30f52a72
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as39eb3475
To: <sip:204@192.168.108.13:5060>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 67dd3b184c520bf51d7e6ab26a7a0089@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:40:36 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.13:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK30f52a72
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as39eb3475
To: "204" <sip:204@192.168.108.13:5060>;tag=BB41E5BC-41C992AD
CSeq: 102 OPTIONS
Call-ID: 67dd3b184c520bf51d7e6ab26a7a0089@192.168.108.176:5060
Contact: <sip:204@192.168.108.13:5060>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Supported: replaces,100rel,100rel,timer,replaces,norefersub,sdp-anat
User-Agent: PolycomVVX-VVX_310-UA/5.5.1.12442
Accept-Language: en
Accept: application/sdp,text/plain,message/sipfrag,application/dialog-info+xml
Accept-Encoding: identity
Content-Length: 0

<------------->
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c: --- (14 headers 0 lines) ---
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '67dd3b184c520bf51d7e6ab26a7a0089@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c: Reliably Transmitting (no NAT) to 192.168.108.18:5060:
OPTIONS sip:203@192.168.108.18:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK4ad4fd50
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as2c35bb96
To: <sip:203@192.168.108.18:5060>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 77c6c02d46b2985b1c1d0f4e11073738@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:40:36 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.18:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK4ad4fd50
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as2c35bb96
To: "203" <sip:203@192.168.108.18:5060>;tag=1F90BE75-735096D2
CSeq: 102 OPTIONS
Call-ID: 77c6c02d46b2985b1c1d0f4e11073738@192.168.108.176:5060
Contact: <sip:203@192.168.108.18:5060>
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER
Supported: replaces,100rel
User-Agent: PolycomVVX-VVX_300-UA/5.9.0.9373
Accept-Language: en
Accept: application/sdp,text/plain,message/sipfrag,application/dialog-info+xml
Accept-Encoding: identity
Supported: 100rel,replaces,norefersub,sdp-anat
Content-Length: 0

<------------->
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c: --- (15 headers 0 lines) ---
[2020-09-09 15:40:36] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '77c6c02d46b2985b1c1d0f4e11073738@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:40:39] VERBOSE[11852] chan_sip.c: Reliably Transmitting (NAT) to 64.136.174.30:5060:
OPTIONS sip:64.136.174.30 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK6b53cee1;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as602dc291
To: <sip:64.136.174.30>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 34163c4a22c64e5d17da5d8e0cc3df26@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:40:39 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:40:39] VERBOSE[11852] chan_sip.c: Reliably Transmitting (NAT) to 64.136.173.31:5060:
OPTIONS sip:64.136.173.31 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK57cacc99;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as26cb1fa1
To: <sip:64.136.173.31>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 7ea9a8192e7fb3de0c7f96d202b1d493@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:40:39 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:40:39] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:64.136.174.30:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK6b53cee1;rport=60387
To: <sip:64.136.174.30>
From: "Unknown" <sip:Unknown@192.168.108.176:5060>;tag=as602dc291
Call-ID: 34163c4a22c64e5d17da5d8e0cc3df26@192.168.108.176:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
[2020-09-09 15:40:39] VERBOSE[11852] chan_sip.c: --- (7 headers 0 lines) ---
[2020-09-09 15:40:39] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '34163c4a22c64e5d17da5d8e0cc3df26@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:40:40] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:64.136.173.31:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK57cacc99;rport=60387
To: <sip:64.136.173.31>
From: "Unknown" <sip:Unknown@192.168.108.176:5060>;tag=as26cb1fa1
Call-ID: 7ea9a8192e7fb3de0c7f96d202b1d493@192.168.108.176:5060
CSeq: 102 OPTIONS
Content-Length: 0

<------------->
[2020-09-09 15:40:40] VERBOSE[11852] chan_sip.c: --- (7 headers 0 lines) ---
[2020-09-09 15:40:40] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '7ea9a8192e7fb3de0c7f96d202b1d493@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:40:46] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->

<------------->
[2020-09-09 15:40:47] VERBOSE[11852] chan_sip.c: Reliably Transmitting (no NAT) to 192.168.108.51:62277:
OPTIONS sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27 SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK0e7ecce6
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as642ed647
To: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 7516942a0a519cbc101bbae007723bbe@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:40:47 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:40:47] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK0e7ecce6
Contact: <sip:192.168.108.51:62277>
To: <sip:301@192.168.108.51:62277;rinstance=5a83dd3df5b83b27>;tag=0d3a7e34
From: "Unknown"<sip:Unknown@192.168.108.176>;tag=as642ed647
Call-ID: 7516942a0a519cbc101bbae007723bbe@192.168.108.176:5060
CSeq: 102 OPTIONS
Accept: application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
Supported: replaces
Allow-Events: presence, message-summary, tunnel-info
Content-Length: 0

<------------->
[2020-09-09 15:40:47] VERBOSE[11852] chan_sip.c: --- (13 headers 0 lines) ---
[2020-09-09 15:40:47] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '7516942a0a519cbc101bbae007723bbe@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:40:52] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:58562 --->

<------------->
[2020-09-09 15:40:54] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '_K5eVJx6y0AUmqX5mwlKIw..' Method: REGISTER
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:58562 --->
REGISTER sip:192.168.108.176:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.108.51:58562;branch=z9hG4bK-524287-1---9d402a8f08745e65;rport
Max-Forwards: 70
Contact: <sip:302@192.168.108.51:58562;rinstance=26d51ac5661f78b5;transport=UDP>
To: <sip:302@192.168.108.176:5060;transport=UDP>
From: <sip:302@192.168.108.176:5060;transport=UDP>;tag=9a393215
Call-ID: _K5eVJx6y0AUmqX5mwlKIw..
CSeq: 688 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Z 5.4.5 rv2.10.9.0
Authorization: Digest username="302",realm="asterisk",nonce="6fd51f5b",uri="sip:192.168.108.176:5060;transport=UDP",response="f42111c48833a32249f6e4e1d2e10eed",algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0

<------------->
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: --- (14 headers 0 lines) ---
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Sending to 192.168.108.51:58562 (NAT)
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Sending to 192.168.108.51:58562 (NAT)
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.108.51:58562 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.108.51:58562;branch=z9hG4bK-524287-1---9d402a8f08745e65;received=192.168.108.51;rport=58562
From: <sip:302@192.168.108.176:5060;transport=UDP>;tag=9a393215
To: <sip:302@192.168.108.176:5060;transport=UDP>;tag=as66e6543e
Call-ID: _K5eVJx6y0AUmqX5mwlKIw..
CSeq: 688 REGISTER
Server: FPBX-14.0.13.34(13.32.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="5de6f470"
Content-Length: 0

<------------>
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Scheduling destruction of SIP dialog '_K5eVJx6y0AUmqX5mwlKIw..' in 32000 ms (Method: REGISTER)
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:58562 --->
REGISTER sip:192.168.108.176:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.108.51:58562;branch=z9hG4bK-524287-1---574d84c330cf1329;rport
Max-Forwards: 70
Contact: <sip:302@192.168.108.51:58562;rinstance=26d51ac5661f78b5;transport=UDP>
To: <sip:302@192.168.108.176:5060;transport=UDP>
From: <sip:302@192.168.108.176:5060;transport=UDP>;tag=9a393215
Call-ID: _K5eVJx6y0AUmqX5mwlKIw..
CSeq: 689 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Z 5.4.5 rv2.10.9.0
Authorization: Digest username="302",realm="asterisk",nonce="5de6f470",uri="sip:192.168.108.176:5060;transport=UDP",response="5a467e4ed23b0f136decbbed7f0bedd4",algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0

<------------->
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: --- (14 headers 0 lines) ---
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Sending to 192.168.108.51:58562 (no NAT)
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Reliably Transmitting (no NAT) to 192.168.108.51:58562:
OPTIONS sip:302@192.168.108.51:58562;rinstance=26d51ac5661f78b5;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK3fb5c085
Max-Forwards: 70
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as676ed889
To: <sip:302@192.168.108.51:58562;rinstance=26d51ac5661f78b5;transport=UDP>
Contact: <sip:Unknown@192.168.108.176:5060>
Call-ID: 7d97f7360597d9694fa5ec2671879e0a@192.168.108.176:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.34(13.32.0)
Date: Wed, 09 Sep 2020 10:41:16 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

---
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.108.51:58562 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.51:58562;branch=z9hG4bK-524287-1---574d84c330cf1329;received=192.168.108.51;rport=58562
From: <sip:302@192.168.108.176:5060;transport=UDP>;tag=9a393215
To: <sip:302@192.168.108.176:5060;transport=UDP>;tag=as66e6543e
Call-ID: _K5eVJx6y0AUmqX5mwlKIw..
CSeq: 689 REGISTER
Server: FPBX-14.0.13.34(13.32.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 60
Contact: <sip:302@192.168.108.51:58562;rinstance=26d51ac5661f78b5;transport=UDP>;expires=60
Date: Wed, 09 Sep 2020 10:41:16 GMT
Content-Length: 0

<------------>
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Scheduling destruction of SIP dialog '_K5eVJx6y0AUmqX5mwlKIw..' in 32000 ms (Method: REGISTER)
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:58562 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.108.176:5060;branch=z9hG4bK3fb5c085
Contact: <sip:192.168.108.51:58562>
To: <sip:302@192.168.108.51:58562;rinstance=26d51ac5661f78b5;transport=UDP>;tag=6c0e5c2b
From: "Unknown" <sip:Unknown@192.168.108.176>;tag=as676ed889
Call-ID: 7d97f7360597d9694fa5ec2671879e0a@192.168.108.176:5060
CSeq: 102 OPTIONS
Accept: application/sdp, application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri
User-Agent: Z 5.4.5 rv2.10.9.0
Allow-Events: presence, kpml, talk
Content-Length: 0

<------------->
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: --- (14 headers 0 lines) ---
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c: Really destroying SIP dialog '7d97f7360597d9694fa5ec2671879e0a@192.168.108.176:5060' Method: OPTIONS
[2020-09-09 15:41:16] VERBOSE[11852] chan_sip.c:
<--- SIP read from UDP:192.168.108.51:62277 --->

<------------->

#2

There is no INVITE in the log posted. What kind of trunk do you have (pjsip, chan_sip, other)?

Assuming a SIP trunk, if it uses registration, it’s likely that the NAT association (in your router/firewall) timed out. Is qualify set for the trunk?

If your trunk uses IP authentication, confirm that the provider portal has been set to send to your correct IP address and port, and that your router/firewall is forwarding that port to the PBX.

Note that by default, pjsip listens on port 5060 and chan_sip on port 5160.


(Ali Abbas) #3

Hey stewart, I’m using chan_sip trunk and yes trunk has ip based authentication. Please have a look at the peer details of inbound.

disallow=all
Host=64.136.173.31
Type=friend
Context=from-trunk
Insecure=port,invite
dtmfmode=rfc2833
allow=ulaw&alaw
qualify=yes
canreinvite=no

Can you please guide me how to debug so that i can identify the exact issue, as i’m newbie on this. Thanks


(TheWebMachine Networks (Sangoma Software Development Partner)) #4

Who is the Trunking provider (the IP looks like VoIP Innovations, but I don’t want to assume)? Is it possible they are sending inbound calls from more than one IP beyond the Host listed in your peer details?

If its VoIP Innovations or any other provider that uses multiple IPs for sending inbound calls to your PBX, you’ll need to approach your setup differently to accommodate this. I’m going to cover two methods here…but I’m sure you’ll want to use #2 in the long run, as it’s maintenance-free:

Method #1: Obtain a list of all Trunking IPs from the provider and add an Incoming trunk for each IP in addition to your default Trunk used for outbound. This is harder to maintain if your Trunk provider has many IPs to maintain on your PBX that might change from time to time, so we prefer method #2.

Method #2: We open up inbound Anonymous settings to allow the multiple IPs and then use Inbound Routes to filter illegitimate calls instead of the Trunks config. You’ll leave your existing Trunk setup alone.

  • First and most importantly, to secure the Inbound Routes, create a new Inbound Route (Name it “Restricted” or something similar) and leave all fields blank (DID and CID), setting only the Destination to Terminate Call > Hangup. Submit.
    • This will block all calls that don’t explicitly match your other Inbound Routes by hanging up the call without playing a message at all.
  • Now, go to Settings > Asterisk SIP Settings and set Allow Anonymous Inbound SIP Calls AND Allow SIP Guests to YES. Submit and Apply Config.

What Method 2 accomplishes is allowing the Trunk calls through regardless of originating IP while still blocking calls that don’t match valid DIDs on your system. One other benefit to Method #2 versus the default security settings is the additional mitigation of DDoS attacks. The default Allow Anonymous No plays a “no service” message to every illegitimate incoming call. If an attacker sent 5000 calls at once, they could crash your system just playing “no service” messages 5000 at one time. With Method #2, the unauthorized calls are simply hung up without playing any message, requiring substantially more effort to overload your server in a DDoS style attack, as virtually no resources are used in simply hanging up those calls.


(Ali Abbas) #5

Thanks for guiding me, yes i’m using VoIP innovation service .I just applied the setting you told for method 2. But the issue is still same, incoming calls are not working. Please have a look at the screenshot. Here is the flow sequence of call i captured.


(TheWebMachine Networks (Sangoma Software Development Partner)) #6

That looks like an Unauthorized response being sent to an Endpoint failing its authentication. IP Authentication wouldn’t get a 401, as no REGISTER with user authentication takes place with IP authentication. With IP authentication Trunking, Asterisk plays the no-service message or, if you employ Method #2 above, just hangs up the on the INVITE. It looks like you might have a number of extensions/endpoints on 192.168.108.x trying to register and failing to authenticate…or a lot of external forces trying to brute force register to your system…hard to tell since your PBX is behind a NAT firewall and everything is coming in via that internal .176 address. This is cluttering up your capture.

As @Stewart1 said, we see no INVITE transactions in what you are posting, and INVITE is what we would see on an IP Auth Trunk call starting off. This would tell us more about what is happening here.