Issues with Phone registration at remote site through ipsec tunnel
I'm having a bizarre phone registration issue that TAC is not able to understand , and i'm hoping someone may have ran into the same issue.
I have a Call Manager 7.0.1 server in location A, running in production, with 40 odd phones registered to it fine, everything is working properly.. We have Location B (Remote Site) which we want phones to register on our Call Manager in Location A. Between the sites we have an IPSEC Tunnel running over a netscreen ssg5 and a netscreen 25. I have a separate vlan for voice traffic set at the remote office on the dhcp server, and the phone gets an ip fine, points to the tftp of the call manager here, downloads its' locale and ofhter data,, get's an auto registration DN from our call manager, but then just unregisters itself, with error 'DNS UNKNOWN HOST' . I've confirmed all dns entries for the call managers are correct, and we've even changed the information on the call managers from name to ip ... still no go... i've attached a network diagram(fake ip's) and the console log of the phone and status messages.. hopefully someone can help me out here as i'm at a loss
The problem phone is a 7945, however i've tried with a 7965 at the same location and it has not worked either. IIf, however I install cisco IP communicator on a pc that's on that 3750 switch, it register's fine and functions properly.. (Tried switching the voice vlan of the phones themselves to vlan 1 when noticed the ip communicator worked, however it made no difference)(
The phone registration status on the call manager stays in 'Unknown' status.. And the phone itself has the incorrect time on the display and that's it.. no DN or anything else.
Re: Issues with Phone registration at remote site through ipsec
I do have a sniffer trace here but am reluctant to post on public forums as ip's are exposed... I will attempt to restart the tftp and call manager service but i'm pretty sure that I restarted the tftp service... If i restart the call manager service as part of a production day what will happen?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.