search

jorge-teixeira / sipml5

Automatically exported from code.google.com/p/sipml5
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Failed to handle new challenge :: === PUBLISH Dialog terminated === #64

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Edit the test_api.html and apply the proxy user and proxy innformation
2. Open test_api.html in Chrome
3. Register and then click publish

What is the expected output? What do you see instead?
Expected the status 200 for publish notification. But I get 

=== PUBLISH Dialog terminated === SIPml-api.js:1
session event = type = i_ao_request - description = Proxy Authentication 
Required testpage.htm:43
session event = type = terminated - description = Proxy Authentication Required 
testpage.htm:43
response code = 407 

What version of the product are you using? On what operating system?
I am using Kamailio Sip Proxy and WebRC2SIP web socket server in CentOS 6.2
Latest Chrome (Version 23.0.1271.97 m) running on Windows 7.

Please provide any additional information below.

API version = 1.0.1 SIPml-api.js:1
User-Agent=Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like 
Gecko) Chrome/23.0.1271.97 Safari/537.11 SIPml-api.js:1
Navigator friendly name = chrome SIPml-api.js:1
OS friendly name = windows SIPml-api.js:1
<initialize> Entering... url: http://dev.stellooo.com/telecom/testpage.htm 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:21
<connectBG> Entering 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:267
<connectBG> currentPort: [object Object] 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:270
<processSpecialWebsite> Entering 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:65
<processSpecialWebsite> http://dev.stellooo.com/telecom/testpage.htm 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:69
<attachSinkToForms> Entering 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:759
<isOnePasswordForm> inputArray.length:6 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:629
<isOnePasswordForm> passwordCount: 0 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:658
<attachSinkToForms> Exitting 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:771
<callJSFunction> -- url: http://dev.stellooo.com/telecom/testpage.htm 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:1104
<addEmbed> embed adding. 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:1000
<addEmbed> embed add completed. 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:1008
<receiveBG> setdocnum: 0 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:290
<isPopupSignInWindow> 
document.location.href:http://dev.stellooo.com/telecom/testpage.htm 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:41
<isPasswordExists> Entering 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:595
<receiveBG> starttoprocessotp, pagetype: undefined, otppagetype: undefined, 
url: http://dev.stellooo.com/telecom/testpage.htm 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:332
<processOTPPage> Entering... 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:11
<processOTPPage> tab URL: http://dev.stellooo.com/telecom/testpage.htm, 
document URL:http://dev.stellooo.com/telecom/testpage.htm 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:12
<processExtendPage> Entering... 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:568
<processExtendPage> currentPageType: , lastPageType: undefined 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:576
<setPageType> Entering... pagetype:  
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogon.js:986
<processExtendPage> Existing... 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:621
<fillOTPPage> Entering... 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:18
<initOTPMap> Entering... 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:523
<initOTPMap> otpArr.length = 5 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:531
<getOTPElements> otp information not found. 
chrome-extension://dfaldikcoaplhepekpbngkepfcoiihef/websiteLogonOTP.js:118
Got stream :) SIPml-api.js:1
s_websocket_server_url=ws://50.62.131.23:10060 SIPml-api.js:1
s_sip_outboundproxy_url=udp://50.62.131.23:5060 SIPml-api.js:1
b_rtcweb_breaker_enabled=no SIPml-api.js:1
SIP stack start: proxy='sipml5.org:6062', realm='<sip:50.62.131.23>', 
impi='1006', impu='<sip:1006@50.62.131.23>' SIPml-api.js:1
Connecting to 'ws://50.62.131.23:10060' SIPml-api.js:1
__tsip_transport_ws_onopen SIPml-api.js:1
State machine: tsip_dialog_register_Started_2_InProgress_X_oRegister 
SIPml-api.js:1
SEND: REGISTER sip:50.62.131.23 SIP/2.0
Via: SIP/2.0/WS 
df7jal23ls0d.invalid;branch=z9hG4bKlcnWVCamsbFZ3iTHoQVGVm3ZyrwrQ34t;rport
From: <sip:1006@50.62.131.23>;tag=H7auG2pc0F3TyRCOqPDr
To: <sip:1006@50.62.131.23>
Contact: 
"1006"<sip:1006@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=ws>;expires=200
Call-ID: fc9ec276-9090-9e06-976c-6036dd570f39
CSeq: 33702 REGISTER
Content-Length: 0
Route: <sip:50.62.131.23:5060;lr;transport=udp>
Max-Forwards: 70
Supported: path

 SIPml-api.js:1
