locked
Audio Call hangs up after 5seconds RRS feed

  • Question

  • Hi,

    When I make a call between 2 Communicator clients internally they initially connect and I get audio however they hang up after around 5seconds with the error Ms-client-diagnostics: 52031; reason="Call terminated on media connectivity failure".

    I have enabled logging and I can see what seems to be causing this

    07/04/2007|16:43:05.597 A08:B1C WARN  :: Connectivity Checks failed for media - 29104492 - Channel 00000001.
    07/04/2007|16:43:05.597 A08:B1C INFO  :: Function: CRTCStream::CollectMidCallMetrics
    07/04/2007|16:43:05.597 A08:B1C ERROR :: HRESULT API failed: c0042003 = hr. failed to get metrics
    07/04/2007|16:43:05.613 A08:B1C INFO  :: Function: CRTCStream::CollectMidCallMetrics
    07/04/2007|16:43:05.613 A08:B1C ERROR :: HRESULT API failed: c0042003 = hr. failed to get metrics

    What are these mid call metrics?
    Thanks
    Wednesday, July 4, 2007 4:01 PM

Answers

  • I don't get it....after rebooting my laptop and reconfiguring the sound in the Communicator tools menu it suddenly works again. So this definitely had something to do with Communicator and not with the server...(?).

     

    /Thomas

     

     

    Monday, August 13, 2007 5:22 AM

