emkei / sipml5

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

Nightly not make a call #128

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (Wireshark) or Javascript console log
if you want quick response

What steps will reproduce the problem?
1. Log in SIPML5 for webRTC2SIP elastix, in Nightly
2. Make a call from Zoiper to Nightly

What is the expected output? What do you see instead?
Normal communication

What version of the product are you using? On what operating system?
Windows 8, Nightly 27, webrtc4all Stable.

Please provide any additional information below.

ps: in google Chorme the communication is a normal.

console script

==stack event = i_new_call" SIPml-api.js:1
09:19:26.268 "onSetRemoteDescriptionError" SIPml-api.js:1
09:19:26.269 [object Object] SIPml-api.js:1
09:19:26.373 removeStream not yet implemented SIPml-api.js:3
09:19:26.371 "onGetUserMediaSuccess" SIPml-api.js:1
09:19:26.371 "createAnswer" SIPml-api.js:1
09:19:26.372 "onCreateSdpError" SIPml-api.js:1
09:19:26.372 [object Object] SIPml-api.js:1
09:19:26.372 "State machine: s0000_Ringing_2_Terminated_X_Reject" SIPml-api.js:1
09:19:26.373 "=== INVITE Dialog terminated ===" SIPml-api.js:1
09:19:26.380 "==stack event = m_permission_accepted" SIPml-api.js:1
09:19:26.380 "State machine: 
tsip_transac_ist_Proceeding_2_Completed_X_300_to_699" SIPml-api.js:1
09:19:26.381 "SEND: SIP/2.0 603 Failed to get local SDP

Via: SIP/2.0/WS 10.1.1.220:10060;rport=10060;branch=z9hG4bK-1229055589

From: <sip:9000@10.1.1.220>;tag=1152305166

To: <sip:9001@10.1.1.220:10060>;tag=1Gs2uzFBit3LaG7mpf1p

Call-ID: 313289da-dbd1-72b4-157b-859934a08bbd

CSeq: 203449991 INVITE

Content-Length: 0

Reason: SIP; cause=603; text="Failed to get local SDP"

" SIPml-api.js:1
09:19:26.388 "__tsip_transport_ws_onmessage" SIPml-api.js:1
09:19:26.392 "recv=ACK sip:9001@10.1.1.220:10060 SIP/2.0

Via: SIP/2.0/WS 10.1.1.220:10060;rport;branch=z9hG4bK-1229055589

From: <sip:9000@10.1.1.220>;tag=1152305166

To: <sip:9001@10.1.1.220:10060>;tag=1Gs2uzFBit3LaG7mpf1p

Call-ID: 313289da-dbd1-72b4-157b-859934a08bbd

CSeq: 203449991 ACK

Content-Length: 0

Max-Forwards: 70

Route: <sip:10.1.1.69:5098;transport=ws;lr>

" SIPml-api.js:1
09:19:26.392 "State machine: tsip_transac_ist_Completed_2_Confirmed_ACK" 
SIPml-api.js:1
09:19:26.396 "State machine: tsip_transac_ist_Confirmed_2_Terminated_timerI" 
SIPml-api.js:1
09:19:35.166 "The FSM is in the final state"

Original issue reported on code.google.com by jeansilv...@gmail.com on 10 Oct 2013 at 12:27

GoogleCodeExporter commented 9 years ago
Same problem!

Original comment by maksim.d...@gmail.com on 24 Mar 2014 at 5:26