session event = type = connecting - description = Connecting... testpage.htm:43
session event = type = sent_request - description = REGISTER request 
successfully sent testpage.htm:43
__tsip_transport_ws_onmessage SIPml-api.js:1
recv=SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 
50.62.131.23:10060;rport=10060;branch=z9hG4bKlcnWVCamsbFZ3iTHoQVGVm3ZyrwrQ34t
From: <sip:1006@50.62.131.23>;tag=H7auG2pc0F3TyRCOqPDr
To: <sip:1006@50.62.131.23>;tag=b01221cac0ed2edd8409481b9ce2d72c.72e9
Call-ID: fc9ec276-9090-9e06-976c-6036dd570f39
CSeq: 33702 REGISTER
Content-Length: 0
Via: SIP/2.0/TCP 
24.130.220.24:3001;rport;branch=z9hG4bKlcnWVCamsbFZ3iTHoQVGVm3ZyrwrQ34t;ws-hacke
d=WS
WWW-Authenticate: Digest 
realm="50.62.131.23",nonce="UOhEs1DoQ4cTq7jCFmUoKT75fBZwxYx2",stale=FALSE
Server: kamailio (3.4.0-dev5 (x86_64/linux))

 SIPml-api.js:1
State machine: tsip_dialog_register_InProgress_2_InProgress_X_401_407_421_494 
SIPml-api.js:1
SEND: REGISTER sip:50.62.131.23 SIP/2.0
Via: SIP/2.0/WS 
df7jal23ls0d.invalid;branch=z9hG4bKqzhDqmssNWIdMAna0T0krJc04IhrLQeZ;rport
From: <sip:1006@50.62.131.23>;tag=H7auG2pc0F3TyRCOqPDr
To: <sip:1006@50.62.131.23>
Contact: 
"1006"<sip:1006@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=ws>;expires=200
Call-ID: fc9ec276-9090-9e06-976c-6036dd570f39
CSeq: 33703 REGISTER
Content-Length: 0
Route: <sip:50.62.131.23:5060;lr;transport=udp>
Max-Forwards: 70
Authorization: Digest 
username="1006",realm="50.62.131.23",nonce="UOhEs1DoQ4cTq7jCFmUoKT75fBZwxYx2",ur
i="sip:50.62.131.23",response="83f2f3d8723eb84513fb6e9e2ebd9c25",algorithm=MD5
Supported: path

 SIPml-api.js:1
session event = type = sent_request - description = REGISTER request 
successfully sent testpage.htm:43
__tsip_transport_ws_onmessage SIPml-api.js:1
recv=SIP/2.0 200 OK
Via: SIP/2.0/UDP 
50.62.131.23:10060;rport=10060;branch=z9hG4bKqzhDqmssNWIdMAna0T0krJc04IhrLQeZ
From: <sip:1006@50.62.131.23>;tag=H7auG2pc0F3TyRCOqPDr
To: <sip:1006@50.62.131.23>;tag=b01221cac0ed2edd8409481b9ce2d72c.0d96
Contact: 
<sip:1006@50.62.131.23:10060;rtcweb-breaker=no;transport=udp;ws-src-ip=24.130.22
0.24;ws-src-port=3001;ws-src-proto=ws>;expires=200
Call-ID: fc9ec276-9090-9e06-976c-6036dd570f39
CSeq: 33703 REGISTER
Content-Length: 0
Via: SIP/2.0/TCP 
24.130.220.24:3001;rport;branch=z9hG4bKqzhDqmssNWIdMAna0T0krJc04IhrLQeZ;ws-hacke
d=WS
Server: kamailio (3.4.0-dev5 (x86_64/linux))

 SIPml-api.js:1
State machine: tsip_dialog_register_InProgress_2_Connected_X_2xx SIPml-api.js:1
session event = type = connected - description = Connected testpage.htm:43
State machine: tsip_dialog_generic_Any_2_InProgress_X_oPublish SIPml-api.js:1
SEND: PUBLISH sip:50.62.131.23 SIP/2.0
Via: SIP/2.0/WS 
df7jal23ls0d.invalid;branch=z9hG4bKeUdgl2bKGPZm5gOdvEv7XW8DxMfwrNyp;rport
From: <sip:1006@50.62.131.23>;tag=Vk4Ivuc290C8Jy39OGc1
To: <sip:1006@50.62.131.23>
Call-ID: 80b12279-6a20-32e6-89fe-0a84fc08fb90
CSeq: 41642 PUBLISH
Expires: 200
Content-Type: application/pidf+xml
Content-Length: 366
Route: <sip:50.62.131.23:5060;lr;transport=udp>
Max-Forwards: 70
Event: presence

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
 xmlns:im="urn:ietf:params:xml:ns:pidf:im" entity="sip:1006@50.62.131.23">
<tuple id="s8794">
<status>
   <basic>open</basic>
   <im:im>online</im:im>
