On Thu, 2010-02-11 at 07:03 -0800, George Niculae wrote: > > --- On Wed, 2/10/10, Dale Worley <[email protected]> wrote: > > Carolyn Beeton wrote: > > > Hmmm... could sipXconfig provide a Test Connection > > button which would do > > > this? > > Yes, I think you've hit it. Of course, if you can't > > connect to that > > destination at the moment, it won't work. But it > > should be possible to > > arrange some way to make a connection to the destination in > > the same way > > as sipXecs would, and if not, to report in some detail what > > went wrong. > > That would include if the certificate subject name wasn't > > what was > > expected, of course. > > > > We could add such button in the TLS Peer main page - so one could > check the availability at any point in time (it will basically open a > SSLSocket to the configured peer and call SSLSocket.startHandshake on > it - a handshake exception is thrown if the certificate is not > trusted). > Does this makes sense?
There are a number of potential complexities in having sipXconfig do the test connection. Might it be easier to have sipXbridge raise an alarm when it rejects a connection because the server name does not match? If the alarm includes the actual name(s) from the connection, a human being could check them and put the right one into the configuration. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
