Asked by:
Problem with PIC, keeping getting disconnected.

Question
-
Hello all,
I have a 2007 R2 edge server set up. We use a RapidSSL certificate. The edge server SEEMS to be working fine, in that external users can actually use it perfectly well. THis means definitely there are no issues with the certificate (like a misspelled domain name), there is no error in routing etc., at least to my knowledge.
What does not work is PIC.
When I try to reach a hotmail contact, I get disconnected.
The sequence I seem to get is:
* TLS negotation starts
TL_INFO(TF_CONNECTION) [0]05C0.0B18::02/27/2009-07:04:59.651.00000034 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(161))$$begin_record
LogType: connection
Severity: information
Text: TLS negotiation started
Local-IP: 80.190.175.42:65477
Peer-IP: 65.54.227.249:5061
Peer-FQDN: federation.messenger.msn.com
Connection-ID: 0x12F02
Transport: TLS
$$end_record
* TLS connection gets established:
TL_INFO(TF_CONNECTION) [0]05C0.0B18::02/27/2009-07:05:00.323.00000039 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(161))$$begin_record
LogType: connection
Severity: information
Text: Connection established
Local-IP: 80.190.175.42:65477
Peer-IP: 65.54.227.249:5061
Peer-FQDN: federation.messenger.msn.com
Peer-Name: federation.messenger.msn.com
Connection-ID: 0x12F02
Transport: M-TLS
$$end_record
I am not sure at this moment whether this means that my certificate was indeed accepted or not.
I then get a sip INVITE going out.
And then I get...
* CONNECTION: Receive Operation on the connection failed
TL_ERROR(TF_CONNECTION) [0]05C0.0B18::02/27/2009-07:05:00.416.00000041 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(157))$$begin_record
LogType: connection
Severity: error
Text: Receive operation on the connection failed
Local-IP: 80.190.175.42:65477
Peer-IP: 65.54.227.249:5061
Peer-FQDN: federation.messenger.msn.com
Peer-Name: federation.messenger.msn.com
Connection-ID: 0x12F02
Transport: M-TLS
Result-Code: 0x80072746 WSAECONNRESET
$$end_record
And that basically "is it". It is followed by a connection close:
TL_INFO(TF_CONNECTION) [0]05C0.0B18::02/27/2009-07:05:00.416.00000042 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(161))$$begin_record
LogType: connection
Severity: information
Text: Connection closed
Local-IP: 80.190.175.42:65477
Peer-IP: 65.54.227.249:5061
Peer-FQDN: federation.messenger.msn.com
Peer-Name: federation.messenger.msn.com
Connection-ID: 0x12F02
Transport: M-TLS
$$end_record
The stupid thing is that there is no more info, and it seems there is no way to get the other sides error report from Microsoft, no way to get ANY error information. Anyone has an idea what may be wrong here? Or an advice how to proceed?
With friendly regards
;)Friday, February 27, 2009 10:15 AM
All replies
-
I have the exact same issue, any update ?
Thank youThursday, April 9, 2009 12:01 PM -
Does your certificate have both, server and client authentication ?
PIC needs both
Cheers
WernerThursday, May 7, 2009 9:32 PM -
Does your certificate have both, server and client authentication ?
I thought this was true, but only if using AOL. I am using only MSN & I have errors as well.
PIC needs both
Cheers
WernerI can initiate a chat from OCS to MSN, but the replies do not return. When I initiate from MSN to OCS, all works well.Monday, May 18, 2009 4:32 PM