Hi, I have a problem with the blind transfer via WebSocket, debugging from the browser we see that in some cases when the REFER is done and the sip message "202 Accepted" arrives, the message "180 Ringing" arrives first and then the "100 Trying" and the transfer goes in error with "500 JsSIP Internal Error"
I have an architecture with Kamailio in frontend and asterisk in backend on the same network, the sip dialogue between FE and BE is in SIP / UDP. The WebRTC client connects to WebSocket at Kamailio's public address. We have verified that the sip messages exchanged between kamailio and asterisk are always correct. Kamailio Ver. 4.4.4 Asterisk Ver. 13.18.3 PJSIP Ver. 2.6 JSSIP Ver. 3.2.2 Thanks Alessio
REFER sip:[email protected]:5160 SIP/2.0 Route: <sip:192.168.33.171:4443;transport=ws;r2=on;lr;did=491.6871> Route: <sip:192.168.33.171:5068;r2=on;lr;did=491.6871> Via: SIP/2.0/WSS tq3hhtsci9bi.invalid;branch=z9hG4bK4056005 Max-Forwards: 69 To: <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 From: <sip:[email protected]>;tag=44egpqrkm1 Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 2663 REFER Refer-To: <sip:[email protected]:4443> Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER,INFO Supported: outbound User-Agent: JsSIP 3.2.2 Content-Length: 0 SIP/2.0 202 Accepted Via: SIP/2.0/WSS tq3hhtsci9bi.invalid;rport=2411;received=192.168.33.222;branch=z9hG4bK4056005 Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af From: <sip:[email protected]>;tag=44egpqrkm1 To: <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 CSeq: 2663 REFER Expires: 600 Contact: <sip:[email protected]:5160> Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, REFER, MESSAGE Supported: 100rel, timer, replaces, norefersub Server: FPBX-14.0.1.20(13.15.1) Content-Length: 0 NOTIFY sip:[email protected];transport=ws SIP/2.0 Via: SIP/2.0/WSS 192.168.33.171:4443;branch=z9hG4bK7001.66cd2ec915ed5f2832f86583c1d95ce0.0 Via: SIP/2.0/UDP 192.168.33.172:5160;received=192.168.33.172;rport=5160;branch=z9hG4bKPj1dc8ebd4-fb71-42de-a893-774fdddb4795 From: "501" <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 To: <sip:[email protected]>;tag=44egpqrkm1 Contact: <sip:[email protected]:5160> Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 6804 NOTIFY Event: refer Subscription-State: active;expires=599 Allow-Events: message-summary, presence, dialog, refer Max-Forwards: 69 User-Agent: FPBX-14.0.1.20(13.15.1) Content-Type: message/sipfrag;version=2.0 Content-Length: 21 SIP/2.0 180 Ringing SIP/2.0 200 OK Via: SIP/2.0/WSS 192.168.33.171:4443;branch=z9hG4bK7001.66cd2ec915ed5f2832f86583c1d95ce0.0 Via: SIP/2.0/UDP 192.168.33.172:5160;received=192.168.33.172;rport=5160;branch=z9hG4bKPj1dc8ebd4-fb71-42de-a893-774fdddb4795 To: <sip:[email protected]>;tag=44egpqrkm1 From: "501" <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 6804 NOTIFY Supported: outbound Content-Length: 0 NOTIFY sip:[email protected];transport=ws SIP/2.0 Via: SIP/2.0/WSS 192.168.33.171:4443;branch=z9hG4bKa001.ed76da8343c72914f2b6511b4e25ba73.0 Via: SIP/2.0/UDP 192.168.33.172:5160;received=192.168.33.172;rport=5160;branch=z9hG4bKPjc79863a7-a074-45c6-ae30-3201695c006a From: "501" <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 To: <sip:[email protected]>;tag=44egpqrkm1 Contact: <sip:[email protected]:5160> Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 6803 NOTIFY Event: refer Subscription-State: active;expires=599 Allow-Events: message-summary, presence, dialog, refer Max-Forwards: 69 User-Agent: FPBX-14.0.1.20(13.15.1) Content-Type: message/sipfrag;version=2.0 Content-Length: 20 SIP/2.0 100 Trying SIP/2.0 500 JsSIP Internal Error Via: SIP/2.0/WSS 192.168.33.171:4443;branch=z9hG4bKa001.ed76da8343c72914f2b6511b4e25ba73.0 Via: SIP/2.0/UDP 192.168.33.172:5160;received=192.168.33.172;rport=5160;branch=z9hG4bKPjc79863a7-a074-45c6-ae30-3201695c006a To: <sip:[email protected]>;tag=44egpqrkm1 From: "501" <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 6803 NOTIFY Supported: outbound Content-Length: 0 NOTIFY sip:[email protected];transport=ws SIP/2.0 Via: SIP/2.0/WSS 192.168.33.171:4443;branch=z9hG4bK8001.d32ab96b07907079919c2b1378988d87.0 Via: SIP/2.0/UDP 192.168.33.172:5160;received=192.168.33.172;rport=5160;branch=z9hG4bKPj7534dbc0-c393-46ad-97f2-f98dba95d51c From: "501" <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 To: <sip:[email protected]>;tag=44egpqrkm1 Contact: <sip:[email protected]:5160> Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 6805 NOTIFY Event: refer Subscription-State: active;expires=599 Allow-Events: message-summary, presence, dialog, refer Max-Forwards: 69 User-Agent: FPBX-14.0.1.20(13.15.1) Content-Type: message/sipfrag;version=2.0 Content-Length: 21 SIP/2.0 180 Ringing SIP/2.0 200 OK Via: SIP/2.0/WSS 192.168.33.171:4443;branch=z9hG4bK8001.d32ab96b07907079919c2b1378988d87.0 Via: SIP/2.0/UDP 192.168.33.172:5160;received=192.168.33.172;rport=5160;branch=z9hG4bKPj7534dbc0-c393-46ad-97f2-f98dba95d51c To: <sip:[email protected]>;tag=44egpqrkm1 From: "501" <sip:[email protected]>;tag=4a0f97f0-d80c-4409-b23c-f067c5dc8957 Call-ID: 44dc493b-e192-4f6d-952b-2b992d0957af CSeq: 6805 NOTIFY Supported: outbound Content-Length: 0
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
