search

nexcra / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

Mobicents HTML5 WebRTC Client app can't work exactly #188

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
I download Mobicents SIP Servlets 2.0.0.Final recently,and this environment can 
work perfectly.However,when I tried to access  
http://10.*.*.*:8080/websockets-sip-servlet/jain-sip/MobicentsWebClient.jsp and 
click "Register" button,it seems something goes wrong and failed.
I found that the client app(websockets-sip-servlet.war) had a problem when 
excuted those codes in websockets-sip-servlet\jain-sip\js\ApplicationSipTest.js 
by Tracking the source code:
//ApplicationSipTest.prototype.initPeerConnectionStateMachine=function()
//line 146
this.jsepPeerConnectionConstructor = webkitPeerConnection00;
this.sessionDescriptionConstructor = SessionDescription; 

I don't know what's the matter and I really want to know how to solve this 
problem.

Could you give me some suggestions ?

B.R. 

Lee 

What version of the product are you using? On what operating system?
Mobicents SIP Servlets 2.0.0.Final is running at Window XP
Test ApplicationSipTest(MobicentsWebClient.jsp) at Mac OS , Chrome 23.0.1271.101

Please provide any additional information below.

Original issue reported on code.google.com by heartlov...@yahoo.com.cn on 10 Jan 2013 at 8:17

Attachments:

GoogleCodeExporter commented 9 years ago 
See http://code.google.com/p/sipservlets/wiki/HTML5WebRTCVideoApplication and 
Google Chrome 23 requirements section. You need to update the application 
bundled by default with a new version located at  
https://oss.sonatype.org/content/repositories/snapshots/org/mobicents/servlet/si
p/examples/websockets-sip-servlet/2.1.0-SNAPSHOT/ to cope with non backward 
compatible changes to the WebRTC API that occurred between version 22 and 23 
from Google Chrome.

Also please provide the Javascript Console Log (Ctrl + Shift + J) if you're 
still running into an issue after updating the application.

Original comment by jean.deruelle on 10 Jan 2013 at 8:55