MWI Issue, CM and Mitel SX-200 with PIMG to Unity 5X

Unanswered Question
Jul 23rd, 2008

I'm having problems with MWI to pbx phones off Mitel system. Some work and some don't. (Cisco phones work just fine) What's odd is the ones that work as far as i can tell are new subscribers that haven't gone through self-enrollment yet. once you enroll, mwi seems to stop working. Subscriber Message section in saweb shows MWI request failed even after refresh. Event logs show the following from one of the errors:

Component Miu: Unity Port 32 (PIMG 10.20.11.9:5061) failed to toggle an MWI for extension 7377 to state OFF.


The extension can be dialed. Check whether this is a valid extension, and whether the port and PIMG are configured and operating properly.


PIMG call log shows TDM: Device not available

Odd thing is when I restart Unity, some mailboxes that didn't work would start working although there's still quite a bit that doesn't. Thoughts?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
SAN J Thu, 07/24/2008 - 15:00

thfergus, this seems to match up the error I'm getting in the application log. However, I think the version I have is newer from what I can tell. See below:

Gateway Application (ROM) |5.1.118_5N| |WED JUN 20 16:27:20 2007|

Gateway Application |5.1.118_5N| |WED JUN 20 16:27:20 2007|

Main Board Boot (ROM) |5.1.118N| |WED MAY 02 18:05:23 2007|

DSP Firmware (ROM) |9.1 w/Fax| |FRI MAY 20 16:38:20 2005|

DSP Firmware |9.1 w/Fax| |FRI MAY 20 16:38:20 2005|

Certificate Bundle (ROM) || |THU JAN 01 00:00:00 1970|

Telephony Interface Firmware (ROM) |4.6| |WED JUN 29 14:34:03 2005|

Telephony Interface Firmware |4.6| |WED JUN 29 14:34:03 2005

I'll check with TAC though and have them look at this bug and see if it still exists in this version. thanks.

justinbois Fri, 07/25/2008 - 11:58

I'm experiencing a similar issue with PIMG's to an Avaya solution. I'm running Unity 5.0(1) with the most recent PIMG software posted (SU3). My event logs during MWI resyncs are particularly ugly. I can usually count on about 50 extensions out of 850 failing their MWI refresh completely and another 30 or so during the course of a standard day of business. Resyncing the MWI from the subscriber page clears the issue temporarily but it continues to bounce around between users & MWI ports. I'm tempted to try editing the integration file to try and play with MWI RetryCounts and RetryIntervals to see if that at least conceals the problem.

Actions

This Discussion