It follows the same as the traditional Expressway deployment with a Single NIC. Namely, as far as I am aware (and I am no pro) that means a Public IP or NAT reflection, a public FQDN, and calls will invoke the B2BUA which results in some additional resource utilization.
I use MRA with a single NIC, no reflection, public IP/FQDN, and it works just fine, but, your environment may vary.
Thanks for your reply. We have successfully configured this setup using NAT reflection. However, we have experiencing issue on login as we have different two domains (for example): External DNS - domain.ph Internal DNS - domain.com, domain.ph
From Core, the services: _cisco-uds._tcp.domain.com and _cisco-uds._tcp.domain.ph / _cuplogin._tcp.domain.com and _cuplogin._tcp.domain.ph was already resolvable to cucm.domain.com.
We have also uploaded jabber-config.xml on all CUCM TFTP. Try to login first internal firstname.lastname@example.org and it was successful. Then connect to external/public, can login but phone services not available. We have also try to sign out first before connect via public but same issue.