MWI on SIP Phone during SRST: an open bug yet to solve!

Well, I discovered it when was trying to solve a issue on IEOC forum. MWI on SCCP phones works without any issue, but for SIP? It’s still a bug (bug idย CSCta76151) on 12.4T trends IOS series.

Cisco Bug Toolkit can really save some of your precious time if you search for the bug rather than getting panic and googling and googling when anything not working.

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. ๐Ÿ™‚

Sending Calling Number to Get Personal Greetings on VoiceMail at SRST

Well, the purpose is simple, without sending the calling number to voicemail server (I have tested with Unity Connection) you can’t get the personal greetings, instead it will always go to general greetings and use general mailbox. To send the calling number you have two options to work with:

1. Use the command set ‘vm-integration’:

Cisco recommends to use these command sets for FXO/FXS ports only, not for PRI/BRI. But I have tested with PRI/BRI and it’s worked fine. The command set is like below:

vm-integration
pattern direct * CGN
pattern ext-to-ext no-answer # FDN
pattern ext-to-ext busy # FDN
pattern trunk-to-ext no-answer # FDN
pattern trunk-to-ext busy # FDN

To know how it works: http://www.cisco.com/en/US/docs/voice_ip_comm/cusrst/admin/srst/configuration/guide/srs_mail.html#wp1348791

But in short I can explain like it: it can tail your calling number after your voicemail pilot number while sending over the WAN. Let’s take an example:

call-manager-fallback
voicemail 912221111
call-forward busy 912221111
call-forward noan 912221111 timeout 10
vm-integration
pattern direct * CGN
pattern ext-to-ext no-answer # FDN
pattern ext-to-ext busy # FDN
pattern trunk-to-ext no-answer # FDN
pattern trunk-to-ext busy # FDN
dial-peer voice 1111 pots
destination-pattern 912221111T
port 0/0/0:23
prefix 912221111

And let’s assume my Calling number is 5005. So when I will press the message button SRST router will call with called number of 912221111#5005, it would be routed through the dial-peer just created and will reach the CUCM. We need some configuration on CUCM to accept the call:

> Strip the incoming number down to 4 digits in the gateway configuration,

> At the line configuration of 5005, forward the phone to voicemail for the cases busy/no-answer/unregistered internal and external.

So, while the call is at CUCM, it will strip the called number ‘912221111#5005’ to ‘5005’ and it will try to reach the DN. As the phone is already unregistered to CUCM, it will directly go to voicemail server with the DN ‘5005’ and I will be able to hear my personal greeting. ๐Ÿ™‚

But it conflicted my configuration because I did set the full E.164 number of 5004 (DID) at unregistered field on call-forwarding option at line to allow 4digits dialing from central phones so that my users can’t understand that the call is traveling over PSTN, not IP WAN.

But again, Cisco recommends this solution only for FXO/FXS lines and not for E1/T1 PRI/BRI. So what about the PRI/BRI?

2. Redirecting the called number to CUCM gateway:

That’s pretty simple and easier, you don’t need to do anything on the gateway side, just configure the voicemail pilot number there:

call-manager-fallback
voicemail 912221111
call-forward busy 912221111
call-forward noan 912221111 timeout 10

That’s all from here, but on CUCM you have to select the option below:

for MGCP GW:

for H.323 GW:

So how do you know what is your redirecting number? Active the debug command ‘debug isdn q931’ at your central gateway from where PSTN calls are coming in and you will get the answer. ๐Ÿ™‚

Calling Party Number i = 0x0081, ‘xxxx’
Plan:Unknown, Type:Unknown
Called Party Number i = 0xC1, ‘12221111’
Plan:ISDN, Type:Subscriber(local)
Redirecting Number i = 0x000082, ‘5005’
Plan:Unknown, Type:Unknown

In my case it was for Inbound calls, if your scenario demands to work with outbound calls you can select the same option for outbound as well.

It automatically inserted my redirected calling number (5005) while calling the VM Pilot and able to hear personal greetings instead of general greeting.

That’s all! Happy labbing!

MWI for the SRST site: not doable

To make your MWI work from SRST site, voicemail server (either unity connection or unity express) must locate on the same lan. SRST doesn’t support MWI yet where unity and CUCM locates centrally, you need to rely on ‘missed call’ to check you message. MWI ports can’t pass over PSTN, ryt? It does make sense to me.