Detected the following WebRTC issue: Error 1004

[Andreas Mls]

I keep getting the same error from my server from firefox and chrome, where should i look first for the cause of this error;
I am not sure , but i think  it showed up after i changed the ip of the server
Thank you in advance

"Detected the following WebRTC issue: Error 1004: Failure on call (reason=SIP Failure Code). Do you want to try Flash instead?"

[Chad Pilkey]

The actual cause will be contained in the browser log (F12). The SIP code that is being returned back will tell you more about where the call is breaking down.

[Andreas Mls]

i dont know if it helps, pressed f12 and then at the Console , part of the message is

Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.inviteclientcontext | closing INVITE session avc568rm6mkn081pj6k47k2b83dvbc
sip.js?v=267:2636 Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.invitecontext.mediahandler | closing PeerConnection
sip.js?v=267:2636 Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.inviteclientcontext | emitting event failed
bbb_webrtc_bridge_sip.js?v=267:318 call failed with cause: SIP Failure Code
bbb_webrtc_bridge_sip.js?v=267:87 Stopping webrtc audio test
bbb_webrtc_bridge_sip.js?v=267:409 Hanging up current session
sip.js?v=267:2636 Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.inviteclientcontext | Error: Attempted to send BYE in a terminated session.module.exports.LoggerFactory.print @ sip.js?v=267:2636module.exports.Object.keys.forEach.LoggerFactory.(anonymous function) @ sip.js?v=267:2653module.exports.Object.keys.forEach.Logger.(anonymous function) @ sip.js?v=267:2647module.exports.Session.bye @ sip.js?v=267:4583webrtc_hangup @ bbb_webrtc_bridge_sip.js?v=267:413stopWebRTCAudioTest @ bbb_webrtc_bridge_sip.js?v=267:89(anonymous function) @ VM428:1BBB.webRTCCallFailed @ bbb_api_bridge.js?v=267:447webRTCCallback @ bbb_webrtc_bridge_sip.js?v=267:11(anonymous function) @ bbb_webrtc_bridge_sip.js?v=267:322(anonymous function) @ sip.js?v=267:1072EventEmitter.emit @ sip.js?v=267:1070module.exports.Session.failed @ sip.js?v=267:5292module.exports.InviteClientContext.receiveInviteResponse @ sip.js?v=267:6418RequestSender.receiveResponse @ sip.js?v=267:3495InviteClientTransaction.receiveResponse @ sip.js?v=267:7314Transport.onMessage @ sip.js?v=267:7967Transport.connect.ws.onmessage @ sip.js?v=267:7840
sip.js?v=267:2636 Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.ua | user requested closure...
sip.js?v=267:2636 Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.ua | closing registerContext
sip.js?v=267:2636 Tue Nov 10 2015 00:49:23 GMT+0200 (Χειμερινή ώρα GTB) | sip.registercontext | already unregistered

[Chad Pilkey]

That part is SIP.js responding to the fail message. The message that caused the failure should be above that section I think.

Also, can you paste the full output of "bbb-conf --check".

[Andreas Mls]

bbb-check gives no errors
Full browser log http://pastebin.com/9w3x8uHs

[Chad Pilkey]

bbb-conf --check will tell background information about your server which helps to rule out issues.

The problem message coming from the server is "502 Bad Gateway Destination Out Of Order" which usually means a type somewhere in the FreeSWITCH configuration files. You mentioned that you changed the IP on your server, did you change the IP manually or did you use "bbb-conf --setip"? Have to made any other modifications to the server? Have you followed the either the HTTPS or "Audio not working" steps?

The only other time someone posted here with a 502 Bad Gateway the cause was a misplaced "s" in one of the configuration files when the person was trying to set up HTTPS.

Chad

[Andreas Mls]

First of all i really thank you for your answers
I did bbb-conf --setip
and i got an error from freeswith
i manualy changed the file bigbluebutton.properties as the
freeswitch.ip and the bbb.sip.app.ip had the old ip

[Andreas Mls]

ups , wrong file, it was the bigbluebutton-sip.properties that i edit

[Chad Pilkey]

The various .properties files shouldn't be edited manually unless you either really know what you are doing, or you are following instructions in our documentation.

I'm still interested in seeing the output of bbb-conf --check as well.

[Andreas Mls]

Here is the output

Here is the output

BigBlueButton Server 0.9.1 (390)

                    Kernel version: 3.19.0-31-generic

                      Distribution: Ubuntu 14.04.3 LTS (64-bit)

                            Memory: 32099 MB

 

/var/www/bigbluebutton/client/conf/config.xml (bbb-client)

                Port test (tunnel): xxx.xxx.xxx.xxx

                              Red5: xxx.xxx.xxx.xxx

              useWebrtcIfAvailable: true

 

/opt/freeswitch/conf/sip_profiles/external.xml (FreeSWITCH)

                    websocket port: 5066

                    WebRTC enabled: true

 

/etc/nginx/sites-available/bigbluebutton (nginx)

                       server name: xxx.xxx.xxx.xxx

                              port: 80

                    bbb-client dir: /var/www/bigbluebutton

 

/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)

                      bbb-web host: xxx.xxx.xxx.xxx

 

/var/www/bigbluebutton/check/conf/config.xml (client check)

                      client check: xxx.xxx.xxx.xxx

 

/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)

                  voice conference: FreeSWITCH

                     capture video: true

                   capture desktop: true

 

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)

                     playback host: xxx.xxx.xxx.xxx

 

 

** Potential problems described below **

# Warning: The client self check is installed and accessible from:

#

#    http://xxx.xxx.xxx.xxx/check

[Chad Pilkey]

I'm not really sure where the issue is, other than to say that there is a problem in one of the many FreeSWITCH configuration files. It's hard to say what to change or where to look. The easiest solution would be to start over with a fresh Ubuntu installation and don't fiddle with files manually and apply your changes one-by-one after checking to make sure the server still works each time.