"Out of Service" when dialing UM pilot number

[probichaux]

I loaded 7.1 UR2 on my 3300 and am now setting it up to work directly with Exchange 2007 UM. To do so I've been using the Mitel instructions, including the following:

- created a network element using the FQDN of the Exchange server
- created a SIP peer profile for the Exchange server, using trunk 1 and setting the session timer to 0
- set trunk service 1 to absorb 0 incoming digits
- created a route assignment to tie route 3 to the Exchange SIP peer and digit mod #1
- edited digit mod #1 to absorb 0 digits
- created a pilot number in ARS Digits Dialed Assignment (using 1300, the Mitel-recommended default) pointing to route 3

The result: when I dial 1300 (or *130, the system speed dial I set up), I get a fast busy and "OUT OF SERVICE" on the 5340. The Exchange logs don't show a call attempt, so presumably I've done something wrong with the routing. Any guesses what?

 

[kwbMitel]

Members of Trunk group?

*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.

 

[probichaux]

None defined. I created a new trunk group, but when I try to assign trunk 1 to it, I get a popup saying "specified trunk not assigned.

 

[kwbMitel]

Did you not create the trunk?

or maybe you created with a different number range?

*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.

 

[probichaux]

I notice that after I installed the 7.1 UR2 load, my existing analog trunk definitions are gone and I can no longer place outgoing calls using the two analog lines I have connected. I didn't explicitly create a new SIP trunk. How do I do that?

 

[kwbMitel]

Sorry, I've never worked with SIP.

I was only speaking to your ARS issue.

Now that you know the issue, start a new thread.

*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.

 

[probichaux]

The problem here was twofold:

- when creating the SIP peer I put in the FQDN of the Exchange server as the SIP registrar. Don't do that. Once I fixed it, I started getting "ACCESS DENIED" messages on the phone.
- this was because the COS options "Public Network Access via DPNSS" and "Public Network to Public Network Connection Allowed" were both off in COS 1. Once I enabled them, boom! works great.