Messages

1

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

2

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

3

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

4

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

5

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

6

MiVoice Office 250/Mitel 5000 / Re: Pre-hook on a Mitel 5000 xd duplex

« on: January 10, 2025, 09:17:01 AM »

Walter,

There is a couple different ways to handle this, but the easiest and most logical is through the Hunt Group.

There are two different announcement that can be utilized with the Hunt Group.

1. Announcement
2. Overflow

The Announcement will play one time and one time only for each new caller and the Overflow will play on a loop based on its timer interval.

If you have both the Announcement and the Overflow setup then the Overflow will be delayed by the Announcement timer the first time and then follow the Overflow timer thereafter.

What you would set the Announcement and Overflow to would be a Call Routing Announcement which is found in the Voice Processor section of the system.

If you need more detail don't hesitate to ask.

Thanks,

TE

7

MiVoice Office 250/Mitel 5000 / Re: Mitel 250/5000 External Dial By Name Option

« on: January 07, 2025, 11:25:45 AM »

ALesher04,

If the phone is from the other node you will need to use Online Monitor to modify it.

If you don't need it, then you can just delete it as well.

Personally, I always delete the entire node when they are decommissioned, but whomever did it probably didn't think about what issues there would be.

There are very few reasons to keep a node that is no longer up.

Anyway, to delete a node you go to the nodes section. System > Devices and Feature Codes > Nodes

Right-Click on the Node you want to get rid of and select delete. It should ask you if you want to delete associated connections and just say yes to any that come up.

Thanks,

TE

8

MiVoice Office 250/Mitel 5000 / Re: Mitel 250/5000 External Dial By Name Option

« on: January 06, 2025, 04:04:57 PM »

ALesher04,

The Directory is based on the description, and it is lastname, firstname, but remember to have a space after the, as that is how it determines where the first name starts.

If the mailbox is associated with an extension/phone number, then you have to make that change under the Phones or the Hotdesk/Phantom section and not the mailbox itself.

If the mailbox is disassociated then you can do it right at the mailbox itself.

Thanks,

TE

9

MiVoice Office 250/Mitel 5000 / Re: Setting up phone for new user

« on: January 03, 2025, 07:28:31 AM »

herpderp,

There isn't a specific thing you need to do as it is based on how the system is configured.

In any case you need to make sure of the following things that tend to always need to be done.

1. Change the Description on the phone in the LastName, FirstName format, don't forget the space after the comma.
2. Change the Username on the phone in the FirstName Last Initial format or whatever you normally want people to see when that person calls them.
3. Change the passcode of the phone IF the user is going to need to do any remote changes on the phone, such as using the Configuration Assistant.
4. Delete any old personal keys on the phone.
5. As for the mailbox I usually tell the customer to delete the old one and create a new so there isn't anything left of the old users personal information.
6. Add the email address in the MB if they have Unified Messaging.
7. Delete and recreate the Users programming if they Dynamic Extension.

After that you just need to make sure the phones are in the correct call flows such as Extension Lists, Hunt Groups, Page Zones and CO Trunk Groups Outgoing Access if necessary.

Thanks,

TE

10

MiVoice Office 250/Mitel 5000 / Re: MiVoice 5000

« on: January 03, 2025, 07:12:00 AM »

Gambler,

If you mean the old Inter-Tel CS controller called the CS-5000 or Inter-Tel 5000 and then the Mitel 5000 followed by the MiVoice Office 250 then yes.

If you are referring to the Aastra 5000 that then became the Mitel 5000 when the old one became the MiVoice Office 250 then no.

The way to know is whether or not it is a SIP based system.

Thanks,

TE

11

MiVoice Office 250/Mitel 5000 / Re: Mitel 250 - Adminstration Training and Plugins

« on: December 11, 2024, 07:24:57 AM »

esoare,

Welcome to the forums!!

There are two different pieces of software that need to be installed to log into the system properly.

1. System Administration and Diagnostics Software.
2. Database Programming Plugin.

Back in the day it just used to be the Database Programming Software and later on they added the System Administration and Diagnostics Software.

So, basically you only need to have the last few of the System Administration and Diagnostics Software and you can install the DB Programming plugins as needed.

As far as the training goes, I am not sure if Mitel still provides that or not since they have discontinued the product line. Even then their last attempts at training some of technicians, pre-COVID, were dismal at best.

One of the best resources you have is F1 when you are in Programming as it will explain a lot of what you are looking at currently.

The next best source of Mitel information, in my opinion, are these forums as many knowledgeable people come here often to help out.

Just looking around the site you will find many of the questions you have are probably already answered, hint about the software.

As far as having bad manners I don't think many people come here with no questions at all, which is why this site exists in the first place.

Thanks,

TE

12

Mitel MiVoice Business/MCD/3300 / Re: Physical 3300 to Virt

« on: November 04, 2024, 08:53:28 AM »

igbe,

You could try the following.

1. SIP LINK STATE PEER <Peer Name>; The peer name is what it is called in Network Elements.
2. SIP TRACE ON
3. SIP BUSY FORCE PEER <Peer Name>
4. SIP RTS PEER <Peer Name>
5. Wait for about 2 minutes to get enough registration and options attempts.
6. SIP TRACE OFF

Use WINSCP to log into the MCD with the Root credentials and then go to the VMAIL folder to get the SIP Packet Capture.

You could just delete the file from the MCD or use the command SIP TRACE CLEAR to get rid of it so it doesn't take up HD space.

Look at the packet capture to see if you are sending or receiving Registration or Options 'keepalive' packets.

The above is similar to disabling the Network Element which just means that it isn't trying to register or use keepalive packets. In reality though you are busying out the SIP Trunk and then Returning it to service which will force it to Register and then send Options packets to make sure the other side is up.

13

Mitel MiVoice Business/MCD/3300 / Re: Trouble With RTP

« on: November 04, 2024, 08:30:35 AM »

Vaxley,

Ralph is correct, but here is a more "technical' explanation if you need one.
 
You have to be aware that the MCD is not NAT aware and has nowhere to put a public IP Address for transfers out of its own network.

Although the call will go out it will not know how to route the packets properly after that.

Look at the SDP portion and see where it is showing the RTP packets are to be routed, and it will make more sense to you then.

Thanks,

TE

14

Mitel MiVoice Business/MCD/3300 / Re: NSU IMAT Manual

« on: November 04, 2024, 08:24:43 AM »

Future Self,

After calling and talking to a retired technician, who after laughing at me, provided me with the information needed to see calls on the NSU.

They had used Procomm+ for this, but I used Putty and it worked fine.

Set your COM Port to 38400, 8, N, 1, No Flow

Once in you can type ? and get a list of commands, but the command that lets you see a list of the incoming DIDs is as follows:

1. option +dispcall to turn on the feature to display calls.
2. option -dispcall to turn off the feature to display calls.

Don't forget to turn it off or it will just keep running constantly and could cause issues later on.

Thanks,

TE

15

MiVoice Office 250/Mitel 5000 / Re: Mitel IP Phone Licenses for 53xx phones

« on: November 04, 2024, 08:20:21 AM »

Acejavelin,

The MiCollab Licenses wouldn't have an affect on the MiVO-250 as it wasn't integrated from what I remember.

The only license I remember crossing over was the Category A license could be used in lieu of the Category D license for IP Phones.

Other than that it has been too long for me to remember much else.

Sorry,

TE