When considering MWI notification methods for a CUCME-CUE integration, there are three options: (1) Outcalling, (2) Subscribe Notify, and (3) Unsolicited Notifiy. While the two SIP notify methods can be used together, you cannot configure Outcalling and Unsolicited notify at the same time.
The following will briefly explain the commands required to configure each method. For the purpose of this posting, the CUCME IP address is 10.10.202.1 and the CUE IP address is 10.10.202.2. Anyone familiar with ProctorLabs’ IP schema will recognize that I use ProctorLabs.com for all my remote vRack studying needs.
Look at the three methods and tell me which one you would rather configure. Based on the number of commands alone, SIP Unsolicited Notify is the prime choice. A study partner of mine actually commented that unsolicited is Cisco’s best practice for MWI delivery in a CUCME-CUE integration. Don’t call that gospel, I haven’t found the documentation for myself, by I can see why it would be a best practice.
Outcalling
CUCME:
dial-peer voice 3600 voip
destination-pattern 3600
session protocol sipv2
session target ipv4:10.10.202.2
incoming called-number 399[89]….
dtmf-relay sip-notify
codec g711ulaw
no vad
!
ephone-dn 11
number 3998…. no-reg primary
mwi off
!
ephone-dn 12
number 3999…. no-reg primary
mwi on
CUE:
ccn application ciscomwiapplication aa
parameter "strMWI_OFF_DN" "3998"
parameter "strMWI_ON_DN" "3999"
end application
SIP Subscribe Notify
CUCME:
sip-ua
mwi-server 10.10.202.2
!
ephone-dn 1
description BR2 Phone 1
number 3001 no-reg
mwi sip
CUE:
ccn subsystem sip
gateway address "10.10.202.1"
mwi envelope-info
mwi sip outcall sub-notify
end subsystem
SIP Unsolicited Notify
CUCME:
sip-ua
mwi-server 10.10.202.2 unsolicited
CUE:
ccn subsystem sip
gateway address "10.10.202.1"
sip unsolicited
end subsystem
Hey Matthew!
Great post my friend, but one things springs to mind. For both the second and third example you would also need to add the dial-peer that you have in the first example. Excluding the “incoming called-number 399[89]….” line, but it will do no harm if left in.
This addition would of course not have anything to do with MWI notification, I guess that’s why you left it out in the first place.
It would “only” be there for routing of calls to the CUE module.
/Roger Kallberg CCIE #26199 (Voice)
Roger -
You’re absolutely right. A dial-peer would be required regardless. That is, unless you wanted to frustrate the customer by notifying them of voicemails, but not allowing them to call into CUE and check them.
It was actually an oversight to not include the dial-peer in the previous section. That’s for keeping me legit.
Oh, so you guys were talking about adding the 'destination-pattern xxx' on the first method?
I guessed creating ephone-dn is much H323 method rather than SIP so I don't use 'incoming dial-peer' on the sip dial-peer while using first method. Also I don't create any ephone-dn while using unsolicited method.
I have also seen some are using outcalling and unsolicited in together and they are happy with it. Is there anything to conflict or mismatch on concept?
\Mijanur Rahman
SIP Unsolicited Notify
"mwi sip unsolicited " is the corret line