What steps will reproduce the problem?
1. CentOS 6.4 run a webrtc2sip.
2. by sipml5 connect to a SIP server.
3. add in expert mode ws, a webrtc2sip address.
4. add in expert mode SIP outbound Proxy, a address server sip.
5. click in login.
What is the expected output? What do you see instead?
successful connection;
in elastix successful connection, and a central siemens does not connect.
What version of the product are you using? On what operating system?
webrtc2sip 2.6, centos 6.4, sipml5 release 203
Please provide server logs with DEBUG level equal to INFO
in txt elastix logs for webrtc2sip connect to elastix;
in siemens logs for webrtc2sip connect to central siemens;
My problem is with the central siemens !
Please provide browser logs
==session event = connecting SIPml-api.js?svn=179:1
==session event = sent_request SIPml-api.js?svn=179:1
State machine: tsip_dialog_register_Any_2_Terminated_X_transportError
SIPml-api.js?svn=179:1
=== REGISTER Dialog terminated === SIPml-api.js?svn=179:1
==session event = transport_error SIPml-api.js?svn=179:1
==session event = terminated SIPml-api.js?svn=179:1
The FSM is in the final state SIPml-api.js?svn=179:1
__tsip_transport_ws_onclose SIPml-api.js?svn=179:1
==stack event = stopped
Original issue reported on code.google.com by jeansilv...@gmail.com on 6 Nov 2013 at 2:02
Original issue reported on code.google.com by
jeansilv...@gmail.comon 6 Nov 2013 at 2:02Attachments: