locked
Lync 2013 SIP Trunk Cisco Callmanger RRS feed

  • Question

  • HI,

    Have a trunk between lync 2013 and the Cisco CallManager.
    After configured'm managing to do internal connection of the lync for cisco of extensions, however when I connect the internal cisco extensions for lync can not find the contact user.
    I'm only with this log monitor the network:


    2166    16:51:45 17/03/2015    35.4069227        10.0.1.1 (IP CISCO CALLMANAGER)     SDP    SDP:Request: INVITE sip:+7080@10.10.2.20:5060 SIP/2.0; SDP:SessionName=SIP Call, Version=0, MediaDescription=audio 30736 RTP/AVP 0 101    {SIP:75, UDP:74, IPv4:73}

    After a while no call connection is closed

    Tuesday, March 17, 2015 8:00 PM

Answers

  • So, +7080 is being sent to Cisco or is this coming from Cisco?  Either way, you may need a trunk translation rule to strip that plus out so Cisco is happy with it.

    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.

    • Proposed as answer by Eason Huang Wednesday, March 18, 2015 5:41 AM
    • Marked as answer by Eason Huang Monday, March 30, 2015 9:41 AM
    Tuesday, March 17, 2015 9:23 PM
  • Hi,

    Lync Server 2013, like its immediate predecessors, requires all dial strings to be normalized to E.164 format for the purpose of performing reverse number lookup (RNL).

    For trunks with gateways or private branch exchanges (PBXs) that require numbers translated in local dialing formats, Lync Server 2013 trunk configuration enable you modify the format of the dialed phone number using an outbound translation rule to ensure the format matches the type required by the PBX.

    Best Regards,
    Eason Huang


    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

    • Marked as answer by Eason Huang Monday, March 30, 2015 9:41 AM
    Wednesday, March 18, 2015 5:53 AM

All replies

  • So, +7080 is being sent to Cisco or is this coming from Cisco?  Either way, you may need a trunk translation rule to strip that plus out so Cisco is happy with it.

    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.

    • Proposed as answer by Eason Huang Wednesday, March 18, 2015 5:41 AM
    • Marked as answer by Eason Huang Monday, March 30, 2015 9:41 AM
    Tuesday, March 17, 2015 9:23 PM
  • Hi,

    Lync Server 2013, like its immediate predecessors, requires all dial strings to be normalized to E.164 format for the purpose of performing reverse number lookup (RNL).

    For trunks with gateways or private branch exchanges (PBXs) that require numbers translated in local dialing formats, Lync Server 2013 trunk configuration enable you modify the format of the dialed phone number using an outbound translation rule to ensure the format matches the type required by the PBX.

    Best Regards,
    Eason Huang


    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

    • Marked as answer by Eason Huang Monday, March 30, 2015 9:41 AM
    Wednesday, March 18, 2015 5:53 AM