</status>
<contact priority="0.8">tel: +33600000000</contact>
<note  xml:lang="fr">Bonjour de Paris :)</note>
</tuple>
</presence> SIPml-api.js:1
session event = type = connecting - description = Connecting... testpage.htm:43
__tsip_transport_ws_onmessage SIPml-api.js:1
recv=SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 
50.62.131.23:10060;rport=10060;branch=z9hG4bKeUdgl2bKGPZm5gOdvEv7XW8DxMfwrNyp
From: <sip:1006@50.62.131.23>;tag=Vk4Ivuc290C8Jy39OGc1
To: <sip:1006@50.62.131.23>;tag=b01221cac0ed2edd8409481b9ce2d72c.0077
Call-ID: 80b12279-6a20-32e6-89fe-0a84fc08fb90
CSeq: 41642 PUBLISH
Content-Length: 0
Via: SIP/2.0/TCP 
24.130.220.24:3001;rport;branch=z9hG4bKeUdgl2bKGPZm5gOdvEv7XW8DxMfwrNyp;ws-hacke
d=WS
Proxy-Authenticate: Digest 
realm="50.62.131.23",nonce="UOhEtlDoQ4rj3SMk3p6VF0tDkDdxLGvQ",stale=FALSE
Server: kamailio (3.4.0-dev5 (x86_64/linux))

 SIPml-api.js:1
State machine: tsip_dialog_generic_InProgress_2_InProgress_X_401_407_421_494 
SIPml-api.js:1
SEND: PUBLISH sip:50.62.131.23 SIP/2.0
Via: SIP/2.0/WS 
df7jal23ls0d.invalid;branch=z9hG4bK41L1TufTVICeVH74l1dN6TRJ8znpRLrX;rport
From: <sip:1006@50.62.131.23>;tag=Vk4Ivuc290C8Jy39OGc1
To: <sip:1006@50.62.131.23>
Call-ID: 80b12279-6a20-32e6-89fe-0a84fc08fb90
CSeq: 41643 PUBLISH
Expires: 200
Content-Type: application/pidf+xml
Content-Length: 366
Route: <sip:50.62.131.23:5060;lr;transport=udp>
Max-Forwards: 70
Proxy-Authorization: Digest 
username="1006",realm="50.62.131.23",nonce="UOhEtlDoQ4rj3SMk3p6VF0tDkDdxLGvQ",ur
i="sip:50.62.131.23",response="40b5e87b715d80bec0afe519705affd3",algorithm=MD5
Event: presence

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
 xmlns:im="urn:ietf:params:xml:ns:pidf:im" entity="sip:1006@50.62.131.23">
<tuple id="s8794">
<status>
   <basic>open</basic>
   <im:im>online</im:im>
</status>
<contact priority="0.8">tel: +33600000000</contact>
<note  xml:lang="fr">Bonjour de Paris :)</note>
</tuple>
</presence> SIPml-api.js:1
__tsip_transport_ws_onmessage SIPml-api.js:1
recv=SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 
50.62.131.23:10060;rport=10060;branch=z9hG4bK41L1TufTVICeVH74l1dN6TRJ8znpRLrX
From: <sip:1006@50.62.131.23>;tag=Vk4Ivuc290C8Jy39OGc1
To: <sip:1006@50.62.131.23>;tag=b01221cac0ed2edd8409481b9ce2d72c.438c
Call-ID: 80b12279-6a20-32e6-89fe-0a84fc08fb90
CSeq: 41643 PUBLISH
Content-Length: 0
Via: SIP/2.0/TCP 
24.130.220.24:3001;rport;branch=z9hG4bK41L1TufTVICeVH74l1dN6TRJ8znpRLrX;ws-hacke
d=WS
Proxy-Authenticate: Digest 
realm="50.62.131.23",nonce="UOhEtlDoQ4rj3SMk3p6VF0tDkDdxLGvQ",stale=FALSE
Server: kamailio (3.4.0-dev5 (x86_64/linux))

 SIPml-api.js:1
State machine: tsip_dialog_generic_InProgress_2_InProgress_X_401_407_421_494 
SIPml-api.js:1
Failed to handle new challenge SIPml-api.js:1
State machine: Exec function failed. Moving to the termnial state SIPml-api.js:1
=== PUBLISH Dialog terminated === SIPml-api.js:1
session event = type = i_ao_request - description = Proxy Authentication 
Required testpage.htm:43
session event = type = terminated - description = Proxy Authentication Required 
testpage.htm:43
response code = 407 testpage.htm:45

Original issue reported on code.google.com by ajithdes...@gmail.com on 5 Jan 2013 at 10:18

GoogleCodeExporter commented 8 years ago 
I believe this issue is caused because a PUBLISH request does not create a 
dialog (as per section 4 of RFC 3903).

This behaviour is already handled for REGISTER requests in tsip_dialog.js so 
the attached patch against trunk revision 174 adds PUBLISH support too.

Original comment by d...@davecardwell.co.uk on 29 Jan 2013 at 12:07

Attachments:

GoogleCodeExporter commented 8 years ago 
I use svn=179 version, still have this problem, Also, I try to update 
src/tinySIP/src/dialogs/tsip_dialog.js as you said, same thing happen

Original comment by dragon2...@gmail.com on 12 Jun 2013 at 8:02

GoogleCodeExporter commented 8 years ago 
Yeah this fix is not working...i have also tried it..

Original comment by jani....@gmail.com on 14 Jun 2013 at 10:52

GoogleCodeExporter commented 8 years ago 
Hi All
 I am also getting the same error.....
If anybody has got it fixed..plz share the same.

Original comment by pratap....@gmail.com on 18 Jan 2014 at 4:26