I have read through the config notes listed on the MS website.  They specify a telephone extension dial plan.  The problem is that Exchange 2013 UM won't use that kind of a dial plan.  It only uses a SIP URI dial plan.  I tried creating a telephone extension dial plan and it errors upon save.

Anyone have this working and if so, how? details please?

Thanks.

Exchange 2013 can do 3 UM Dial Plan types - Telephone Extension (default), SIP URI, E.164

Do the other UM Dial Plan types that you try to create result in the same error when saving?  If so, it sounds like you may have a permissions issue.

You can create the 3 types of dial plans, but you can only associate the Exchange 2013 server with a SIP dial plan.  I have tried it on a lab system and 2 production systems so far.  I have tried Telephone extension and E.164 as well.  the Exchange 2013 is a combined server with both the CAS and Mailbox roles.

What we are finding is that it will work IF you point the Session Manager to port 5065 not 5060.  In reading through all I can find, this issue is something that has been a round for awhile.  The config note we have looked at says the Location settings on the PBX should alleviate the issue but it hasn't.

exact error is: "

error

The dial plan 'teste164' can't be associated with the Client Access or Mailbox server. Only SIP URI dial plans can be associated with a Client Access or Mailbox server."

From http://technet.microsoft.com/en-us/library/aa996399(v=exchg.150).aspx:

"You can add Client Access and Mailbox servers to SIP URI dial plans. Client Access and Mailbox servers cant be associated with Telephone Extension or E.164 dial plans, but the servers will answer all incoming calls. "

So you may be trying to do something that is not required if you are not using a SIP URI UM Dial Plan.

Here is what is set up now:

Exch2010UM with 2 dialplans and Lync 2010 EV:

DP1 is a telephone extension dial plan set up using the SM as a gateway.

DP2 is a SIP Dial plan set up with Lync 2010 as the gateway.

Users are setup with the DP2 as their primary dial plan and DP1 as a secondary (using EUM entries).

The site is using both Avaya and Lync phones.

We are in the process of migrating to Lync 2013 and Exchange 2013.

Lync 2013 is setup and added as a gateway and works.

The issue I am seeing is that when I am in the EAC>Servers>ex13umserver properties>unified messaging I can add DP2 to the UM Call router Settings and UM Service Settings, but I can not add the DP1.

Is what you are saying is I don't need to add DP1 in those fields?

What happens when I decommission the Ex2010UM and those are not entered?

Thanks.

I think this answers my question..

"When youre installing your Client Access and Mailbox servers and deploying Unified Messaging, you dont have to associate or add Client Access or Mailbox servers to UM dial plans. Client Access and Mailbox servers answer all incoming calls and then use the UM dial plans to locate users.

However, if youre integrating Unified Messaging with Microsoft Office Communications Server 2007 R2 or Microsoft Lync Server, both the SIP and the RTP or SRTP media channels for incoming calls are handled by Lync servers and the Mailbox server. In a Lync integrated environment, you dont have VoIP gateways, IP PBXs, or SBCs. To Lync, the Mailbox server thats running the Microsoft Exchange Unified Messaging service looks just like an Exchange 2010 UM server. The Mailbox server and the Client Access server are considered trusted peers because both servers must be added to a SIP dial plan. Lync routes the incoming call using the Inbound Routing component, which uses SIP to communicate with the Client Access server and then route the call to a Mailbox server."

The UM call router etc. is only for SIP dial plans it seems.  the other dialplans are handled straightforward.

I didn't know you were in a mix environment.  In your case you might have to upgrade the 2010 UM Dial Plans so Exchange 2013 can use them.  At least that was the case with 2007 to 2010.

Did you follow the upgrade instructions here?: http://technet.microsoft.com/en-us/library/dn169226(v=exchg.150).aspx

BiggJake, we are trying to set up Avaya Session Manager against our 2013 environment and we are having issues.  We have it working against 2010 just fine.  Any chance you can help us out with configuration settings you used on the Session Manager?

What issues are you having?

I am not the telephony guy, I am the Exchange guy, but my understanding from the telecom team is that Avaya SM is establishing the call on 5060 to one of the CAS servers.  CAS is responding with a 302 redirect with fqdnofmailboxserver:5062.  However, Avaya SM still continues to try to talk to the CAS server that responded and seems to ignore the redirect to port 5062. 

In 2010, we still have issues with call pickup groups and the header information order.  Exchange is top to bottom.  Avaya is bottom to top.

I want to hear too if there's experience around this. Yeah, the diversion header is often an issue and an SBC where you can flip the order helps, but with the added cost and direct SIP mostly working people want to tend to avoid this.  Since we can't change the diversion header order on the Exchange side, can we do it on the Session Manager side or should we always be suggesting the SBC? 

More importantly, I'd like to know if people have gotten Session Manager to connect direct to Exchange 2013 when there are multiple servers involved with the new way Exchange 2013 redirects as JasonCarter noted. 

What has been the experience with pure SM and Exchange 2013 with nothing but that trunk?

Also, thanks for the resurrect on this, I'm voting helpful points to you all!

Not to resurrect an old thread but I came across this... I am pleased to say that I have this working with direct sip between my two avaya session managers and two exchange 2013 servers with no caveats. Let me know if you would like more info on the process.

Not to resurrect an old thread but I came across this... I am pleased to say that I have this working with direct sip between my two avaya session managers and two exchange 2013 servers with no caveats. Let me know if you would like more info on the process.

I would. Please share.

I would like the information as well please.

I would appreciate the information as well.

I would like information on this as well. We are moving to Exchange 2013 very soon. We have a working AVAYA SM to Exchange 2010 UM, but will need to move UM

Thank,

Jeff

Hello,

Could you please provide the instructions on how you were able to get Avaya SM and Exchange 2013 to work?

If any one have a working sollution, please share how :)