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 184.108.40.206 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.
Shortcut ActionCtrl+W Close Meeting CenterCtrl+T Transfer filesCtrl+Z Undo last actionCtrl+Y Redo last undone actionCtrl+Alt+F Display Font Formatting dialog boxCtrl+Alt+O Share presentation or documentCtrl+Alt+A Share applicationCtrl+Alt+D Share DesktopC...
Do you experience the following error on Cisco Unity Connection: Sometimes when you try to play or upload Audio Files for greetings in Unity Connection under the Call Handlers such as the System Call Handler Opening Greeting, in Standard/Closed/Holi...
When an Ad hoc conference is triggered by an endpoint to escalate a point-to-point call into a three-way call.HQ-CUCM sends an API request via HTTPS to the Cisco Meeting Server to set up a conference. You can see from the event log of CMS that API us...
You want in some scenarios different URIs or call-IDs and different access code are used by guest and host participants to join a meeting, and different rights or privileges, for example add or remove participants, mute audio or video, or when there...