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 - jackpod

Pages: [1] 2
1
Mitel MiVoice Business/MCD/3300 / Re: Exchange 2010 MWI
« on: December 09, 2010, 01:00:19 PM »
Update... Keeping in mind that I am still on Exchange 2007 using a 3rd party app called Exchange MWI from AaronSoftware and 4.2 on my 3300. I was able to get MWI working at last.

2
Mitel MiVoice Business/MCD/3300 / Re: Exchange 2010 MWI
« on: December 08, 2010, 04:02:18 PM »
Ok, great info - minus the fingers :) since I am still on exchange 07 and am not impacted by SP1 for exch 2010, maybe I can get this working until we upgrade to to 2010... First not-so-good thing I have heard about SP1, I am running it on a couple other networks but the PBX is not Mitel and SP1 really stabilized 2010, although the speech to text can be quite amusing, especially if the caller has an accent

3
Mitel MiVoice Business/MCD/3300 / Re: 4.2, Exchange and MWI
« on: December 08, 2010, 03:57:39 PM »
Thanks BW, I'll continue on your thread....

4
Mitel MiVoice Business/MCD/3300 / 4.2, Exchange and MWI
« on: December 07, 2010, 01:53:27 PM »
So I upgraded to the latest 4.2 for my 3300, am using Exchange 2007 Unified Messaging as my voicemail and a 3rd party app from AaronSoftware called Exchange MWI Enterprise and I still can't get MWI to function. Exchange UM has been working fine for over a year, so obviously my network elements and SIP peers are working correctly. According to Mitel anything above 4.1 supports unsolicited sip notification and works with Exchange 2010 and according to the 3rd party developer, this application works exactly the same as exchange 2010.

When I run the test app from the 3rd party app I am getting the error "SIP/2.0 404 Not Found" and we are just not ready to migrate to exchange 2010....

5
I have moved my main campus from an SX-200 to a 3300 and the security department notified me that they no longer have the 911 alert that they had with the SX200. Previously if any deskset dialed 911, it triggered an alert on their phone and they could see on the display which room and extension placed the 911 call. I did a search for 911 detection and reporting in the 4.0 technician handbook, but with no results. Is the feature called something else now? I really need to get this working

6
Mitel MiVoice Business/MCD/3300 / Re: access denied on system speed dial
« on: September 17, 2010, 01:43:57 PM »
7351 routes to an exchange auto attendant, which is a sip trunk (network element). Yes it fails on both internal and external calls

I'll try the override and I'll check the COS and COR

7
Mitel MiVoice Business/MCD/3300 / access denied on system speed dial
« on: September 16, 2010, 01:56:21 PM »
I am trying to forward to a speed dial and when it transfers I get an access denied... What I am trying to do. I created a single line on my phone as 4394. In system speed call assignment I created 333 to 7351 no to override, type s/c. in call rerouting always alternative assignment, I created 9 as reroute, reroute, reroute, reroute, directory number 333, in call rerouting first alternative, all fields are "this" with directory number 333. in call rerouting assignment, i set 4394 first alternative to 9. I can dial 7351 it works, I can dial 333 it works, but when I call 4394 it rings 5 times and when it transfers it I get "access denied" what did I forget?


8
I have a remote campus in rural northern arizona (Page, Arizona) The campus is small and I have an SX200 and 1 peripheral node and 19 desksets. The incoming lines are 5 POTS lines into a LS/GS card. I only took over the telephony last July and it came to my attention that the Page campus has never had Caller ID in the 20 years it has been in existence. I have the SX200 talking to my home campus via 4 IP Trunks over my 1.5mb mpls. They were using a very old version of CallXpress (version 3 running on OS2) With my implementation of a 3300 at my home campus and moving to Exchange UM, is what brought the lack of Caller ID to my attention because all voicemail and missed call notifications come to Outlook as anonymous caller. This is causing issues since occasionally a VM is lost because if a deskset is called, and not answered it is forwarded to a speed dial which routes it 130 miles to the exchange server here at the home campus (Flagstaff), then sent as an email with VM wmv file back to the exchange server in Page. With all calls showing as anonymous caller, the staff at page has no way to know who tried to call them.

Now that the background is laid out, what could be causing lack of caller ID? have there been more than one version of LS/GS cards for the SX200 or a firmware upgrade that supports CID? I might point out that before I moved to IP Trunking, we had E&M tie lines and 4 digit dialing between campus's did not have CID, now with IP Trunking 4 digit dialing displays CID just fine. I had someone at the Page campus call me from the outside and CID came thru just fine, which would make one assume that the pots lines do have the CID service.

Any ideas, suggestions are welcome.

Keep in mind that Page Arizona is extremely rural, I was lucky to obtain a pair of wires for the MPLS, service is minimal

Thanks!

Jack

9
Mitel MiVoice Business/MCD/3300 / 3300 and polycom ip 6000 conference phone
« on: February 24, 2010, 04:47:09 PM »
I am trying to get a polycom soundstation ip 6000 conference phone to connect to my 3300. I got a doc from mitel but it isn't the greatest of docs. Any one have any of that "been there, done that" experience? I still am not sure which device is not configured properly

Ideas, suggestions?

Thanks!

Jack

10
Mitel MiVoice Business/MCD/3300 / Re: Call Rerouting?
« on: January 13, 2010, 04:51:36 PM »
I got it to work, the call rerouting scheme on the 3300 is a little strange, but it is working...

Now to plan how to move 325 desksets from the sx200 to the 3300 without interrupting service  :-\

11
Mitel MiVoice Business/MCD/3300 / Call Rerouting?
« on: January 13, 2010, 03:14:18 PM »
So I got a new bay control card for my spare peripheral node and put a couple digital line cards in it and have a couple of 4025's and a 4150 working, setup a couple digit strings in the 200 and setup a route so the "added" desksets can dial anything on the 200 install or the PSTN. On my 200 side desksets I have call forwarding set to a speed dial routed to a SIP trunk and am using Microsoft UM. On the 3300 it looks like the speed dial functions of the 200 are now called "call rerouting"? or maybe I am missing something. I tried to go into the first alternative and put my SIP trunk number (73xx) in the directory number field and It errors out saying the directory number is not allowed

So I guess my question is how would I forward busy/no answer to system speed dial 73 for desksets that are attached to the 3300?

12
sorry for the delay in answering but with vacation and holidays and all :0

I haven't seen what you describe, but all my users have a multiple appearance on their phones. Is your operator a person or are you using the exchange auto attendant?

13
A couple things I found, in the network elements form make sure the SIP Peer Status is set to always active (it defaults to auto) otherwise the SIP Trunk won't come up

and the docs say to enable Mitel Proprietary SDP, this has to be set to no or Exchange won't answer.

I have it working and have several people on a pilot before I roll it out campus wide. It is pretty much functional out of the box

Now to learn about the UM features of Exchange and get my Auto Attendants working :)


14
Ralph, thanks for the docs, I now have my sip trunk up, but exchange won't answer when I dial the sip peer number. There appears to still be a lot of differences in the docs for version 9 versus version 10. The sip peer page in the document looks nothing like the same form in the switch

15
I found the how-to on the web but it is for mitel software version 7.1 ur2 I am running release 4.0 10.0.0.10_2 and it looks to have a lot of changes. Is there a newer "how-to" out there?

Pages: [1] 2