locked
Lync not routing to PBX RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am trying to get Lync to route calls to my existing PBX a Cisco 1760 with a SIP trunk. However Lync seems to be trying to connect to the device on port 5070 even though I have specified 5060 in topology. Call coming into lync work fine from the 1760.

    I tried wiresharking the server, but it seems no traffic is even leaving the lync box to the 1760. :(

    Running Snooper there seems to be a SIP server time out error.

    TL_INFO(TF_PROTOCOL) [1]09D4.1020::05/24/2012-10:58:30.438.00084bff (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 4101426482
    Instance-Id: 0000095E
    Direction: outgoing;source="local"
    Peer: 10.0.0.124:49736
    Message-Type: response
    Start-Line: SIP/2.0 504 Server time-out
    From: "myname"<sip:admin@mydomain.net>;tag=ff6dd1eece;epid=bf30df2b8a
    To: <sip:+101@mydomain.net;user=phone>;tag=D37487D5DE78AC9D1D5DA679210CC26D
    CSeq: 1 INVITE
    Call-ID: 1274460ce76c1ab97f8e1538d751fc2c
    Authentication-Info: TLS-DSK qop="auth", opaque="6CA9E629", srand="BF899B78", snum="392", rspauth="70fc5bffe22b9ec11d0241ebe0cfc75c9712f412", targetname="Lync-Server.mydomain.net", realm="SIP Communications Service", version=4
    Via: SIP/2.0/TLS 10.0.0.124:49736;ms-received-port=49736;ms-received-cid=200
    ms-diagnostics: 1014;reason="Unable to resolve DNS A record";LookupFQDN="LyncPool";source="Lync-Server.mydomain.net"
    Server: OutboundRouting/4.0.0.0
    Content-Length: 0
    Message-Body: –
    $$end_record

    I have checked that the mediation server is running, and that the LyncPool DNS name is actually valid. Help is appreciated.

    Thursday, May 24, 2012 11:08 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    SOLVED!

    I accidentally used an incomplete FQDN when I created my FrontEnd server. Instead of LyncPool.mydomain.net I just used LyncPool. I had to remove the topology and front end server and re-provision the Lync installs.

    • Marked as answer by Hyperlight Friday, May 25, 2012 3:34 AM
    Friday, May 25, 2012 3:34 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Is there a port conflict with running the co-located mediation server on port 5060?

    • Edited by Hyperlight Thursday, May 24, 2012 5:37 PM
    Thursday, May 24, 2012 5:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hyperlight, restart the servers once you've verified the topology is pushed to it.

    BBB


    • Edited by indubious Thursday, May 24, 2012 6:37 PM
    Thursday, May 24, 2012 6:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have already tried. It still isn't sending traffic.

    I am thinking I will have to deploy a dedicated mediation server. I can't seem to find out whats causing this timeout.

    Thursday, May 24, 2012 8:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am also getting the following a few lines before the server timeout:


    TL_WARN(TF_DIAG) [4]0984.1B98::05/24/2012-21:11:42.862.000500d8 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(145))$$begin_record
    LogType: diagnostic
    Severity: warning
    Text: Host name resolution failure
    SIP-Start-Line: INVITE sip:100@Cisco-1760.mydomain.net:5070;user=phone;maddr=LyncPool SIP/2.0
    SIP-Call-ID: 80ea46437d1c44a28304ce8e027d8a3b
    SIP-CSeq: 1 INVITE
    Data: fqdn="LyncPool"
    $$end_record

    Thursday, May 24, 2012 9:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    SOLVED!

    I accidentally used an incomplete FQDN when I created my FrontEnd server. Instead of LyncPool.mydomain.net I just used LyncPool. I had to remove the topology and front end server and re-provision the Lync installs.

    • Marked as answer by Hyperlight Friday, May 25, 2012 3:34 AM
    Friday, May 25, 2012 3:34 AM