Configuring a conference bridge in Cisco CME

I recently ran into an issue configuring a conference bridge for a client. What makes this particular problem worth sharing is that I found the documentation provided by Cisco on this issue to be a little confusing and a little unhelpful. The initial document I used to try to configure this issue can be found here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeconf.html#wp1021179. In particular what confused me were the differences in step 5 of “Configuring SCCP for Cisco Unified CME” and step 3 of “Associating Cisco Unified CME with a DSP Farm Profile.”  I have included the full configuration example of both of these sections below. As you can see, if you follow the configuration examples in this document, you end up with two separate groups, one which contains the binding of an interface and another which associates your configured CME router and the DSP farm profile with a group.  The problem with this is that all of these commands should take place in  the same group.  There is also nothing in the “Purpose” section to indicate that these groups should in fact be one and the same.  Additionally, step 5 in “Configuring SCCP for Cisco Unified CME” turns out to not be needed at all but this is probably due to the document being outdated. Additionally, most configuration documents I’ve read on Cisco’s site include at least some troubleshooting information.  This document lists commands you can issue to see if things are working but leaves many out and doesn’t include any advice on how to fix issues. Luckily, while researching this online in order to get the conference bridge working right I did find a much...

Using Cisco 8945 IP phones with CME

We just finished testing the Cisco 8945 IP phone with CME using SCCP and it worked great.  Point to point video works flawlessly.  A few things to note in setting up these phones: Make sure you add the “video” command under telephony-service as well as under the ephone. We found that we could not call out our PRI with these phones once video was enabled.  We had to add  “bearer-cap Speech” under the voice-port to force speech only out the PRI.  (The phones were trying to advertise video capabilities out the PRI and our service provider didn’t like that!) Although the phones are capable of sending and receiving 640×480 (VGA) video we were noticing that the max we were getting was 325×288 (CIF) resolution.  We found that VT Advantage (which is what CME uses) maxes out at CIF resolution per this document. Bluetooth works great, setup was very easy! You can’t change the background on this phone — dissapointing! Here are the relevant parts of the config: ! ! voice-port 0/0/0:23 bearer-cap Speech ! ! telephony-service video ! ! ephone  18 device-security-mode none description 8945_A video mac-address 0000.AAAA.BBBB max-calls-per-button 3 busy-trigger-per-button 2 type 8945 button  1:1 ! ! ephone  19 device-security-mode none description 8945_B video mac-address 0000.1111.2222 max-calls-per-button 3 busy-trigger-per-button 2 type 8945 button  1:2 !...

CME 8.8 upgrade and Exchange UM voicemail problem

We recently upgraded to the new Cisco CallManager Express (CME) version 8.8 so that we could try out the new 8945 phones for point to point video.  Immediately after the upgrade Exchange no longer answered calls to voicemail or auto-attendants and instead gave us a busy signal.  In reviewing the Exchange logs I found the following error: Event ID: 1021 Source: MSExchange Unified Messaging Task Category: UMCore The Unified Messaging server rejected an incoming call with the ID “2ACCC6EF-E2F911E0-9286A0ED-1857E3E@10.1.1.22“. Reason: “The Unified Messaging server received “INVITE” request with an invalid SIP header “USER-AGENT” with value “”.” That seemed strange that the USER-AGENT field would be “. so I created a sip-profile and modified the header to be “CME” instead. router(config)# router(config)#voice class sip-profiles 1 router(config)#request INVITE sip-header User-Agent modify “.” “CME” then I applied the profile under “voice service voip” router(config)#voice service voip router(config)#sip router(config)#sip-profiles 1 Now the calls go through.  Here is the entire SIP config: voice service voip cti csta mode basic no cti shutdown allow-connections sip to sip no supplementary-service sip moved-temporarily no supplementary-service sip refer fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none sip session transport tcp header-passing registrar server expires max 300 min 60 sip-profiles 1 ! voice class sip-profiles 1 request INVITE sip-header User-Agent modify “.” “CME”    ...