Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel MXe 3300 / Exchange 2007 UM issue

Status
Not open for further replies.

RDECIT

Technical User
Apr 28, 2009
376
GB
I have a working setup where I have two pilot numbers (one for exchange voicemail the other for exchange AA) Both pilot numbers work but for some weird reason most (but not all) of my handsets don't appear to work with it. When I say don't work, when asked to enter my pin or mailbox number, it doesn't register any key presses and then asks if I'm still there. Also if I try the 'speak the persons name' it doesn't hear me. A small number of sets do work, so I'm a little confused, I've checked the COS and they are all the same.

Mitel is 3300 MXe MCD 4.2 - Exchange 2007 SP2
 
Connection between 3300 and Exchange via SIP?

The single biggest problem with communications is the illusion that it has taken place.
 
Sorry should have included that info. Yes the link is SIP.
 
Are the working and non working sets all on the same subnet? Is there any type of firewall or ACL between the network and where the exchange server is? Have you gone through any Mitel provided documentation for SIP integration between a 3300 and Exchange 2007? Finally any difference in the exchange programming between the users experiencing and those not experiencing the problem?

The single biggest problem with communications is the illusion that it has taken place.
 
Lou, I'm going through this now.

Working and none working sets are on the same subnet
The Mitel and Exchange servers sit on different subnets and routing is done through a gateway which is a firewall (SonicWall)
I had followed some Mitel documentation, but never found any specific programming guide. I'll take a look for that now.
Finally no differences in Exchange programming.
All sets working and non, has the same COS and COR.
 
COS and COR won't be an issue more likely the sonicWall.

The single biggest problem with communications is the illusion that it has taken place.
 
Treid some more sets and there is a slight trend appearing.

Our technical office, the users are all ACD users, none work.

Our sales office (in the same building) are hotdesk users and all apart from one work.

All sets are 5340's.
 
On the ACD sets. Does it make a difference if they are logged on or logged off? On the hotdesk sets does it make a difference if the hotdesk user is logged in or logged off?

The single biggest problem with communications is the illusion that it has taken place.
 
On both sets logging out has the same effect, ACD sets don't register voice or key presses and Hotdesk enabled do.

What are the chances of it being the sets themselves.
 
Sorry do you mean an ACD set that is not logged in still can't access exchange but a hotdesk set can access exchange whether someone is logged in or not?

The single biggest problem with communications is the illusion that it has taken place.
 
You're hurting my brain.

That said the chances of only the ACD sets being defective is low. Are you using hotdesk ACD agent ID's or are the agent the traditional method where the set is programmed as an ACD set?


The single biggest problem with communications is the illusion that it has taken place.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top