> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Scott Lawrence > > For example, some systems may require that connections to > them be made with mutually authenticated TLS; in order to > interoperate with them, a peer would be configured so that > there is somewhere to insert the > required certificate chain and to give it a name. You don't want to > have to invent a dummy permission to give them just to be > able to connect to them. >
I don't think the TLS Peer configuration has anything to do with certificate chains, but what do I know :-) The remote system will send us its cert when a TLS connection is set up, and the admin must have installed the CA that that cert is signed with. This is done on the Certificates page, not on the TLS Peer page. The only thing that adding a TLS Peer does is apply permissions to calls coming in from that peer. It is entirely optional, and not having a TLS Peer configured is the same as having one configured which has no permissions. Carolyn _______________________________________________ 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/
