IP Communicator

Unanswered Question
andrewjuliz Wed, 10/24/2007 - 23:33

You should try to ping your CallManager from your home PC to check routing issues.

Next, you should check IP Communicator configuration (CallManager IP address).

If both are ok, the next step is checking the registration of your IP Communicator (based on MAC Address of your Home PC) on CallManager.

Hope this helps.



Dennis Fogler Thu, 10/25/2007 - 05:27

What version of Windows, IP Communicator & VPN client are you running? Also if you are using WIndows XP check the firewall settings.

Two different workstations have been tried.

One running XP (firewall disabled) one running VISTA Ultimate (firewall disabled).

IP Communicator version: 2.1

CISCO VPN version:

IP Communicator is pointing to the correct CM server, it just can not talk to it (I think).

Once I connect to the VPN (on either the laptop or the desktop) I CAN ping the CM Server. The IP Communitcator is set to use the VPN Adapter MAC, which has been configured in the CM.

I think what might be happening it our VPN connection blocking the communication some how. I can ping the CM server (the TFTP server) but I can not remote into that server from the VPN, I can remote in when in the office on the network.

Does this sound like a Cisco VPN issue?


This Discussion