Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Can a MITEL 5330e speakerphone be disabled permanently?

« on: October 24, 2019, 10:33:09 AM »

  Yes, cut the mic! Why didn't think about that I would do it but my department will definitely not allow it

As far as removing the feature code, yes we can do it.  The phones will still have a working microphone which means eavesdropping remains a potential threat.

Thanks everyone for your input!

2

Mitel MiVoice Business/MCD/3300 / Can a MITEL 5330e speakerphone be disabled permanently?

« on: October 23, 2019, 01:05:04 PM »

Hi folks!

Is there a way to permanently disable the use of the speaker on the 5330e to prevent hands free mode?

My understanding is that IT CANNOT be disabled.

Our concern is that Direct page FC + extension can allow an insider to listen in on a user without their knowledge.

Your input is as always greatly appreciated!

3

Mitel MiVoice Business/MCD/3300 / Re: ICP Comms Card

« on: March 26, 2018, 03:36:36 PM »

we had the same issue not long ago and it was discovered by one of my colleague that it relates to the inactivity timer on the IPX trunk. If the timer is not configured, the ICP COM Card will trigger an alarm. We could not figure it out until she took some notes. Our network has more than 300 elements but we would get those alarms randomly not knowing why.

Configure the inactivity timer to 1 hr or 30 min, it has to match at both ends ( meaning that if one of you MCD is for a satellite office, your main PBX at the main office must match the same inactivity timer as your satellite ). If that inactivity timer is not configure and no calls are made, the link will remain up indefinitely preventing calls to be made.

Just try it, it may solve your issue

We had the exact same problem.  We also have over 300 elements.  The MCD can only assign 255 simultaneous link handles.  If you run the command STATE XNET ALL, you'll see the Link Handle number.  When all 255 link handles are "established", no other XNET trunks work (out-of-service).  The solution was to set the inactivity timer to 1 hour at both ends.

4

Mitel MiVoice Business/MCD/3300 / Re: 911 Address update - Urgent

« on: March 26, 2018, 03:26:49 PM »

You are correct.  You enter that DID under CPN substitution form "Default Voice CPN"

5

Mitel MiVoice Business/MCD/3300 / Re: MiVoice Business Installer Software Installation Question

« on: March 26, 2018, 08:18:11 AM »

Thank you! This saved me time from getting an approval to install the software on the server.

6

Mitel MiVoice Business/MCD/3300 / MiVoice Business Installer Software Installation Question

« on: March 12, 2018, 01:50:46 PM »

Hi Everyone,

Is there an installation guide for the MiVoice Business Installer Software? I want to know if I can install version 13.2.1.2 on a Windows 2008 virtual server.

I have the same version on a Windows 2003 server (physical), but the server will need be decommissioned soon.

Thank you!

7

Mitel MiVoice Business/MCD/3300 / Re: Different XNET status

« on: October 16, 2017, 08:44:27 AM »

The IP address was the first thing I checked.  It is programmed correctly.

8

Mitel MiVoice Business/MCD/3300 / Different XNET status

« on: October 13, 2017, 11:08:16 AM »

Hi Everyone.

I'm puzzled by the XNET status of our systems.  Our main gateway -ICP #1 is showing "out of service" on many endpoints but I'm choosing one end point -ICP #396 as an example.  If I look at ICP 396, it is showing "idle" to ICP 1.  I've rebooted ICP 396.  Same status.  Where is ICP 396 synching to? Any idea?

W

Output from ICP 1:
 Signalling   | Link | Dest |   XNET   | State        |  Owner  | ID   |Status 
Dvc Location  |Handle|Switch| Trunk Id |              |         |      |       
-------------------------------------------------------------------------------
 1 1 11       |      |  396 |          |Out of Service|         |      |       
-------------------------------------------------------------------------------

Output from ICP 396:
 Signalling   | Link | Dest |   XNET   | State        |  Owner  | ID   |Status 
Dvc Location  |Handle|Switch| Trunk Id |              |         |      |       
-------------------------------------------------------------------------------
 1 1 11       |      |    1 |          |Idle          |         |      |       
-------------------------------------------------------------------------------

