GoogleCodeExporter
commented
9 years ago Additional observations. The call flow is below:
Chrome Browser --> webrtc2sip server --> Broadsoft BroadWorks application server
1. When web breaker is enabled, call authentication challenge dialog between
the webrtc2sip server and the browser is not seen. Is this normal? Does the
webrts2sip server handle this dialog without notifying the browser?
2. When calls are placed with web breaker enabled, the HA1 string is included
in the contact header. Since we do not see dialog between the webrtc2sip server
and the browser, what purpose does this serve?
3. Calls fail when the webrtc2sip server sends a re-invite with authentication
and is not recognized by the BroadWorks server. The BroadWorks server then
re-sends the challenge. At this point the webrtc2sip server issues the
following error:
*INFO: State machine: x0000_Any_2_Any_X_i401_407_Challenge
***ERROR: function: "tsip_dialog_update_challenges()"
file: "src/dialogs/tsip_dialog.c"
line: "904"
MSG: Failed to handle new challenge
*INFO: State machine: Exec function failed. Moving to terminal state.
Is the code designed to handle initial authentication failures?
4. While this dialog is taking place (web breaker enabled), the browser console
shows a 100 trying message is received from the transaction layer, followed be
a 180 ringing message and a 603 decline message. These messages seem to be
generated by the browser SIP stack:
tsk_utils.js:110
__tsip_transport_ws_onmessage tsk_utils.js:110
recv=SIP/2.0 100 Trying (sent from the Transaction Layer)
Via: SIP/2.0/WSS
df7jal23ls0d.invalid;rport;branch=z9hG4bKeaaUbvuTblpscH69GWuXP2ss9R1XTZpc
From: <sip:YYYYYYYYYY@REALM>;tag=MnCvAkDXiIAbhcns1wmk
To: <sip:XXXXXXXXXX@REALM>
Call-ID: 5c52e263-3a84-54f4-7d6b-29391930ed32
CSeq: 55650 INVITE
Content-Length: 0
tsk_utils.js:110
State machine: x0000_Any_2_Any_X_i1xx tsk_utils.js:110
==session event = i_ao_request call.htm:720
__tsip_transport_ws_onmessage tsk_utils.js:110
recv=SIP/2.0 180 Ringing
Via: SIP/2.0/WSS
df7jal23ls0d.invalid;rport;branch=z9hG4bKeaaUbvuTblpscH69GWuXP2ss9R1XTZpc
From: <sip:YYYYYYYYYY@REALM>;tag=MnCvAkDXiIAbhcns1wmk
To: <sip:XXXXXXXXXX@REALM>;tag=1363503001173
Contact:
<sips:XXXXXXXXXX@webrtc2sip_server:5060;transport=wss;ws-src-ip=zzz.zzz.zzz.zzz;
ws-src-port=33544;ws-src-proto=wss>
Call-ID: 5c52e263-3a84-54f4-7d6b-29391930ed32
CSeq: 55650 INVITE
Content-Length: 0
Allow: ACK,BYE,CANCEL,INVITE,MESSAGE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE
tsk_utils.js:110
State machine: x0000_Any_2_Any_X_i1xx tsk_utils.js:110
==session event = i_ao_request call.htm:720
__tsip_transport_ws_onmessage tsk_utils.js:110
recv=SIP/2.0 603 Decline
Via: SIP/2.0/WSS
df7jal23ls0d.invalid;rport;branch=z9hG4bKeaaUbvuTblpscH69GWuXP2ss9R1XTZpc
From: <sip:YYYYYYYYYY@REALM>;tag=MnCvAkDXiIAbhcns1wmk
To: <sip:XXXXXXXXXX@REALM>;tag=1363503001173
Call-ID: 5c52e263-3a84-54f4-7d6b-29391930ed32
CSeq: 55650 INVITE
Content-Length: 0
Reason: text="Decline";cause=603;text="Decline"
tsk_utils.js:110
SEND: ACK sip:XXXXXXXXXX@REALM SIP/2.0
Via: SIP/2.0/WSS
df7jal23ls0d.invalid;branch=z9hG4bKeaaUbvuTblpscH69GWuXP2ss9R1XTZpc;rport
From: <sip:YYYYYYYYYY@REALM>;tag=MnCvAkDXiIAbhcns1wmk
To: <sip:XXXXXXXXXX@REALM>;tag=1363503001173
Call-ID: 5c52e263-3a84-54f4-7d6b-29391930ed32
CSeq: 55650 ACK
Content-Length: 0
Route: <sip:BroadWorks_server:5060;lr;transport=udp>
Max-Forwards: 70
tsk_utils.js:110
State machine: c0000_Outgoing_2_Terminated_X_i300_to_i699INVITE tsk_utils.js:110
=== INVITE Dialog terminated === tsk_utils.js:110
PeerConnection::stop() tsk_utils.js:110
==session event = i_ao_request call.htm:720
__on_state_change tsk_utils.js:110
==session event = terminated call.htm:720
The FSM is in the final state tsk_utils.js:116
The webrtc2sip server does not receive or generate any of these messages. Is
this normal? When calls are made with web breaker disabled, normal SIP
messaging is seen on the browser console.
5. The webrtc2sip debug shows incoming messages from the browser and BroadWorks
server. Is there a way to also view the outgoing messages?
Thanks!Original comment by GuyLeo...@gmail.com on 20 Mar 2013 at 10:32
Original issue reported on code.google.com by
nikesh...@gmail.comon 6 Mar 2013 at 8:58