Jump to content

WebRtc Not using referring uri or ip


Recommended Posts

We have managed to use the user web dialer to make calls and is working 100% within our LAN network.

When performing the same from externalyl the actual call is initiated but no voice or ringing. When we run wireshark on the desktop we can see the that there is STUN traffic trying to connect to the internal IP address of the PBX server which is obviously not reachable from external.

Is there any configuration that has to happen so the web dialer knows to use the referring uri or IP instead?

Link to comment
Share on other sites

Unfortunately when i tested the above i had my VPN connection on and only realised this now when trying to test this again. 

I still think we have a NAT problem but what i do not understand is this do not want to work internally now. When using chrome's WebRTC Internals it seems that it is now trying to use the external IP configured in the IP Routing List when we are coming from an internal IP and this information is coming from googles stun server (stun:stun.l.google.com:19302).  See attached image.

Any clarity on how this works would be appreciated.

2017-12-05 18_47_15-WebRTC Internals.png

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...