Messages

1

SIP On Mitel / Re: 6867i 6.2 Firmware Interesting Issue

« on: March 27, 2024, 10:11:13 AM »

Found part of the issue, the Outbound proxy server being a URL was causing the phone some issues. Based off of the PCAP I did where I saw no registration attempts this leads me to believe it is a DNS issue as it cant resolve our URL to an IP thus has nowhere to send a registration attempt to. The odd part is our provisioning server is configured as a URL as well so DNS must be working if it grabs configurations just fine.

Rolling back to pre 6.X firmware also resolves the issue and the phones register just fine. Anyone know if there were any kind of DNS changes in the 6.X firmware?

2

Non-Mitel Chatter / Re: eFax service

« on: March 21, 2024, 09:49:22 AM »

Great to hear, I ended up getting our Canon MFPs configured for FAX server which is a direct replacement for regular FAXing. So now the MFPs send an email that gets routed to our XMedius servers whenever an end user is sending a FAX. Process is seamless in terms of user experience except now they don't hear the dialtone and FAX tones as the FAX is establishing anymore which throws people off.

3

SIP On Mitel / Re: 6867i 6.2 Firmware Interesting Issue

« on: March 21, 2024, 12:09:39 AM »

Yep tried that as well, still no dice. Phone pulls the config from our server but just 503 on registration but not sending anything out on the network at all for SIP traffic. Was just curious if there is an issue with the 6.2 firmware that is maybe known.

4

Introduction and Announcements / Hello from New England

« on: March 20, 2024, 06:26:13 PM »

Hello everyone,

Just someone that is fairly new to telecom (7 years now which is new compared to a lot of folks I see/work with). I mostly work on VoIP platforms (Broadworks, Adtrans with Asterisk, Genesys Cloud, OneCall) but dabble in some TDM stuff here and there with Pointspan and prior to that a lot of PRI/T1 handoffs from Adtrans to Mitel/Avaya/Nortels. Currently my only exposure to Mitel is that we use their IP phones (68XX series) where I work and we have quite a few of them (5k+)

Good to be here and hope to learn a bit more and talk to some of the people in the industry!

5

Non-Mitel Chatter / Re: eFax service

« on: March 20, 2024, 05:45:12 PM »

Another vote for opentext. We are running XMedius 9.0 (a bit older at this point and non cloud), it works great and we have been getting rid of our Centrex lines and lines off of our Audiocodes ATAs in favor of transitioning them to Xmedius.

6

SIP On Mitel / Re: Alarm lines on ATA's

« on: March 20, 2024, 05:38:40 PM »

Aren't these just ATAs anyways? We worked with a few companies that offered POTS replacements and it was just ATAs with SIP registrations and a cellular backup, we ended up having the same amount of issues with them so we opted to go back to using Audiocodes ATAs for our elevators/alarm lines and have those working pretty well.

7

SIP On Mitel / 6867i 6.2 Firmware Interesting Issue

« on: March 20, 2024, 05:36:30 PM »

So we recently started upgrading to 6.2 firmware for our 5k or so Mitel phones from 4.0. We got through about 1000 phones without any issues but a small batch of 20 phones in this latest push ended up having some issues registering. Configuration doesn't change, the phones don't fail the upgrade as they show they are on the 6.2 load but for some reason they all display 503 for registration status which indicates a server issue.

I tested from our SBCs to the phones and confirm that UDP 5060 is open as I get a 200OK response to an OPTIONS ping. Downgrading them back to 4.0 gets them to register again. I set logging appropriately in the troubleshooting section but the log files all show up as 0KB for some reason. I did also do a PCAP from the SBCs and can confirm no registration attempts or any traffic at all from the phones to our SBCs. Doing a capture from the phone side for all ports shows only my port 443 (Web GUI) traffic and nothing for SIP at all. Anyone ever run into anything like this and have any advice?

8

Aastra - MiVoice Office 400 and MiVoice MX-One / Re: Mivoice 400, 69xx SIP phones, DHCP, voice VLAN and Fortinet

« on: March 20, 2024, 05:29:15 PM »

You have to make sure that wherever the SMBC connects to your network stack that the VLAN is tagged between SMBC and the Switches so that it can provide DHCP when the phones broadcast requesting one. As long as the phones voice vlan is the same VLAN the SMBC is tagged on then the DHCP request which is a broadcast from the devices will reach the SMBC and it should assign an IP address to the phones.