Messages

1

MiVoice Office 250/Mitel 5000 / Re: Password Length Limitation on MiVoice Business 5000

« on: May 22, 2025, 02:41:04 PM »

jlopez,

I am not sure what version you are on, but the latest version 6.3 SP7 is set to 49 characters not 26.

Out-bound Username: This field applies only if the SIP peer requires registration or call authentication. The username is provided by the SIP peer. The MiVoice Office 250 uses this username as part of the SIP Digest Credentials in the SIP Request. The username is limited to 64 characters.

Out-bound Password: This field applies only if the SIP peer requires registration or call authentication. The password is provided by the SIP peer. The password is limited to 49 characters.

You may want to try an MBG or some other SBC that can do what you need for credentials if your version doesn't allow for it.

You may also be in the wrong forum if you mean the Aastra 5000 and not the Inter-Tel 5000 that Mitel bought out. I can move this thread if you need me to.

Thanks,

TE

2

MiVoice Office 250/Mitel 5000 / Re: TDIL - How to add Emergency Call Notification to a phone

« on: April 28, 2025, 07:13:02 AM »

esoare,

I am not sure what ChatGPT is or why you would use that for this, but the manual and pressing F1 inside of programming are your best bet.

As for how you did it that is correct, administrators are alerted for any alarm in the system.

You could also send out an email for Critical Alarms which would also be a way to alert them since there isn't an audible associated with either one.

Thanks,

TE

3

MiVoice Office 250/Mitel 5000 / Re: IP address issue on Mivoice 250

« on: April 17, 2025, 02:21:54 PM »

Tripoth,

Like I said, .10 is not allowed as an IP Address with the /30 subnet [255.255.255.252]. If you set the IP Address of the system to 192.168.62.2 and then set your PC to 192.168.62.3 then you will be able to access the phone system.

Otherwise, you will need to allow more IP Addresses to access the phone system by changing the subnet mask to one that allows up to .10 like /28 [255.255.255.240] which will give you 192.168.62.0 to 15 to work with.

If you just want to clear the IP Address you can do that through the menu built into the system.

Click the round button once, select Network and then move up and down through the menu to change whatever you want.

If you want to just default the entire system you do that through the system menu. This will keep the licensing and get rid of everything else. If you are just uploading a new DB it will use the credentials supplied in that DB when it reboots.

Now that I think about it, I am not sure I understand what the real issue is here. Are you having problems with the IP Address or the System Programming?

Thanks,

TE

4

MiVoice Office 250/Mitel 5000 / Re: IP address issue on Mivoice 250

« on: April 17, 2025, 09:34:31 AM »

Tripoth,

First off you have a different gateway then the PBX which isn't correct.

Your biggest issue though is that you have a /30 network which only allows 4 IP addresses.

192.168.62.0
192.168.62.1
192.168.62.2
192.168.62.3

You set your system and PC outside of that IP Address range so you would need to have the correct gateway to access it from a different network.

Thanks,

TE

5

MiVoice Office 250/Mitel 5000 / Re: Station speed dial issue

« on: April 11, 2025, 11:27:28 AM »

NSTech,

Did you verify whether or not the System Flag for requirement of the Special Key was on or off?

If it is On then you will need to put a '!' (exclamation mark) on the end of the feature code used in a speedcall.

Thanks,

TE

6

MiVoice Office 250/Mitel 5000 / Re: Station speed dial issue

« on: April 11, 2025, 08:20:17 AM »

NSTech,

So, when you tried this manually from the phone you put the button on what happens?

My guess is that you didn't put in the correct passcode for x1170 and so your remote programming feature failed.

To do it the way you have it then you must remove the passcode from x1170 and if it has # marks in that field it isn't empty.

I am not going to ask why you are using CRAs as that isn't really relevant, but you do know you can just send them to the phantoms that are actually forwarded.

Thanks,

TE

7

MiVoice Office 250/Mitel 5000 / Re: Adtran PRI to Mitel 5000 Auto Attendant recordings won't play

