locked
Lync 2013 inbound calls not working - outbound okay RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a Lync 2013 topology, migrated from OCS 2007 R2 initially - having a working Lync 2010 with enterprise voice working.

    When we migrated, we were able to call via SIP Trunk on Lync 2010 - but the customer decided to change to Avaya as a gateway between SIP-trunk and Lync.

    And we moved to Lync 2013 at the same time. I changed trunk and routes to new PSTN trunk.

    I can make outbound calls okay, but inbound stops. No ringing.

    I've compared to a working Lync 2013 EV at another site - and it is more or less identical setup (but they have different gateways).

    When logging on mediation server - i get the following log entry:

    TL_INFO(TF_PROTOCOL) [0]0CC4.0470::07/02/2013-12:00:56.975.0000318c (S4,SipMessage.DataLoggingHelper:1844.idx(774))[495952505]
    <<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_37F2C72>], 172.17.100.155:5060<-172.17.10.15:39081
    CANCEL sip:+4756131419@xxxxx.no SIP/2.0
    FROM: "92063015" <sip:+4792063015@172.17.10.30:20882;user=phone>;tag=SDc3cbd01-512f52b7-1372766452729497-gm-pt-lucentPCSF-092905
    TO: <sip:+4756131419@xxxxx.no>
    CSEQ: 1 CANCEL
    CALL-ID: 40868a6e3742b923c7c6603a90f7c418
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TCP 172.17.10.15;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927-AP;ft=125204
    VIA: SIP/2.0/TCP 172.17.10.14:15070;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927
    ROUTE: <sip:172.17.100.155;transport=tcp;lr;phase=terminating>
    RECORD-ROUTE: <sip:717d181f@172.17.10.15;transport=tcp;lr>
    CONTENT-LENGTH: 0
    USER-AGENT: AVAYA-SM-6.1.7.0.617012

    ------------EndOfIncoming SipMessage

    and

    TL_INFO(TF_PROTOCOL) [0]0CC4.0D40::07/02/2013-12:00:56.976.000031f4 (S4,SipMessage.DataLoggingHelper:1844.idx(774))[493136405]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_37F2C72>], 172.17.100.155:5060->172.17.10.15:39081
    SIP/2.0 487 Request Terminated
    FROM: "92063015"<sip:+4792063015@172.17.10.30:20882;user=phone>;tag=SDc3cbd01-512f52b7-1372766452729497-gm-pt-lucentPCSF-092905
    TO: <sip:+4756131419@xxxxxx.no>;epid=A621647001;tag=3bc23e8ec0
    CSEQ: 1 INVITE
    CALL-ID: 40868a6e3742b923c7c6603a90f7c418
    VIA: SIP/2.0/TCP 172.17.10.15;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927-AP;ft=125204,SIP/2.0/TCP 172.17.10.14:15070;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927,SIP/2.0/TCP 172.17.10.14:15070;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A491512925,SIP/2.0/TCP 172.17.10.14:15070;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A491512924,SIP/2.0/TCP 172.17.10.15;branch=z9hG4bK-s1632-000017228450-1--s1632--AP;ft=124350,SIP/2.0/TCP 172.17.10.30:5060;branch=z9hG4bK-s1632-000017228450-1--s1632-
    CONTENT-LENGTH: 0
    SERVER: RTCC/5.0.0.0 MediationServer

    ------------EndOfOutgoing SipMessage

    and

    TL_INFO(TF_PROTOCOL) [0]0CC4.0D40::07/02/2013-12:00:56.976.0000320d (S4,SipMessage.DataLoggingHelper:1844.idx(774))[495952505]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_37F2C72>], 172.17.100.155:5060->172.17.10.15:39081
    SIP/2.0 200 OK
    FROM: "92063015"<sip:+4792063015@172.17.10.30:20882;user=phone>;tag=SDc3cbd01-512f52b7-1372766452729497-gm-pt-lucentPCSF-092905
    TO: <sip:+4756131419@xxxxxx.no>;epid=A621647001
    CSEQ: 1 CANCEL
    CALL-ID: 40868a6e3742b923c7c6603a90f7c418
    VIA: SIP/2.0/TCP 172.17.10.15;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927-AP;ft=125204,SIP/2.0/TCP 172.17.10.14:15070;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927
    RECORD-ROUTE: <sip:717d181f@172.17.10.15;transport=tcp;lr>
    CONTENT-LENGTH: 0
    SERVER: RTCC/5.0.0.0 MediationServer

    ------------EndOfOutgoing SipMessage

    finally an ACK from Gateway:

    TL_INFO(TF_PROTOCOL) [0]0CC4.0470::07/02/2013-12:00:56.979.00003252 (S4,SipMessage.DataLoggingHelper:1844.idx(774))[278233693]
    <<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_37F2C72>], 172.17.100.155:5060<-172.17.10.15:39081
    ACK sip:+4756131419@xxxxx.no;routeinfo=0-0 SIP/2.0
    FROM: "92063015" <sip:+4792063015@172.17.10.30:20882;user=phone>;tag=SDc3cbd01-512f52b7-1372766452729497-gm-pt-lucentPCSF-092905
    TO: <sip:+4755998659@172.17.10.15>;epid=A621647001;tag=3bc23e8ec0
    CSEQ: 1 ACK
    CALL-ID: 40868a6e3742b923c7c6603a90f7c418
    MAX-FORWARDS: 69
    VIA: SIP/2.0/TCP 172.17.10.15;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927-AP;ft=125204
    VIA: SIP/2.0/TCP 172.17.10.14:15070;branch=z9hG4bKAC110A0EFFFFFFFFB9B74A490512927
    ROUTE: <sip:172.17.100.155;transport=tcp;lr;phase=terminating>
    CONTENT-LENGTH: 0

    ------------EndOfIncoming SipMessage

    This logging is on Mediation server, stand alone.

    I see no traces of this traffic on the front end server--- as with the working server - i see the +47telephone traffic on front end as well

    Tuesday, July 2, 2013 12:09 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Please check the configuration note for Avaya gateway.

    1.On Lync Mediation Server, Media Bypass and REFER are set to disabled. Testing found Media Bypass does not work for inbound calls and REFER is not supported.

    2.TLS and SRTP are not supported by Avaya and as a result need to be set to disabled on Mediation Server.

    For the details, see http://technet.microsoft.com/en-us/lync/gg131938

    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.

    • Proposed as answer by Lisa.zheng Monday, July 15, 2013 8:53 AM
    • Marked as answer by Lisa.zheng Tuesday, July 16, 2013 1:26 AM
    Monday, July 8, 2013 9:19 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    in avaya how your normalization rule for inbound calls to lync looks like?
    what number format you are using in your lync server for the users?

    Cheers 
    Peter

    Tuesday, July 2, 2013 12:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Lync Server has tel:+4755555555 as numbers.

    The Avaya appear to give me number in +47 first ... I was told that the Avaya gave me numers in +47 Maybe I should configure a called number translation rule ..... for testing

    Tuesday, July 2, 2013 12:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Are you working with extensions? 
    like: tel:+47555555;ext=555
    Tuesday, July 2, 2013 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Nope ...

    just plain numbers ...

    i see in logs that it tries to call sip:+4755555555 rather than tel:+47 ---

    but that might be normal, haven't given that any thought in previous deployments :-)

    Tuesday, July 2, 2013 12:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Please check the configuration note for Avaya gateway.

    1.On Lync Mediation Server, Media Bypass and REFER are set to disabled. Testing found Media Bypass does not work for inbound calls and REFER is not supported.

    2.TLS and SRTP are not supported by Avaya and as a result need to be set to disabled on Mediation Server.

    For the details, see http://technet.microsoft.com/en-us/lync/gg131938

    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.

    • Proposed as answer by Lisa.zheng Monday, July 15, 2013 8:53 AM
    • Marked as answer by Lisa.zheng Tuesday, July 16, 2013 1:26 AM
    Monday, July 8, 2013 9:19 AM