On Tue, Sep 4, 2012 at 3:26 PM, John Lightfoot <j...@vizhn.com> wrote: > > > I thought I'd put some effort into getting 4.6 to work with > Exchange Online UM which requires TLS transport with a > non-self-signed SSL certificate. Right out of the gate, the > TLS handshake fails when Exchange requests Sipx's client > certificate and Sipx returns a handshake message with the > cert empty. There's nothing logged that indicates Sipx > doesn't like the request, signing authority (MS's > intermediate authority certs are loaded in Sipx) or the > like. The sipxbridge.log only indicates that the far end > rudely tears the session down but nothing else. I had it > configured with 4.4 with the same cert and same Exchange > config and the cert exchange happened as expected. I'm a > little unclear how to turn the TLS logging to debug or what
John, no takers as far as developers responding, but I'm very thrilled you're testing. sipXbridge's TLS implementation hasn't changed AFAIK, but cert. management certainly has. Can you verify proper cert is delivered? _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
