Route from one gateway to another RRS feed

  • Question

  • I have Lync Server 2010 Standard with Edge.

    My implementatins contains 2 gateways

    • asterisk.company.local which connects Lync to PSTN
    • dv-vgate1 is AudioCodes MP gateway which connects legacy PBX to Lync

    From Lync Clients I can call to PSTN thru asterisk, can call to Legacy PBX thru dv-vgate1.

    From dv-vgate1 I can call any Lync number, but cannot reach any PSTN number.

    SIP trace on Lync Server indicates what calls from dv-vgate1 are properly normalazed, but Lync even don't tries to route call to asterisk (there's no such address in logs).

    How can I get Lync to route calls from dv-vgate1 to PSTN thru asterisk gateway?

    Saturday, January 22, 2011 6:08 PM

All replies

  • You probably assigned Lync users a voice policy that has the required routes to asterisk and allows them to dial out to the PSTN.

    When the call is coming from the legacy gateway, it uses the default policy which might not include a route to the PSTN connection through asterisk, and Lync is blocking the call as it has no route in the voice policy. Can you add the route to Asterisk to the default voice policy and test if it works?

    Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
    If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.
    Tuesday, January 25, 2011 9:32 AM
  • Thanks, Ruben. In my small installation only one default policy exists.

    I think Lync don't routing calls from one gate to another because of licensing consideration.

    I've managed to get it work by using new-csAnalogDevice command. It created Lync user for my getaway. Now I want to test if it works with multiple concurrent lines.

    Tuesday, January 25, 2011 10:04 AM
  • I have another issue...

    My Setup:
    "Asterisk" <-> "Lync" <-> "AudiocodesMP"
    No direct routes between "Asterisk" and "AudiocodesMP", both configured as voice gate in Lync.

    From Lync I can call extensions on both "Asterisk" and "AudiocodesMP".

    From "AudiocodesMP" I was not able to call any extensions on "Asterisk" until i've configured New-CSAnalogDevice account in Lync for "AudiocodesMP" (TEL:+900). Now using +900 as CallerID I can call any number from "AudiocodesMP". When calling +900 from Lync I can reach "AudiocodesMP".

    But when I call +900 from "Asterisk", always get "SIP 404 Not Found" error. While monitoring Asterisk SIP log, i've noticed what when I call +900 from "Asterisk", Lync is trying to call +900 extension on "Asterisk" instead of "AudiocodesMP".

    I've tried to create CSAnalogDevice account for "Asterisk", when use its TEL:+950 as CallerID when I call from "Asterisk" to TEL:901 (which is routed to "AudiocodesMP", but this number is not assigned to any Lync account). This call is routed. But in this case i'm loosing my original Asterisk CallerID and this is not acceptable. Also, call to +900 still fails.

    How can I solve my problems: enable calls from "Asterisk" to "AudiocodesMP" thru "Lync" and keep original CallerID?

    Wednesday, March 16, 2011 8:04 PM
  • Let me try to ask my question with different words.

    We have two Voice Gateways connected to Lync.

    No direct routes between gateways. All calls routed thru Lync.

    Call from any gateway to Lync User is successful, from Lync to both gateways too.

    A general Call from gateway1 to gateway2 thru Lync is not routed. (IN SIP Logs says Text: Routed a request towards the edge of the enterprise)

    If we create CSAnalogDevice on Lync Server with tel URI=+900, then call same number from gateway 1 to gateway2 with CallerID=900, all is OK. (SIP Log says: Text: Response successfully routed)

    Tha sad thing is what gateway1 is connected to PSTN, so we can't create CSAnalogDevice with corresponding CallerID accounts for each caller.

    Is there any way to allow calls from gateway1 to gateway2 thru Lync Server allowing original CallerIDs?

    Tuesday, April 12, 2011 7:18 AM
  • So if i get it right, you want to take all calls on gateway1 and send it to gateway2. We had problems trying to get a similar setup (PSTN -> Lync -> IVR)

    We managed to create such a scenario using response groups (specifically hunt group)

    1) Create a hunt group with telephone number the call in number for gateway1 (usually your external PSTN number)

    2) Select a custom business hours schedule and make sure you are always closed (select custom an leave everything empty)

    3) Set the "Outside business hours" forward to telephone number and fill in the access number for gateway2 (example: +900@domain)

    This should put all calls from gateway1 onto gateway2 while maintaining their caller id. If you have multiple external numbers, you'll need to create a group for each.

    It ain't pretty but its the best i managed so far. I'd love to hear better solutions

    • Edited by Kris Vanherck Tuesday, April 12, 2011 1:30 PM missing line breaks
    Tuesday, April 12, 2011 1:29 PM
  • Argon,

    I don’t consider myself UC expertJ… yet.

    I am trying to understand what is that you want to achieve. Might be we need to chat or exchange emails? Email me here – drago at windstream.net. I will be available after Friday his week.

    Meanwhile, you I don’t think you should consider Lync in the middle but rather as an end leg. Anyhow, let’s talk first so I can understand your intend.



    Tuesday, April 12, 2011 3:51 PM
  • Thanks for sharing such tricky method, Kris!

    It's nice to see what I'm not alone with this problem.

    I can solve this by creating AnalogDevice accound for each target number on Gateway2, but it's would be not practical for enterprise environment.

    Tuesday, April 12, 2011 3:55 PM
  • Dear Drago, I think it's better to post all content here, because it can be found and help somebody in the future.

    My lync account is i.rom(=at=)rubicon-it.ru, my personal email is ar(=at=)my-nickname

    The general problem of this topic is the fact what Lync Server not route any call thru itself if source or target not authenticated by eny means.

    Here's the visio http://img690.imageshack.us/i/lyncschema.png/


    anonymous call from gateway1 to lync account works

    anonymous call from gateway1 to any number on gateway2 thru lync fails

    anonymous call from gateway1 to Lync AnalogDevice pointed to gateway2 works

    call with CallerID=Lync_AnalogDevice_Tel from gateway1 to any number on gateway2 thru lync works

    I need:

    anonymous call from gateway1 to any number on gateway2 thru lync

    Tuesday, April 12, 2011 4:24 PM
  • Have you considered registering MP118 to Asterisk and not Lync? This way the routing will be Lync -> Gateway (Asterisk) and you can handle the routing to MP there with RegEx for example. I don't see any benefits from having Analog Device application contact in AD besides... having support for Analog Device within Lync.



    Wednesday, April 13, 2011 2:19 AM
  • Direct routes works ok, but it have a big disadvantage, we want to handle all number normalization in one place -- on Lync Server. Lync normalization is the best i've ever seen.
    Wednesday, April 13, 2011 5:21 AM