locked
Communicator call RRS feed

  • Question

  •  

    I am currently having some trouble when I use communicator to make a call to someone that is a contact.  Below is the errors I was able to grab from the Windows Application log.

    Code Block

    Log Name:      Application

    Source:        Communicator

    Date:          11/29/2007 10:05:29 AM

    Event ID:      11

    Task Category: None

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      machine.corp.company.com

    Description:

    A SIP request made by Communicator failed in an unexpected manner (status code 80ef01e0). More information is contained in the following technical data:

     

     RequestUri:   sip:+phone#@company.com;user=phone

    From:         sip:firstname.lastname@company.com;tag=20a0dd390f

    To:           sip:+phone#@company.com;user=phone;tag=8763C7D3363BAAE317D977B98F94368D

    Call-ID:      427bbf72252b49af8db275a9a99c18a4

    Content-type: application/sdp;call-type=audiovideo

     

    v=0

    o=- 0 0 IN IP4 192.254.x.x

    s=session

    c=IN IP4 192.254.x.x

    b=CT:99980

    t=0 0

    m=audio 8448 RTP/AVP 114 111 112 115 116 4 8 0 97 101

    k=base64:ddfU2pjqg42IVLnYiED/5aX2J/kkEzBDWY4lROKthpD8ccun6POE3g+YjXlI

    a=candidate:0dK7CxKzYWTLDxEd8JHd6hhL9h9X/qX2e1YnlbmtN6A 1 5kswv5PRaWfjiFUS7RShBA UDP 0.900 192.168.206.1 62208

    a=candidate:0dK7CxKzYWTLDxEd8JHd6hhL9h9X/qX2e1YnlbmtN6A 2 5kswv5PRaWfjiFUS7RShBA UDP 0.900 192.168.206.1 30464

    a=candidate:iy1/YvuO+9X1xMyv4VHh+HW5P9giwTOFP0UBDxW8YJU 1 2qjAbMNB/umgCAMIhQ6nIQ UDP 0.900 192.254.20.46 8448

    a=candidate:iy1/YvuO+9X1xMyv4VHh+HW5P9giwTOFP0UBDxW8YJU 2 2qjAbMNB/umgCAMIhQ6nIQ UDP 0.900 192.254.20.46 21504

    a=candidate:7tAn9vf7iv0F0Gkqr0SSn0iBAxDbdqn1Fse9Joqzmto 1 LVB/M+nNZRWHMR/ih3PG4A UDP 0.900 192.168.159.1 15488

    a=candidate:7tAn9vf7iv0F0Gkqr0SSn0iBAxDbdqn1Fse9Joqzmto 2 LVB/M+nNZRWHMR/ih3PG4A UDP 0.900 192.168.159.1 63232

    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:Pub946RDBO8WbLDe1RmjHA8LBu9JD5TETiZoZ6LB|2^31|1:1

    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:x+dLAzoNq6+Ei4w/pvn08VtYI6a4UOMokqafytui|2^31|1:1

    a=maxptime:200

    a=rtcp:21504

    a=rtpmap:114 x-msrta/16000

    a=fmtp:114 bitrate=29000

    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=11800

    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=encryption:optional

     

     

    Response Data:

     

    480  Temporarily Unavailable

    ms-diagnostics:  2;reason="See response code and reason phrase";source="servername.corp.company.com";AppUri="http://www.microsoft.com/LCS/DefaultRouting"

     

     

     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.

    Event Xml:

     

     

    Then using Snooper I was able to grab the trace file from the tracing folder to get more detail.  This is what I was able to get from that:

    Code Block

    11/29/2007|09:11:53.905 340:17B4 INFO  :: Data Received - 192.254.x.x:5061 (To Local Address: 192.254.20.46:53033) 805 bytes:

    11/29/2007|09:11:53.905 340:17B4 INFO  :: SIP/2.0 480 Temporarily Unavailable

    Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF8068C3665D1C9C9EDBB7A3ED163F7CC6", srand="A44BA6A0", snum="160", opaque="544FF40B", qop="auth", targetname="sip/servername.corp.company.com", realm="SIP Communications Service"

    Via: SIP/2.0/TLS 192.254.x.x:53033;ms-received-port=53033;ms-received-cid=8400

    From: "Firstname Lastname"<sip:Firstname.Lastname@company.com>;tag=d86cd2ca4b;epid=255f4a491d

    To: <sip:phone#;phone-context=corporate.corp.company.com@company.com;user=phone>;tag=8763C7D3363BAAE317D977B98F94368D

    Call-ID: fcdd70ed5e2046da9eaaf63421381b9f

    CSeq: 1 INVITE

    ms-diagnostics: 2;reason="See response code and reason phrase";source="servername.corp.company.com";AppUri="http://www.microsoft.com/LCS/DefaultRouting"

    Content-Length: 0

     

     

    11/29/2007|09:11:53.905 340:17B4 INFO  :: End of Data Received - 192.254.x.x:5061 (To Local Address: 192.254.x.x:53033) 805 bytes

     

     

    While testing this, I was also running a debug session on the Medation server as well to see if something was set wrong and the server never even got the invite. 

    Any thoughts?
    Thursday, November 29, 2007 6:02 PM