OCS Web Access won't come online RRS feed

  • Question

  • Hi all,


    I would be grateful if I could get some pointers/ideas on how to solve an issue with CWA that i'm having at the moment.


    I have installed CWA on the same server as my OCS 2k7 standard server (is this supported?). I have created an internal web app listening on port 446. Once I get things working I will use ISA 2k6 to publish CWA. BUT, I have to get things working first. Here's my problem. I can get to the CWA web page and I can authenticate alright (using forms or windows auth). The CWA opens up in a new window but it refuses to come online. This is the error inside the CWA window:

    "Your session was ended. Communicator Web Access cannot sign in to the server. If this problem persists, contact your system administrator.(Error code: 0-0-18100-2-400)  
      Sign in will be automatically retried at 6:16 AM. "

    I have started logging on the server (S4-all) and I think this is the primary error.


    <<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_145303B>],<-
    SIP/2.0 400 Malformed Edge Proxy header
    FROM: <sipTongue Tiedtefan@domain.com>;epid=C6638E8AD8;tag=b920416bc7
    TO: <sipTongue Tiedtefan@domain.com>;tag=1FB1685E5163015999647ABFA0B02AD5
    CALL-ID: 26d0b0bafde14273a9bb2fa0d74c5b37
    VIA: SIP/2.0/TLS;branch=z9hG4bK8faf5270;ms-received-port=1971;ms-received-cid=1E00
    ms-diagnostics: 1018;reason="Parsing failure";source="mabwlgocs002.domain.com"

    ------------EndOfIncoming SipMessage



    Any ideas? The full communicator client works fine both interally and externally. I



    Tuesday, August 14, 2007 7:20 PM

All replies

  • I am going to guess this has to do with CWA being installed on your OCS 2007 server. Are you able to move it to a different computer? You can virtualize the CWA server if no otehr server is available and the OCS server has enough resources.


    Friday, September 14, 2007 10:40 PM
  • Well I have CWA installed on the same server as OCS2k7 and it does work. so that should not be a problem.

    However, I found that I had to specify the server name rather that the IP address in IE7 to connect because we have ISA2k4 as our proxy.

    I too have not published the server until I know it works! ;-)

    Monday, September 17, 2007 8:31 AM