Show Posts
1
Mitel MiVoice Business/MCD/3300 / One way audio issue with a single site
« on: December 04, 2017, 11:05:00 AM »
Hi all. At my wits end diagnosing this one thus far...
We are running a Mitel 3300 here at this site, on version 44.0.1.26. The other site in question runs a 3300 on 40.2.0.16.
When we call that site by using their 4 digit extension, we can hear them, but they can't hear us.
If we dial their full DID, they can hear us, and we can hear them.
Normally, I'd say, well this is a networking issue, as the sites are connected via VPN and thus this would have to be a firewall and/or routing issue....except...it sure as heck does not appear to be.
They are running their site off a Model 200 Dell NSA, and we are using a 4600 series, so my thoughts have somewhat strayed to thinking maybe there is a VOIP setting we need to turn on there, but... previoulsy, we ran another 3300 from another vendor with a slightly older version of the software (same as the other site), and two way audio worked just fine.
The only changes have been to the 3300 box itself (different box, different vendor), the software it runs (new version on this end), and a VLAN change (We implemented the VLAN for voice at the same time). Now, the firewalls I can verify all have the correct setup for in and out traffic, where it's allowing what, and they all know about each other's networks including our new VLAN. We have two other sites with 3300's that talk to us internally via the same exact VPN channels with the same settings with 0 issues. It's only this one site.
Now, my boss mentioned to me that there was an issue like this when the last box was first implemented, and there was a CoS setting that had to be tweaked here for it to work. We haven't been able to find our notes (it was so long ago) and I have been pouring over everything I can to figure it out.
Settings between systems seems to match up. The only glaring difference was that in our LAN Policy (QoS) settings, Voice Signalling is set to 24, and on the old system it was 26, and on all the other sites it's 26. But the other sites work just fine, and the DHCP settings for the phones being handed out have the correct 26 setting for the same voice signalling setting. So...still not sure.
But..that being said, any ideas here? I am considering trying to race the call via the maintenance interface, but not sure how to do that, and our vendor keeps pointing us to our network settings. While it still could be something obscure, I'd still like to rule out the 3300 itself and see if there is anything offhand anyone can think about to try that won't require a reboot per say (as that would have to be done after hours, and noone will be at that site then).
I also tried placing the call to the site on hold and picked it back up, as I read that someone had that kind of issue that alluded to being a 3300 issue and not networking.
But, out of ideas at the moment. I went down the networking path a dozen times now, and everything says both sites can talk between our VLAN and theirs, etc. And again, it's the only site with an issue as such.
Appreciate any insight.
We are running a Mitel 3300 here at this site, on version 44.0.1.26. The other site in question runs a 3300 on 40.2.0.16.
When we call that site by using their 4 digit extension, we can hear them, but they can't hear us.
If we dial their full DID, they can hear us, and we can hear them.
Normally, I'd say, well this is a networking issue, as the sites are connected via VPN and thus this would have to be a firewall and/or routing issue....except...it sure as heck does not appear to be.
They are running their site off a Model 200 Dell NSA, and we are using a 4600 series, so my thoughts have somewhat strayed to thinking maybe there is a VOIP setting we need to turn on there, but... previoulsy, we ran another 3300 from another vendor with a slightly older version of the software (same as the other site), and two way audio worked just fine.
The only changes have been to the 3300 box itself (different box, different vendor), the software it runs (new version on this end), and a VLAN change (We implemented the VLAN for voice at the same time). Now, the firewalls I can verify all have the correct setup for in and out traffic, where it's allowing what, and they all know about each other's networks including our new VLAN. We have two other sites with 3300's that talk to us internally via the same exact VPN channels with the same settings with 0 issues. It's only this one site.
Now, my boss mentioned to me that there was an issue like this when the last box was first implemented, and there was a CoS setting that had to be tweaked here for it to work. We haven't been able to find our notes (it was so long ago) and I have been pouring over everything I can to figure it out.
Settings between systems seems to match up. The only glaring difference was that in our LAN Policy (QoS) settings, Voice Signalling is set to 24, and on the old system it was 26, and on all the other sites it's 26. But the other sites work just fine, and the DHCP settings for the phones being handed out have the correct 26 setting for the same voice signalling setting. So...still not sure.
But..that being said, any ideas here? I am considering trying to race the call via the maintenance interface, but not sure how to do that, and our vendor keeps pointing us to our network settings. While it still could be something obscure, I'd still like to rule out the 3300 itself and see if there is anything offhand anyone can think about to try that won't require a reboot per say (as that would have to be done after hours, and noone will be at that site then).
I also tried placing the call to the site on hold and picked it back up, as I read that someone had that kind of issue that alluded to being a 3300 issue and not networking.
But, out of ideas at the moment. I went down the networking path a dozen times now, and everything says both sites can talk between our VLAN and theirs, etc. And again, it's the only site with an issue as such.
Appreciate any insight.
