LMS 4.1 - no phone registered in CUCM

Hi all,
the customer has CUCM in the inventory database of LMS 4.1. He has all accesses from LMS to CUCM. One phone 7961 is seen in the UT report. When the customer click on the CUCM in the inventory - there is no IP phone registered in the CUCM. What is wrong?:-( See the attachment.Thank you. Roman

Duplicate post #1.

Similar Messages

Recording Cisco phones registered on CUCM 8.6 with Verint Impact 360 not working.

Hello,
We're trying to record audio from Cisco IP phones registered to a CUCM 8.6 using SPAN and Verint Impact 360 with no success.
Verint provided us with some information to do the integration but we understand we don't need to do much on Cisco side besides configuring SPAN session to monitor the traffic we want.
We configured the following SPAN session:
monitor session 2 source interface Gi1/0/1 - 48
monitor session 2 source interface Gi2/0/1 - 47
monitor session 2 destination interface Gi2/0/48
Verint Impact 360 NIC is connected on port Gi2/0/48 but no RTP traffic is being detected.
Phones are connected to ports 1/0/5 and 1/0/6, this is a two 3750E switches stack. The configuration on the ports is:
interface GigabitEthernet1/0/5
switchport access vlan 186
switchport mode access
switchport voice vlan 176
switchport port-security maximum 2
switchport port-security
speed 100
duplex full
spanning-tree portfast
interface GigabitEthernet1/0/6
switchport access vlan 186
switchport mode access
switchport voice vlan 176
switchport port-security maximum 2
switchport port-security
speed 100
duplex full
spanning-tree portfast
Vlan 176 is the voice vlan we're using. Wireshark will see SCCP traffic but nothing else.
Does anybody have any tips or recommendations we could try?
Regards,
Daniel G.

is there any difference when you SPAN based on vlan?
monitor session 1 source vlan 176
monitor session 1 destination interface Gi2/0/48

Cisco 7821 IP Phone not registered in CUCM 9.1.2

Dear all,
We have CUCM 9.1.2.11900-12 and we have uploaded this device package: cmterm-devicepack9.1.2.12028-1.cop.sgn and reboot cluster
But the Cisco 7821 IP phone not registered in CUCM
can some one advise me?
Thanks and best regards,
Tan

Hi
Can you please share the output for show version active from CUCM.
Please check the following thread as well:
https://supportforums.cisco.com/discussion/12030206/adding-7800-phones-cucm-8691

Percentage of Phones won't register after CUCM 9.1.2 Sub and TFTP failover

Hoping this has happened to someone else and they can shed some light on the subject. I have a CUCM 9.1.2 cluster running, pub, 2 subs, and 2 tftp servers. At the moment it's a small deployment so I have all phones registered to sub 01 as primary and using tftp01 as the primary tftp server. In order to have some VMWare maintenance done I recently shut down the pub, primary sub and primary tftp server forcing the phones to use the other half of the cluster. Everything there worked as expected, phones failed over, etc. The problem occurred after the VMWare maintenance was done. At that point I brought up the Pub and the primary sub (maintenance wasn't yet completed on the host that contained the primary tftp server). After the primary sub was up and back online is where the problem started. Random phones (all 8945 SIP that are all running the same firmware version SIP8941_8945.9-3-2-12) would just not register. Some of them would show registered in CUCM, however they were non-functional as DNs weren't displayed, no dial tone, etc. Others would just not register all together. In order to get a phone to register I had to perform a factory reset on the physical phone, if I did that they came back with no problem. Later after the maintenance was completed on the host that contained the primary tftp server and I brought that back online, I still had issues with phones however just a power cycle was enough to get those phones registered. I opened a TAC case one this but it ended up at packet captures and at that point ever phone I reset would just register correctly so I could never get an example of a phone that wouldn't register.
I'm convinced it's certificate related and having to do with the trust list, which is why I believe the factory reset on the phone would allow the phone to correctly register. There just doesn't seem to be any clear indication as to why it would be certificate related. Names weren't changed on any of the UC servers, VMWare version was upgraded from 5.0 to 5.1 but I can't see how that would have caused certificate issues.
Any help would be grateful or if this has also happened to anyone I'd love to hear what you did to resolve this as for future maintenance windows I have to be confident that phones will be able to fail over between cluster nodes.
Thank you,
Alex

