wondering whether  FQDN is configurable in webrtc client public address

Dear Rober,

my banking customer has 3 service providers for internet service.

to avoid client traffice got affected by inter service provider lines.

they has three f5 for each service provider.

even banking customer exopose same FQDN name to client, but, each  service provider will route client to different f5 with providers own DNS resolution.

so, customer is asking us whehter REAS can expose REMB public address as FQDN name to clients.

and then, clients on each providers network could be route to each F5 in banking data center and then F5 will NAT the address to REMB internal address---192.168.9.242

i pasted configuration below to give us a picture.

i guest this may working.

please let me know your comment.

yours

Alan

wepeng

wli6

Hi Alan,

REM hasn't been widely tested with FQDN and the recommended value for the public address is an IP address.

However traffic from the 3 different F5s can be differentiated by creating 3 lists of "RTP Public/Local Ports" with different Source Address CIDRs.

The CIDR would generally need to target the internal address of the RP sending traffic to the REAS (not the MB). If one F5 (for each ISP) is forwarding all traffic to both the REAS and MB then the CIDR should target it.

Regards,

Rob

hi Rob,

thanks for your email as always!

i think your recommended methods is working in below scenario, right?

After we created 3 lists of "RTP Public/Local Ports" tables in REAS.

each f5 with a dedicated internal IP to isolate different SP traffice by different Source Address CIDRs configuration in REAS, so, REAS will reture desired SP public address to clients, and then f5 will NAT UDP traffic to REMB.

that is really a great idea!!

please let me know whether my understanding is correct or nor.

Yours

Alan

Hi Alan,

Sorry for delay in answering, I've been away.

Yes your understanding is correct.

Regards,

Rob