CME phones cant reach CUE - Other phones can reach it
I have a 2821 router running IOS c2800nm-adventerprisek9-mz.151-4.M8.bin. The router has a CUE module:
NAME: "NM-SE on Slot 1", DESCR: "NM-SE" PID: NM-CUE , VID: NA , SN: FOC093220KH
NAME: "20GB IDE Disc Daughter Card on Slot 1 SubSlot 0", DESCR: "20GB IDE Disc Daughter Card"
It is running Unity Express 7.0.6.
I am studying for my CCIE Collaboration, so I have set the phones up as SIP. The phones register, and can call each other. I have configured the CUE module, and have the info all set up under the voice pool dn's and voice register global. I can call my CME from a phone on a different cluster. The calls do make it to voicemail, and I can leave a message. However, the actual phones on the CME can not reach the CUE module. They also dont get their MWI's.
Also, the phones are a 7941 and 7961. I suspect there is an incompatibility with the SIP integration and this CUE module. But the commands all take. So I could be wrong. Unfortunately all of my experience is with CUCM and Unity Connection. So I dont have a frame of reference.
Sorry for my ignorance. I'm not seeing a way to configure IP Comm as a sip phone. Under "voice register pool 3", under type, I do not see an IP Communicator option. Did you want me to use telephony-service and provision this as a SCCP phone for testing?
I havent gotten around to doing this yet, but I do beleive it is an incompatibility. My router has CME 8.6. I found the compatibility matrix, and this version of CUE isnt compatible. Unfortunately I have the highest revision of CUE that this hardware supports. Looks like I'm gonna have to make the $400 investment and buy an NME-CUE off ebay.
To add to what I was saying. I decided to try downgrading my CME to a compatible version. So I was in the process of downloading an IOS that has CME 7.0.1 built in. I went to download the CME support files, and I see that there is no SIP loads. I think I just need to face the fact that SIP is not support on this version of CUE.
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.