locked
Problem calling after 5 sec RRS feed

  • Question

  • Hello!

    There is a problem: while calling Lync – Lync after approx. 5 sec (3 rings) call is terminated and in the event log there is next error:

    TL_INFO(TF_DIAG) [3]0BAC.1704::09/28/2011-12:08:02.192.0001305e (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Routed a request on behalf of an application
    SIP-Start-Line: CANCEL sip:10.10.5.211:49991;transport=tls;ms-opaque=f1485abae6;ms-received-cid=4B00 SIP/2.0
    SIP-Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    SIP-CSeq: 1 CANCEL
    Peer: LyncEdge.co.FIRMA.com:49170
    Data: destination="LyncEdge.co.FIRMA.com";application="http://www.microsoft.com/LCS/DefaultRouting"
    $$end_record

    TL_INFO(TF_PROTOCOL) [3]0BAC.1704::09/28/2011-12:08:02.192.0001309b (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 2075636592
    Instance-Id: 00000DF7
    Direction: outgoing;source="local"
    Peer: LyncEdge.co.FIRMA.com:49170
    Message-Type: request
    Start-Line: CANCEL sip:10.10.5.211:49991;transport=tls;ms-opaque=f1485abae6;ms-received-cid=4B00 SIP/2.0
    From: "Горбатюк Олександр"<sip:oleksandr.horbatyuk@FIRMA.com>;tag=4d569698fc;epid=e840d86b78
    To: <sip:oleksandr.radnianyi@FIRMA.com>;epid=7275675eb7
    CSeq: 1 CANCEL
    Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    Via: SIP/2.0/TLS 10.10.16.103:5061;branch=z9hG4bK4451F1AB.17CCBA436D12D1CE;branched=FALSE
    Authentication-Info: TLS-DSK qop="auth", opaque="97A96FF1", srand="2CC7ED90", snum="53", rspauth="d2b568ba45267040f1828ecdbac8f6fe42dc6b53", targetname="Lync01.co.FIRMA.com", realm="SIP Communications Service", version=4
    Max-Forwards: 70
    Content-Length: 0
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting
    ms-application-via: ms-icr-to;ms-processing-icr=lync.co.FIRMA.com;state=ToPrimary;ms-pool=lync.co.FIRMA.com;ms-application=http%3A%2F%2Fwww.microsoft.com%2FLCS%2FInterClusterRouting;ms-server=Lync01.co.FIRMA.com
    ms-application-via: SIP;ms-urc-rs-from;ms-server=Lync01.co.FIRMA.com;ms-pool=lync.co.FIRMA.com;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
    ms-application-via: lyncSQL.co.FIRMA.com_;ms-server=Lync01.co.FIRMA.com;ms-pool=lync.co.FIRMA.com;ms-application=51FB453D-5B9F-45df-83B4-ADD1F7E604A8
    ms-routing-phase: from-uri-routing-done
    Route: <sip:LyncEdge.co.FIRMA.com:49170;transport=tls;maddr=10.10.20.10;opaque=state:Ee.aanpqM1qd-Cwt_sKnP22rzcQAA;lr;ms-received-cid=500>
    Reason: SIP;cause=408;text="Request Expired"
    ms-diagnostics-public: 5025;reason="Cancel sent by application for INVITE client transaction.";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting"
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [0]0BAC.1704::09/28/2011-12:08:02.192.00013750 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Response successfully routed
    SIP-Start-Line: SIP/2.0 480 Temporarily Unavailable
    SIP-Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    SIP-CSeq: 1 INVITE
    Peer: 10.116.2.64:60114
    Data: destination="oleksandr.horbatyuk@FIRMA.com"
    $$end_record

    TL_INFO(TF_PROTOCOL) [0]0BAC.1704::09/28/2011-12:08:02.192.0001377f (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 978099856
    Instance-Id: 00000E15
    Direction: outgoing;source="local"
    Peer: 10.116.2.64:60114
    Message-Type: response
    Start-Line: SIP/2.0 480 Temporarily Unavailable
    From: "Горбатюк Олександр"<sip:oleksandr.horbatyuk@FIRMA.com>;tag=4d569698fc;epid=e840d86b78
    To: <sip:oleksandr.radnianyi@FIRMA.com>;tag=018328DBA0798D38F965268D7AADBCBC
    CSeq: 1 INVITE
    Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    Authentication-Info: TLS-DSK qop="auth", opaque="F1E36322", srand="B75E5A9E", snum="107", rspauth="9b259caa3e4397346fc9a51e261d2eb3e728f03d", targetname="Lync01.co.FIRMA.com", realm="SIP Communications Service", version=4
    Content-Length: 0
    Via: SIP/2.0/TLS 10.116.2.64:60114;ms-received-port=60114;ms-received-cid=2E00
    ms-diagnostics: 13014;reason="The routing rules did not result in a final response and callee is not enabled for Unified Messaging";source="Lync01.co.FIRMA.com";Callee="oleksandr.radnianyi@FIRMA.com";appName="InboundRouting"
    Server: InboundRouting/4.0.0.0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [3]0BAC.1704::09/28/2011-12:08:02.200.00013b04 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 978099856
    Instance-Id: 00000E18
    Direction: incoming
    Peer: 10.116.2.64:60114
    Message-Type: request
    Start-Line: ACK sip:oleksandr.radnianyi@FIRMA.com SIP/2.0
    From: <sip:oleksandr.horbatyuk@FIRMA.com>;tag=4d569698fc;epid=e840d86b78
    To: <sip:oleksandr.radnianyi@FIRMA.com>;tag=018328DBA0798D38F965268D7AADBCBC
    CSeq: 1 ACK
    Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    Via: SIP/2.0/TLS 10.116.2.64:60114
    Max-Forwards: 70
    User-Agent: UCCAPI/4.0.7577.314 OC/4.0.7577.314 (Microsoft Lync 2010)
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="F1E36322", targetname="Lync01.co.FIRMA.com", crand="c7d60932", cnum="56", response="dace874e9e40bd3e62118f774458bd2e530c74c9"
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_PROTOCOL) [3]0BAC.0DB0::09/28/2011-12:08:02.396.00013ee7 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 978099856
    Instance-Id: 00000E19
    Direction: incoming
    Peer: LyncEdge.co.FIRMA.com:49170
    Message-Type: response
    Start-Line: SIP/2.0 487 Request Terminated
    From: "Горбатюк Олександр"<sip:oleksandr.horbatyuk@FIRMA.com>;tag=4d569698fc;epid=e840d86b78
    To: <sip:oleksandr.radnianyi@FIRMA.com>;epid=7275675eb7;tag=3f3666413a
    CSeq: 1 INVITE
    Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    Via: SIP/2.0/TLS 10.10.16.103:5061;branch=z9hG4bK4451F1AB.17CCBA436D12D1CE;branched=TRUE;ms-received-port=5061;ms-received-cid=2900
    Via: SIP/2.0/TLS 10.116.2.64:60114;ms-received-port=60114;ms-received-cid=2E00
    Record-Route: <sip:lync.co.FIRMA.com:5061;transport=tls;ms-fe=Lync01.co.FIRMA.com;opaque=state:T:F;lr>;tag=018328DBA0798D38F965268D7AADBCBC
    User-Agent: UCCAPI/4.0.7577.314 OC/4.0.7577.314 (Microsoft Lync 2010)
    Ms-client-diagnostics: 52092;reason="The call was cancelled by the caller before the remote party answered"
    Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="97A96FF1", targetname="Lync01.co.FIRMA.com", crand="2a38c6c7", cnum="58", response="85f43830d85c4638bed9c0dad6bac85d002f3051"
    Content-Length: 0
    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=LyncEdge.co.FIRMA.com;ms-source-verified-user=verified
    Message-Body: –
    $$end_record

    TL_INFO(TF_DIAG) [3]0BAC.0DB0::09/28/2011-12:08:02.396.00014363 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(147))$$begin_record
    LogType: diagnostic
    Severity: information
    Text: Routed a request on behalf of an application
    SIP-Start-Line: ACK sip:10.10.5.211:49991;transport=tls;ms-opaque=f1485abae6;ms-received-cid=4B00 SIP/2.0
    SIP-Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    SIP-CSeq: 1 ACK
    Peer: LyncEdge.co.FIRMA.com:49170
    Data: destination="LyncEdge.co.FIRMA.com";application="http://www.microsoft.com/LCS/DefaultRouting"
    $$end_record

    TL_INFO(TF_PROTOCOL) [3]0BAC.0DB0::09/28/2011-12:08:02.396.0001439e (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
    Trace-Correlation-Id: 2075636592
    Instance-Id: 00000E1A
    Direction: outgoing;source="local"
    Peer: LyncEdge.co.FIRMA.com:49170
    Message-Type: request
    Start-Line: ACK sip:10.10.5.211:49991;transport=tls;ms-opaque=f1485abae6;ms-received-cid=4B00 SIP/2.0
    From: "Горбатюк Олександр"<sip:oleksandr.horbatyuk@FIRMA.com>;tag=4d569698fc;epid=e840d86b78
    To: <sip:oleksandr.radnianyi@FIRMA.com>;epid=7275675eb7;tag=3f3666413a
    CSeq: 1 ACK
    Call-ID: b6f0c59cf6d747e49ade26b0fdf2c374
    Via: SIP/2.0/TLS 10.10.16.103:5061;branch=z9hG4bK4451F1AB.17CCBA436D12D1CE;branched=FALSE
    Authentication-Info: TLS-DSK qop="auth", opaque="97A96FF1", srand="AD8C3159", snum="54", rspauth="2af1de84249c35caacc1efefcb0cc9845d2db99a", targetname="Lync01.co.FIRMA.com", realm="SIP Communications Service", version=4
    Max-Forwards: 70
    Content-Length: 0
    ms-application-via: ms-icr-to;ms-processing-icr=lync.co.FIRMA.com;state=ToPrimary;ms-pool=lync.co.FIRMA.com;ms-application=http%3A%2F%2Fwww.microsoft.com%2FLCS%2FInterClusterRouting;ms-server=Lync01.co.FIRMA.com
    ms-application-via: SIP;ms-urc-rs-from;ms-server=Lync01.co.FIRMA.com;ms-pool=lync.co.FIRMA.com;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
    ms-application-via: lyncSQL.co.FIRMA.com_;ms-server=Lync01.co.FIRMA.com;ms-pool=lync.co.FIRMA.com;ms-application=51FB453D-5B9F-45df-83B4-ADD1F7E604A8
    ms-routing-phase: from-uri-routing-done
    Route: <sip:LyncEdge.co.FIRMA.com:49170;transport=tls;maddr=10.10.20.10;opaque=state:Ee.aanpqM1qd-Cwt_sKnP22rzcQAA;lr;ms-received-cid=500>
    Server: http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting
    ms-diagnostics-public: 5011;reason="ACK is being generated on receipt of a 487 canceled response for an INVITE forked by application";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting"
    Message-Body: –
    $$end_record

    If succeed to pick up phone then possible to talk.

    What can be the reason of error?

    If needed more detailed logs I’m ready to provide them.

    Thursday, September 29, 2011 8:23 AM

Answers

  • it seems as expected. Server terminated the call since there's no response from the user. This is how it usually happen.

    Thamara.

    • Proposed as answer by Sean_Xiao Wednesday, October 12, 2011 2:06 AM
    • Marked as answer by Sean_Xiao Friday, October 14, 2011 7:03 AM
    Monday, October 10, 2011 12:53 PM

All replies

  • Hi,

    Help me with Answering below questions,

    1. When you make a Peer to Peer call using the LYNC Client, are you getting the toast pop  up in the other end?

    2. If it doesn't ring at all, what's the error message that you get in the LYNC Client

    Thamara.

    Thursday, September 29, 2011 10:17 AM
  • sorry for my English

    1-Yes there is a popup window, if you pick up "the phone" , you can talk

    2-the user is unavailable or offline (in reality user is available)

    Aplication log:

    Произошел неожиданный сбой запроса SIP, сделанного программой Communicator (код состояния 80ef01e0). Дополнительные сведения содержатся в следующих технических данных:

     

    RequestUri: sip:ser.dovhan@FIRMA.com

    From: sip:oleksandr.horbatyuk@FIRMA.com;tag=c0276558e1

    To: sip:se.dovhan@FIRMA.com;tag=018328DBA0798D38F965268D7AADBCBC

    Call-ID: 0d66a14c14294d85a8555bb77fc42c59

    Content-type: multipart/alternative;boundary="----=_NextPart_000_0B27_01CC7EAD.0D81E3C0";call-type=audiovideo

    ------=_NextPart_000_0B27_01CC7EAD.0D81E3C0

    Content-Type: application/sdp

    Content-Transfer-Encoding: 7bit

    Content-ID: <fe8753ff587c4cf280e5bda5bd7fd533@FIRMA.com>

    Content-Disposition: session; handling=optional; ms-proxy-2007fallback

    v=0

    o=- 0 0 IN IP4 10.116.2.64

    s=session

    c=IN IP4 10.116.2.64

    b=CT:99980

    t=0 0

    m=audio 28832 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101

    a=candidate:cPn0z5J+bPDa5SM0Q956NgHerswGXuDMeSMe2jbyrpQ 1 39Jucj8toipVUhQjcsHLJQ UDP 0.830 10.116.2.64 28832

    a=candidate:cPn0z5J+bPDa5SM0Q956NgHerswGXuDMeSMe2jbyrpQ 2 39Jucj8toipVUhQjcsHLJQ UDP 0.830 10.116.2.64 28833

    a=candidate:Ub7gSwz8iFIJEIzjF213qLg4RDOsreh1JruQ/PegqfY 1 DkzltubCvGyI4pz7yX/yZA UDP 0.490 77.120.XXX.YYY 58443

    a=candidate:Ub7gSwz8iFIJEIzjF213qLg4RDOsreh1JruQ/PegqfY 2 DkzltubCvGyI4pz7yX/yZA UDP 0.490 77.120.XXX.YYY 55396

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:Ut/7wkQpHa3To1zm6adNsG4r/CNyDzwmtus2a57l|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:mJWvmOvw6YH3mQXr1R6YoKVBp7QzPBQcsJ4KmU9A|2^31|1:1

    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:0ozuvhRGVySh8KzD3OpcsnNI085JDjoftEFBEqCQ|2^31

    a=maxptime:200

    a=rtpmap:114 x-msrta/16000

    a=fmtp:114 bitrate=29000

    a=rtpmap:9 G722/8000

    a=rtpmap:112 G7221/16000

    a=fmtp:112 bitrate=24000

    a=rtpmap:111 SIREN/16000

    a=fmtp:111 bitrate=16000

    a=rtpmap:0 PCMU/8000

    a=rtpmap:8 PCMA/8000

    a=rtpmap:116 AAL2-G726-32/8000

    a=rtpmap:115 x-msrta/8000

    a=fmtp:115 bitrate=11800

    a=rtpmap:4 G723/8000

    a=rtpmap:97 RED/8000

    a=rtpmap:13 CN/8000

    a=rtpmap:118 CN/16000

    a=rtpmap:101 telephone-event/8000

    a=fmtp:101 0-16

    a=encryption:required

    ------=_NextPart_000_0B27_01CC7EAD.0D81E3C0

    Content-Type: application/sdp

    Content-Transfer-Encoding: 7bit

    Content-ID: <692a0488c4e5439284c5d4a1f7ef8df7@FIRMA.com>

    Content-Disposition: session; handling=optional

    v=0

    o=- 0 0 IN IP4 10.116.2.64

    s=session

    c=IN IP4 10.116.2.64

    b=CT:99980

    t=0 0

    m=audio 7626 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101

    a=ice-ufrag:N1un

    a=ice-pwd:sf80vBglTzabqaVig/6r0Uj8

    a=candidate:1 1 UDP 2130706431 10.116.2.64 7626 typ host

    a=candidate:1 2 UDP 2130705918 10.116.2.64 7627 typ host

    a=candidate:2 1 UDP 16648703 77.120.XXX.YYY 58966 typ relay raddr 10.116.2.64 rport 14500

    a=candidate:2 2 UDP 16648702 77.120.XXX.YYY 57865 typ relay raddr 10.116.2.64 rport 14501

    a=candidate:3 1 TCP-ACT 1684798719 10.116.2.64 7626 typ srflx raddr 10.116.2.64 rport 7626

    a=candidate:3 2 TCP-ACT 1684798206 10.116.2.64 7626 typ srflx raddr 10.116.2.64 rport 7626

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:Ut/7wkQpHa3To1zm6adNsG4r/CNyDzwmtus2a57l|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:mJWvmOvw6YH3mQXr1R6YoKVBp7QzPBQcsJ4KmU9A|2^31|1:1

    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:0ozuvhRGVySh8KzD3OpcsnNI085JDjoftEFBEqCQ|2^31

    a=maxptime:200

    a=rtpmap:114 x-msrta/16000

    a=fmtp:114 bitrate=29000

    a=rtpmap:9 G722/8000

    a=rtpmap:112 G7221/16000

    a=fmtp:112 bitrate=24000

    a=rtpmap:111 SIREN/16000

    a=fmtp:111 bitrate=16000

    a=rtpmap:0 PCMU/8000

    a=rtpmap:8 PCMA/8000

    a=rtpmap:116 AAL2-G726-32/8000

    a=rtpmap:115 x-msrta/8000

    a=fmtp:115 bitrate=11800

    a=rtpmap:4 G723/8000

    a=rtpmap:97 RED/8000

    a=rtpmap:13 CN/8000

    a=rtpmap:118 CN/16000

    a=rtpmap:101 telephone-event/8000

    a=fmtp:101 0-16

    a=encryption:required

    ------=_NextPart_000_0B27_01CC7EAD.0D81E3C0--

     

    Response Data:

    183 Session Progress

     

    101 Progress Report

    ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="Lync01.co.FIRMA.com";Count="1";appName="InboundRouting"

     

    180 Ringing

     

    183 Session Progress

     

    480 Temporarily Unavailable

    ms-client-diagnostics: 52086;reason="The conversation could not be established as the remote party is not available";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"

     

    Thursday, September 29, 2011 11:01 AM
  • Hi,

    according to this log file, i see that the other end rings (180 Message) and after some time it disconnects due to time out.

    according to this log file, the call should get connected (given that other party answer the call in time). and you should be able to have a conversation. What's actually happening there??

    Thamara.

    Thursday, September 29, 2011 4:59 PM
  • I have a test about it.

    I find that if you do not deploy UM and do not set call forwarding and the callee's pc desktop is not active, the call will have call will stop ringing after about 5 seconds.

    If the callee's pc desktop is ative(as the mouse is moving, or input), the ringing will be last more times.


    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 Sean_Xiao Wednesday, October 12, 2011 2:06 AM
    Friday, September 30, 2011 9:43 AM
  • sorry for my English

    Deploy UM - NO

    call forward - NO

    user active (mouse is moving in my desktop)

    Friday, September 30, 2011 9:50 AM
  • Hi,

    is the other end LYNC Client that youu calling is in "Available" mode? is he/she getting the toast pop up?

    Thamara.

    Friday, September 30, 2011 10:03 AM
  • yes and yes, after 5 sec call reject

    client LYNC status "Available" (green ico)

    Friday, September 30, 2011 10:10 AM
  • HI,

    1. Is this condition happens to only one User or all the LYNC users having it? (Try running peer to peer calls with several users)

    2. if the call get answered within 5 sec window, will the call last till any of the party terminate it

    Thamara.

    Saturday, October 1, 2011 3:14 PM
  • Hello
    tested 7-10 users, the situation is identical for all
    If you call something a conversation is not interrupted,



    • Edited by AlexGorby Monday, October 3, 2011 6:46 AM
    • Proposed as answer by Santosh_More Wednesday, October 5, 2011 6:29 PM
    • Marked as answer by Sean_Xiao Thursday, October 6, 2011 8:16 AM
    • Unmarked as answer by Sean_Xiao Thursday, October 6, 2011 9:58 AM
    Monday, October 3, 2011 6:45 AM
  • hi,

    Every thing looks fine.. you have Session progress message and ringing message. But i need to ask you one more thing. Is there a situation where the same user logged in from 2 end points? may be from a LYNC Client and a IP Phone with the same login.

    I suspect it due to this

    ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="Lync01.co.FIRMA.com";Count="1";appName="InboundRouting"

    And i ask you is there any IP Phones involved is due to this

    ;RemotePartyCanDoIM="No"


    Monday, October 3, 2011 4:29 PM
  • Dear Sean Xiao the issue is not resolved: (

    Thursday, October 6, 2011 9:54 AM
  • Did you check below,

    Is there a situation where the same user logged in from 2 end points? may be from a LYNC Client and a IP Phone with the same login.

    I suspect it due to this

    ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="Lync01.co.FIRMA.com";Count="1";appName="InboundRouting"

    And i ask you is there any IP Phones involved is due to this

    ;RemotePartyCanDoIM="No"

    Thursday, October 6, 2011 10:09 AM
  • I'm sorry
    I'm using only a software client
    and only one registration
    Thursday, October 6, 2011 11:29 AM
  • no clue what's going on there.. Every thing seems ok.. If there's no multiple logins  with the same sign in address...

    by any chance have you restart the system and try?

    Thamara.

    Thursday, October 6, 2011 11:49 AM
  • :)
    already did restart
    unchanged
    Thursday, October 6, 2011 11:52 AM
  • Here logs from softswitch:

    2011-10-06 14:57:33.712180 [DEBUG] mod_sofia.c:458 Channel sofia/trunks/5404 hanging up, cause: NO_USER_RESPONSE
    2011-10-06 14:57:33.712180 [DEBUG] switch_ivr_originate.c:3346 Originate Resulted in Error Cause: 18 [NO_USER_RESPONSE]

    So answer came from Ms Lync side.

     

     

    Thursday, October 6, 2011 12:00 PM
  • it seems as expected. Server terminated the call since there's no response from the user. This is how it usually happen.

    Thamara.

    • Proposed as answer by Sean_Xiao Wednesday, October 12, 2011 2:06 AM
    • Marked as answer by Sean_Xiao Friday, October 14, 2011 7:03 AM
    Monday, October 10, 2011 12:53 PM
  • Hello Tamara, I am having a disconnection issue with external calls only. When calling to PSTN, using Lync/Audiocodes, the calls during is 2m30s.
    I got some traces from server and client, with snooper and wireshark, and I see a CANCEL.
    Any idea?
    Thanks in advance.
    Wednesday, April 3, 2013 2:45 PM
  • from which side that you get the CANCEL request from? is it from the PSTN/Audiocodes side or the mediation server side?




    Z-Hire -- Automate Lync User Account creation process ( AD / Exchange / Lync )

    Wednesday, April 3, 2013 2:51 PM
  • Lync send cancel to the gateway.
    Wednesday, April 3, 2013 3:13 PM
  • have you try disabling refer support in Voice routes>Trunks? if it's enabled, make sure that it's the same with the Gateway. is the connectivity is over TLS or TCP? if it's TLS try with TCP.




    Z-Hire -- Automate Lync User Account creation process ( AD / Exchange / Lync )

    Wednesday, April 3, 2013 3:19 PM