9

Mitel MiVoice Business/MCD/3300 / Silence on outgoing local calls after EDT FORCE FAILOVER Command

« on: September 27, 2017, 04:25:55 AM »

Hi Everyone,

Here's another strange issue...

The primary MCD has an E1 ISDN link configured as resilient link to the secondary MCD, with the failover cable connected between the two units. 
From the primary MCD, all outgoing/incoming local calls work. 
My phone is registered on the main MCD.
To test the resiliency of the E1, I ran the command "EDT FORCE FAILOVER ALL" from the main MCD.  The E1 ISDN link on the secondary MCD came in sync.

However, when I made a call from my phone, I saw the digits dialed, silence, then the call disconnects.

CCS trace shows the primary MCD handed off the call to the secondary MCD, but the secondary MCD doesn't seize any E1 channel. 

With the primary MCD turned off, the call works on the secondary MCD so I know it's programmed correctly.

Any ideas?

10

Mitel MiVoice Business/MCD/3300 / Re: E1 ISDN Problem - Receiving Alarm

« on: September 25, 2017, 07:36:32 AM »

Problem fixed.  Telco did something to fix the E1.  That something.... no idea.  They did not return our call.

11

Mitel MiVoice Business/MCD/3300 / Re: E1 ISDN Problem - Receiving Alarm

« on: September 25, 2017, 02:57:16 AM »

What can cause a BLUE layer 1 alarm? It was RED on Friday morning. 

Here's the output of command "EDT SHOW LINK STATUS PRI"


PRI Logical link number: 3
Layer 1 Status:  BLUE
Layer 2 Status:  DOWN
Interface Activated: TRUE

12

Mitel MiVoice Business/MCD/3300 / Re: E1 ISDN Problem - Receiving Alarm

« on: September 22, 2017, 11:51:41 AM »

The lights are green and yellow.  I connected a loopback plug on the MCD, it turned blinking green.  Then also a loopback on the BIX.  MCD also turned green.  So yeah, connections are good to our MCD and the BIX.

13

Mitel MiVoice Business/MCD/3300 / E1 ISDN Problem - Receiving Alarm

« on: September 22, 2017, 10:12:26 AM »

Hi everyone!

Local and outgoing local calls stopped working for us this morning.  DTSTAT output is below.  There's a green LED and yellow LED on the MCD.  From my experience, this points to a Telco problem.  They came to replace a fiber module on their modem which did not change the status of the E1.  Now they're saying it's a break in the fiber link. 

From my end, I've rebooted the MCD, did loopback tests to the MCD, and just waiting for the Telco to get back. I don't see why they can't just reset their link.

Any ideas?

Universal E1          5 1  2  1                                                 
Link is not available, receiving alarm                                         
         duty                             bit                                   
         cycle       framing              error                                 
Time     (%)         losses     slips     rate                                 
------------------------------------------------                               
16:05      0            0           0         0                                 
------------------------------------------------   

14

Mitel MiVoice Business/MCD/3300 / Re: Can't call certain mobile numbers after changing Mitel MCD

« on: September 21, 2017, 12:11:40 PM »

Problem fixed! Changed the Bearer Capabilities setting from 3.1khz to Speech.

And yes, I also tested it on the MCD that was set to country "Germany".  With Bearer set to 3.1kHz, the call didn't go through AND only to those numbers.  With Bearer set to Speech, the calls worked on all the cellphone numbers we've tested prior to changing the PBX to MCD.

My active MCD is set to North America and it works with "Speech".

15

Mitel MiVoice Business/MCD/3300 / Re: Can't call certain mobile numbers after changing Mitel MCD

« on: September 21, 2017, 08:08:31 AM »

Unfortunately, there's not a single analog trunk on the MCD.  This would have been a test, and likely the workaround for these numbers.

BUT... BUT.. I'm in Dusseldorf now changing the Nortel Option 11 with a Mitel MCD, and I've got the exact same problem.

Those numbers worked on the Option 11, but not on the MCD.  No analog trunks here either.  So yeah, since we made the change, the Telco says it's our problem (obviously).

Any ideas?