Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bojo387

Pages: [1] 2 3 ... 19
1
I've updated the title for you.

2
What do the maintenance commands LOCATE EXTENSION and LOCATE NUMBER tell you?

3
As you suspected, the Analog-FXS (EX-Controller) isn't doing a full hold as the flash + FAC doesn't work. Therefore, the held call cannot be retrieved remotely.

I am now waiting for Mitel to fix the issue. It looks like a SIP issue to me in general since the EX-FXS, Generic SIP and Analog-AG are affected. (These are all SIP anyway).

4
What's the error you get? Maybe it's been locked out due to multiple attempts?

5
I've opened a ticket with Mitel so hopefully, I get a resolution.

For the FXS, as soon as I hit flash, the call is put on hold. Dialing the hold FAC after a flash does nothing....

I'll keep this thread updated once I hear back from Mitel. 

6
Thanks, Ralph.

The problem with the EX-Controller is that the analog interfaces (FXS and FXO) are converted to SIP so some ONS functions, I understand, work differently. I will try putting the call on hold via FAC when I'm back at the office but I recall it not working... as soon as I hit the flash key, the call already gets put on hold. Another flash retrieves the call. In hold - retrieve though, I can also use the retrieve FAC on the same extension that initiated the hold.

I'll dig up more.

7
I'm trying to remotely retrieve an internal call that was put on hold by either a Generic SIP phone or the EX-Controller's FXS but fail to do so. However, I can remotely retrieve any call held by a MiNET user. The COS, SIP device capabilities, Interconnect no. are the same for my test users.

Call Hold done by MiNET - Remote Retrieve is OK by MiNET, Analog-FXS, Generic SIP
Call Hold done by Analog-FXS or Generic SIP - Remote Retrieve is NOK by MiNET, Analog-FXS, Generic SIP

The message on the MiNET phone says Not Allowed.

I simply follow the FAC<number of who placed the call on hold>.

Any suggestions on what I should check?

8
Mitel MiVoice Business/MCD/3300 / Re: Mitel 6940 Phone firmware
« on: July 16, 2025, 12:50:56 AM »
Put the phone in web recovery again and upload a different firmware version.

9
Thanks, Ralph!

And Congratulations, Tech Electronics! Heck Yeah, Mate!

10
Introduction and Announcements / Re: MitelForums.com is Closing.
« on: July 02, 2025, 12:03:49 PM »
Sad news... But I appreciate the ride with you all!

All the best to everyone!

11
Aastra - MiVoice Office 400 and MiVoice MX-One / Re: 6970 reset
« on: June 15, 2025, 10:27:43 PM »
It looks like it is SIP FW. This is from the Admin guide:

Note: For Web Recovery Mode on 6970 IP Phone:
1. Tap Settings > Advanced > Reset and choose Factory Default.
2. Open Recovery mode by pressing Directory and End button during reboot.

I hope this helps.

12
When you say it doesn't log in, what exactly happens?

13
It doesn't matter what is serving up DHCP really... If you are using VLAN's you will need two DHCP scopes/servers. Using option 43, you define it as a ASCII text or "Custom Text" option.

In the default data VLAN, you give it an option that essentially does nothing except tell the phone to move to the voice VLAN (VLAN 6 in this case, using an example address of the MiVB server at 192.168.192.10 as call and tftp server, adjust as necessary)

id:ipphone.mitel.com;sw_tftp=192.168.192.10;call_srv=192.168.192.10;vlan=6;l2p=6;dscp=56

Then if you are not using the Mitel itself in the voice VLAN for DHCP, you set the DHCP server for that VLAN to NOT have a VLAN tag.

id:ipphone.mitel.com;sw_tftp=192.168.192.10;call_srv=192.168.192.10;l2p=6;dscp=56

I still say the better way these days is to use LLPD-MED to "move" the phone to the voice VLAN, than only one DHCP scope is required in the voice VLAN.

Quote
I still say the better way these days is to use LLPD-MED to "move" the phone to the voice VLAN, than only one DHCP scope is required in the voice VLAN.

This also speeds up the boot process and removes a point of failure.

Alright, thanks for the rundown. I'll be trying this out.

14
Mitel MiVoice Business/MCD/3300 / Re: MiVB 8 to 10 upgrade path
« on: May 06, 2025, 11:35:30 PM »
Sorry but no intention to hijack this thread. Just that topic is related to my question. But what would be the best way to migrate (replace) MiVB using an old CX controller to EX + AG41XX? I don't know the version of the current system running on the CX but I'm assuming it is old.
My training only started from V10.0 and I'm only familiar with the VA, EX-Controller, and SMBC Controller.
Is it possible to take an backup from the CX system and import that into the new MiVB on EX for a baseline to re-program?

15
I appreciate the responses  :)

We always just use DHCP option 43...

Do you have a dedicated voice VLAN? The phones support LLDP-MED auto voice VLAN and you can just run the DHCP server in the Mitel... That is the easiest and recommended way these days.

Option 43 would be easiest for me to try as we already do that for MX-ONE/M400 in our lab using a Windows DHCP server. I can also use VLANs for testing... I understand that LLDP-MED is on the network switch side, right? I'll take a look at that.

*EDIT: I realized you probably mean to use the MiVB as the DHCP server with option 43...

I think the 2012 setup is still valid, it is a bit hard to actually do IMHO

That's what I thought when I saw it too. I did manage to find the DHCP Helper in github so I'll give it a shot soon.

Pages: [1] 2 3 ... 19