Showing results for 
Search instead for 
Did you mean: 

IP Communicator and Forticlient VPN


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
Call Manager 11.6


2 Replies 2

Jaime Valencia
Hall of Fame Cisco Employee Hall of Fame Cisco Employee
Hall of Fame Cisco Employee

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.



if this helps, please rate

Cisco Employee
Cisco Employee



Just like Jaime said, the actual MAC address doesn't really matter. There is definitely another problem.


Just be informed that CIPC (and Jabber for that matter) are not supported on 3rd party VPNs You also may consider moving away from CIPC since it approaching the End-Of-Life (30-SEP-2021) 


Since this is probably not an option for you, then you can take packet captures from the VPN appliance and/or CUCM to see if what's happening when the phone requests the configuration file. You can also download TFTP logs from CUCM and search by the device name / MAC you've configured in CUCM. This forum post should be helpful

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers