CUCME-CUE MWI configuration: Two ways to do it

MWI (Message Waiting Indicator)  is a headache for someone for the lack of good concept and lack of knowing the configurations. There are two days to configure MWI with CUE:

1. Traditional H.323 DN concept:

It’s simple, you have to configure two h.323 DN and assign them for MWI like below:

!
ephone-dn 1
number 1001…. no-reg primary
mwi on
!
ephone-dn 2
number 1002…. no-reg primary
mwi off
!

Don’t forget to add those additional dots at the tail of the numbers, number of dots would be just equal to site numbering plan.

2. SIP Method:

That’s new to me I’m loving this method:

!
sip-ua
mwi-server ipv4:10.10.10.15 unsolicited
!
telephony-service
mwi relay
mwi reg-e164
!
ephone-dn-template  1
mwi sip
!
!
ephone-dn  1  octo-line
ephone-dn-template 1
!

At CUE: Never forget to work on CUE and add the MWI DNs, it’s unique for both of the cases just discussed:

!
ccn application ciscomwiapplication aa
parameter strMWI_OFF_DN 1002
parameter strMWI_ON_DN 1001
exit
!

Happy Labbing!!!

Advertisements

MWI at CUE SRST: so doable!

I know it’s scaring for someones, even it was such scaring for me once 😀 but believe me it’s so simple! I’m talking about the case when your remote site CUE is registered with central site CUCM and you want to make the MWI working while in SRST.

You have to configure the SIP-UA on fallback router also you have to relay the sip MWI through the fallback process, I am using CME SRST rather than using ‘call-manager-fallback’ for some specific reasons, so I didn’t test it with ‘call-manager-fallback’ options. You can test with ‘call-manager-fallback’  i hope it will work as well. Okey let’s look at the configurations rather than continuing discussions 😛

!
sip-ua
mwi-server ipv4:10.10.10.11 unsolicited

!
telephony-service
srst mode auto-provision none
srst dn template 1
max-ephones x
max-dn x
ip source-address 10.10.10.10 port 2000
voicemail 2222
mwi relay
!

!
ephone-dn-template  1
call-forward busy 2222
call-forward noan 2222 timeout 8
mwi sip
!

Now have a test and let me know if you are facing the same again! It won’t I know. 🙂

Live-Record at Cisco Unity Express (CUE)

Live-Record option let you record running conversation of phone (along with conference also) and store as voice mail at your mailbox. It’s configuration is not a big deal, just follow the procedures, I have done it for CME only, you can also do it for CUCM.

1. Create Live-Record DN at CME:

ephone-dn  10

number 1111

description *** Live Record DN ***

call-forward all 2222 ! <voice-mail DN of your CME system>

!

2. Modify ephone template with a new softkey named ‘LiveRec’, this button will allow u to start and end recording:

ephone-template  1

softkeys connected  Hold Endcall Confrn LiveRcd Park Trnsfer Join

3. Assign the template to your phone:

ephone  1

ephone-template 1

4. Add Live-Record DN under SCCP Telephony-Service

telephony-service

conference hardware

live-record 1111

voicemail 2222

5. Now time for CUE configuration, that’s the easiest task on CUE I have ever seen 😀

CUE(config)# voicemail live-record pilot-number 1111

With these optional commands, leave those if you wanna put those default

CUE(config)# voicemail live-record beep interval 10

CUE(config)# voicemail live-record beep duration 500

Well, all done 🙂 now test the recording feature just pressing the softkey ‘LiveRec’ while in conversation, keep it mind the recorded files take place in your voice mailbox storage and might occupy all if you don’t pay attention while recording, that’s why I liked to configure the ‘Beep’ parameters to warn you at regular interval.