Home Page Articles User Guides News Letter  



Author Topic: MiCollab Client WebRTC problem  (Read 154 times)

Offline august

  • Full Member
  • ***
  • Posts: 185
  • Country: ca
  • Karma: +3/-0
    • View Profile
MiCollab Client WebRTC problem
« on: January 13, 2018, 03:59:38 PM »
MiCollab client 8.0 on cell phone and PC are working fine, but I have a problem to connect with WebRTC from the WAN.  It's working from the LAN but not from the WAN.  Config seem to be basic as per the doc. 

Is there something specific that need to be done?

I'm using all latest release of MiCollab, MBG and MiVoiceBusiness.


Offline Navarre

  • Jr. Member
  • **
  • Posts: 64
  • Karma: +0/-1
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #1 on: January 13, 2018, 06:07:43 PM »
Need more info.

2 server MiCollab setup, or one?

What domain names are you using? Split DNS config?

Offline august

  • Full Member
  • ***
  • Posts: 185
  • Country: ca
  • Karma: +3/-0
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #2 on: January 14, 2018, 07:05:42 AM »
MiCollab in the Lan with Mbg in the network Edge (LAN/WAN)

External ip adress of the MiCollab Client is the FQDN of the host name and domain name of the MiCollab which is proxy by the MBG to the MiCollab,

Offline PC77375

  • Jr. Member
  • **
  • Posts: 86
  • Country: us
  • Karma: +1/-0
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #3 on: January 15, 2018, 04:09:32 PM »
Are you accessing webrtc via the pub address from the LAN? I am not sure that the MBG it will respond to webrtc requests on the LAN interface. I am attempting now- it is crucial to have TCP port 5063 allowed from the WAN as well, as per the documentation. Once we allowed TCP 5063 from WAN we are able to authenticate; I cannot even get the login screen from the LAN requests.

Offline august

  • Full Member
  • ***
  • Posts: 185
  • Country: ca
  • Karma: +3/-0
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #4 on: January 15, 2018, 07:16:54 PM »
From the LAN, it talk directly to the MiCollab via the internal DNS.  From the WAN, it goes through the MGB, then remote proxy to MiCollab.

Offline Tech Electronics

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1927
  • Country: us
  • Karma: +48/-0
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #5 on: Yesterday at 09:21:51 AM »
August,

Have you tried testing with the Teleworker Network Analyzer to see if the firewall is setup properly?

Thanks,

TE

Offline Navarre

  • Jr. Member
  • **
  • Posts: 64
  • Karma: +0/-1
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #6 on: Yesterday at 09:57:14 AM »
MiCollab in the Lan with Mbg in the network Edge (LAN/WAN)

External ip adress of the MiCollab Client is the FQDN of the host name and domain name of the MiCollab which is proxy by the MBG to the MiCollab,

WebRTC on the MBG should be accessed via the dedicated FQDN that always points to the MBG WAN address. Split-DNS is not going to work as expected for services going through MBG. Just like all phones use an IP address pointed to the MBG WAN interface, if using an FQDN, it should resolve to the WAN as well.

Offline Navarre

  • Jr. Member
  • **
  • Posts: 64
  • Karma: +0/-1
    • View Profile
Re: MiCollab Client WebRTC problem
« Reply #7 on: Yesterday at 09:58:41 AM »
From the LAN, it talk directly to the MiCollab via the internal DNS.  From the WAN, it goes through the MGB, then remote proxy to MiCollab.

Which will not work, as the remote proxy proxies https, not webrtc. Different protocol.


 

Sitemap 1 2 3 4 5 6 7 8 9