locked
Lync Cannot Receive Calls RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear Team,

    We have configured Lync SBA to work with Siemens Hi Path 4000 ,

    The Setup is as below 

    Lync SBA (Installed on Sangoma Lync Express) --> Netbooder Card -> E1 (//Trunk) to --> Siemens HiPath 4000,

    Siemens HiPath has assigned some 5 ext to be used for Lync , 

    The problem is for DID to work , there should be only four digits sent from Lync to Siemens HiPath,

    Currently we have applied translation rule to Trunk configuration so the E.164 number is translated and only last 4 digits are sent,

    Tel:+0014444710 --> 4710 , so the outgoing call received the proper did number , but if the Below 

    Tel:+0014444710;ext=4710, then the call goes from the pilot number , instead of the proper did ext,

    Also  the receiving of calls is not working, if we set the Ext to ext=+4410 , then we can receive call but if set to proper E.164 format , even after applying the incoming call translation , call is not received is routed back to the same trunk,

    SIP/2.0 404 Not Found

    SO in all there two issue, 

    Call receiving and call dialing out,

    Need help very very urgently,

    May be i need to configure Trunk Configuration, calling number rule translation and called number rule translation,

    Appreciate your help.

    Regards,

    Hasan Reza

    

    Wednesday, January 27, 2016 9:18 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear Anthony,

    I am not sure how can i do the modification on Sangoma, if some link could be provided on this subject,

    Moreover i was just checking the below link which is exactly the issue that i am facing,

    https://social.technet.microsoft.com/Forums/lync/en-US/1ae69176-6274-4409-95c4-ad130db8c024/lync-2013-not-accepting-incoming-calls?forum=lyncvoice

    (I have already created a site policy)

    Also if you could tell me why did number are not shown during call out, if i set the line uri to : tel+00144444710;ext=4710, but works when the line uri is set to tel+00144444710,

    Please guide,

    Regards,

    Hasan reza,

    • Proposed as answer by AshrafJamal Wednesday, February 17, 2016 11:13 PM
    • Marked as answer by Hasan Reza Wednesday, February 17, 2016 11:14 PM
    Wednesday, January 27, 2016 11:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You can use trunk translation rule for called and Calling number translation.

    Pattern to Match - ^+001444(\d{3});ext=(\d{3})
    Translation Rule - $1

    Regards,

    Malinda

    Malinda Perer | MCSM - Chatter Communication | MCM - Lync 2010 and OCS 2007 | http://malinblog.com/ | https://sg.linkedin.com/in/malindap

    • Proposed as answer by Malinda Perera Saturday, January 30, 2016 12:14 AM
    • Marked as answer by Hasan Reza Wednesday, February 17, 2016 11:15 PM
    Saturday, January 30, 2016 12:14 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Why perform the translation in Lync at all, why not do it on the Sangoma SBC?  It might just be easier that way?

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Wednesday, January 27, 2016 10:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear Anthony,

    I am not sure how can i do the modification on Sangoma, if some link could be provided on this subject,

    Moreover i was just checking the below link which is exactly the issue that i am facing,

    https://social.technet.microsoft.com/Forums/lync/en-US/1ae69176-6274-4409-95c4-ad130db8c024/lync-2013-not-accepting-incoming-calls?forum=lyncvoice

    (I have already created a site policy)

    Also if you could tell me why did number are not shown during call out, if i set the line uri to : tel+00144444710;ext=4710, but works when the line uri is set to tel+00144444710,

    Please guide,

    Regards,

    Hasan reza,

    • Proposed as answer by AshrafJamal Wednesday, February 17, 2016 11:13 PM
    • Marked as answer by Hasan Reza Wednesday, February 17, 2016 11:14 PM
    Wednesday, January 27, 2016 11:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would suggest reaching out to Sangoma for support on their product.  I know AudioCodes well, but not Sangoma. 

    Can you post the translation rules you've put in place?

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Thursday, January 28, 2016 3:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You can use trunk translation rule for called and Calling number translation.

    Pattern to Match - ^+001444(\d{3});ext=(\d{3})
    Translation Rule - $1

    Regards,

    Malinda

    Malinda Perer | MCSM - Chatter Communication | MCM - Lync 2010 and OCS 2007 | http://malinblog.com/ | https://sg.linkedin.com/in/malindap

    • Proposed as answer by Malinda Perera Saturday, January 30, 2016 12:14 AM
    • Marked as answer by Hasan Reza Wednesday, February 17, 2016 11:15 PM
    Saturday, January 30, 2016 12:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear Malinda,

    Thanks for the response , i had this issue sorted the same day reading the below post , but was not well so could not update the forum, 

    Below is the procedure i followed.

    Why incoming call could not be received ?

    When Sangoma Forwarded the call to Lync it added a "+" , after reading the below article By Ken , i understand that if there is a + added to number , lync assumes the number to be normalized , and hence forth does not apply any dialplan (Normalization) to it,

    Ken Article ,

    http://ucken.blogspot.ae/2011/07/lync-bug-with-incoming-e164-phone.html

    In Sangoma http://127.0.0.1:7783/ -> Configuration

     <rule name="primary_sip_out" outbound_interface="sip" qvalue="0.001">

    Removed the + from below 

          <param name="sip.out.to.uri" expr="sip:+%0@192.168.81.10:5068"/>

    For call dialout not happening with proper DID , i followed the below translation,

    http://blogs.technet.com/b/dodeitte/archive/2013/04/21/issue-with-calling-number-translation-rules-and-e-164-extensions.aspx

    Lync Control Panel -> Voice Routing -> Trunk Configuration -> Calling Number Translation rule ->

    ^\+\d{7}(\d{2}\d+)(;ext=\d{4})?$

    Translation Rule - $1

    Now i have only one issue left , for any call (incoming / outgoing) there is delay of 8 seconds before dialout and dialin, 

    I have checked with the Telco/PBX , as soon as the call is received at their end , it is immediately forwarded (If inbound to Lync , if outbound to E1/pstn cloud),

    Can you please shed some light on this as well,

    Regards, (Appreciate your response,)

    Hasan Reza,


    • Edited by Hasan Reza Saturday, January 30, 2016 8:51 AM
    Saturday, January 30, 2016 8:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Yes, if there is a "+" lync assume number is already normalized.

    For the delay, can you check in the time delay in each session (SIP trace) after the initial INVITE.

    It will provide some idea where is the processing delay.  

    Malinda Perer | MCSM - Chatter Communication | MCM - Lync 2010 and OCS 2007 | http://malinblog.com/ | https://sg.linkedin.com/in/malindap

    Saturday, January 30, 2016 12:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hasan Reza,

    I’m writing to follow up on this thread. Do you have any updates on this issue? Please post back at your convenience.

     

    Best regards,

    Eric

    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.

    Sunday, February 7, 2016 12:15 PM