Hello everyone,

For one of our customers we have a setup where Edge port 1 (WAN) is supporting the SIP trunk and port 2 is supporting the WebRTC phone trunk.
Port 1 is using a public IP whereas port 2 is using a private one.
Everything's working as expected when users are on site.
Now customer wants remote workers to use PureCloud as well, but doesn't want to have to use a VPN.
What would be the recommended setup here ?
Add the WebRTC on port 1 as well ? But in that case where do the on-site users get the webRTC ? port 1 or port 2 ?
Your comments are welcome.
Thanks
#SIP/VolP
#Telephony

------------------------------
Mayeul BRIVET
CoverApps
------------------------------

Hi Mayeul,

As far as I know, if you have WebRTC on both your internal and external ports the client is smart enough to know which one to use. If the user is on the LAN it'll use the internal one, keeping the audio local. If the user is at home it'll use the internet connection to the Edge. Just make sure you have any required ports opened on your firewall.

You can find all of the ports required here: Ports and services to configure on your company firewall - PureCloud Resource Center

Hope that helps,

------------------------------
Craig Stevenson
https://www.linkedin.com/in/craig-stevenson-contact-centre-cx-specialist-b5249996/

QPC UK
https://www.linkedin.com/company/qpc/
------------------------------

Original Message:
Sent: 10-25-2018 04:37
From: Mayeul BRIVET
Subject: WebRTC for remote worker

Hello everyone,

For one of our customers we have a setup where Edge port 1 (WAN) is supporting the SIP trunk and port 2 is supporting the WebRTC phone trunk.
Port 1 is using a public IP whereas port 2 is using a private one.
Everything's working as expected when users are on site.
Now customer wants remote workers to use PureCloud as well, but doesn't want to have to use a VPN.
What would be the recommended setup here ?
Add the WebRTC on port 1 as well ? But in that case where do the on-site users get the webRTC ? port 1 or port 2 ?
Your comments are welcome.
Thanks
#SIP/VolP
#Telephony

------------------------------
Mayeul BRIVET
CoverApps
------------------------------

Hi Mayeul,

We have the WebRTC trunk on our internet-facing side only. If the client is on the internal LAN, the internet-facing router knows to not send the traffic all the way to the internet and back. Traffic may need to go through the firewall, so make sure the required ports are open.
Having the WebRTC trunk on both sides may work as well, we haven't tested this.

Also, in a dual-NIC setup, we found that you want to leave the default gateway on the LAN side blank and use static routes instead. We had traffic routing issues if our edges had a default gateway on the WAN and also on the LAN side.

------------------------------
Sven Schiller
Kognitiv
------------------------------

Original Message:
Sent: 10-25-2018 04:37
From: Mayeul BRIVET
Subject: WebRTC for remote worker

Hello everyone,

For one of our customers we have a setup where Edge port 1 (WAN) is supporting the SIP trunk and port 2 is supporting the WebRTC phone trunk.
Port 1 is using a public IP whereas port 2 is using a private one.
Everything's working as expected when users are on site.
Now customer wants remote workers to use PureCloud as well, but doesn't want to have to use a VPN.
What would be the recommended setup here ?
Add the WebRTC on port 1 as well ? But in that case where do the on-site users get the webRTC ? port 1 or port 2 ?
Your comments are welcome.
Thanks
#SIP/VolP
#Telephony

------------------------------
Mayeul BRIVET
CoverApps
------------------------------

Thanks Craig & Sven for you inputs.
I think I will add the WebRTC trunk to port 1 (so it will be configured on both port 1 and port 2) and test to check if the RTP flow is using the expected network in both cases.
I'll post my results.
Thanks

------------------------------
Mayeul BRIVET
CoverApps
------------------------------

Original Message:
Sent: 10-26-2018 11:10
From: Sven Schiller
Subject: WebRTC for remote worker

Hi Mayeul,

We have the WebRTC trunk on our internet-facing side only. If the client is on the internal LAN, the internet-facing router knows to not send the traffic all the way to the internet and back. Traffic may need to go through the firewall, so make sure the required ports are open.
Having the WebRTC trunk on both sides may work as well, we haven't tested this.

Also, in a dual-NIC setup, we found that you want to leave the default gateway on the LAN side blank and use static routes instead. We had traffic routing issues if our edges had a default gateway on the WAN and also on the LAN side.

------------------------------
Sven Schiller
Kognitiv

Original Message:
Sent: 10-25-2018 04:37
From: Mayeul BRIVET
Subject: WebRTC for remote worker

Hello everyone,

For one of our customers we have a setup where Edge port 1 (WAN) is supporting the SIP trunk and port 2 is supporting the WebRTC phone trunk.
Port 1 is using a public IP whereas port 2 is using a private one.
Everything's working as expected when users are on site.
Now customer wants remote workers to use PureCloud as well, but doesn't want to have to use a VPN.
What would be the recommended setup here ?
Add the WebRTC on port 1 as well ? But in that case where do the on-site users get the webRTC ? port 1 or port 2 ?
Your comments are welcome.
Thanks
#SIP/VolP
#Telephony

------------------------------
Mayeul BRIVET
CoverApps
------------------------------

Enabling WebRTC using Genesys Cloud on PureConnect is not exactly straight-forward.  We at Avtex have come up with a number of FAQs and other resources for enabling your remote agents at https://avtex.com/articles/exploring-remote-solutions-to-combat-crisis-situations-the-contact-center.  Feel free to connect with us if you are using PureConnect and need assistance immediately.  

Robert

------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
robertwc@avtex.com
https://www.Avtex.com
https://RobertWC.Blogspot.com
------------------------------

Original Message:
Sent: 10-29-2018 14:13
From: Mayeul BRIVET
Subject: WebRTC for remote worker

Thanks Craig & Sven for you inputs.
I think I will add the WebRTC trunk to port 1 (so it will be configured on both port 1 and port 2) and test to check if the RTP flow is using the expected network in both cases.
I'll post my results.
Thanks

------------------------------
Mayeul BRIVET
CoverApps

Original Message:
Sent: 10-26-2018 11:10
From: Sven Schiller
Subject: WebRTC for remote worker

Hi Mayeul,

We have the WebRTC trunk on our internet-facing side only. If the client is on the internal LAN, the internet-facing router knows to not send the traffic all the way to the internet and back. Traffic may need to go through the firewall, so make sure the required ports are open.
Having the WebRTC trunk on both sides may work as well, we haven't tested this.

Also, in a dual-NIC setup, we found that you want to leave the default gateway on the LAN side blank and use static routes instead. We had traffic routing issues if our edges had a default gateway on the WAN and also on the LAN side.

------------------------------
Sven Schiller
Kognitiv

Original Message:
Sent: 10-25-2018 04:37
From: Mayeul BRIVET
Subject: WebRTC for remote worker

Hello everyone,

For one of our customers we have a setup where Edge port 1 (WAN) is supporting the SIP trunk and port 2 is supporting the WebRTC phone trunk.
Port 1 is using a public IP whereas port 2 is using a private one.
Everything's working as expected when users are on site.
Now customer wants remote workers to use PureCloud as well, but doesn't want to have to use a VPN.
What would be the recommended setup here ?
Add the WebRTC on port 1 as well ? But in that case where do the on-site users get the webRTC ? port 1 or port 2 ?
Your comments are welcome.
Thanks
#SIP/VolP
#Telephony

------------------------------
Mayeul BRIVET
CoverApps
------------------------------