Topics

16

Mitel MiVoice Business/MCD/3300 / t.38 fax error

« on: October 22, 2014, 04:28:38 PM »

We have been using fax over SIP trunks through SIP converter boxes (Cisco ATA-122) without using t.38.  DID numbers point to internal extensions assigned to the SIP boxes.  Completion rates are OK, not great.  We have t.38 licenses, so I thought I'd try it out.  I followed the instructions in the on-line help (see attached file for these instructions), but I'm getting the following error in the log:

   Port:11930f90 Failed to Apply Policies.Most likely T38 is not allowed in the zoning plan. (substate 7)

The error only shows up when I enable t.38 in the SIP boxes.  Has anyone seen anything similar?

Release level: 7.0 PR1
Active software load: 13.0.0.83

17

Mitel MiVoice Business/MCD/3300 / Delay when dialing certain phones from 3300 to 200ICP

« on: September 24, 2014, 12:31:17 PM »

I have an environment with a 3300 and a 200ICP.  When dialing 2 extensions on the 200 from the 3300, there's a delay of 9 seconds before the call completes.  The calls are directed to the 200 via the ARS Digits Dialed form.  We have hundreds of other extensions set up like this which work fine.  Any thoughts?

18

Mitel MiVoice Business/MCD/3300 / Two apparent bugs in 7.0PR1

« on: August 22, 2014, 01:35:37 PM »

We recently upgraded to 7.0PR1 on both our 3300 and our VMCD.  We have experienced two show-stopping bugs.

1.  Controller crashes when modifying hunt group resiliency.  Twice the 3300 has crashed when we modify the "2nd element" resiliency on a hunt group pilot number.  The hunt group points to 16 SIP trunks on our voicemail server.  As soon as this setting is changed, the administrative interface responds very slowly, and all the phones on that controller behave strangely.  They experience a delay in dialing and a delay in picking up a call.  Other strange behaviours have been reported, as well.  The only fix is to reboot the controller.

3.  One-way audio caused by congestion of logical ports.  My understanding of this phenomenon is incomplete, and is based on conversations with our vendor, who have a ticket open with Mitel.  We have several DID numbers pointing to ATA SIP boxes, and are experiencing a high volume of spam faxes.  This is not a problem in itself.  However, it appears that many of these calls are not terminated properly, and cause the consumption of logical ports on the controller.  I've been told there are about 11,000 of these ports, and when they are congested, we experience one-way audio.  Does this make any kind of sense to anyone?

This brings me to a general observation: we have no visibility into Mitel bugs.  The Mitel OnLine site has nothing of substance in this regard.  So far this forum is my best option for troubleshooting outside of vendor channels.  Does anyone else have other resources that you could point to?

Thanks!

19

Mitel MiVoice Business/MCD/3300 / SIP trunk congestion

« on: August 05, 2014, 12:21:51 PM »

We have 2 MCD instances recently upgraded to 7.0PR1, with SIP trunks going through Mitel Border Gateway boxes.  We have a sporadic ring-no-answer on incoming calls, which began after we upgraded from an earlier release (6.something, I think).  There should be no reason for higher than average call volume, because this is our low season.  We noticed a very high number of calls coming into various DID numbers that point to Cisco SPA-112 ATAs serving fax machines.  See the SMDR log for an example of these calls.  We believe the high volume of calls is causing congestion on the SIP trunks, which results in the ring-no-answer on incoming calls.  However, it's very suspicious that the problems began after the software upgrade.  Any thoughts would be highly appreciated! 

Code: [Select]

08/01 06:15P 00:00:03 T889  *** 774201                                         
           1234567890 774201                                                   
 08/01 06:15P 00:00:02 T889  *** 774201                                         
           1234567890 774201                                                   
 08/01 06:15P 00:00:03 T889  *** 774201                                         
           234567890  774201                                                   
 08/01 06:15P 00:00:02 T889  *** 774201                                         
           234567890  774201                                                   
 08/01 06:15P 00:00:03 T889  *** 774201                                         
           234567890  774201                                                   
 08/01 06:15P 00:00:03 T889  *** 774201                                         
           234567890  774201                                                   
 08/01 06:15P 00:00:02 T889  *** 774201                                         
           1234567890 774201                                                   
 08/01 06:15P 00:00:03 T889  *** 774201                                         
           1234567890 774201                                                   
 08/01 06:15P 00:00:03 T889  *** 774201                                         
           1234567890 774201