Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Modular Messaging 5.2 MWI Single Server 1

Status
Not open for further replies.

wallot

Vendor
Jul 15, 2009
252
US
I am having difficulties in making my MWI lamps work on a single server configuration. This is a SIP trunks only platform.

Thanks,
Richard
 
Should be able to use the same tools on this platform.
Validate that the mailbox is in a COS that includes Message Waiting.
Validate that the station form on the PBX has it set for MWI (check configuration note for proper LWC code)
Check the MWIView tool (\Avaya_Support\Tools\MWIView) to validate what the MM thinks the lamp should be (On or Off).
Can reset the MWI service on the MAS:
1. Turn off Call Me, Message Waiting then Mailbox Monitor service
2. Rename the mwistate.mdb (\Program Files\Avaya Modular Messaging\MWIServer\) to something like oldddmmyymwistate.mdb
3. Turn on Mailbox Monitor then Call Me and MWI services (in that order)
4. Review MWIView tool to validate MWI
 
That works great for seeing what the MM thinks is going on. It does show when the lamp is supposed to be on and off. (This tool is new to me).

I was doing a wireshark trace and didn't see any communication with CM after the call completed. I search for traffic between CM IP and MAS IP and didn't see but a few items that were not what I'd call MWI messages.

And I didn't see anything doing a trace RAS on CM.

Any more good advice?

Richard
 
OK, found it, since my signalling group in CM was TCP (5060), I needed to go to the PBX integration in MM and change the TLS (default) to TCP as well. All is great. Thanks for your good advice.

Richard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top