Recent Posts

Pages: [1] 2 3 ... 10
2
Hi, we're currently doing that for a 5000 + users. We're now at the point of fine tuning. Calls works fine, inside to outside, outside to inside (almost), but I have a very anoying thing happening to me and I have no clue what is the cause.

Here's my set-up resume: Mitel pbxs, Unify SBC, Teams office 365 infra. Got my trunk/SIP peer profile/ars route worked out, but when I was doing some testing we couldn't place call to certain cellphones providers.

In the Call routing tab of my SIP peer Profile, I setted the "Private SIP Trunk" to Yes. Since then, I can call everywhere without problem, but since the modification, I lost the ring back tone when we place a call from an device to my Teams extension. To fixed that, in the "Signaling and Header Manipulation", I changed "Require Reliable Provisional Responses on Outgoing Calls" to No and I got the ring back tone again BUT NOW instead of the extension number I see on the phone's acd screen "Private Ringing".

Look like it's a never ending series of I fixe something to create an other problem.

thanks
3
Join this session to gain insights on how to maximize your MUG membership.  Discover why so many of your peers utilize this exclusive access to Mitel resources, product demos, trainings, product updates and networking.

Webinar:  Maximize Your MUG Membership: Resources at Your Fingertips
When: Thursday, November 14 at 10am CST / 4pm UTC

REGISTER:  https://mitelusergroup.org/events/mugmembershipoct2024/
4
Hello,

I have tried all those commands, but they don't work. (And I have tried this at multiple customers)
For now I have feedback from the customer that phone is ringing again.
I have had an answer form the MIVB guy from Mitel NL in the past:
If you have a phone that is registered on the secondary controller and you call  the number, the * will move back to primary element.

I have done this, and this seems to work, but this is not a solution for all customers as not all customers have licenses on the secondary controller to make a phone.

Still strange that this * does not move with the IP address of the phone, it was clear that the phone was on the primary controller (again?)

Regards

Jo
5
HST STATUS_HANDOFF should tell you if there's any active resiliency in effect. Run it on both and compare.

You can also force the secondary to push all failed over sets back via the "hsPushback" shell command, but getting to the shell will be a bit different depending on your software version (VxWorks or MSL/uBoot). There's a few other commands as well, listed in the Online help under Maintenance -> Commands -> HandoffService Shell Commands
6
Hello All,

I have a question about the location of the * when you do a locate feature extension.
Situation:
- locate feature extension on primary controller has the * on primary element
- locate feature extension on secondary controller has the * on secondary element (see attach printscreen)
- according to the All IP Telephones form on the primary controller, the phone has an IP and is in service on the primary controller
- according to the All IP Telephones form on the secondary controller, the phone is out of service and doesn't have an IP.

Could the * on the secondary controller be the cause that the phone is not ringing when a call is offered to a ring group (ring all) on the the primary controller?
If so, is there a way without rebooting the secondary controller to get the * back on primary element?
I have asked this a few time at Mitel as well but the response was never on point.

Regards

Jo
7
Mitel MiVoice Business/MCD/3300 / Re: Trouble With RTP
« Last post by ralph on Yesterday at 09:34:28 AM »
Not gonna happen without an MBG as an anchor point.
After the call is set up then the audio sent directly from endpoint to end point.
Without an MBG to act as an endpoint, the audio won't know how to get to the external number.

Ralph
8
MiVoice Office 250/Mitel 5000 / DECT 112 Repeaters
« Last post by gjfruita on Yesterday at 08:32:21 AM »
Hello Everyone,

I am trying to setup a repeater for the Mitel DECT 112 Base station

but upon going to the add repeaters section and  placing both DECT sync mode on "Local Automatic" or Manual, the repeater is not being detected.

On manual, it does not ask me to input the mac nor IPEI

9
Mitel MiVoice Business/MCD/3300 / Re: MiVB 8 to 10 upgrade path
« Last post by acejavelin on October 29, 2024, 08:59:03 PM »
You have to use the Migration Tool to go from 8.1 to 9.0 first, then you can upgrade to whatever...

The OS has to to be upgraded to upgraded to Linux going from 8 to 9 and the partitions reformatted and boot code changes completely... it's changes a ton of stuff under the hood, it's all automated but takes some time.

There is no way to go to any version above 9 from any version below 9 directly, you must go to 9 first.
10
Mitel MiVoice Business/MCD/3300 / Re: MiVB 9.2 MXIII curious about 6940W
« Last post by sarond on October 29, 2024, 06:54:23 PM »
You should be able to program as a standard 6940 to get it working.

I would also recommend uploading the firmware into the tftp folder of the MiVB
Pages: [1] 2 3 ... 10