locked
Lync SIP/2.0 302 Moved Temporarily appears to not work RRS feed

  • Question

  • I have an AudioCodes MP-124 gateway setup to Call Forward a particular number.  When I dial that number from Lync, it rings and rings, and does not appear to forward at all.

    Here is the snooper of the SIP 302:

    TL_INFO(TF_PROTOCOL) [8]0B00.4550::08/11/2011-09:26:35.346.0250bcad ((Shared),SipMessage.DataLoggingHelper:sipmessage.cs(686))[4034347661]
    <<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_1D185C6>], 10.10.0.160:60384<-10.10.0.140:5067
    SIP/2.0 302 Moved Temporarily
    FROM: "John"<sip:+15035551234@srv220.abc.com;user=phone>;epid=6AAEF04140;tag=1751c75ca3
    TO: <sip:+2205@ang01.abc.com;user=phone>;tag=1c2055386549
    CSEQ: 14324 INVITE
    CALL-ID: bd8d0603-c1c1-4d7b-8f78-cb418be54273
    VIA: SIP/2.0/TLS 10.10.0.160:60384;branch=z9hG4bK6117eea
    CONTACT: <sip:+15035553333@abc.com;transport=tls>
    CONTENT-LENGTH: 0
    SUPPORTED: em,timer,replaces,path,early-session,resource-priority
    ALLOW: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
    SERVER: Audiocodes-Sip-Gateway-MP-124 FXS/v.6.00A.041.001
    Diversion: <tel:+2205>;reason=unconditional;counter=1
    Reason: SIP ;cause=302 ;text="302 Moved Temporarily"
    ------------EndOfIncoming SipMessage

    However, there is nothing showing the FE server sending an invite to +15035553333.

    What am I missing?

     

    Thursday, August 11, 2011 5:40 PM

All replies

  • I have an AudioCodes MP-124 gateway setup to Call Forward a particular number.  When I dial that number from Lync, it rings and rings, and does not appear to forward at all.


    CONTACT: <sip:+15035553333@abc.com;transport=tls>
      However, there is nothing showing the FE server sending an invite to +15035553333.

    What am I missing?

    Do you see any TLS errors in the snooper?
    If you view the mediation server trace in the notepad, instead of opening it in snooper (in my experience, there are some extra details if you are viewing mediation traces through notepad), do you see any exceptions raised by TLS negotiation?
    Is CONTACT header really  "sip:...@abc.com;transport=tls" ?

    In my experience, Contact header should contain FQDN of the gateway handling the forwarded number and since you are using TLS it is also important for the certificate on that gateway to be installed correctly, it should match the contact FQDN and lync mediation server should trust the gateway certificate.

    Make sure the gateway name (FQDN) is configured on audiocodes, matching the FQDN defined in Lync topology and verify that name is presented in the contact header.

     

    Saturday, August 13, 2011 3:08 AM
  • Where did you set the call forwarding, phone or lync client?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, August 15, 2011 9:27 AM
  • Fwd to Lync client.
    Monday, August 15, 2011 3:31 PM
  • No TLS errors that I can see.

    Regular phone calls involving this gateway and Lync happen without any problems.  As far as I know, any TLS problem would impact all calls on this gateway, not just forwarding.

    Yes, it really is "sip:...@abc.com;transport=tls"

    Since +15035553333@abc.com is an internal Lync number, should not Lync find it OK?


    Monday, August 15, 2011 6:03 PM
  • Yes, it really is "sip:...@abc.com;transport=tls"

    Since +15035553333@abc.com is an internal Lync number, should not Lync find it OK?


    Lync is checking the "Contact" header and will try to resolve it. the Number/User portion of contact is irrelevant in this case. If "abc.com" is not resolving in anything, the call would die just there. If it resolves into anything, Lync would try to establish a TLS connection to that IP and is going to expect "ABC.COM" in the certificate "CN" field.

    I had a similar problem with Lync and an Audiocodes Mediant--1000 gateway configured with QSIG. Gateway was returning 302-Moved messages for "forwarded calls" and it was failing, because the contact header was using an IP address and not FQDN. Since I was using TLS, that was failing, because IP address wasn't matching the certificate CN field, configured as FQDN. All calls, but forwarded were working just fine.

     

     

    Friday, August 19, 2011 4:16 AM
  • abc.com is the primary SIP domain.  I don't think the Lync servers should have any problem resolving it, and the certificate for TLS will match.

     

    Friday, August 19, 2011 3:45 PM
  • Did you ever figure out what was wrong ?

    I have the exact same scenario, only i'm also getting a 480 Temporarily Unavailable as the last line in the SIP message.

    Don't want to bother with too much troubleshooting if the answer is straight ahead :)

    br

    Steffen

    Sunday, February 7, 2016 12:39 PM