Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

MWI Indicator not working - Invalid DN?

Hi All,

I have CCM 4.1(3)SR1 running, integrated with CallXpress 7.6 Voicemail system.

I have most features working, except MWI on the telephones. In the trace files, I am recieving the following error when there is an attempt to turn on the lamps:

02/17/2006 13:54:18.635 CCM|MessageWaiting - ERROR wait_mwi_apdu_SsNewCallErr: Invalid DN = 7702 or PSS = {F7E72A4D-B11E-47FE-BC91-89AC6B31EF32} for Mwi Lamp Off

Anyone able to offer some pointers on what could be wrong here?

Cheers,

Mark

3 REPLIES

Re: MWI Indicator not working - Invalid DN?

This sounds like you have a partition and calling search space issue. Is 7702 the DN of a phone? Sounds like you are using an SMDI integration for your voicemail. Look under the Cisco Messaging interface service parameters (this will be on all callmanagers that have the serial cable connected to it) and you will see a Calling Search Space for MWI. This will need to be able to dial 7702. If you are using a VG248 with SMDI, you will have to make sure the ports can dial 7702 and other phones.

Thanks

Steven

New Member

Re: MWI Indicator not working - Invalid DN?

Hi,

Yes, 7702 is the DN of one of the phones.

I am not using SMDI intergration. CallXpress works by simulating 7940 telephones, and having a hunt group that the voicemail pilot dials.

The phone and voicemail is setup as follows:

Phone (DN 7702)

------------------

Partition: BAE EdParks Users

CSS: COS Unrestricted

Message Waiting Indicator

-------------------------

On DN: 1604

Off DN: 1605

Partition: BAE EdParks Users

CSS: COS Unrestricted

The Voicemail software is configured to send the MWI setting using the above two DN's.

I have set the CSS for WMI within the Cisco Messaging Interface paramaters as suggested, but it does not make a difference (I guess because that setting is specific for SMDI intergration maybe?)

I have also set the "Message Waiting Indicator InBound Calling Search Space" within the Call Manager parameters to "COS Unresticted" and that did not help.

Any other suggestions are appreciated :)

New Member

Re: MWI Indicator not working - Invalid DN?

more to this.... i have the full bit of the CCM trace file for when an attempt is made to change the MWI on a phone:

02/18/2006 14:51:22.857 CCM|MessageWaitingManager - - findChildPidGivenSsParty - Child PID does not exist, pid= 0x0 |<:STANDALONECLUSTER><:10.194.3.20><:2><:10.194.18.170><:SEP0015638AC524>

02/18/2006 14:51:22.857 CCM|MessageWaitingManager - - findChildPidGivenSsParty - Child PID does not exist, pid= 0x0 |<:STANDALONECLUSTER><:10.194.3.20><:2><:10.194.18.170><:SEP0015638AC524>

02/18/2006 14:51:22.857 CCM|MessageWaiting - ERROR wait_mwi_apdu_SsNewCallErr: Invalid DN = 7702 or PSS = {F7E72A4D-B11E-47FE-BC91-89AC6B31EF32} for Mwi Lamp On Action|<:STANDALONECLUSTER><:10.194.3.20><:2><:10.194.18.170><:SEP0015638AC524>

02/18/2006 14:51:22.857 CCM|ConnectionManager - wait_AuDisconnectRequest(33623056,0): NO ENTRY FOUND IN TABLE|<:STANDALONECLUSTER><:10.194.3.20><:2><:10.194.18.170><:SEP0015638AC524>

02/18/2006 14:51:22.857 CCM|MessageWaitingManager - - findChildPidGivenSsParty - Child PID does not exist, pid= 0x0 |<:STANDALONECLUSTER><:10.194.3.20><:2><:10.194.18.170><:SEP0015638AC524>

02/18/2006 14:51:22.857 CCM|MessageWaitingManager - - findChildPidGivenSsParty - Child PID does not exist, pid= 0x0 |<:STANDALONECLUSTER><:10.194.3.20><:2><:10.194.18.170><:SEP0015638AC524>

436
Views
0
Helpful
3
Replies