Exchange AA transfer to extension to Lync 2013

Question

I'm having issues getting the Exchange AA to transfer to extensions when using key mapping. Basically you can say a person's name and it will transfer to their extension just fine but not with the key mapping.
We are using Exchange 2010 SP3 RU4 with Lync 2013 Hosting Pack.
I found the issue but not sure how to go about resolving it.
Lync User: [email protected]
Lync Extension: [phone];ext=151
Exchange Extension: 151
Dial plan in Lync 2013 will convert 3-digit numbers to: [phone];ext=$1 for these users
Each company has their own dial plan. This particular dial plan in Lync translates the 3-digit to the full number. The problem is the transfer from Exchange AA to Lync doesn't seem to use the user's dial plan. I also cannot put a translation on the Exchange
side to do this type of format: [phone];ext=$1
It looks like with the key mapping it is trying to transfer to this:
REFER-TO: <sip:151;[email protected];user=phone>
P-ASSERTED-IDENTITY: <sip:[email protected]>
But of course that doesn't exist. The SIP for this user is sip:[email protected]
I ran the Lync Debugging utility and saw this:
ms-diagnostics: 14011;reason="Called Number translated";source="LYNCFE0101.COMPSYSCLOUD.COM";RuleName="Keep All";CalledNumber="151";TranslatedNumber="151";appName="TranslationService"
Start-Line: SIP/2.0 403 Forbidden
From: <sip:[email protected];user=phone>;epid=786443AA96;tag=61bfdb74d3
To: <sip:151;[email protected];user=phone>;tag=7C193436618B4C0FD1DD5B0D9EA788A5
Call-ID: d71f8c3b-0b1e-45c5-b917-0bb71ab9e240
CSeq: 16062 INVITE
Via: SIP/2.0/TLS 10.1.15.6:50244;branch=z9hG4bKf79f7414;ms-received-port=50244;ms-received-cid=BC2600
Content-Length: 0
ms-diagnostics: 12004;reason="The user is not authorized to call the specified number or none of the
routes have a valid gateway configured.";source="LYNCFE0101.DOMAIN.COM";appName="OutboundRouting"
To: <sip:151;[email protected];user=phone>;tag=4FFA2DD9248FE7799456F95533983128
Call-ID: 92f65e8040e1453e85a09ef45bc27c18
CSeq: 16063 SERVICE
Via: SIP/2.0/TLS 10.1.15.1:61309;branch=z9hG4bK957FF7E7.C2D462B71F179899;branched=FALSE;ms-received-port=61309;ms-received-cid=AFA00
Via: SIP/2.0/TLS 10.1.15.6:50244;branch=z9hG4bK488849d7;ms-received-port=50244;ms-received-cid=BC2600
Content-Length: 0
ms-diagnostics: 1003;reason="User does not exist";destination="151;[email protected]";source="sip.domain.com"
ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=edge.domain.com;ms-source-verified-user=verified

Answer 1

Hi,
You need create a UM auto-attendant for each Lync Server dial plan with the following command:
New-umautoattendant -name <auto attendant name> -umdialplan < name of dial plan created in step 1> -PilotIdentifierList <auto attendant phone number in E.164 format> -SpeechEnabled $true -Status
Enabled
You can refer to the link of “Configure Unified Messaging on Microsoft Exchange”:
http://technet.microsoft.com/en-us/library/gg398129.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support