Hi,
I am almost new on sip and am trying to do communication through webrtc with sip. I am developing this on nodejs platform using sip.js.
From web application, ext 202 is calling ext 201 (on zoiper) and all extensions are in sip.conf. Everytime I am getting incoming call and can answer the call. But after 6 seconds its gone automatically with no media. Here my web, webrtc (kurento) is on one local vm and the sip one is on another local vm and they are connected locally through LAN.
I paste the log here in below. Please help me
<-------------
— (11 headers 0 lines) —
[2019-11-07 06:46:35] NOTICE[5155]: chan_sip.c:24599 handle_response_peerpoke: Peer ‘202’ is now Reachable. (22ms / 2000ms)
Really destroying SIP dialog ‘3dc1520c47a36cd0308bf17534e12bd5_AT_192.168.102.237:5160’ Method: OPTIONS
Reliably Transmitting (no NAT) to 192.168.102.194:55836:
OPTIONS sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK0184809e
Max-Forwards: 70
From: “Unknown” <sip:Unknown_AT_192.168.102.237:5160 ;tag=as2971d29a
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
Contact: <sip:Unknown_AT_192.168.102.237:5160
Call-ID: 3724a9e44a4f3f3a5f47a52a6f06aff5_AT_192.168.102.237:5160
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.19.1)
Date: Thu, 07 Nov 2019 06:46:40 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK0184809e
Contact: <sip:192.168.102.194:55836
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=1861967b
From: “Unknown” <sip:Unknown_AT_192.168.102.237:5160;tag=as2971d29a
Call-ID: 3724a9e44a4f3f3a5f47a52a6f06aff5_AT_192.168.102.237:5160
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: Zoiper rv2.10.3.0
Allow-Events: presence, kpml, talk
Content-Length: 0
<-------------
— (14 headers 0 lines) —
Really destroying SIP dialog ‘3724a9e44a4f3f3a5f47a52a6f06aff5_AT_192.168.102.237:5160’ Method: OPTIONS
<— SIP read from UDP:192.168.102.194:55836 —
<-------------
<— SIP read from UDP:192.168.102.194:55836 —
REGISTER sip:192.168.102.237:5160;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.102.194:55836;branch=z9hG4bK-524287-1—a168c2fb5380199b;rport
Max-Forwards: 70
Contact: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
To: <sip:201_AT_192.168.102.237:5160;transport=UDP
From: <sip:201_AT_192.168.102.237:5160;transport=UDP;tag=d53e5c01
Call-ID: 5pp8gdnwqH1JI0uUBYrSvQ…
CSeq: 29 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Zoiper rv2.10.3.0
Authorization: Digest username=“201”,realm=“asterisk”,nonce=“79920a3c”,uri=“sip:192.168.102.237:5160;transport=UDP”,response=“bb14e31b6b9c2d369d22ef8dc5c455a7”,algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0
<-------------
— (14 headers 0 lines) —
Sending to 192.168.102.194:55836 (no NAT)
Sending to 192.168.102.194:55836 (no NAT)
<— Transmitting (no NAT) to 192.168.102.194:55836 —
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.102.194:55836;branch=z9hG4bK-524287-1—a168c2fb5380199b;received=192.168.102.194;rport=55836
From: <sip:201_AT_192.168.102.237:5160;transport=UDP;tag=d53e5c01
To: <sip:201_AT_192.168.102.237:5160;transport=UDP;tag=as7e668d5b
Call-ID: 5pp8gdnwqH1JI0uUBYrSvQ…
CSeq: 29 REGISTER
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“19ca1a1a”
Content-Length: 0
<------------
Scheduling destruction of SIP dialog ‘5pp8gdnwqH1JI0uUBYrSvQ…’ in 32000 ms (Method: REGISTER)
<— SIP read from UDP:192.168.102.194:55836 —
REGISTER sip:192.168.102.237:5160;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.102.194:55836;branch=z9hG4bK-524287-1—2de7e430134567a0;rport
Max-Forwards: 70
Contact: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
To: <sip:201_AT_192.168.102.237:5160;transport=UDP
From: <sip:201_AT_192.168.102.237:5160;transport=UDP;tag=d53e5c01
Call-ID: 5pp8gdnwqH1JI0uUBYrSvQ…
CSeq: 30 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Zoiper rv2.10.3.0
Authorization: Digest username=“201”,realm=“asterisk”,nonce=“19ca1a1a”,uri=“sip:192.168.102.237:5160;transport=UDP”,response=“4afa432ad123bb391969397533016f7f”,algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0
<-------------
— (14 headers 0 lines) —
Sending to 192.168.102.194:55836 (no NAT)
Reliably Transmitting (no NAT) to 192.168.102.194:55836:
OPTIONS sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK28bbb5f8
Max-Forwards: 70
From: “Unknown” <sip:Unknown_AT_192.168.102.237:5160;tag=as29e1d49b
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
Contact: <sip:Unknown_AT_192.168.102.237:5160
Call-ID: 3606e61b464733340917f3b14eaad4ee_AT_192.168.102.237:5160
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.13.4(13.19.1)
Date: Thu, 07 Nov 2019 06:46:41 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0
<— Transmitting (no NAT) to 192.168.102.194:55836 —
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.102.194:55836;branch=z9hG4bK-524287-1—2de7e430134567a0;received=192.168.102.194;rport=55836
From: <sip:201_AT_192.168.102.237:5160;transport=UDP;tag=d53e5c01
To: <sip:201_AT_192.168.102.237:5160;transport=UDP;tag=as7e668d5b
Call-ID: 5pp8gdnwqH1JI0uUBYrSvQ…
CSeq: 30 REGISTER
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 60
Contact: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;expires=60
Date: Thu, 07 Nov 2019 06:46:41 GMT
Content-Length: 0
<------------
Scheduling destruction of SIP dialog ‘6023e75903c9b74e1442f009150a3704_AT_192.168.102.237:5160’ in 31680 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.102.194:55836:
NOTIFY sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK1cc8e6a5
Max-Forwards: 70
From: “Unknown” <sip:Unknown_AT_192.168.102.237:5160;tag=as75ed69c7
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
Contact: <sip:Unknown_AT_192.168.102.237:5160
Call-ID: 6023e75903c9b74e1442f009150a3704_AT_192.168.102.237:5160
CSeq: 102 NOTIFY
User-Agent: FPBX-14.0.13.4(13.19.1)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 95
Messages-Waiting: no
Message-Account: sip:*97_AT_192.168.102.237:5160
Voice-Message: 0/0 (0/0)
Scheduling destruction of SIP dialog ‘5pp8gdnwqH1JI0uUBYrSvQ…’ in 32000 ms (Method: REGISTER)
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK28bbb5f8
Contact: <sip:192.168.102.194:55836
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=22315377
From: “Unknown” <sip:Unknown_AT_192.168.102.237:5160;tag=as29e1d49b
Call-ID: 3606e61b464733340917f3b14eaad4ee_AT_192.168.102.237:5160
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: Zoiper rv2.10.3.0
Allow-Events: presence, kpml, talk
Content-Length: 0
<-------------
— (14 headers 0 lines) —
Really destroying SIP dialog ‘3606e61b464733340917f3b14eaad4ee_AT_192.168.102.237:5160’ Method: OPTIONS
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK1cc8e6a5
Contact: <sip:192.168.102.194:55836
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=42fe706b
From: “Unknown” <sip:Unknown_AT_192.168.102.237:5160;tag=as75ed69c7
Call-ID: 6023e75903c9b74e1442f009150a3704_AT_192.168.102.237:5160
CSeq: 102 NOTIFY
User-Agent: Zoiper rv2.10.3.0
Content-Length: 0
<-------------
— (9 headers 0 lines) —
Really destroying SIP dialog ‘6023e75903c9b74e1442f009150a3704_AT_192.168.102.237:5160’ Method: NOTIFY
<— SIP read from WS:192.168.102.240:45542 —
INVITE sip:201_AT_192.168.102.237 SIP/2.0
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK1149428
Max-Forwards: 70
To: <sip:201_AT_192.168.102.237
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1090 INVITE
Contact: <sip:6kudpouh_AT_192.0.2.238;transport=ws;ob
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
Supported: outbound
User-Agent: SIP.js/0.7.8
Content-Length: 0
<-------------
— (12 headers 0 lines) —
Using INVITE request as basis request - hsrm6uqmt76jlk04if8l
Found peer ‘202’ for ‘202’ from 192.168.102.240:45542
<— Reliably Transmitting (no NAT) to 192.168.102.240:5060 —
SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK1149428;received=192.168.102.240
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
To: <sip:201_AT_192.168.102.237;tag=as2ed5a804
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1090 INVITE
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“5242cc05”
Content-Length: 0
<------------
Scheduling destruction of SIP dialog ‘hsrm6uqmt76jlk04if8l’ in 6400 ms (Method: INVITE)
<— SIP read from WS:192.168.102.240:45542 —
ACK sip:201_AT_192.168.102.237 SIP/2.0
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK1149428
To: <sip:201_AT_192.168.102.237;tag=as2ed5a804
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
Call-ID: hsrm6uqmt76jlk04if8l
Content-Length: 0
CSeq: 1090 ACK
<-------------
— (7 headers 0 lines) —
<— SIP read from WS:192.168.102.240:45542 —
INVITE sip:201_AT_192.168.102.237 SIP/2.0
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK2904666
Max-Forwards: 70
To: <sip:201_AT_192.168.102.237
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1091 INVITE
Authorization: Digest algorithm=MD5, username=“202”, realm=“asterisk”, nonce=“5242cc05”, uri=“sip:201_AT_192.168.102.237”, response=“36293be12250fbf0109c6ef6d9108370”
Contact: <sip:6kudpouh_AT_192.0.2.238;transport=ws;ob
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
Supported: outbound
User-Agent: SIP.js/0.7.8
Content-Length: 0
<-------------
— (13 headers 0 lines) —
Using INVITE request as basis request - hsrm6uqmt76jlk04if8l
Found peer ‘202’ for ‘202’ from 192.168.102.240:45542
Looking for 201 in from-internal (domain 192.168.102.237)
sip_route_dump: route/path hop: <sip:6kudpouh_AT_192.0.2.238;transport=ws;ob
<— Transmitting (no NAT) to 192.168.102.240:5060 —
SIP/2.0 100 Trying
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK2904666;received=192.168.102.240
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
To: <sip:201_AT_192.168.102.237
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1091 INVITE
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:201_AT_192.168.102.237:5160;transport=ws
Content-Length: 0
<------------
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
[2019-11-07 06:46:46] ERROR[5157][C-00000019]: res_pjsip_header_funcs.c:461 func_read_header: This function requires a PJSIP channel.
Audio is at 17470
Video is at 192.168.102.237:15770
Adding codec ulaw to SDP
Adding video codec vp8 to SDP
Adding codec alaw to SDP
Adding codec gsm to SDP
Adding codec g726 to SDP
Adding codec g722 to SDP
Adding video codec h264 to SDP
Adding video codec mpeg4 to SDP
Adding non-codec 0x1 (telephone-event) to SDP
Reliably Transmitting (no NAT) to 192.168.102.194:55836:
INVITE sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK377a6c13
Max-Forwards: 70
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
Contact: <sip:202_AT_192.168.102.237:5160
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 102 INVITE
User-Agent: FPBX-14.0.13.4(13.19.1)
Date: Thu, 07 Nov 2019 06:46:46 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
P-Asserted-Identity: “Kurento-sip” <sip:202_AT_192.168.102.237
Content-Type: application/sdp
Content-Length: 965
v=0
o=root 1236270955 1236270955 IN IP4 192.168.102.237
s=Asterisk PBX 13.19.1
c=IN IP4 192.168.102.237
b=CT:384
t=0 0
m=audio 17470 RTP/AVP 0 8 3 111 9 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:111 G726-32/8000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=maxptime:150
a=ice-ufrag:249a7bc61da134e410ef4afe4491d0f3
a=ice-pwd:106285f759eb19492ed3ddef5b82d2db
a=candidate:Hc0a866ed 1 UDP 2130706431 192.168.102.237 17470 typ host
a=candidate:Hc0a866ed 2 UDP 2130706430 192.168.102.237 17471 typ host
a=sendrecv
m=video 15770 RTP/AVP 100 99 104
a=ice-ufrag:4f5504db34ce45010851d7aa5d11806e
a=ice-pwd:48cd5c3511fc1c49057f054e2d9f4903
a=candidate:Hc0a866ed 1 UDP 2130706431 192.168.102.237 15770 typ host
a=candidate:Hc0a866ed 2 UDP 2130706430 192.168.102.237 15771 typ host
a=rtpmap:100 VP8/90000
a=rtcp-fb:* ccm fir
a=rtpmap:99 H264/90000
a=rtpmap:104 MP4V-ES/90000
a=sendrecv
<— Transmitting (no NAT) to 192.168.102.240:5060 —
SIP/2.0 180 Ringing
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK2904666;received=192.168.102.240
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
To: <sip:201_AT_192.168.102.237;tag=as7431f1c7
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1091 INVITE
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:201_AT_192.168.102.237:5160;transport=ws
P-Asserted-Identity: “tanim1” <sip:201_AT_192.168.102.237
Content-Length: 0
<------------
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK377a6c13
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 102 INVITE
Content-Length: 0
<-------------
— (7 headers 0 lines) —
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK377a6c13
Contact: <sip:201_AT_192.168.102.194:55836
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=7781e136
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Zoiper rv2.10.3.0
Allow-Events: presence, kpml, talk
Content-Length: 0
<-------------
— (11 headers 0 lines) —
sip_route_dump: route/path hop: <sip:201_AT_192.168.102.194:55836
<— Transmitting (no NAT) to 192.168.102.240:5060 —
SIP/2.0 180 Ringing
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK2904666;received=192.168.102.240
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
To: <sip:201_AT_192.168.102.237;tag=as7431f1c7
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1091 INVITE
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:201_AT_192.168.102.237:5160;transport=ws
Content-Length: 0
<------------
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK377a6c13
Contact: <sip:201_AT_192.168.102.194:55836
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=7781e136
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
User-Agent: Zoiper rv2.10.3.0
Allow-Events: presence, kpml, talk
Content-Length: 236
v=0
o=Zoiper 0 3 IN IP4 192.168.102.194
s=Z
c=IN IP4 192.168.102.194
t=0 0
m=audio 41064 RTP/AVP 0 8 3 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=sendrecv
m=video 0 RTP/AVP 100
a=rtpmap:100 VP8/90000
a=sendrecv
<-------------
— (12 headers 12 lines) —
Found RTP audio format 0
Found RTP audio format 8
Found RTP audio format 3
Found RTP audio format 101
Found audio description format telephone-event for ID 101
Capabilities: us - (ulaw|alaw|gsm|g726|g722|h264|mpeg4|vp8), peer - audio=(ulaw|gsm|alaw)/video=(nothing)/text=(nothing), combined - (ulaw|alaw|gsm)
Non-codec capabilities (dtmf): us - 0x1 (telephone-event|), peer - 0x1 (telephone-event|), combined - 0x1 (telephone-event|)
Peer audio RTP is at port 192.168.102.194:41064
Peer doesn’t provide video
sip_route_dump: route/path hop: <sip:201_AT_192.168.102.194:55836
set_destination: Parsing <sip:201_AT_192.168.102.194:55836 for address/port to send to
set_destination: set destination to 192.168.102.194:55836
Transmitting (no NAT) to 192.168.102.194:55836:
ACK sip:201_AT_192.168.102.194:55836 SIP/2.0
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK08a5443c
Max-Forwards: 70
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=7781e136
Contact: <sip:202_AT_192.168.102.237:5160
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 102 ACK
User-Agent: FPBX-14.0.13.4(13.19.1)
Content-Length: 0
Audio is at 11508
Video is at 192.168.102.237:17970
Adding codec ulaw to SDP
Adding codec opus to SDP
Adding video codec vp8 to SDP
Adding non-codec 0x1 (telephone-event) to SDP
<— Reliably Transmitting (no NAT) to 192.168.102.240:5060 —
SIP/2.0 200 OK
Via: SIP/2.0/WS 192.0.2.238;branch=z9hG4bK2904666;received=192.168.102.240
From: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
To: <sip:201_AT_192.168.102.237;tag=as7431f1c7
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 1091 INVITE
Server: FPBX-14.0.13.4(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:201_AT_192.168.102.237:5160;transport=ws
P-Asserted-Identity: “tanim1” <sip:201_AT_192.168.102.237
Content-Type: application/sdp
Content-Length: 863
v=0
o=root 1963643784 1963643784 IN IP4 192.168.102.237
s=Asterisk PBX 13.19.1
c=IN IP4 192.168.102.237
b=CT:384
t=0 0
m=audio 11508 RTP/AVPF 0 107 101
a=rtpmap:0 PCMU/8000
a=rtpmap:107 opus/48000/2
a=fmtp:107 useinbandfec=1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=maxptime:20
a=ice-ufrag:4bd2932521544f6c2c9018ce28c4ccea
a=ice-pwd:30fd912566d17ffa4c10c86e6e2b8945
a=candidate:Hc0a866ed 1 UDP 2130706431 192.168.102.237 11508 typ host
a=candidate:Hc0a866ed 2 UDP 2130706430 192.168.102.237 11509 typ host
a=sendrecv
m=video 17970 RTP/AVPF 100
a=ice-ufrag:62a2d33d4696fcfd5605139419ae2a69
a=ice-pwd:67ed66d562978e172f9a3d4232d66981
a=candidate:Hc0a866ed 1 UDP 2130706431 192.168.102.237 17970 typ host
a=candidate:Hc0a866ed 2 UDP 2130706430 192.168.102.237 17971 typ host
a=rtpmap:100 VP8/90000
a=rtcp-fb:* ccm fir
a=sendrecv
<------------
[2019-11-07 06:46:56] WARNING[6865]: chan_sip.c:4065 retrans_pkt: Retransmission timeout reached on transmission hsrm6uqmt76jlk04if8l for seqno 1091 (Critical Response) – See Packet timed out after 6399ms with no response
[2019-11-07 06:46:56] WARNING[6865]: chan_sip.c:4089 retrans_pkt: Hanging up call hsrm6uqmt76jlk04if8l - no reply to our critical packet (see).
Scheduling destruction of SIP dialog ‘79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160’ in 6400 ms (Method: INVITE)
set_destination: Parsing <sip:201_AT_192.168.102.194:55836 for address/port to send to
set_destination: set destination to 192.168.102.194:55836
Reliably Transmitting (no NAT) to 192.168.102.194:55836:
BYE sip:201_AT_192.168.102.194:55836 SIP/2.0
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK14f250c9
Max-Forwards: 70
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=7781e136
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 103 BYE
User-Agent: FPBX-14.0.13.4(13.19.1)
X-Asterisk-HangupCause: No user responding
X-Asterisk-HangupCauseCode: 18
Content-Length: 0
<— SIP read from UDP:192.168.102.194:55836 —
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.102.237:5160;branch=z9hG4bK14f250c9
Contact: <sip:201_AT_192.168.102.194:55836
To: <sip:201_AT_192.168.102.194:55836;rinstance=02ac6aa420d947a9;transport=UDP;tag=7781e136
From: “Kurento-sip” <sip:202_AT_192.168.102.237:5160;tag=as3f213ceb
Call-ID: 79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160
CSeq: 103 BYE
User-Agent: Zoiper rv2.10.3.0
Content-Length: 0
<-------------
— (9 headers 0 lines) —
Really destroying SIP dialog ‘79b59aca55e328e441778a63050decd6_AT_192.168.102.237:5160’ Method: INVITE
Scheduling destruction of SIP dialog ‘hsrm6uqmt76jlk04if8l’ in 6400 ms (Method: INVITE)
set_destination: Parsing <sip:6kudpouh_AT_192.0.2.238;transport=ws;ob for address/port to send to
set_destination: URI is for WebSocket, we can’t set destination
Reliably Transmitting (no NAT) to 192.168.102.240:5060:
BYE sip:6kudpouh_AT_192.0.2.238;transport=ws;ob SIP/2.0
Via: SIP/2.0/WS 192.168.102.237:5160;branch=z9hG4bK3686dd0e
Max-Forwards: 70
From: <sip:201_AT_192.168.102.237;tag=as7431f1c7
To: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 102 BYE
User-Agent: FPBX-14.0.13.4(13.19.1)
Proxy-Authorization: Digest username=“sgpaam4g”, realm=“asterisk”, algorithm=MD5, uri=“sip:192.168.102.237”, nonce=“5242cc05”, response=“43b017524ddbfd7a249c580d7ca5bf20”
X-Asterisk-HangupCause: No user responding
X-Asterisk-HangupCauseCode: 18
Content-Length: 0
<— SIP read from WS:192.168.102.240:45542 —
SIP/2.0 200 OK
Via: SIP/2.0/WS 192.168.102.237:5160;branch=z9hG4bK3686dd0e
To: <sip:202_AT_192.168.102.237;tag=1ucf77uuh5
From: <sip:201_AT_192.168.102.237;tag=as7431f1c7
Call-ID: hsrm6uqmt76jlk04if8l
CSeq: 102 BYE
Supported: outbound
User-Agent: SIP.js/0.7.8
Content-Length: 0
Please help me… 