locked
Problems with calling PBX extensions from Lync RRS feed

  • Question

  • Hello,

    We would like to connect Lync with a PBX. Therefore we installed a Dialogic DMG 4000 for routing calls from Lync to PBX.

    The GW is connected with the PBX through PRI. Using the Line Test Tool on the GW, we can call a PBX extension.

    But we can't call a PBX extension from Lync.

    The GW has been added to the Topology and the Topology has been published.

    We also configured the GW (SIP Peer, Routing).

    There is a new Dialplan for the GW (send 4 digit number to GW) and users are enabled for Enterprise Voice.

     

    How does Lync send a dialed number (e.g. 1111) to the GW?

     

    Any ideas? Is there a tool to test connectivity (Lync - GW)?

     

    Thanks!

    Jan


    Saturday, August 27, 2011 1:46 PM

Answers

  • This depends on the normalization rules you configured.  At minimum (by default) Lync is appending a + to the beginning of the dial string, so you'll need to look at the SIP traffic to determine the actual dial string which is being sent to your Dialogic gateway.

    You should be normalizing all numbers in Lync as +E.164 (+1 AreaCode Prefix Extension) and then in the Dialogic stripping digits down to the 4-digit extension that your PBX uses.  A major role of the media gateway is to translate number patterns into the formats that both your PBX and Lync work best with and not try to normalize the numbers down to 4 digits only within Lync.


    Jeff Schertz, Microsoft Solutions Architect - Polycom | Lync MVP
    • Proposed as answer by Sean_Xiao Monday, August 29, 2011 5:33 AM
    • Unproposed as answer by JaSch Monday, August 29, 2011 6:14 PM
    • Marked as answer by JaSch Tuesday, August 30, 2011 8:58 AM
    Saturday, August 27, 2011 3:42 PM

All replies

  • This depends on the normalization rules you configured.  At minimum (by default) Lync is appending a + to the beginning of the dial string, so you'll need to look at the SIP traffic to determine the actual dial string which is being sent to your Dialogic gateway.

    You should be normalizing all numbers in Lync as +E.164 (+1 AreaCode Prefix Extension) and then in the Dialogic stripping digits down to the 4-digit extension that your PBX uses.  A major role of the media gateway is to translate number patterns into the formats that both your PBX and Lync work best with and not try to normalize the numbers down to 4 digits only within Lync.


    Jeff Schertz, Microsoft Solutions Architect - Polycom | Lync MVP
    • Proposed as answer by Sean_Xiao Monday, August 29, 2011 5:33 AM
    • Unproposed as answer by JaSch Monday, August 29, 2011 6:14 PM
    • Marked as answer by JaSch Tuesday, August 30, 2011 8:58 AM
    Saturday, August 27, 2011 3:42 PM
  • You can start the log on the Dialogic to see if your Lync dialplan is correct if yo configure the dialplan like Jeff explain.

    You have also to configure the GW to send extension numbers in e.164 format


    regards Holger Technical Specialist UC
    Saturday, August 27, 2011 3:53 PM
  • I added a normalization rule in Lync to translate a 4 digit extension to +49xxxxyy1111.

    The Test Voice Routing is positive.

    How can I verify the connection Lync - GW?

     

    Update: I installed the telnet client on the Mediation Server and the GW and telneted <hostname> <port>.

    Result: Could not connect to host...

    Firewalls are disabled!

     

    Thanks!




    Monday, August 29, 2011 8:16 AM
  •  

    When calling a PBX extension from a Lync Client I can hear the dial tone and then I get the following error on the Lync Phone:

     

    "The calling service or server temporarily unavailable".

     

    regards,



    Update: solved

     

    Monday, August 29, 2011 7:10 PM