Messages

31

MiVoice Office 250/Mitel 5000 / Re: Admin transfers call, wants call to ring back to admin if not picked up

« on: September 13, 2021, 07:15:57 AM »

Uncheck the CO Transfer/AA/VM flag in the forwarding path, then make the admin phone the Transfer Recall Destination for the station.

32

MiVoice Office 250/Mitel 5000 / Re: 911 call routing, separate route and facility group

« on: September 13, 2021, 07:07:02 AM »

Your ARS programing is correct. Change your Interdigit Long timer from default of 15 seconds to 4 seconds so calls will be dialed faster.

33

MiVoice Office 250/Mitel 5000 / Re: old analog 550 phone swap to 8568 phone

« on: August 03, 2021, 09:06:42 PM »

The 550 series phones use the orange pair on the jack, 8568 phones use the blue pair. You'll need to swing the cross-connect on the block to the blue pair.

The 550 phones are digital keysets, not analog. You don't have to change the phone type, but you'll need to change the keymap.

34

MiVoice Office 250/Mitel 5000 / Re: Moved from ISDN30 (PRI) to SIP, how to stop PRI red alarm?

« on: July 30, 2021, 07:28:26 AM »

Short of removing the card in programming, you can loop up the span.

The lowest numbered trunk group will be the default when creating new endpoints.

35

MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 - SYS ALARM #10 EXT. OFF HOOK

« on: July 28, 2021, 05:07:50 PM »

Does the alarm keep coming back when you clear it?

36

MiVoice Office 250/Mitel 5000 / Re: Teleworker one-way audio outbound

« on: July 23, 2021, 03:05:01 PM »

It's been years since I programmed one of these, but I seem to remember that NAT will create one-way audio issues. I think it should be set to Native.

37

MiVoice Office 250/Mitel 5000 / Re: Denying Ability to Page and Internal Calls

« on: July 23, 2021, 03:01:38 PM »

You can't prevent a station from dialing intercom calls or feature codes. 7 is a feature code.

Class of Service rules only apply to external calls. If you're using a paging adapter connected to a trunk port, you could deny outgoing access to the trunk group.

38

MiVoice Office 250/Mitel 5000 / Re: 250 End of Life

« on: June 19, 2021, 11:41:09 AM »

Ace, I have to agree. We’re halfway through a multi-year, multi-million dollar transition from 250 to 3300 for all of our offices. To say that I hate the 3300 would be a gross understatement.

Features that are native and seamless on the 250 require convoluted work-arounds or simply aren’t available on the 3300. But it is what it is, and I’ll just slug it out until retirement.

39

MiVoice Office 250/Mitel 5000 / Re: Hunt Group callers cutting off

« on: April 23, 2021, 09:19:13 AM »

Thinking about it some more, I would eliminate all Announcement and Overflow greetings. Voice mail ports are a valuable resource, and needlessly wasting them for RADs in a busy system doesn’t make a lot of sense. Additionally, make sure that AA greetings are as short as possible.

Busy voice mail ports can cause routing issues. I’m constantly battling with folks who want to use announcements instead of MOH.

40

MiVoice Office 250/Mitel 5000 / Re: Hunt Group callers cutting off

« on: April 23, 2021, 08:12:25 AM »

Is the call really dropped, or is there just silence?

There are several reasons for audio to be dropped, including MOH settings, busy VM ports, or even carrier issues. I had an issue where SIP trunks would drop MOH after several minutes, and everyone thought the call was dropped.

41

MiVoice Office 250/Mitel 5000 / Re: MiVoice 250 Numbering plan

« on: April 15, 2021, 12:23:19 PM »

There’s no requirement for a comprehensive numbering plan, so you won’t see it in a manual. You could simply randomly number things and hope for the best.

Those of us who’ve been doing this for a while know that a bit of planning now will make your life much easier for years to come.

42

MiVoice Office 250/Mitel 5000 / Re: ACD Huntgroup Recall

« on: April 12, 2021, 07:48:34 AM »

Things I have tried with no luck.

• Creating a UCD huntgroup with an extension list containing the two phones that the ACD agents would normally use and another huntgroup member list containing those two users as well as local and off-node extensions that they would like the calls to overflow to.
  When testing this, even though the huntgroup is setup as linear, it seems to ring all members of both lists at the same time.
  
• Keeping the initial ACD setup and using Overflow timer/destination instead of recall.  This had no effect and calls still stay camped on first group even though all agents are logged out.
  I wasn't totally surprised by this as the feature and programming guide states that the Overflow timer is not used on ACD groups.
  

That behavior makes no sense. What is the No Answer Advance timer set to?

Overflow is commonly used for ACDs. I have no idea why the guide would say otherwise.

43

MiVoice Office 250/Mitel 5000 / Re: ACD Huntgroup Recall

« on: April 12, 2021, 07:42:23 AM »

If no agents are logged into first group, doesn't that immediately invoke OVERFLOW not RECALL destination?? Do you have the 2nd group defined as an OVERFLOW destination what is the timer? That 3mins stuck in first group doesn't sound right.

That's not how overflow works on a 250. If you use a phone as an overflow destination, calls will be pulled back to the original hunt group member if one become available.

44

MiVoice Office 250/Mitel 5000 / Re: Music On Hold recorder question

« on: April 09, 2021, 01:12:27 PM »

File-based MOH uses a proprietary format. There is a conversion utility, if you have appropriate user permission to access it. Check the Help files for details.

45

MiVoice Office 250/Mitel 5000 / Re: MiVoice 250 Numbering plan

« on: April 09, 2021, 01:09:58 PM »

Only 8 sites? A walk in the park. My 68 nodes play nicely together, but only because the numbering plan was well thought out.

I used 4 through 7 for extension numbers, 2 for voice mail applications, 3 for feature codes, and 9 for all trunks and trunk groups (which also should be unique). Use feature keys, end users should never be expected to remember feature codes.

Forget about reserving 1,000 number blocks for extensions. You'll run out of numbers before using a fraction of the system capacity.

Reserve smaller blocks: 4100 to 4199, 4200 to 4299, etc. Actual size will be determined by the anticipated number of phones, leaving plenty of room for expansion.

Number your hunt groups within the reserved block, so you can instantly identify which site it belongs to. Reserve 2xxxx blocks for voice mail applications, for the same reason. You'll just make yourself crazy if you mix everything together randomly.

Number your IP Connections to match the node number: P6001 and P6101 for Node 1, P6002 and P6102 for Node 2, etc. You'll know instantly what you're looking at.

Create a detailed spreadsheet to document your numbering plan before even thinking about starting any programming. Let me know if you have any specific questions.