04-29-2015 02:38 AM - edited 03-18-2019 04:24 AM
04-29-2015 05:22 AM
I am using dual interfaces on EXPWYE and E's FQDN isn't reachable by C
04-29-2015 01:06 PM
You can try the following.
1 First try and confirm network reachability to the Lan facing ethernet interface of the Exp-e. You can use the Ping, traceroute tools also try pinging the hostname of the expressway-e(This should help you check you have the correct DNS records) it should resolve to the internal IP.
2 You should look in the 1st DMZ , the Cisco Expressway guide provides ports that are required to be open or mapped(http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Cisco-Expressway-Basic-Configuration-Deployment-Guide-X8-1.pdf). Kindly make sure yours are.
3 If the above are fine you should make sure you have configured the Traversal Zone on the EXP-E to also use the same port as you did on the EXP-C.
4 You can look at status - logs - network logs to see network data.
04-30-2015 12:56 AM
I have solved the issue and it was due to inappropriate Cert template
10-12-2017 05:18 AM
This is mean that i can`t create zone before creating cert ?
10-12-2017 09:05 AM
10-15-2017 12:09 AM
Thanks friend , I have other question , How can expressway E know FQDN of expressway C although i put external domain on expressway E , how connectivity through internal dns occur ?
10-15-2017 09:04 PM
Expressway E knows about the FQDN of the Expressway C when u enter the same while creating Traversal/UC Traversal Zone on the same.
Expressway E doesn't initiate any connection however accepts the connection from Expressway C based on the port number configured on the UC Traversal and Traversal Zone , thus it learns about the IP address of Expressway C.
10-16-2017 12:10 AM
Big thanks :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide