Tag Archive - CUCME

CUCME Presence

Fact: Every CUCME deployment should contain presence information.

When you realize how easy it is to configure presence within CUCME, it’s amazing that more engineers do not deploy this useful feature.  CUCME Presence provides line state information to other users using the SIP methods of SUBSCRIBE and NOTIFY.

There are two ways that presence information is made visible in a CUCME deployment: (1) BLF speed dials configured on phones and (2) phone directories accessed through the phone menu. Continue Reading…

Guru Guide: IIUC (CUCM Express)

The year of 2009 was my Cisco certification marathon. I took nine Cisco Pearson VUE tests in eleven months and received 4.5 certifications: CCENT, CCNA, CCNA Voice, CCVP, CCIE (written). I gave up my life and threw myself into Cisco Press and SRNDs. Truth be told, I loved every minute of it! Well, let me go back and clarify. I loved every minute of it except the sleep deprivation, poor diet, mental fatigue, and bodily stress. Simply put: my brain said, “Thank you!” while my body said, “You jerk!

During the journey, I learned a lot about myself. Perhaps the greatest lesson I learned was how I best receive and retain information. For me, blogging and creating my own personal study guides were the ticket.

Here’s is one study guide that may be of use to voice folks. It’s for the CCNA Voice exam that will be replaced in February, but it’s an excellent quick reference resource for CUCME. Enjoy! Continue Reading…

Rapidly Configuring CoR in CUCME

How you can configure CoR in CUCME in four minutes or less.

  1. Open the CUCM SRND and search for “dial-peer cor custom”.
  2. Copy the entire CoR example and paste into Notepad.
  3. Remove the unneeded text commentary that is in between the commands.
  4. Change “port 1/0:23″ with the correct POTS port number.
  5. Change “prefix-digits” to “prefix” (depending on your IOS version).

CUCME SIP Phone Re-Registers Intermittently

Problem: After configuring SIP-based CUCME, I noticed that my SIP phones would intermittently re-register.  The phone would also be non-responsive when I tried to initiate outbound calls. Ironically, though, was that the SIP phones could receive calls.  During the troubleshooting phase, I tried everything I could think of.  I even made sure that the firmware on the SIP phone was the version explicitly stated in the CUCME Admin Guide.

Debugs: I ran the following debugs to gather logs: debug voice register events, debug voice register errors, debug ccsip message, debug ccsip info.  Based on the debugs, this is what I was seeing:

Resolution: Based on the logs, the phone was never receiving the 401 challenge to the register refresh request.  To correct this issue, I bound the SIP signaling to the interface used as the source address under voice register global.  In my case, this was Vlan400:

Conf t
Voice service voip
Sip
Bind control source-interface VLAN400
Bind media source-interface VLAN400
End

The phone has been stable and the registration refreshes successfully.

It seemed the phone was not receiving the 401 challenge to the register refresh.  Due to this the phone was resending the register without authentication information and the CUCME would again reject the request.  This process would repeat until registration timed out and the CUCME closed the TCP connection.  At this point the phone would reset and would successfully register.

Sample CUCME SIP Configuration

This post attempts to lay out the basic commands needed for a functional CUCME SIP system.  I pulled this configuration off a Cisco TechNote and added my comments inline in red.  For those of you following my blog and also studying for the lab, do you see any commands that may be missing?

Continue Reading…

Page 1 of 212»