Ok.. we were doing the CME-CUE integration at Class last week and although straight forward after the below config the MWI did not light on and off when a message was left...
CME CONFIG:
ephone-dn 18
number 8001.... no-reg
mwi on
ephone-dn 19
number 8000.... no-reg
mwi off
interface fastethernet 0/0.102
ip address 192.168.1.254 255.255.255.0
interface Service-Engine 1/0
ip unnumbered fastethernet0/0.102
service-module ip address 192.168.1.253 255.255.255.0
service-module ip default-gateway 192.168.1.254
ip route 192.168.1.253 255.255.255.255 Service-Engine 1/0
service-module service-engine 1/0 session
CUE#
" The cue module was taken offline and restored to factory default and then the we performed the system initialization from the CUE GUI, was able to see the MWI numbers and everything was right.. saved config to cue finally and re-logged in to CUE"
Now when press the message button on the phone, the user is able to reach his mailbox on cue and when we dial the 8001xxxx (where xxxx is a registered extention) the mwi on the phone lights up and when 8000xxxx is dialed the mwi light turns off, so basically everything seems to work fine except that when a message is left to a users mailbox the mwi does not light up....
after looking at the "debug ccsip messages"
it turned out that the mwi was actually hitting the incoming dial-peer configured
dial-peer voice 1 voip
incoming called-number .
After removing the incoming dial-peer with the "incoming called-number ." ... the mwi started to work fine....
Things to keep in mind when configuring CUE to integrate with CME.
1) Make sure you are able to access the CME first from GUI
2) Telephony-Service should have the "dn-webedit" and "time-webedit"
3) ip http-server should be in the config
4) The CUE Module should have the right license "show software licenses", if integrating with cme then the license should be cme and if integrating with cucm then the license should be cucm...
5) the username and password configured on cue should be part of the Administrators group (by default it is...)
CME CONFIG:
ephone-dn 18
number 8001.... no-reg
mwi on
ephone-dn 19
number 8000.... no-reg
mwi off
interface fastethernet 0/0.102
ip address 192.168.1.254 255.255.255.0
interface Service-Engine 1/0
ip unnumbered fastethernet0/0.102
service-module ip address 192.168.1.253 255.255.255.0
service-module ip default-gateway 192.168.1.254
ip route 192.168.1.253 255.255.255.255 Service-Engine 1/0
service-module service-engine 1/0 session
CUE#
" The cue module was taken offline and restored to factory default and then the we performed the system initialization from the CUE GUI, was able to see the MWI numbers and everything was right.. saved config to cue finally and re-logged in to CUE"
Now when press the message button on the phone, the user is able to reach his mailbox on cue and when we dial the 8001xxxx (where xxxx is a registered extention) the mwi on the phone lights up and when 8000xxxx is dialed the mwi light turns off, so basically everything seems to work fine except that when a message is left to a users mailbox the mwi does not light up....
after looking at the "debug ccsip messages"
it turned out that the mwi was actually hitting the incoming dial-peer configured
dial-peer voice 1 voip
incoming called-number .
After removing the incoming dial-peer with the "incoming called-number ." ... the mwi started to work fine....
Things to keep in mind when configuring CUE to integrate with CME.
1) Make sure you are able to access the CME first from GUI
2) Telephony-Service should have the "dn-webedit" and "time-webedit"
3) ip http-server should be in the config
4) The CUE Module should have the right license "show software licenses", if integrating with cme then the license should be cme and if integrating with cucm then the license should be cucm...
5) the username and password configured on cue should be part of the Administrators group (by default it is...)
No comments:
Post a Comment