Messages

1

MiVoice Office 250/Mitel 5000 / Re: Transferring to a Hunt Group from an Application

« on: November 07, 2021, 01:38:09 AM »

Thank you for your response.

I actually did specify in the beginning of my post that I made an Extension ID. It should have anyway been self understood. If there's no mailbox or extension ID then you would get an Invalid Extension message when you tried it. That's not what's happening.

I'll try to explain it better.

The main DID goes to a phantom with a forward path to a CRA set to immediate. The Digit Translation of that CRA is set so if you dial 2 it goes to the Collected Extension. This works fine.

I made an application 2501 and gave it an Extension ID. I made a Hunt Group 2502 and gave it an Extension ID. CRA 2501 times out to HG 2502.

If I make a DID that goes straight to CRA 2501 then HG 2502 rings. CRA 2501 must obviously work.

If I enter 2501 from the main menu then I successfully get to CRA 2501.

If I set digit translation for number 2 in CRA 2501 to transfer to Collected Extension then I can call the main number, dial 2501 to get to the CRA then dial 2502 and the HG rings.

But:

If I set a digit translation number, say number 4, in 2501 to transfer to extension 2502 or if 2501 times out to 2502 then I get a message that Extension 2502 is Not Available. If I give 2502 a mailbox instead of an ID then the call will go straight to the mailbox and never ring on any phone.

For some reason when trying to transfer the call to the HG automatically either via a number on the menu or via timeout the system acts as though the entire hunt group is busy. The overflow on the HG is set to go to another CRA but even that doesn't happen. It treats it as totally busy.

Why might this be happening?

Thanks for your help!

2

MiVoice Office 250/Mitel 5000 / Transferring to a Hunt Group from an Application

« on: November 02, 2021, 11:45:04 PM »

I have an CRA that times out to a Hunt Group. If I direct a DID directly to the CRA it works fine. The company's main number goes to a CRA that has a digit translation to transfer to the collected extension. If I make an Extension ID or VM for the CRA and enter that number from the main menu I get a message that "Extension Number [Hunt Group] is not available." Yet, if I make in the same CRA a digit translation for the collected extension and I manually enter the Hunt Group number it works fine!

I tried having the CRA go to a phantom which is either forwarded to the HG or uses System Forwarding to the HG and then the Phantom reports as not available.

Why can't I transfer calls to the HG?

Thanks!

3

MiVoice Office 250/Mitel 5000 / Re: Forwarded calls are ringing the Primary Attendant

« on: December 18, 2020, 02:50:44 AM »

Thanks!

I'll have not  been able to try it yet but it sounds promising!

4

MiVoice Office 250/Mitel 5000 / Forwarded calls are ringing the Primary Attendant

« on: December 15, 2020, 03:08:15 PM »

We have a MVO250 system that's been running for the last few years with no primary attendant configured. It hasn't been missed. Operator is configured through Dial 0 Destination and it's doing all we need.

I recently upgraded the system to 6.3. Since the update the software keeps pestering me to configure a Primary Attendant. So, I gave in. I configured the receptionist's phone as the Primary Attendant. What's to lose, right?

Wrong. The next day the client calls me with a big problem. There are a number of employees working from home who forwarded their extensions to their cell phones. For some wacky reason, while they are in the middle of a conversation, their call starts ringing at the attendant's phone as if it was an abandoned call. The receptionist picks up and essentially barges into the ongoing conversation. When she hangs up the whole call gets disconnected.

This obviously isn't a workable situation so I was forced to delete the attendant.

Question, is there something I can do different to prevent forwarded calls from going to the attendant or, maybe better yet, is there a way to shut off that message that pesters me about the attendant every time I log in?

Thanks!

5

MiVoice Office 250/Mitel 5000 / Re: SIP Phone Group Insecure Password

« on: June 27, 2019, 01:48:52 PM »

It is odd and I'm very curious to know why but I did turn off that flag and it did clear the alarm so I guess that solved the issue.

Thanks!

6

MiVoice Office 250/Mitel 5000 / Re: RFP 12 DECT phone can't receive calls

« on: June 27, 2019, 01:21:00 PM »

I'm sorry for the very, very long delay in replying. I somehow never saw that there were replies here to look at.

This is issue is still not resolved. I am using a STUN server and I believe that RPORT had to be enabled as well to get it to work at all. The router at the DECT end is a Verizon branded Actiontec but this not the intended permanent install location. I don't know of anything in the router that would be blocking it although I can try this on another network and see what happens. Any other thoughts? Any specifics on what router settings could be blocking this?

Thanks!

7

MiVoice Office 250/Mitel 5000 / SIP Phone Group Insecure Password

« on: June 27, 2019, 01:05:09 PM »

I have a Mivoice Office 250 system with firmware 6.2.5.81. I am connecting a Mitel conference room phone model UC360 which connects as a SIP phone. This is the only phone in its SIP phone group. I set a very secure authentication password. The phone connects and works fine but I keep getting this error anyway. The authentication password is not  blank and is not the extension number. It is 15 characters consisting of capital, lowercase symbols and numbers. Enable In-bound Authentication is set to No. If I change that then the phone won't connect. If I clear the alarm it comes right back. I have a cordless phone configured exactly the same way as far as I can tell and it isn't causing any alarms. The UC360 and the PBX are on the same LAN.

What else can I do to clear this alarm?

Thanks!

8

MiVoice Office 250/Mitel 5000 / RFP 12 DECT phone can't receive calls

« on: March 07, 2018, 08:40:52 PM »

I'm setting up an RFP 12 DECT phone to a Mitel 5000. This phone will be running over the internet. I was able to get it to register by setting Disable Domain Validation to Yes and it now works perfectly for outgoing. When you try to call that extension though you get an error that the phone is busy or it rings on the caller's side but not on the DECT phone. The SIP log on the RFP 12 shows no entries when an incoming call is attempted so the calls don't seem to be hitting it at all.

In the SIP Phone Group I tried setting the IP Address to the WAN IP where the RFP 12 resides. I also tried forwarding port 5060 to at the  RFP 12 end to the base station. Nothing has worked.

What little detail must I be missing?

Thanks!