none
"Benotify" only work in Debug mode

    Question

  • One problem that I have unable to find a solution to is an inability to subscribe to presence events in the OCS from a OCS Server. In fact, the subscribe message are successfully sent but there is no notification from the OCS. However, when the application runs in "Debug F5" mode in visual studio, it seems work correctly.

    Any ideas of why would this happen? Thanks a lot.

    Wednesday, April 07, 2010 9:12 AM

Answers

  • Thanks again.

    This issue has been addressed. This is because it seems UCMA 2.0 is not compatible with windows server 2008 R2. I run the same application in windows server 2008 and everything works properly.

    • Marked as answer by deeplin Friday, April 09, 2010 3:03 PM
    Friday, April 09, 2010 3:03 PM

All replies

  • Here is the error trace from OCS Server.

    TL_VERBOSE(TF_COMPONENT) [0]0C78.08F0::04/07/2010-09:16:23.964.0000054f (SIPStack,DiagStoreBucketEventCounter<unsigned:DiagStoreBucketEventCounter.h(143))( 0000000000459350 ) A few buckets were rolled over, but not the entire table
    TL_ERROR(TF_CONNECTION) [0]0C78.08F0::04/07/2010-09:16:23.964.00000550 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(157))$$begin_record
    LogType: connection
    Severity: error
    Text: Receive operation on the connection failed
    Local-IP: 192.168.10.10:56101
    Peer-IP: 192.168.10.12:5061
    Peer-FQDN: moloco.vfrndbeta.com
    Connection-ID: 0x3500
    Transport: TLS
    Result-Code: 0x80072746 WSAECONNRESET
    $$end_record

    TL_ERROR(TF_CONNECTION) [0]0C78.08F0::04/07/2010-09:16:23.964.00000551 (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(157))$$begin_record
    LogType: connection
    Severity: error
    Text: The connection was closed before TLS negotiation completed. Did the remote peer accept our certificate?
    Local-IP: 192.168.10.10:56101
    Peer-IP: 192.168.10.12:5061
    Peer-FQDN: moloco.vfrndbeta.com
    Connection-ID: 0x3500
    Transport: TLS
    $$end_record

    Wednesday, April 07, 2010 9:26 AM
  • Are you debugging on different machine and problem occurs on different machine. From first look it appears that your debugging machine/account have OCS certificate trusted but other machine does not trust OCS certificate.
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, April 07, 2010 8:17 PM
  • Thanks for replying.

    Yes, I am debuging in the same machine with same user account. Because it works fine in debug mode, it seems the certificate should be properly issued.

    However, from the trace, it seems the OCS server tries to establish a new TLS connection to the Client on port 5061 insteading of reusing existing established subscribe TLS connection which would not occur in debug mode.

    Local-IP: 192.168.10.10:56101
    Peer-IP: 192.168.10.12:5061

    Any reason why the ocs server tried to establish a new TLS connection? Thanks a lot.

    Thursday, April 08, 2010 8:03 AM
  • That's really surprising that it works on same box in debug time but not otherwise. Can you tell me little bit more about your application, are you using Server/Client platform, UserEndpoint/ApplicationEndpoint. Also what is your deployment topology.
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, April 08, 2010 9:39 PM
  • Thanks again.

    This issue has been addressed. This is because it seems UCMA 2.0 is not compatible with windows server 2008 R2. I run the same application in windows server 2008 and everything works properly.

    • Marked as answer by deeplin Friday, April 09, 2010 3:03 PM
    Friday, April 09, 2010 3:03 PM
  • Hi Deeplin,

             There was an issue in TLS negotiation in original UCMA 2.0, which was fixed in later patches. Now UCMA 2.0 should be working with Windows server 2008 R2.

    You can get details from http://support.microsoft.com/kb/972713/EN-US, you can download the fix through Windows Update or from http://support.microsoft.com/kb/970679/


    Posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, April 09, 2010 4:55 PM
  • However, I have already installed that hot fix. So, there should be another bug.
    Friday, April 09, 2010 9:23 PM
  • Yes, if you are hitting this issue even after hot fix installation. This could be some other unknown issue, could you possibly share the logs for the failure.
    Posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, April 16, 2010 6:08 PM
  • We have the same problem. Is there any solution available?
    Wednesday, September 29, 2010 11:21 AM