Nadeem is likely on to something here with the codec issue. Your outbound dial peer is 9, which defines the SIP codec but uses H323 methods for DTMF. Try changing this on both ends of the call to use SIP with rtp-nte, or H323 with h245-alpha.  dial-peer voice 9 voip translation-profile outgoing To-DhAMAR destination-pattern 011... session protocol sipv2 session target ipv4:10.100.11.20 voice-class codec 5 dtmf-relay h245-alphanumeric h245-signal no vad    If you're using SIP, use these debugs and the issue should be much easier to identify: debug ccsip messages debug ccsip error debug ccsip call debug voip ccapi   Run the debugs on both ends if you manage both devices. And make sure the CME/CUBE on the receiving end is set to allow the codecs at the inbound dial-peer and, if applicable, with the "allow-connections" commands in 'voice service voip' params.   If you're still hitting issues, paste your debugs. ... View more

I agree with your logic. It seems like it'd be a major function to be omitted, so I must be overlooking something. I had the carrier change the DNIS they deliver and CCB worked with no changes.   We're having other CCB issues right now. I'll re-test and touch base with you once those are resolved and I'm able to try again. ... View more

The service entry should include the service name and the params, for clarity. Like so: service cvp-survivability flash:survivability.tcl param ccb id:10.86.132.177;loc:doclab;trunks:1   And always link! http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/pcce/pcce_10_5_1/maintenance/guide/PCCE_BK_P256CEA3_00_packaged-cce-features/PCCE_BK_P256CEA3_00_packaged-cce-features_chapter_0100.html#CCVP_TK_C40AB8DB_00 ... View more

In their simplest form-- An Ingress Gateway is the enterprise border between the PSTN and your Enterprise Network. The Gateway terminates TDM signaling and transmits that via IP into your network. A CUBE terminates IP-to-IP calls. The most common application is as your "ingress gateway" for a SIP PSTN connection. But CUBE is so much more powerful than just that... ... View more

Monday Bump ... View more

This is an old fix but I believe it still works: http://www.fatturtle.com/2010/06/ip-voice-media-streaming-app-service-wont-start/   The process is basically: 1) Boot to an Ubuntu live CD to gain access to the file system 2) Copy the Intel binaries and change the name so they work with Athlon (AMD)   I believe the file structure is slightly different on UCCX, but you can still find what you're looking for.   Also, I believe this is fixed in 9.x and 10.x versions since they have support for specs-based UCS. So give those a try if there's no compelling reason to be using 8.x. ... View more

In hindsight, this may have been related to my lab server using AMD CPU instead of Intel. Which do you have? ... View more

Good pro tip on the Jabra relationship. I've pinged them again to clarify firmware version(s) supported or tested.   At what level of the phone logging am I able the debug this particular interaction/behavior to see if there are any alarms? No alarms are present on the phone's webpage logs, and the /FS/cache logs are useless here.   ... View more

I found that the issue was with users who had the Greeting Administrators role assigned; the Help Desk Admin users weren't able to change the passwords for those with this privilege. I opened a TAC case in which they confirmed that this is expected behavior (for both Help Desk Administrators AND the User Administrators role) and advised me to open an enhancement request, which I didn't do. From my take on it, the "Greeting Administrators" are seen as administrative accounts, whereas the help desk admin and user admin roles are intended to modify end users. If someone has a better theory, I'm open to it... I worked around it by adding a new account for one of the admins, and assigning it the System Administrator role; anyone who has this issue contacts him and he knows how to fix it. That's obviously a very scary solution, but it's what we had to do. ... View more

Got a resolution for us? I'm seeing the same thing now in 8.6.1.20000-109      ... View more

Resolved by removing my registry flub. The problem was that the VM I'm using was once part of my lab domain, and I had pushed the registry entries contained in the HKCU\Policies branch of the registry. Those policies take precedence over any defined in the HKCU\Software folder, and my voicemail settings were not even being referenced. ... View more

I bring up the VVM in case it conflicts with the VV (I assume VV is the right acronym for the IMAP one). Don't see how it would, just erring towards the side of TMI. I'm using the default COS for all users, and all services are running. Here is the latest registry, after many iterations: [HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Client Services Framework\AdminData] "TftpServer1"="1.1.1.9" "CcmcipServer1"="" "LDAP_Server_1"="1.1.2.2" "LDAP_UserLogonDomain"="cms.local" "CtiServer1"="" "AutomaticDeviceSelectionMode"="0" "LDAP_Server_2"="1.1.2.3" "VVM_SystemServer_0"="1.1.1.12" "VVM_Mailstore_ImapPort_0"="143" "VVM_Mailstore_ImapProtocol_0"="TCP" "VVM_Mailstore_InboxFolderName"="INBOX" "VVM_Mailstore_PollingInterval"="60" "VVM_Mailstore_Server_0"="1.1.1.12" "UseCUCMGroupForCti"="true" "CcmcipServerValidation"="0" ... View more