locked
Issue integrating lync 2013 standard edition with Avaya aura 5.2. RRS feed

  • Question

  • Hi,

    We have configured Lync standard edition along with edge server everything is working fine and now we are trying to integrate the same with Avaya aura 5.2 using the step by step instructions available in the link mentioned below (Lync Side). www.microsoft.com/en-sa/download/details.aspx?id=41152

    Avaya side configuration shows trunk is in-service, however calls are not forwarded to avaya and I could not see any events logged in lync server for the activity. We tried telnetting 5060 port, but it is not letting to do so.

    What we want to achieve here is, whenever a call is placed or received in Avaya, it should simultaneously ring is Lync and vice versa.

    Please help us in the finding the correct solution.

    Thanks,

    Wednesday, November 4, 2015 5:07 AM

Answers

  • Hi,

    the issue is resolved.

    I re-assign certificate and everything start working. but is it required to reassign certificate each time I make any change to topology or in the trunk configuration.

    thanks a lot for the help.

    Regards,

    • Proposed as answer by Eason Huang Monday, November 23, 2015 8:50 AM
    • Marked as answer by Eason Huang Friday, December 4, 2015 7:48 AM
    Wednesday, November 18, 2015 6:22 PM

All replies

  • Hi,

    From Lync Server side, you need to normalize number to E.164 format, then route it to the suitable trunk to PSTN gateway.

    You can test if the call fail or successfully route to trunk by using Lync Server Control Panel--Voice Routing--Test Voice Routing. If it shows successfully without issue, then the number may fail on the PSTN Gateway side.

    Make sure both Lync Server Mediation Server side and Gateway side use the same port (in your case, port 5060).

    On Avaya aura 5.2 side, make sure inbound and outbound route set correctly.

    Best Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Eason Huang
    TechNet Community Support

    Thursday, November 5, 2015 7:44 AM
  • Hi,

    thanks for the reply, as you suggested above I have test the same with voice routing by 4 digit extension every thing comes ok however when I check the same using Test-CsPstnOutboundCall I got below mentioned error. I checked everything in voice policy, dial plan etc. everything is exactly the same as it is mentioned in the document I referred. 

    ErrorCode=12001,Source=FE-01.mydomain.com,Reason=User Policy
    does not contain phone route
    usage,appname=OutboundRouting,useruri=sip:testuser@mydomain.com
    Microsoft.Rtc.Signaling.DiagnosticHeader

     correct voice policy is defined in the user property. hope for your soon response.

    Regards,


    Thursday, November 5, 2015 3:53 PM
  • Telnet from Lync to Avaya 5060 is working?

    You can also use Wireshark on the Lync Mediation server to see, if traffic comes from Avaya.

    Routing from Avaya to Lync and vice versa are configured correct. (Avaya Trunk routing and Lync Voice Policy etc.)


    regards Holger Technical Specialist UC

    Thursday, November 5, 2015 4:35 PM
  • hi,

    yes I am able to telnet on 5060 port. i have checked with wireshark there is no traffic flow only a few echo request and reply.

    on the lync side i have configured the trunk with ip address then route and voice policy which is mapped with user.

    Regards,

    Thursday, November 5, 2015 5:06 PM
  • OK. can you run the debugging tool on mediation server and check what's the error that you get there?. Did you configure TCP on the topology and configure the port as 5060?. By default, TCP and port 5060 is not enabled.


    http://thamaraw.com

    Thursday, November 5, 2015 5:56 PM
  • Hi,

    Sorry for the delay. Yes, I have configured TCP in topology with port 5060 for both pstngateway and mediation server. 

    I have checked with debugging tool and I found nothing. However, if I check with outbound routing using (Test-CsPstnOutboundCall -TargetFqdn fe-01.domain.com -TargetPstnPhoneNumber "1666" -UserSipAddress "sip:jkhan@domain.com" -UserCredential $cred1) I do get a call in lync but not on Avaya. Also in the debugging tool it shows below mentioned logs.

    TL_VERBOSE(TF_COMPONENT) [4]50B8.6E40::11/09/2015-10:55:40.591.0012696c (OutboundRouting,ClusterPingEngine.TimerCallback:clusterpingengine.cs(221))(0000000001205A74)Enter TimerCallback
    TL_VERBOSE(TF_COMPONENT) [4]50B8.6E40::11/09/2015-10:55:40.591.0012696d (OutboundRouting,ClusterPingEngine.GetQueuedEvents:clusterpingengine.cs(286))(0000000001205A74)No events to process
    TL_VERBOSE(TF_COMPONENT) [4]50B8.6E40::11/09/2015-10:55:40.591.0012696e (OutboundRouting,ClusterPingEngine.ScheduleTimer:clusterpingengine.cs(309))(0000000001205A74)Enter
    TL_VERBOSE(TF_COMPONENT) [4]50B8.6E40::11/09/2015-10:55:40.591.0012696f (OutboundRouting,ClusterPingEngine.ScheduleTimer:clusterpingengine.cs(349))(0000000001205A74)Exit
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126971 (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(289))[320535948]Enter
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126981 (OutboundRouting,EmergencyCallHelper.IsEmergencyCall:emergencycallhelper.cs(38))IsEmergencyCall = False
    TL_NOISE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126983 (OutboundRouting,Settings.GetMatchingVacantNumberEntry:settings.cs(323))Checking for Vacant number entries for +96612345671666
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126984 (OutboundRouting,NumberRangeListT<>.GetMatchingRange:numberrangelist.cs(235))(000000000369552A)No matching range found.
    TL_NOISE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126985 (OutboundRouting,Settings.GetMatchingVacantNumberEntry:settings.cs(363))No matching Vacant Number Range found.
    TL_NOISE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126988 (OutboundRouting,Settings.GetMatchingCPSEntry:settings.cs(291))Checking for CPS entry for +96612345671666
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.00126989 (OutboundRouting,NumberRangeListT<>.GetMatchingRange:numberrangelist.cs(235))(000000000309092D)No matching range found.
    TL_NOISE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.489.0012698a (OutboundRouting,Settings.GetMatchingCPSEntry:settings.cs(316))No matching range found
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.494.0012698d (OutboundRouting,RoutingHelper.AddHeaderIfNotAlreadyPresent:routinghelper.cs(169))[320535948]Adding ms-forked header with value true
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.494.00126993 (OutboundRouting,RoutingHelper.AddHeaderIfNotAlreadyPresent:routinghelper.cs(169))[320535948]Adding ms-privacy header with value id
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.494.00126996 (OutboundRouting,RoutingHelper.RemoveHeaderIfPresent:routinghelper.cs(202))[320535948]ms-vm-escape-timer header not present request.
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.494.00126997 (OutboundRouting,EmergencyCallHelper.IsEmergencyCall:emergencycallhelper.cs(38))IsEmergencyCall = False
    TL_ERROR(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.495.00126999 (OutboundRouting,ExceptionWpp.WriteLine:exceptiontracer.cs(51))An exception 'Microsoft.Rtc.OutboundRouting.OutboundRoutingException' was thrown at '   at Microsoft.Rtc.OutboundRouting.OutboundRoutingDispatcher.PrepareNewRequest(OutboundRoutingTransaction transaction, String userUri, String policyAssignment, IList`1 usages, String policyName)
       at Microsoft.Rtc.OutboundRouting.OutboundRoutingDispatcher.RouteNewRequest(OutboundRoutingTransaction transaction, String callerUri, String callerPolicyAssignment, IList`1 pstnUsages, String policyName)'. Message 'No phone usage found for sip:jkhan@domain.com'
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.495.0012699d (OutboundRouting,ORTransactionTimer.RemovePendingTransaction:ortransactiontimer.cs(255))(000000000296F3C1)Enter
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.495.0012699e (OutboundRouting,ORTransactionTimer.RemovePendingTransaction:ortransactiontimer.cs(262))(000000000296F3C1)Global timer stopped.
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.495.0012699f (OutboundRouting,ORTransactionTimer.RemovePendingTransaction:ortransactiontimer.cs(267))(000000000296F3C1)Exit
    TL_VERBOSE(TF_COMPONENT) [4]50B8.3534::11/09/2015-10:55:42.495.001269a0 (OutboundRouting,OutboundRouting.OnRequest:outboundrouting.cs(292))[320535948]Exit

    PS C:\Users\qccadmin> Test-CsPstnOutboundCall -TargetFqdn fe-01.domain.com -TargetPstnPhoneNumber "1606" -UserSipAddress "sip:jkhan@domain.com" -UserCredent
    ial $cred1

    Target Fqdn   : fe-01.domain.com
    Result        : Success
    Latency       : 00:00:11.0149905
    Error Message :
    Diagnosis     :

    please help me with these I have spent hours but found nothing to overcome with these.

    Regards,

    Javed Khan.

    Monday, November 9, 2015 11:12 AM
  • Hi,

    From the log above description, it seems that the E.164 format number +96612345671666 not be accepted by Avaya side. Please make sure that Avaya accept E.164 format number without issue. You can double check the inbound and outbound route from Avaya side.

    Best Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Eason Huang
    TechNet Community Support

    • Proposed as answer by Eason Huang Monday, November 23, 2015 8:50 AM
    Thursday, November 12, 2015 7:36 AM
  • Hi,

    the issue is resolved.

    I re-assign certificate and everything start working. but is it required to reassign certificate each time I make any change to topology or in the trunk configuration.

    thanks a lot for the help.

    Regards,

    • Proposed as answer by Eason Huang Monday, November 23, 2015 8:50 AM
    • Marked as answer by Eason Huang Friday, December 4, 2015 7:48 AM
    Wednesday, November 18, 2015 6:22 PM