All replies

  • I haven't been able to find out what the CollectMidCallMetrics are. Can you let us know your current status? Have you tried any other troubleshooting?
    Friday, July 27, 2007 5:09 PM
  • I have the same issue. I'm getting this in the error log (I was using the logging tool in OCS):

     

    ms-edge-proxy-message-trust:  ms-source-type=InternetUser;ms-ep-fqdn=EDGESERVER.DOMAIN.NAME;ms-source-verified-user=verified

    Via:  SIP/2.0/TLS LOCAL_LAPTOP_IP:1579;received=PUBLIC_IP_INTERNET;ms-received-port=1579;ms-received-cid=2500

    Route:  <sip:INTERNALOCS.DOMAIN.NAME:5061;transport=tls;ms-role-rs-from;lr>

    User-Agent:  UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)

    Ms-client-diagnostics:  52031; reason="Call terminated on media connectivity failure"

    Proxy-Authorization:  NTLM qop="auth", realm="SIP Communications Service", opaque="C326CE34", crand="7a4dc7af", cnum="37", targetname="INTERNALOCS.DOMAIN.NAME", response="010000002b333136a73b497034b51dc8"

    Content-Length:  0

    Message-Body: –

    $$end_record

     

    I can log on using office communicator. Once I make a outbound call to a fixed line or mobile number... the phone rings and after picking it up the line, Communicators shows "Connecting call", after a while the line is disconnected.

     

    When I click on the "Call was disconnected" in COmmunicator I can see:

     

    The call was disconnected because Communicator stopped receiving audio from CALLER NAME. Please try the call again.

     

    I can't find any more information in the eventvwr. I can only find:

     

    "

    Communicator has enabled event logging.

    Information about failed calls will be sent to the Windows event log.

    "

     

    Is there any more information logged somewhere on my laptop?

     

    Why is this happening. It used to work and suddenly I can't make calls anymore?

     

    Is the audio blocked by a firewall or something?

    Could there be AV authentication errors because of non -valid certificates?

     

    When I call the communicator and divert to voice mail it works. I can hear my voice mail box so audio works in this case.

     

    Any resolutions/advice?

    Any debugging tips?

     

    /Thomas

     

    Sunday, August 12, 2007 6:07 PM
  • I don't get it....after rebooting my laptop and reconfiguring the sound in the Communicator tools menu it suddenly works again. So this definitely had something to do with Communicator and not with the server...(?).

     

    /Thomas

     

     

    Monday, August 13, 2007 5:22 AM
  • But when I call my voicemail I get another error:

     

     The call was disconnected because Communicator stopped receiving audio from Voice Mail. Please try the call again.

     

    I only get this message when I call my voicemail connected via Edge server. When I'm connect via OCS I can call the Exchange voice mail.

     

    Why is it that calls via OCS are working fine while Exchange can not find it's route back via Edge to the client? Is this an Exchange UM setting?

     

    /Thomas

    Monday, August 13, 2007 5:27 AM
  • I was scanning through the logs...

     

    My Inbound routing log  gives the following:

     

    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.295.000000a4 (InboundRouting,InboundRoutingResponse.constructor:1077.idx(1335))Response has ms-diagnostic header with value: 15009
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.295.000000a5 (InboundRouting,RoutingContext.SetState:240.idx(680))( 00EA7AEC )Context State: ScriptComplete->ScriptCompleteResponse
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.295.000000a6 (InboundRouting,InboundRoutingContext.ProxyResponseImpl:1077.idx(559))( 00EA7AEC )Proxying response 101
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.295.000000a7 (InboundRouting,RoutingContext.SetState:240.idx(680))( 00EA7AEC )Context State: ScriptCompleteResponse->ScriptComplete
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.556.000000a8 (InboundRouting,InboundRoutingClientTransaction.ResponseReceived:1077.idx(1194))( 0239D878 )ResponseReceived 200 from sip:SogetiAA.Sogeti.sgtiocs.nl@sgtiocs.nl;opaque=app:exumTongue Tiedogeti.sgtiocs.nlTongue TiedogetiAA
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.556.000000a9 (InboundRouting,RoutingContext.SetState:240.idx(680))( 00EA7AEC )Context State: ScriptComplete->ScriptCompleteResponse
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.556.000000aa (InboundRouting,InboundRoutingContext.ProxyResponseImpl:1077.idx(559))( 00EA7AEC )Proxying response 200
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.556.000000ab (InboundRouting,RoutingContext.CancelAllOutstandingRequests:240.idx(1216))( 00EA7AEC )CancelAllOutstandingRequests() reason=SIP; cause=200; ms-acceptedby=\"sipTongue TiedogetiAA.Sogeti.sgtiocs.nl@sgtiocs.nl;opaque=app:exumTongue Tiedogeti.sgtiocs.nlTongue TiedogetiAA\"
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.556.000000ac (InboundRouting,RoutingContext.SetState:240.idx(680))( 00EA7AEC )Context State: ScriptCompleteResponse->Terminated
    TL_INFO(TF_COMPONENT) [0]1628.1CC4::08/13/2007-13:05:56.556.000000ad (InboundRouting,InboundRoutingContext.OnSessionTerminated:1077.idx(612))( 00EA7AEC )Session terminated.

     

    My SIP stack log gives the following (SogetiAA.Sogeti.sgtiocs.nl = the auto attandent):

     

    TL_INFO(TF_PROTOCOL) [0]126C.1CB4::08/13/2007-13:05:56.385.00021dfa (SIPStack,SIPAdminLog::WriteProtocolMessage:8.idx(234))$$begin_record

    Instance-Id: 00001300

    Direction: outgoing

    Peer: INTERNAL_EXCHANGE_SERVER_NAMEsgtiocs.nl:5068

    Message-Type: request

    Start-Line: INVITE sipTongue TiedogetiAA.Sogeti@INTERNAL_EXCHANGE_SERVER_NAME.sgtiocs.nl:5068;transport=tls;maddr=INTERNAL_EXCHANGE_SERVER_NAME.sgtiocs.nl SIP/2.0

    From: "Thomas Wesseling"<sip:wesselth@sgtiocs.nl>;tag=8ddd0095e2;epid=9c9672a6c4

    To: <sip:150;phone-context=sogeti.sgtiocs.nl@sgtiocs.nl;user=phone>

    CSeq: 1 INVITE

    Call-ID: dd558f7e422f4bd6a80f0d79df3b45f3

    ms-user-data: ms-publiccloud=true;ms-federation=true

    Record-Route: <sip:INTERNAL_OCS_SERVER_NAME.sgtiocs.nl:5061;transport=tls;ms-role-rs-to;ms-opaque=da3rBFK_xhkAciF07bCbQGzgAA;lr>;tag=2943638E5F7844CFC0CA88AC6030E6BE

    Via: SIP/2.0/TLS 172.19.160.20:3533;branch=z9hG4bK88DA219D.E49982A4;branched=TRUE

    Max-Forwards: 9

    Content-Length: 1518

    Via: SIP/2.0/TLS 172.19.160.25:4948;branch=z9hG4bK729D4DDC.FD7E5FA0;branched=FALSE;ms-received-port=4948;ms-received-cid=1FA00

    Via: SIP/2.0/TLS 172.19.65.81:33522;received=194.151.67.13;ms-received-port=33522;ms-received-cid=7800

    P-Asserted-Identity: "Thomas Wesseling"<sip:wesselth@sgtiocs.nl>,<tel:+31347324151>

    ms-edge-proxy-message-trust: ms-source-type=InternetUser;ms-ep-fqdn=INTERNAL_EDGE_SERVER_NAME.sgtiocs.nl;ms-source-verified-user=verified

    Contact: <sip:wesselth@sgtiocs.nl;opaque=user:epid:89pVLVMHN1y24fH4_hlBdAAA;gruu>

    User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)

    Ms-Conversation-ID: Acfdqrk2noKtGxs8T+KO05MQg7/oPQ==

    Supported: timer

    Supported: ms-sender

    Supported: ms-early-media

    ms-keep-alive: UAC;hop-hop=yes

    Supported: ms-conf-invite

    Content-Type: application/sdp

    Referred-By: <sip:SogetiAA.Sogeti.sgtiocs.nl@sgtiocs.nl>;ms-identity="MIIBLAYJKoZIhvcNAQcCoIIBHTCCARkCAQExDzANBgkqhkiG9w0BAQUFADALBgkqhkiG9w0BBwExgfUwgfICAQEwTDA-MRIwEAYKCZImiZPyLGQBGRYCbmwxFzAVBgoJkiaJk_IsZAEZFgdzZ3Rpb2NzMQ8wDQYDVQQDEwZTb2dldGkCChidkEUAAAAAACgwDQYJKoZIhvcNAQEFBQAwDQYJKoZIhvcNAQEBBQAEgYBN2KCIhm4-9Qa52Q5bGH5IHD8vFws6eZA07M7XfwTAM_uxtrlxPugv_BEX9vNOeb4SJZiEP5XRr-efkPJ6owFCunImxdiWz4D0-tpyhJlzDvJUCqHyXH7mfi7nt7MeouSOtZyoMOooaWRfiQzZDyMmlDrvjC7KeNVTWNsF8RiqlwAA:Mon, 13 Aug 2007 13:05:56 GMT";ms-identity-info="sip:INTERNAL_OCS_SERVER_NAME.sgtiocs.nl:5061;transport=tls";ms-identity-alg=rsa-sha1

    Ms-Target-Class: Primary

    Ms-Mras-Address: <sip:INTERNAL_EDGE_SERVER_NAME@sgtiocs.nl;gruu;opaque=srvr:MRAS:Z9gESNnRQt-qWXpv_H9A_gAA>

    Message-Body: ----****MESSAGE BODY DELETED****----

    $$end_record

     

    It looks that the routing works ok. Is this a firewall issue? Why can I make outbound phone calls  via Edge and receive audio and not call receive audio by calling my internal voice mail?

     

    /Thomas

    Tuesday, August 14, 2007 2:04 PM
  • Hi everyone,

    it might be quite an old topic, but one of my users is complaining with exactly the same problem after getting his new laptop:

    he cannot finish some calls in communicator because when he clicks disconnect, the communicator is freezing (the call roaster stops responding). In the communicator logfile this is the very last section (not sure if it was able to flush the real cause of the problem into the trace):

    04/28/2008|16:52:47.961 9F8:F48 INFO  :: End of Sending Packet - OCS-IP-ADDRESS:5061 (From Local Address: 192.168.1.129:2130) 803 bytes
    04/28/2008|16:52:47.961 9F8:F48 TRACE :: - encrypted buffer length: 824 bytes.  First 8 bytes:
    04/28/2008|16:52:47.961 9F8:F48 TRACE ::     17 03 01 03 33 FA 30 B9  :....3˙0╣
    04/28/2008|16:52:47.961 9F8:F48 TRACE :: ASYNC_SOCKET:Tongue TiedendOrQueueIfSendIsBlocking sending sendBuffer 032747E0, this 012CE848
    04/28/2008|16:52:47.961 9F8:F48 TRACE :: ASYNC_SOCKET:Tongue TiedendHelperFn sendBuffer 032747E0 sent, this 012CE848
    04/28/2008|16:52:47.961 9F8:F48 ERROR :: SIP_MESSAGE::GetSipReasonFromReasonHeaders GetHeader(Reason) failed 80ee0005, this 03029AC0
    04/28/2008|16:52:47.961 9F8:F48 TRACE :: call.SetState[012C7978]  SIP_CALL_STATE_DISCONNECTED-->SIP_CALL_STATE_DISCONNECTED for sip:+441-PSTN-PHONE-NUMBER@DOMAINNAME.com;user=phone, stack=01C83C60
    04/28/2008|16:52:47.961 9F8:F48 TRACE :: SIP_CALL::NotifyCallStateChange[012C7978] : CallState : 2 StatusCode: 0, s=2
    04/28/2008|16:52:47.961 9F8:F48 TRACE :: MULTIPARTY_SESSION::NotifyCallChange[01210880]- call-leg:012C7978, Callstate:2 StatusCode:0 SessionState:4
    04/28/2008|16:52:47.961 9F8:F48 INFO  :: CUccMultipartySession::NotifyPartyChange[0303D59C] - for participant [sip:+441-PSTN-PHONE-NUMBER@DOMAINNAME.com;user=phone]
    04/28/2008|16:52:47.961 9F8:F48 INFO  :: Function: CRTCStream::CollectMidCallMetrics
    04/28/2008|16:52:47.961 9F8:F48 ERROR :: HRESULT API failed: c0042003 = hr. failed to get metrics
    04/28/2008|16:52:47.977 9F8:F48 INFO  :: Function: CRTCStream::CollectMidCallMetrics
    04/28/2008|16:52:47.977 9F8:F48 ERROR :: HRESULT API failed: c0042003 = hr. failed to get metrics
    04/28/2008|16:52:47.977 9F8:F48 INFO  :: Function: CRTCChannel::CreateUCCPMediaAddress
    04/28/2008|16:52:47.977 9F8:F48 ERROR :: HRESULT API failed: 80ee0058 = hr. failed to get the subnet mask

    And that is all. Any idea? The user is running the Apr02 hotfix of Communicator.
    Saturday, May 3, 2008 6:59 PM