The 3 applications everyone talks about are: - ITSP (sipXbridge to ITSP)
- "federated" systems (sipXproxy to another proxy) - phones (remote and local) The first two can use manually configured certificates. But for phones, we need to manage the certificates automatically, I think. I am assuming that each phone should have an individual certificate, and we need to be able to (implicitly or explicitly) invalidate certificates that are compromised. There is also a bootstrap problem: How do we get the certificate into the phone in the first place? Fortunately, we can generate individual certificates automatically. Dale _______________________________________________ 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/