So the phone is unable to authenticate the ITL it is getting or the new config file. This could mean that the ITL is corrupt on one of the nodes or that TVS isn't working properly.
I would try running "show itl" on each node and check the bottom of the output to see if the ITL is verified successfully.
I would also make sure TVS is running on all nodes okay.
You also should be able to just delete the ITL from the affected phones rather than doing a full factory reset in case this comes up again.

Problems with IP Phones registration to CUCME on SG200-50P

Problems with IP Phones registration to CUCME on SG200-50P
System setup:
- Router Cisco 2811 with IOS 12.4(24)T5 Advanced IP Services, CUCME 7.1, DHCP Server
   with HWIC-4ESW
- Switches:
   - old - SLM224P
   - new - SG200-50P (SLM2048PT), OS v1.3.2.02
- IP Phones 7911 and 7931, OS v8.4.2
One VLAN (for desktops and IP Phones) and one IP subnet, no voice VLAN.
Network diagram:
C2811---HWIC-4ESW---SWITCH---IPPhones
Problem description:
1. In the old setup with SLM224P everything works fine.
   Connected phones almost immediately (1-2 sec. after power up) get ip address, configuration and registers to CUCME.
2. When switch is changed to new SG200-50G:
   - ip phones get their ip address and tftp configuration very slowly - about 10-20 seconds
   - ip phones cant register to CUCME at all. On the router with SCCP debugging turned on there is no sing of registration attempt
   - after reconnecting the old SLM224P situation backs to normal
Things that have been checked or tried without success:
- ports speed and duplex auto, correct detection - although not tested with manual settings
- CDP/LLDP on/off
- smartport mode auto and most static settings, also with disabled smartport
- power cycle / reset
- spanning tree and port security settings
- solutions from that post - https://supportforums.cisco.com/thread/2232161
None of the above methods worked.
The only action that allowed ip phones to register was changing smartport role to static IPPhone + Desktop.
After that when phone was disconnected and then reconnected the problem exists again - no registration (IP Phone status DECEASED in CUCME). Same with power cycle/reset.
Please advice.
Thanks in advance.

1 - You have created the voice vlan?
Nope, flat network, one ip subnet (10 hosts and 10 phones)
2 - Have you set a phone on an untagged access port for the voice vlan to see if it works?
Yep, phones are connected to untagged access ports of the one and only vlan
3 - Have you tried to set the auto voice vlan on the switch so it dynamically assigns the role for ip phone + desktop?
Not sure about auto voice vlan setting, although there was no triggers to AVV - no static voice vlan, no CDP/VSDP advertisements of voice vlan.
We've tested static and auto smartport roles (independently of auto voice vlan feature) with successful auto-detection.
The switch was pretty much in default out-of-the-box config (beside management parameters).
4 - When rebooting the switch, you did ensure to save the start up to running config?
Yes, running to startup
5 - Have you manually set spanning tree PORT FAST for the phone ports?
No, we haven't tested that. But portfast should be set automatically for the desktop and ip phone smartport roles.

Cisco 9971 Not Registering on CUCM 8.6

