locked
Issue with internal Call Connection RRS feed

  • Question

  • My OCS environment seems to be working well internally, but I am trying to figure out why calls are failing between two internal workstations.  Everyting I initiate a call the client rings the call picks up and ends.  On one of my workstation the event log reports no errors.  The other workstation reports the following:

     

    A SIP request made by Communicator failed in an unexpected manner (status code 80004005). More information is contained in the following technical data:
     
     RequestUri:   sip:ITLLCS1.ocstest.com:5061;transport=tls;ms-role-rs-from;ms-role-rs-to;ms-opaque=aasYI7OwbmsvebYAcBnGjL1QAA;lr;ms-route-sig=aa2e7iLpse8EjFhfdQjUOEHG6zH-QEnNDDaGw3MAAA
    From:         sip:jsmith@ocstest.com;tag=4454da9000
    To:           sip:janed@ocstest.com;tag=ef627f57e7
    Call-ID:      c782a0e5b1e341b2a2e74731bf088e38
    Content-type: application/sdp

    v=0
    o=- 0 0 IN IP4 172.17.0.57
    s=session
    c=IN IP4 172.17.0.57
    b=CT:99980
    t=0 0
    m=audio 30336 RTP/AVP 114 111 112 115 116 4 8 0 97 101
    k=base64:MRqIFVg5vWCWsTs+DahlW/udjx1P/37otdpClNWXtzycq6BI3Sj9qUWYUv9a
    a=candidate:yP+fB0P4EmYigGLM29q3IlMITEhSfHtN8HC0ZJ4tYjQ 1 4Boz39DLHR8te2O75jAYdQ UDP 0.900 172.17.0.50 45568
    a=candidate:yP+fB0P4EmYigGLM29q3IlMITEhSfHtN8HC0ZJ4tYjQ 2 4Boz39DLHR8te2O75jAYdQ UDP 0.900 172.17.0.50 58496
    a=candidate:TYNiPpnSdErJSp5kllaJfiNcHJHYZHWUVBMdKJuRRXk 1 s0if9bMIJqqZ2Q5ieT5FWQ UDP 0.900 172.17.0.57 30336
    a=candidate:TYNiPpnSdErJSp5kllaJfiNcHJHYZHWUVBMdKJuRRXk 2 s0if9bMIJqqZ2Q5ieT5FWQ UDP 0.900 172.17.0.57 18176
    a=candidateSurpriseRzCLaaUMv00/tVAfd1l9nzwayPiqLysNm51WmrFJyU 1 8yFdc6jojUCtXIUv5LGXYw TCP 0.190 172.17.1.109 51212
    a=candidateSurpriseRzCLaaUMv00/tVAfd1l9nzwayPiqLysNm51WmrFJyU 2 8yFdc6jojUCtXIUv5LGXYw TCP 0.190 172.17.1.109 51212
    a=candidate:/nSPPahiz/0wXFWH5TzjZPWNvZVRU/xlbuCJbnGZqy4 1 z8Wu5lzA96gu7QYmb6CB+A UDP 0.490 172.17.1.109 57532
    a=candidate:/nSPPahiz/0wXFWH5TzjZPWNvZVRU/xlbuCJbnGZqy4 2 z8Wu5lzA96gu7QYmb6CB+A UDP 0.490 172.17.1.109 56732
    a=candidate:vn6rwLeGPJk1io1pY2wthOavVRmK8e8+Zd8Yt58kcmA 1 sffI89iCh/5ZeZ2NBWcpcw TCP 0.250 172.17.0.57 38656
    a=candidate:vn6rwLeGPJk1io1pY2wthOavVRmK8e8+Zd8Yt58kcmA 2 sffI89iCh/5ZeZ2NBWcpcw TCP 0.250 172.17.0.57 38656
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:xfScXZ/jOVblNCQW39gNZVUbzJufHk362VQeX1uk|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:KNelD0/jJmj56UW1IV5LCvK9ZefuylPde+DLTz4f|2^31|1:1
    a=maxptime:200
    a=rtcp:18176
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=12000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=12000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:4 G723/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryptionSurpriseptional


    Response Data:

    100  Trying


    180  Ringing

     
     Resolution:
     If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

    Monday, April 23, 2007 1:10 AM

Answers

  • Are both computers able to use their mics and speakers ok? When you speak into the computer after the call has connected, do you see the sound indicator bar go up indicating sound has been received? I have seen this issue in the past on Vista where the sound driver is the culprit and preventing correct recording and playback of voice. Check to make sure the computer itself can record sound.
    Monday, April 23, 2007 1:16 AM

All replies

  • Are both computers able to use their mics and speakers ok? When you speak into the computer after the call has connected, do you see the sound indicator bar go up indicating sound has been received? I have seen this issue in the past on Vista where the sound driver is the culprit and preventing correct recording and playback of voice. Check to make sure the computer itself can record sound.
    Monday, April 23, 2007 1:16 AM
  • It turns out that it was a driver issue.  After updating the driver on one of the workstations, the issue was resolved.

     

    Thanks!

    Tuesday, May 1, 2007 3:52 PM