Message Waiting Indicator for a user

[adamgibs7]

Dears,

MWI on is working for some users and for some user not, I have followed the link but no success.

http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unity-connection-version-70/111997-mwi-issue-on-uc-00.html

[Suresh Hudda]

If it doesn't work for some users all time, then it might be issue with partition/CSS. Please check the same on MWI port and phone devices in CUCM.

Suresh

[adamgibs7]

Dear ,

I have checked these before, it is same in the user partition/css in which it is for working user.

thanks

[Marco Rojas Abarca]

Adam,

Couple of questions to you:

-What are the CUCM and CUC versions that you are currently running on?

-How is Unity Connection integrated with CUCM? SCCP ports? SIP trunk?

-How many CUCM servers do you have within the cluster?

-Have you checked replication between CUCM servers? You will be able to check this by running the following command through Publisher's CLI: "utils dbreplication runtimestate"

-Have you checked CUC and CCM traces to verify what happens after the message is left?

-Are you sure there is no other pattern within your dial plan that may be somehow confusing the CUCM platform?

I might be able to provide further insight if you get all this information.

Hope to hear from you soon,

Marco Rojas.

[adamgibs7]

Dear Marco,

Thanks for the reply.

9.1 version for CUCM and CUC

Integrated with SCCP ports

I have 4 CUCM clusters within the cluster.

replication is perfect status (2)

Have you checked CUC and CCM traces to verify what happens after the message is left? which traces i shld enable please advice.

Are you sure there is no other pattern within your dial plan that may be somehow confusing the CUCM platform?

The MWI on DN is 9001 and for OFF is 9002, and i have other extension in 901X, But if i agree on ur words then why it is affecting for some user and for sme not.

thanks

[Marco Rojas Abarca]

Adam,

Thanks for the information provided. Since I am more familiar with CUCM platform then, I would say that you can provide the CCM traces set a detailed level. Below you will find a document that talks about how to set and collect the CCM traces from RTMT:

http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/10124-cm-trace.html#calm

Once you have set the traces at a detailed level, reproduce the problem gather the files, zip them and upload them to this thread along with the following information:

-Calling #:

-Called #:

VM Pilot #:

-Time:

It will be helpful if this can be reproduced from an internal phone, as that will help me analyze the trace files faster.

Regards,

Marco Rojas.

[adamgibs7]

Dear

Please helps,

The MWI is working for Internal partition  only when the user log out he can see the MWI is on but  when he is logged in UDP MWI doesnt work.

-Calling #: 400

-Called #: 208

VM Pilot #:9000

-Time: 20:13 to 20:15

[adamgibs7]

Dear Experts,

Anybody can help me with the traces and guide me the where the problem is lying. why MWI doesnt come up when the user is logged in UDP.

Thanks

[Marco Rojas Abarca · Accepted solution]

Adam,

I can see the following lines from the traces after the call is hung up:

