...
| # | Title | Importance | Notes |
|---|---|---|---|
| 1 | SHALL support SIP with TLS (RFC5246) and use cases shall follow SIP TLS examples shown in RFC6216 (SIP Secure Call Flows) | ||
| 2 | SHALL support SIP TLS with SSLv3 and TLSv1 security | ||
| 3 | SHALL support standard cipher suites, such as: TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 | ||
| 4 | SHALL allow SIP TLS to establish RTP media with G.711 or to establish T.38 SIP TLS SHALL be independent of media. It SHALL not be required to use SIP TLS to establish a secure media channel. | ||
| Config Tool Requirements | |||
| 5 | SHALL allow a configurable port for SIP TLS(through the Config Tool); the default port SHALL be 5061field to enable or disable the use of SIP over TLS. | ||
| 6 | SHALL provide certificate management capability. Customers will require a method to create, store and select certificates, as well as to export certificate to use on the remote endpoint. This capability SHALL be built into (Config Tool?)allow a field to allow the end user to provide a configuration file for SIP over TLS. This configuration file will be used to config the required SIP over TLS parameters. | ||
| 7 | SIP TLS implementation SHALL be tested against a variety of endpoints and network equipment for accurate implementation. | BN2020 gateway, Cisco Gateway, SIP registrar (such as OpenSIPS) | |
| 8 | SIP over TLS supported on by a single license keywork (TBDSecurity). This keyword enables TLS functionality on a per system basis. | Part #951-105-20 | |
| Documentation Requirements TBD | |||
| COO Will need to be updated with changes to include OpenSSL into the product | |||
| Part numbers will need to be defined for SR140 with Security. Add on part will need to be defined to add security to an existing SR140 deployment. | |||
...