Bug 922895

Description of problem:
Upgrade sipe plugin to the following
purple-sipe-1.15.0-1.fc18.x86_64
pidgin-sipe-1.15.0-1.fc18.x86_64

Started up Pidgin, getting failed to authenticate to server.  Debug show this output.

MESSAGE END >>>>>>>>>> SIP - 2013-03-18T17:59:34.815926Z
(12:59:35) sipe: transport_input_common: new buffer length 4096
(12:59:35) sipe: 
MESSAGE START <<<<<<<<<< SIP - 2013-03-18T17:59:35.042087Z
SIP/2.0 401 Unauthorized
Date: Mon, 18 Mar 2013 17:59:34 GMT
/CertProvisioningService.svc"

Call-ID: CA8FgB845a4BA5iB743m77E1tA2DCbFA1CxDEE0x
CSeq: 1 REGISTER
Via: SIP/2.0/tls 192.168.1.63:59713;branch=z9hG4bKB89838A851EC52D05940;received=192.168.31.171;ms-received-port=59713;ms-received-cid=CC8500
Server: RTC/4.0
Content-Length: 0


MESSAGE END <<<<<<<<<< SIP - 2013-03-18T17:59:35.042087Z
(12:59:35) sipe: process_input_message: msg->response(401),msg->method(REGISTER)
(12:59:35) sipe: process_input_message: RE-REGISTER CSeq: 1
(12:59:35) sipe: process_input_message: we have a transaction callback
(12:59:35) sipe: process_register_response: got response to REGISTER; expires = 0
(12:59:35) sipe: process_register_response: REGISTER retries 1
(12:59:35) sipe: process_register_response: Auth header: NTLM realm="SIP Communications Service", targetname="USAP101.leinternal.com", version=4
(12:59:35) stun: using server 
(12:59:35) stun: using server 
(12:59:35) sipe: sip_sec_create_context: type: 1, Single Sign-On: yes, protocol: SIP
(12:59:35) sipe: ERROR: sip_sec_create_context: failed to acquire credentials.
(12:59:35) connection: Connection error on 0x2978190 (reason: 2 description: Failed to authenticate to server)
(12:59:35) sipe: sipe_schedule_allocate timeouts count 2 after addition
(12:59:35) sipe: scheduling action <transaction timeout><CA8FgB845a4BA5iB743m77E1tA2DCbFA1CxDEE0x><2 REGISTER> timeout 60 seconds
(12:59:35) sipe: SIP transactions count:2 after addition
(12:59:35) sipe: 
MESSAGE START >>>>>>>>>> SIP - 2013-03-18T17:59:35.053109Z

Max-Forwards: 70
CSeq: 2 REGISTER
User-Agent: Purple/2.10.7 Sipe/1.15.0 (linux-x86_64; )
Call-ID: CA8FgB845a4BA5iB743m77E1tA2DCbFA1CxDEE0x
Contact: <sip:192.168.1.63:59713;transport=tls;ms-opaque=d3470f2e1d>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:cfc39854-8db7-5f28-92f6-0328ff4df454>"
Supported: gruu-10, adhoclist, msrtc-event-categories, com.microsoft.msrtc.presence
Event: registration
Allow-Events: presence
ms-keep-alive: UAC;hop-hop=yes
Content-Length: 0


Seems to be having issues with certification.  I downgraded from the updates back to:

purple-sipe-1.13.3-1.fc18.x86_64
pidgin-sipe-1.13.3-1.fc18.x86_64


And it connects fine


Version-Release number of selected component (if applicable):



Steps to Reproduce:
1. Start up Pidgin
2.
3.
  
Actual results:
Fails authentication to server

Expected results:
Should connect

Additional info:
Downgrading purple-sipe and pidgin-sipe I am able to connect.