« on: April 03, 2025, 12:55:54 PM »

KTSaved,

Are you sure you had a PRI before and not just a T-1?

Most of the time, unless it is old, you would use NI-2 [National ISDN 2] for a PRI.

If you are set to AT&T 5ESS Custom then you may have to adjust your Call Types on the MiVO-250 to work with the Adtran.

I would try changing both the Adtran and the MiVO-250 to NI-2 and see if that helps with some of the issues you are having.

Now, just to honest, some of the audio issues you were having with going through the STAR to a Call Routing Announcement, that did happen on older versions of software. What version of software are you running, not that upgrading your software is valid without Mitel Software Assurance.

Thanks,

TE

8

MiVoice Office 250/Mitel 5000 / Re: reception line is ringing but unable to attend outside calls!

« on: April 03, 2025, 12:45:45 PM »

techsupport786,

That is just an alert to let you know that Hunt Group 2001 has someone waiting in it.

What you need to do is log someone into the Hunt Group and it will present them the call.

Thanks,

TE

9

MiVoice Office 250/Mitel 5000 / Re: Ext to Ext not working

« on: March 07, 2025, 07:49:26 AM »

drawntogether,

Well, you have to remember that BGP isn't a trusting network protocol and doesn't always use the best path to reach its destination.

Systems like the MiVO-250 and voice in general do not like delays and will most likely see them as disconnected due to high latency.

Here are the port numbers you will need to know based on what type of connection you are making through your firewalls.

53xx phones:
TCP - 5566, 6800-6802, 3998-3999
UDP - 6004-7039, 5567, 5004-5007, 50098-50508
TFTP - 69, 20001

Database Programming and System Administration and Diagnostics:
TCP - 44000, 443, 22

Network Systems:
UDP - 6004
TCP - 5570

You may also want to go into each of your systems and change the Audio RTP Type of Service and Data Type of Service for each IP Connection to 184. This value requests Expedited Forwarding if used for Differentiates Services (DiffServ). If used for IP Precedence, this value requests critical precedence, low delay, and best throughput.

To get there go to System > Devices and Feature Codes > IP Connections > Node:
Audio RTP Type of Service - 184
Data Type of Service - 184

Thanks,

TE

10

MiVoice Office 250/Mitel 5000 / Re: Ext to Ext not working

« on: March 06, 2025, 09:17:53 AM »

drawntogether,

I am not sure a log is going to show you anything that would help you.

Do you know for sure that those sites are networked together and can do extension to extension calling?

Were they able to do it before and they can't now?

Thanks,

TE

11

MiVoice Office 250/Mitel 5000 / Re: Mivoice 250 SIP trunk license transfer

« on: February 19, 2025, 12:06:55 PM »

Tripoth,

I don't see Mitel allowing you to do that.

1. You would need to contact Mitel to get the licenses removed from the old CF.
2. You would then need to pay Mitel to go into the existing CF to clear out the license so you can apply the updated one.
3. There is nothing stopping you from saving the old licensing and putting it back in so Mitel may require you to order a new CF and return the old one.
4. You would then need to see if they will allow you to use the now released SIP licenses for a different customer.

Personally, I would say no and most likely Mitel will too.

Thanks,

TE

12

MiVoice Office 250/Mitel 5000 / Re: Trouble migrating some extensions off of Mitel 5000 to cloud solution

« on: January 15, 2025, 02:05:24 PM »

jjc8008,

Yes, it looks as though it is a carrier issue and not a Mitel issue.

If you can call 666-666-6661 from you cell phone and it rings the new system, but when you call it from a Mitel phone going out through the PRI [92001] and it comes back in and hits the extension 6697 that you routed it to that is a carrier not routing correctly.

I would contact both of your carriers and let them know what is going on and have them fix their mistake as the losing carrier should know to update their routing to match all the others.

Thanks,

TE

13

MiVoice Office 250/Mitel 5000 / Re: Difference between a Category C and F license

« on: January 15, 2025, 10:32:58 AM »

Acejavelin,

