We have recently aquired the IP communicator using 126.96.36.199
I have setup on my laptop no problem but tried to setup on my managers laptop. Have done exactly the same as for myself but his version does not seem to recognise the ext number. I have deleted and reinstalled a couple of times with no luck.
I currently have a Cisco 7912 phone while he has a cisco 7940 ( not sure if that has any effect)
I have alos setup OK on another Cisco 7912
The communicator starts ok but the screen is blank with no ext number showing and no softkey options. We are both running windows XP
Basically whatever 'other' physical phones you have isn't really important.
What is important is that:
1) You configure each instance of CIPC in CallManager as you would a physical phone - so add an 'IP Communicator' and assign it the extension it should have.
2) When you install the software on a PC, it automatically grabs the MAC address of the laptop to use as a Device Name. This can be a problem, as the MAC address might change, or might not be the one you expect it to get. The best way to do this (in my opinion at least) is to use a different ID for the CIPC - so you might pick:
- Hostname of the PC it is installed on
- Username of the PC's owner
In CallManager, you would then put 'SEPhostname' or 'SEPusername' in the Device Name field when you configure the CIPC device.
In the CIPC application, go in to Preferences, then the 'Network' tab, and select 'Use this device name' - type in the SEPhostname or SEPusername you configured in CallManager. The CIPC will then register using those details when you hit OK.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Hi, we are having the same issues on our laptops too since upgrading to Windows 7..
If we stick with the default ID ( ie. the MAC address of the laptop ), the softphone will cycle for a while and then come back with Registration Rejected on Call Manager and the softphone.
I have also tried removing the existing database entry for the device ID from call manager altogether to force the softphone to auto register again.. The Device ID correctly reappears on Call Manager, however the registration is again rejected..
Yesterday, I tried out your suggestion below before regarding manually creating a new device ID and then pointing the softphone to the custom ID within perferences..
This works sucessfully on a laptop running Win XP.. proving that the profile and tftp settings are correct
However, on the Win 7 computer, the softphone cycles for ages and does not pick up the profile or get as far as rejecting the registration..
I have seen serveral suggestions on the web regarding turning Windows firewall off, which we have done... but this has not fixed it..
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.