Hi there. My IP Communicator installs cannot get back to the TFTP server when connecting through the Forticlient VPN on their laptops. I install IP Communicator with their WiFi adapter's MAC as Device Name. But when Forticlient creates the VPN tunnel, it changes the MAC in IP Communicator to a generic Forticlient Virtual Ethernet Adapter MAC which is identical on all laptops.
Is it firewall ports that will fix this or am I missing something else?
Thanks for any help. First time posting.
IP Communicator version v 22.214.171.124 Call Manager 11.6
The IPC can use anything that resembles a valid MAC address, and whatever you configure as device name, is what will be sent, regardless of the actual MAC on the device. Hardcode the device name you wish to use and not let it use a NIC to generate the device name.
If that value matches IPC and your CUCM config, then start looking at connectivity issues on your VPN/firewall.
[ The link to the discussion will be published on October 22nd ]
This topic is a chance to clarify your questions about the implementation, best practices and support of Customer Voice Portal (CVP) and IP Interactive Voice Response (IP IVR) deploymen...
I have questions from the above guides:
A company currently has two different UC environments. One in the US and one in the UK. The US UC environment has (3) CUCM servers (Publisher and 2 subscribers), (2) IMP servers (P...
IP telephony (Internet Protocol telephony) is a term used to describe technologies that use a variety of protocols to exchange voice, fax, and other forms of information, traditionally carried over the Public Switched Telephone Netwo...
SymptomsCUCM Cluster with either:Dedicated TFTP nodes (TFTP1 & TFTP2, Primary & Secondary)Only certain nodes within cluster running TFTP services.Requirements to upgrade specific device phone models with new firmware load version.DiagnosisLimit lo...