I know that the F license is the actual SIP License.

The C license is just for those specific devices and I remember something about High CPU usage on 86xx phones or maybe even a specific one when it was in SIP mode which required the C license.

Let me look in my old notes and see what I can find as I haven't had to deal with MiVO-250 licensing in a long time.

****Update****

OK, it appears as the reason for the C license is like I stated before it is just for the above list of devices as the C license came before the F license and is only used for those Dual-Mode phones.

So, you can think of it this way, the F License if for those devices that are in SIP Peers and the C license is for those devices that are created as 8600 and the IP SLA as they are dual mode devices.

The issue I remembered about the 8600 and High CPU usage was with the 8662 using when a Category C license was causing High CPU usage in versions prior to 6.3 SP6.

MIVO-1049 - CPU usage increases until system resets when Inter-Tel 8662 E phones are used in sip mode with category C sip licenses.

Thanks,

TE

14

MiVoice Office 250/Mitel 5000 / Re: Trouble migrating some extensions off of Mitel 5000 to cloud solution

« on: January 14, 2025, 01:57:22 PM »

jjc8008,

OK, that makes more sense to me now.

First of all, when making an outside call, meaning you dial 8+number, it doesn't use the Call Routing Table to make that call.

The Call Routing Table is for Inbound Calls through the CO Trunk Group that the calls come in on.

The Outbound Call will use the Outgoing Extension of the device to make a call. Typically, you will want this to be the CO Trunk Group Extension [Typically 92001] or 92000[ARS], best if it is ARS.

If it is set to ARS [92000] then it will look at Route Groups under Numbering Plan to decide what type of call it is and then use the Associated Facility Group to pick a trunk to go out of.

I have never seen 92001 in the Forward Destination Extension, but I guess that will work. Typically, we use ARS which is PP040, and it would look more like this.

Forward Information:
> Forward Destination Extension: PP040
> Forward Username: ARS
> Forward Description: ARS Device
> Forward Outside Number: 16666666661
> Forward Extension: 355
> Forward Type: 1
> Forward Public Network: Yes

Did you use the Remote Programming Feature [Default: 359] or just manually set this with Online Monitor?

Now, it could be that the existing Carrier on the MiVO-250 is still routing the DID to itself as it hasn't updated its routing yet which is why the call keep coming back to the MiVO-250 and not the new one. You can test that by putting a Route in the Call Routing Table to send it to a phone on the MiVO-250 that you are standing near and see if it rings there, if it is then it is a Carrier issue.

As for the Operator issue look at what extension is setup for the System Operator. Go to System > Phone-Related Information > Primary Attendants which is typically the first programmed phone 1000 which is usually also the Attendant as that exists in the Phones Extension Programming under Attendant.

Let me know if you need me to explain something in more detail.

Thanks,

TE

15

MiVoice Office 250/Mitel 5000 / Re: Trouble migrating some extensions off of Mitel 5000 to cloud solution

« on: January 14, 2025, 08:35:49 AM »

jjc8008,

Let me see if I understand correctly.

You moved a sight to a new phone system with a DID range of 777-777-7700 thru 7800 instead of porting your old DIDs numbers to the new system? Are you at some point going to port the old DIDs to the new system?

The old phone system still has the DID range of 666-666-6600 thru 6800 and the phones use the last 4 digits of the of the DID as their extension.

When you call out of the new site on the new phones there they seem to work fine when calling a cell phone, as expected.

You deleted the old phone extension and recreated it as a phantom extension that is Forwarded to its own DID which no longer has a route in the Call Routing Table.

IF you didn't port your DIDs to the new phone system then the calls will ring into the old system.

IF the old system can't route the DID anymore because you deleted the Call Routing Table entry it will just ring with no answer if you don't have a + or E entry as a catch all.

I am not sure how you setup your new Phantom extension to make it call the front desk, but look at the associated extensions of that phantom and tell me how they are programmed. Also make sure you setup your System Forwarding to support Internal Calls as by default it doesn't.

Thanks,

TE