00183005.000 |20:14:17.361 |SdlSig   |DbObjectCacheTimer                     |initialized                    |Db(1,100,202,1)                  |SdlTimerService(1,100,3,1)       |1,100,139,1.1^*^*                        |[T:H-H:0,N:0,L:0,V:0,Z:0,D:0]  AppCorr: 0
00183006.000 |20:14:17.928 |SdlSig   |SdlDataInd                             |wait                           |StationInit(1,100,57,1)          |SdlTCPConnection(1,100,13,117)   |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |*TraceFlagOverrode
00183006.001 |20:14:17.928 |AppInfo  |StationInit: (0000047) StationMwiNotificationMessage mwiTarget=208 mwiCtrl=9001 msgsWaiting=1 totalVm(-1/-1) priVm(-1/-1) totalFax(-1/-1) priFax(-1/-1)
00183007.000 |20:14:17.928 |SdlSig   |StationMwiNotification                 |restart0                       |StationD(1,100,58,47)            |StationInit(1,100,57,1)          |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0]  mwiTargetDn=208 mwiControlDn=9001 msgsWaiting=1
00183008.000 |20:14:17.928 |SdlSig   |SsInfoReq                              |wait                           |Cc(1,100,213,1)                  |StationD(1,100,58,47)            |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] Type=0 Key=0 Node=1 Party=0 DevId=(1,58,47) CSS=c59208fc-e8b5-70ed-a331-ed1a5c8ba3d5 dn=ti=1nd=208pi=0si1 FeatId=122 FeatVal=2 WhichLamps=0 LampPersis=0 Signal=0 Cause=0 clientCodeReq=F authCodeReq=F mwiOnOffDn=9001 FDataType=0opId=0ssType=0 SsKey=0invokeId=0resultExp=Fbpda=F
00183009.000 |20:14:17.928 |SdlSig   |SsInfoReq                              |wait                           |MessageWaitingManager(1,100,126,1) |Cc(1,100,213,1)                  |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] Type=0 Key=0 Node=1 Party=0 DevId=(1,58,47) CSS=c59208fc-e8b5-70ed-a331-ed1a5c8ba3d5 dn=ti=1nd=208pi=0si1 FeatId=122 FeatVal=2 WhichLamps=0 LampPersis=0 Signal=0 Cause=0 clientCodeReq=F authCodeReq=F mwiOnOffDn=9001 FDataType=0opId=0ssType=0 SsKey=0invokeId=0resultExp=Fbpda=F
00183009.001 |20:14:17.928 |AppInfo  |MessageWaitingManager::ssInforeq mwiOnOffDn=9001 passedCSS=c59208fc-e8b5-70ed-a331-ed1a5c8ba3d5 mwiDnCss=c59208fc-e8b5-70ed-a331-ed1a5c8ba3d5
00183009.002 |20:14:17.928 |Created  |                                       |                               |MessageWaiting(1,100,127,3)      |MessageWaitingManager(1,100,126,1) |                                         |NumOfCurrentInstances: 1
00183009.003 |20:14:17.928 |AppInfo  |MessageWaitingManager -  hashChildProcess - entries in the messageWaiting table = 0x1 
00183010.000 |20:14:17.928 |SdlSig   |SsInfoReq                              |wait                           |MessageWaiting(1,100,127,3)      |MessageWaitingManager(1,100,126,1) |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] Type=0 Key=0 Node=1 Party=20342525 DevId=(1,58,47) CSS=c59208fc-e8b5-70ed-a331-ed1a5c8ba3d5 dn=ti=1nd=208pi=0si1 FeatId=122 FeatVal=2 WhichLamps=0 LampPersis=0 Signal=0 Cause=0 clientCodeReq=F authCodeReq=F mwiOnOffDn=9001 FDataType=0opId=0ssType=0 SsKey=0invokeId=0resultExp=Fbpda=F
00183010.001 |20:14:17.928 |AppInfo  |MessageWaiting::sendDaReq dialingPattern=208 dialingPartition=df6e560d-ede9-0b1c-e9dc-6d6287c36932 voiceMailbox= orig digitString=208, cmDeviceType 0
00183010.002 |20:14:17.928 |Stopping |                                       |                               |MessageWaiting(1,100,127,3)      |MessageWaiting(1,100,127,3)      |                                         |NumOfCurrentInstances: 1
00183011.000 |20:14:17.928 |SdlSig   |DbVoiceMailUpdtReq                     |initialized                    |Db(1,100,202,1)                  |MessageWaiting(1,100,127,3)      |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[T:N-H:0,N:0,L:0,V:0,Z:0,D:0] 02000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000001 58af10b1 187f95b2 00000000
00183011.001 |20:14:17.928 |AppInfo  |DB: SQL1[execute procedure dblSetMWIEx('208', 'df6e560d-ede9-0b1c-e9dc-6d6287c36932', 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)]
00183012.000 |20:14:17.928 |SdlSig   |SsInfoRes                              |restart0                       |StationD(1,100,58,47)            |MessageWaiting(1,100,127,3)      |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] SsType=0 SsKey=3 SsNode=1 SsParty=0 DevId=(0,0,0) CSS=c59208fc-e8b5-70ed-a331-ed1a5c8ba3d5 dn=ti=1nd=208pi=0si1 FeatId=122 FeatVal=2 WhichLamps=0 LampPersis=0 SsSignal=0 SsCause=16
00183012.001 |20:14:17.929 |AppInfo  |StationD:    (0000047) TX StationMwiResponse: mwiTarget=208 result=0.
00183013.000 |20:14:17.929 |SdlSig   |MessageWaitingComplete                 |wait                           |MessageWaitingManager(1,100,126,1) |MessageWaiting(1,100,127,3)      |1,100,13,117.1567^10.1.15.15^CiscoUM1-VI23 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] 
00183013.001 |20:14:17.929 |AppInfo  |MessageWaitingManager - deleteEntryFromMwiTable - entries in the messageWaiting table = 0x0 
00183011.002 |20:14:17.930 |AppInfo  |DB: SQL2[execute procedure dblSetMWIEx('208', 'df6e560d-ede9-0b1c-e9dc-6d6287c36932', 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)]

This should be enough for the phone to light up whenever a voice mail is received.

Please find below some threads from customers on the Cisco Support Community about MWI with EM:

https://supportforums.cisco.com/discussion/10006201/extension-mobility-not-registering-mwi

https://supportforums.cisco.com/discussion/11449451/voicemail-messages-unity-connection-extension-mobility

Aside of that, please find the documentation for EM on the version that you are running on below:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_1_1/ccmfeat/CUCM_BK_C3E0EFA0_00_cucm-features-services-guide-91/CUCM_BK_C3E0EFA0_00_cucm-features-services-guide-91_chapter_0110111.html

Your problem could be related to the configuration on EM itself. Because as I said, the MWI notification is being received and processed.

Hope this information helps,

Marco Rojas

[adamgibs7]

thanks Marco for ur precious time on my post

I can see the logs showing about the MWI number but can you show me the actual lines from the logs showing that the MWI has been triggered

MWI not working with EM this is the actual case hence you have route me to the link I will continue with that and expect to have a reply from experts.

Thanks