Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
332
Views
3
Helpful
4
Replies

IP Communicator

navingolani
Level 1
Level 1

‎03-26-2008 11:31 PM - edited ‎03-15-2019 09:40 AM

Hi,

I am connecting to CCM4.1 thru VPN & have IPcommunicator installed on my machine.In IPC,under the preference option for TFTP server i have given CCM IP,i have done the phone config in CCM,but its still showing the error as "Phone not registered".

I checked the connectivity to CCM thru my machine, ping response is fine.

Can any one let me know what could be the possible reason for this error.

Labels:
0 Helpful
4 Replies 4

Adam Thompson
Level 4
Level 4

‎03-27-2008 08:08 AM

I am assuming that the CCM IP that you configured is running the TFTP service.

Is there a firewall between the CCM server and the general network? If so, TFTP/voice traffic from your VPN network may not be allowed through the firewall.

If you are connected normally at work (not through VPN) does your communicator register?

0 Helpful

navingolani
Level 1
Level 1
In response to Adam Thompson

‎03-28-2008 12:03 AM

Hi Adam,

Yes we do have a firewall in between CCM server & local network.I have asked the local team to open the TCP port 2000.Will let you know once done.

0 Helpful

jbarcena
Level 9
Level 9

‎03-27-2008 11:25 AM

On the IPC Preferences are you choosing the PC adaptor or the VPN? Try using the VPN, I also recommend you to take a sniffer trace to see the packet exchange

navingolani
Level 1
Level 1
In response to jbarcena

‎03-27-2008 11:59 PM

hi jbarcena,

I have used VPN Adaptor for under the IPC Preferences.

Regards,

Navin

0 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:

Customers Also Viewed These Support Documents