Hey,
Ive run into some trouble with a 9971 phone running on CUCM 8.6. The phone has been registered with the server before with its settings locked down so the access to the settings menu via the phone has been disabled. Around a few weeks later the CUCM server ran into some problems and had to be restored. Since then I am unable to get the phone to register back with the CUCM server. i get the rejected message in the phones tab. and the message Telephony service unavaliable on the phone itself.
I would factory reset the phone however as the settings were locked out from before i am unable to get into the menu and dont know another way to reset the phone, the method used with previous models (turn on hold # then press 1234...etc) does not work.
Any help would be appricated.
Regards,
Fraser

Hello Guys,
Anyone got to solve this problem? I have it on multiple 9951 phones, the factory reset process does not work as the phone apparently ignores that you are pressing the # button... As per the below link:
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/9971_9951_8961/9_0/english/admin_guide/P567_BK_CEC6105C_00_admin-guide-8961-9951-9971_chapter_01100.html#P567_TK_PB2EC99B_00
"When the light on the Mute button and handset light strip turns                 off and all other lights (Line button, Headset button, Speakerphone button and                 Select button) stay green, press                 123456789*0# in sequence.
When you press                     1, the lights on the line buttons turn red.                     The light on the Select button flashes when a button is pressed.
If you press the buttons out of sequence, the lights on the line                     button, headset button, speakerphone button, and Select button turn green. You                     need to start over and press                     123456789*0# in sequence again."
In my situation this never happen, the line buttons turn on green and after that they all turn off and the phones displays "Phone not registered"

How to move phones from one CUCM server to another?

How easy is it to migrate IP phones from one CUCM server to another?
The situation is this:
A vessel currently sitting in dry dock has 14 IP phones onboard which currently register with a CUCM server half way round the world (literally). As you can imagine there is quite a fair amount of delay for the signal processing, not to mention the connectivity being over a VSAT link. This being a temporary solution.
A CUCM server has been configured and installed on the vessel with all the relevant partitions, route patterns, trunks etc. The phones have also been added to the new server ready for migration. The only real thing that will be different when the phones are migrated is the Directory Number on each phone. Both CUCM servers are running software version 7.1.3
The phones currently pick up their local IP addresses via a local DHCP server which assigns 150 TFTP Server IP Address for the remote CUCM server. Is changing the the TFTP Server IP address to the local CUCM server enough to have the phones register with the local server.
This is not something I've tried before so would appreciate feedback or any comments that may indicate anything I missed along the way.
Thanks,
Ric

Hi Ricardo,
On the DHCP scope created for the voice vlan change the Option 150(TFTP Server IP address) to the new CUCM and remove/delete the remote CUCM IP address just to ensure that phones once after registering to the new CUCM will not fetch any config from the remote CUCM as the DN's of the phones are changed on the new CUCM please ensure this.
Apart from this i dont see any challenges as the firmware of the IP Phones will also remain same as CUCM version is same.
Hope that helps.
Regards
Najaf

Telepresence Conductor OBTP scheduled conferences and TC endpoints registered to CUCM

Dear community,
I am experiencing an interesting issue with TP Conductor based OBTP scheduled conferences and the behavior of TC software based endpoints natively registered to CUCM.
Software versions:
- TelePresence Conductor XC2.2.1
- CUCM 9.1.2
- TMS 14.3.2
- TC 7.0.2
Scheduled conferences are configured as OBTP and the Conductor is the preffered MCU in routing.
Behind the Conductor is a TelePresence Server 7010 appliance.
The Conductor Alias Pattern is 805%, priority 100, is immersive is not checked, the generated regular expression is (805[^@]*).*
Numeric ID Base for the alias is 10, Numeric ID Step is 1, Numeric ID Quantity is 9.
When scheduling conferences with TMS, TMS is generating numbers in this sequence:
80510, 80511, 80512, etc.
In CUCM, the Conductor IP alias for rendezvous is a destination of a SIP trunk, and there is a
route pattern 8051X
pointing to it.
The conference alias in Conductor is
(805[^@]*).*
With OBTP and CTS software based endpoints everything works well, these 8051X numbers are pushed to the MIDlets of the IP Phone or Touch 12" and the endpoints connect to the telepresence server scheduled conference.
With the TC software based endpoints, when selecting Join now on the conference reminder pop up screen with the remote control, the endpoint is dialing both:
80510@<CUCM-IP-Address> and
[email protected]
where example.com is the CUCM cluster domain.
The TC endpoint then somehow automatically connects with two sessions to the telepresence server which is extremely awkward.
When pushing the red disconnect button on the remote control, I have an option to disconnect all calls, or disconnect the first or second call to the same dialed alias 80510@<CUCM-IP-Address>. If I disconnect one of the calls everything is OK.
But then, how come the TC based endpoint initates two calls in parallel to the Conductor and then Telepresence Server ?
Has anybody experienced a similar issue ?
If I manually dial 80510 everything is fine, the endpoint dials
80510@<CUCM-IP-Address> and it connects successfully.

Hello Patrick,
Thank you very much for the input.
I also have the
log ctx SIPStack debug 9
from the endpoint when initiating the call. I can provide it to you privately.
Did not have enough time to get the traces from CUCM but will also check them.
If we are really hitting a bug, I will have to quickly do a workaround removing the Conductor from scheduling and trying directly with the TelePresence Server.
Mihail

7925G - Registering to CUCM issue

Hi all,
I am trying to configure a new 7925G phone. The phone uses a certificate for authetication to the AP.
Regarding the connection is ok as I can access the phone acress the Network.
When I create the phone into the CUCM, it seems that the phone is registered as per the status:
Registration Registered with Cisco Unified Communications Manager 10.x.x.x
The issue is that the registration step turns with no stop on the phone, and I found the following error in the log file:
2012-09-18 10:51:08:0460 HERMIT user.info modprobe: insmod -s -k eth0
2012-09-18 10:51:10:0270 HERMIT user.err SCCP: Skinny_get_tftpIp: Could NOT getGNetutilVarVal!
2012-09-18 10:51:10:0270 HERMIT user.err SCCP: Skinny_get_alt_tftpIp: Could NOT getGNetutilVarVal!
Any idea to fix it ?
Please find the log file in attachment.
Thanks
TS

Hi all,
I am trying to configure a new 7925G phone. The phone uses a certificate for authetication to the AP.
Regarding the connection is ok as I can access the phone acress the Network.
When I create the phone into the CUCM, it seems that the phone is registered as per the status:
Registration Registered with Cisco Unified Communications Manager 10.x.x.x
The issue is that the registration step turns with no stop on the phone, and I found the following error in the log file:
2012-09-18 10:51:08:0460 HERMIT user.info modprobe: insmod -s -k eth0
2012-09-18 10:51:10:0270 HERMIT user.err SCCP: Skinny_get_tftpIp: Could NOT getGNetutilVarVal!
2012-09-18 10:51:10:0270 HERMIT user.err SCCP: Skinny_get_alt_tftpIp: Could NOT getGNetutilVarVal!
Any idea to fix it ?
Please find the log file in attachment.
Thanks
TS

Can not add intercom button to phone template in cucm 8.5

For some reason I can not add the intercom button to phone template in cucm 8.5

Hi Matthew,
You may be seeing this (it's older info);
Intercom Support for Cisco Unified IP Phones
Cisco Unified IP Phone Model
SCCP
7931
7941
7941G-GE
7942
7945
7961
7961G-GE
7962
7965
7970
7971
7975
You can check your version;
Intercom Support for Cisco Unified IP Phones
The list of devices that support the Intercom feature varies per version and device pack.
Use the Cisco Unified Reporting application to generate a complete list of devices that support the Intercom feature for a particular release and device pack. To do so, follow these steps:
1. Start Cisco Unified Reporting by using any of the methods that follow.
The system uses the Cisco Tomcat service to authenticate users before allowing access to the web application. You can access the application
–by choosing Cisco Unified Reporting in the Navigation menu in Cisco Unified Communications Manager Administration and clicking Go.
–by choosing File > Cisco Unified Reporting at the Cisco Unified Real Time Monitoring Tool (RTMT) menu.
–by entering https://:8443/cucreports/ and then entering your authorized username and password.
2. Click System Reports in the navigation bar.
3. In the list of reports that displays in the left column, click the Unified CM Phone Feature List option.
4. Click the Generate a new report link to generate a new report, or click the Unified CM Phone Feature List link if a report already exists.
5. To generate a report of all devices that support Intercom, choose these settings from the respective drop-down list boxes and click the Submit button:
Product: All
Feature: Intercom
The List Features pane displays a list of all devices that support the Intercom feature. You can click on the Up and Down arrows next to the column headers (Product or Protocol) to sort the list.
Cheers!
Rob

I need to setup 7800 Series IP Phones in the CUCM 8.6.2 which by default are not support but will work after install the software. Anyone have document from Cisco as I remember I seen once before.

I need to setup 7800 Series IP Phones in the CUCM 8.6.2 which by default are not support but will work after install the software. Anyone have document from Cisco as I remember I seen once before.

Hi Ali,
I'll just add this reference to the good tips from my friend Manish (+5)
Support for the 7800 series in CUCM 8.6.2 was first added with this
Device Pack;
Cisco Unified Communications Manager
Device Package 8.6(2)(24104-1)Release Notes
Cisco Unified Communications Manager Device Package Release 8.6(2)
adds support for the Cisco IP Phones
7821, 7841, and 7861 running SIP firmware release 10.1(1).
The steps are in this doc
http://www.cisco.com/web/software/282074299/107528/cmterm-devicepack-8.6.2.24104-1_Readme.pdf
You might as well install the latest 8.6.2 Device pack
cmterm-devicepack8.6.2.24112-1.cop.sgn
Cheers!
Rob
"Seek it out and ye shall find "
- OneRepublic

HT2204 I changed my itunes email and password on my computer and now my phone says the password is wrong. How do I make my phone register the new changes?

I changed my itunes email and password on my computer and now my phone says the password is wrong. How do I make my phone register the new changes?

Try logging out of your account on the phone by tapping on your id in Settings > iTunes & App Store and then log back in with the updated id so as to 'refresh' the acccount on it

Unable to find phone type in CUCM for manual registration

Hi
We are using CUCM 8.0.3 , unable to find Phone type Cisco 8831 for manual registration. How can I add this phone type to CUCM ? Any help is appreciated.

Hi there,
+5 to my friends Mahmood & Nadeem here for their good ideas.
The problem here is that there is no Device Pack for CUCM 8.0.3 that supports the 8831 :( The ReadMe below is for the last/latest 8.0.3 device pack;
http://www.cisco.com/web/software/282074299/92918/cmterm-devicepack-8_0_3_24051-1_Readme.pdf
You would need to upgrade CUCM to a minimum of 8.5.1 and then install ;
Cisco Unified Communications Manager 8.5(1.17118-1) Device Package - Compatible UCM Version: 8.5
cmterm-devicepack8.5.1.17121-1.cop.sgn
Cheers!
Rob

New Subscriber add in CM Cluster but agents are not logging in on IP Phones registered to new subscriber

Hi,
I have added a new subscriber to existing cluster in Contact Center Environment. Agents are unable to login the CTI application using the phones registered on new subscriber. Call Manager version is 7.0.2 and ICM version is 7.5.8.
Please advise.
Regards,
Hammad.

Is the CTI Manager running on the new subscriber?
What do you see in the .ems file for the JTAPI gateway?
Are the phones still associated with the JTAPI user?
If you unassociate and reassociate a phone, does that work?
Regards,
Geoff

Download Phone Firmware form CUCM by TFTP

Hi all,
I have to download a Cisco Phone Firmware from CUCM.
Would you mind to help me how to do this ?
Thanks in advance
CHAM

You would need to know the exact names of all the phone firmware files. Once you have that, you can either turn on the "TFTP Client" service on Windows 7 or use your router to download the files, using TFTP.
Windows 7:
1.) Click the 'Start Menu' and then the 'Control Panel' button.
NOTE: If you cannot locate the 'Control Panel' button follow these instructions, otherwise skip to step 2.):
Right click on the 'Start Menu' button
Left click the 'Properties' option
Left click the 'Customize...' button at the top right corner of the window that appears
Locate the 'Control Panel' option (options are in alphabetical order)
Beneath the 'Control Panel' option, there are three radio buttons
'Display as a link' (When this option is selected, the 'Control Panel' button will open a new window when clicked)
'Display as a menu' (When this option is selected, hovering the cursor over the option causes a sub-menu to open)
'Don't display this item' (The 'Control Panel' option is not available in the 'Start Menu')
Choose the desired radio button and click 'OK'
Click 'OK' on the 'Taskbar and Start Menu Properties' window
2.) Double click on the 'Programs and Features' option
3.) Click on the 'Turn Windows Features On or Off' option
4.) A new window will appear. Place a check mark in the 'TFTP Client' option and click 'OK'
5.) A window will appear with a status bar. Once this windows disappears, the TFTP client has been activated.
tftp [-i] [Host] [{get | put}] [Source] [Destination]
Top of page
Parameters
-i : Specifies binary image transfer mode (also called octet mode). In binary image mode, the file is transferred in one-byte units. Use this mode when transferring binary files. If -i is omitted, the file is transferred in ASCII mode. This is the default transfer mode. This mode converts the end-of-line (EOL) characters to an appropriate format for the specified computer. Use this mode when transferring text files. If a file transfer is successful, the data transfer rate is displayed.
Host : Specifies the local or remote computer.
put : Transfers the file Destination on the local computer to the file Source on the remote computer. Because the TFTP protocol does not support user authentication, the user must be logged onto the remote computer, and the files must be writable on the remote computer.
get : Transfers the file Destination on the remote computer to the file Source on the local computer.
Source : Specifies the file to transfer.
Destination : Specifies where to transfer the file. If Destination is omitted, it is assumed to have the same name as Source.
/? : Displays help at the command prompt.
Router TFTP:
router#copy tftp://X.X.X.X/filename flash:
Regards,
Yosh

LMS 4.1 - no phone registered in CUCM

Similar Messages

Maybe you are looking for