Topics

1

Mitel MiVoice Business/MCD/3300 / ARS Specific Only to a Group of SIP Phones

« on: June 06, 2013, 01:42:55 PM »

We have a group of 10 Polycom IP 7000 SIP conference phones and I'm trying to figure out how to program the 3300 such that if a user dials a 4 digit extension (7314) from the IP700 that the 3300 will actually dial the number as 92067887314. 

This would be simple enough, but the problem is all non-SIP phones need to behave differently.  The non-SIP phones need to dial that 4-digit extension directly, and not go to an outside line.

Is there any way to accomplish this?  The problem I'm running into is how to segregate the SIP phones from all the other phones such that an ARS digit dialed entry will only apply to the SIP phones.

Our vendor is saying it can't be done but I wanted to double-check here.

Thanks!

2

Mitel MiVoice Business/MCD/3300 / DigitMap for Polycom IP7000 Conference Phone

« on: March 20, 2013, 04:03:53 PM »

We have a Mitel 3300 MXe running release 5.0 SP2 PR2.  We've just installed several Polycom IP7000 SIP phones and I'm having trouble with the conferencing feature.  I removed everything in the digitmap on the Polycom and I can get conferencing to work if I hit #5 (our feature access code for conference on the Mitel), but it's kind of a clunky way to do it.  Does anyone have a digitmap that works for conferencing that I could see as an example?  I'm far from an expert on this stuff.

Thanks!

3

Mitel MiVoice Business/MCD/3300 / One-Way Audio on Internal 5240 Calls

« on: January 04, 2013, 03:32:01 PM »

We've been fighting this issue for the better part of a year now.  We have 4 3300 controllers in our main office and pretty consistently have one-way audio issues between 5240 phones.  The controllers are all on the same subnet and are all running 4.2 SP2 PR1.  This issue seemed to start when we replaced all our old 3300 controllers with the newer MXe-III (we had to upgrade the hardware in order to have capacity for enough memory to go to 10.0)  We use a separate VLAN for all voice traffic.

We have gone round and round with our vendor, who is working with Mitel to figure out what is going on.  Mitel's final determination is that we have some servers on our network broadcasting ARP requests and it's confusing the phones. 

To quote Mitel: "From the captures we can see the following:
Once the phone has received the signalling to send audio to the other destination it sends an ARP requested as a broadcast message to the network:
10359 2012-06-28 15:14:41.468495000 Mitel_12:43:f3 Broadcast ARP Who has 20.1.1.143? Tell 20.1.1.109 60  That ARP request never receives an answer, therefore the phone can not send the audio."


The ball is in our court now and I still need to determine if their conclusion is valid.  My hunch is that it isn't, as they've been running us in circles with different wire captures etc for months now and our network really hasn't changed.

I'm just posting this in case anyone has any insight that might help us get to the bottom of this issue more quickly.

Thanks!

4

Mitel Software Applications / NuPoint Auto Attendant LDAP Data Source for Extension Number

« on: September 14, 2012, 02:29:50 PM »

I am trying to figure out how to change the LDAP data source where NuPoint pulls our users' extension number for the Speech Rec feature.  The system appears to have been setup originally to pull from the "Telephone Number" field on the "General" tab in AD.  I want it to pull from the "ipphone" field on the "Telephones" tabe instead. 

On Nupoint Auto Attendant Data Source, I try to change the value in the LDAP SAA Default User Extension Attribute to "ipphone", (which should be the correct syntax for the field in AD) and force an update, but it doesn't change anything in NuPoint.  What am I missing here?  That field (LDAP SAA Default User Extension Attribute)  originally had a value of "extensionAttribute3", but when I query that in AD using Powershell, it doesn't come up with the Telephone number unless I add to the query "telephonenumber,extensionAttribute3".  If I query AD using "ipphone,extensionAttribute3" it returns the data in the ip phone field in AD, so I tried using "ipphone,extensionAttribute3" as the value in NuPoint but it still didn't make a difference.

What am I missing here?  Our vendor opened a ticket with Mitel 4 days ago and they haven't been able to come up with a solution for what I want to do.  I can't believe it should be that complicated.

I've attached a screen shot of how I think it should be set up to pull from the ipphone field, but it's not working.

Thanks!