Difference between revisions of "VoIP Security"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
(→Documentation) |
Hans.zeiner (talk | contribs) (→IEEE 802.1X) |
||
| (5 intermediate revisions by 5 users not shown) | |||
| Line 4: | Line 4: | ||
Buzzwords to improve the above mentioned properties are [[Signalling and Payload Encryption|SPE]], [[TLS]], [[SRTP]] and [[PKI]]. | Buzzwords to improve the above mentioned properties are [[Signalling and Payload Encryption|SPE]], [[TLS]], [[SRTP]] and [[PKI]]. | ||
| − | HiPath platforms like [[HiPath | + | HiPath platforms like [[HiPath 3000]] or [[OpenScape Office MX]] use the most current technology to protect voice and signalling data from unauthorized access. |
How to use secure [[VoIP]] on optiPoint [[SIP]] phones in general: {{File-DL|Gesicherte Sprachübertragung in SIP 7|pdf|de}} | How to use secure [[VoIP]] on optiPoint [[SIP]] phones in general: {{File-DL|Gesicherte Sprachübertragung in SIP 7|pdf|de}} | ||
| Line 15: | Line 15: | ||
== Signalling and Payload Encryption (SPE) == | == Signalling and Payload Encryption (SPE) == | ||
| + | === Activate Signalling and Payload Encryption (SPE) on a [[OpenStage]] HFA Phone === | ||
| + | |||
| + | To enable security support on the optipoint HFA phones following settings must be done via local configuration or administration web page. | ||
| + | *Configure transport mode LocalAdmin: Administration -> System -> Security -> Signalling main = TLS | ||
| + | *Configure transport mode WEB: Admin -> System -> Security -> Secure H.235 main = TLS | ||
| + | **Configure C-TC TLS port in accordance to the CGW configuration (AMO-CGWB: (…), TYP=globif, TLSP=<C-TC TLS port>;), default: 4061 | ||
| + | **H.225 TLS port: 1300 (fixed) | ||
| + | **Transport mode: TLS | ||
| + | **Certificate validation main can now be enabled, in this case certificate must be downloaded via DLS | ||
| + | **If you use the feature SRSR. And the standby System is using SPE too, then please configure also Secure H.235 standby(WEB) -or- Signalling standby(LocalAdmin). And Certificate validation standby (if used) | ||
| + | [[Image:SPE_config_OST_HFA.jpg]] | ||
| Line 26: | Line 37: | ||
**Certificate check can now be enabled, in this case certificate must be downloaded via DLS | **Certificate check can now be enabled, in this case certificate must be downloaded via DLS | ||
[[Image:SPE_config_HFA.jpg]] | [[Image:SPE_config_HFA.jpg]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== IEEE 802.1X == | == IEEE 802.1X == | ||
| Line 37: | Line 42: | ||
How to configure IEEE 802.1X by [[DLS]]: | How to configure IEEE 802.1X by [[DLS]]: | ||
* {{File-DL|IEEE 802.1X Configuration Management|pdf}} | * {{File-DL|IEEE 802.1X Configuration Management|pdf}} | ||
| − | + | ||
Basic Requirements For 802.1x Certificates | Basic Requirements For 802.1x Certificates | ||
* {{en}} [[802.1x Certificates]] | * {{en}} [[802.1x Certificates]] | ||
* {{de}} [[802.1x Zertifikate]] | * {{de}} [[802.1x Zertifikate]] | ||
| + | |||
| + | == Certificate Management (an alternative, available on [[optiPoint]] phones only) == | ||
| + | |||
| + | How to implement and set up a secure environment and provide [[optiPoint]] phones with configuration data by the use of XML files via secure Web server (note, that this type of interface is not provided by [[OpenStage]] phones): | ||
| + | * {{File-DL|Certificate over secure link|pdf}} | ||
| + | * {{File-DL|Zertifikate über gesicherte Verbindung|pdf|de}} | ||
Latest revision as of 13:27, 20 October 2021
Regarding IP telephony the subject VoIP Security becomes more and more important. VoIP must have the same confidentiality, authenticity, availability and integrity as traditional telephony solutions.
Buzzwords to improve the above mentioned properties are SPE, TLS, SRTP and PKI.
HiPath platforms like HiPath 3000 or OpenScape Office MX use the most current technology to protect voice and signalling data from unauthorized access.
How to use secure VoIP on optiPoint SIP phones in general: 
Gesicherte Sprachübertragung in SIP 7
|
Please have a look also at the administrator documentation to IP phones of the optiPoint and OpenStage families and the service documentation for the IP platforms. |
Contents
Signalling and Payload Encryption (SPE)
Activate Signalling and Payload Encryption (SPE) on a OpenStage HFA Phone
To enable security support on the optipoint HFA phones following settings must be done via local configuration or administration web page.
- Configure transport mode LocalAdmin: Administration -> System -> Security -> Signalling main = TLS
- Configure transport mode WEB: Admin -> System -> Security -> Secure H.235 main = TLS
- Configure C-TC TLS port in accordance to the CGW configuration (AMO-CGWB: (…), TYP=globif, TLSP=<C-TC TLS port>;), default: 4061
- H.225 TLS port: 1300 (fixed)
- Transport mode: TLS
- Certificate validation main can now be enabled, in this case certificate must be downloaded via DLS
- If you use the feature SRSR. And the standby System is using SPE too, then please configure also Secure H.235 standby(WEB) -or- Signalling standby(LocalAdmin). And Certificate validation standby (if used)
Activate Signalling and Payload Encryption (SPE) on a optiPoint HFA Phone
To enable security support on the optipoint HFA phones following settings must be done via local configuration or administration web page.
- Configure transport mode: Administration -> System -> Signaling & Payload Encryption (SPE)
- Configure C-TC TLS port in accordance to the CGW configuration (AMO-CGWB: (…), TYP=globif, TLSP=<C-TC TLS port>;), default: 4061
- H.225 TLS port: 1300 (fixed)
- Transport mode: TLS
- Certificate check can now be enabled, in this case certificate must be downloaded via DLS
IEEE 802.1X
How to configure IEEE 802.1X by DLS:
Basic Requirements For 802.1x Certificates
Certificate Management (an alternative, available on optiPoint phones only)
How to implement and set up a secure environment and provide optiPoint phones with configuration data by the use of XML files via secure Web server (note, that this type of interface is not provided by OpenStage phones):
