12.2.7 |
Trace Options and Evaluations in Connection with SRTP |
| The Secure Realtime Transport Protocol (SRTP) is the secure version of the RTP protocol. It is used in IP telephony for transferring encrypted voice traffic. |
| Data can be encrypted from: |
| • | gateway to gateway |
| • | gateway to workpoint client |
| • | workpoint client to workpoint client |
| This results in two scenarios: |
| • | Encrypted signaling from gateway to gateway: CorNet NQ is encrypted. |
| Firstly, the connection is set up via H.323. The CorNet NQ container is then sent in encrypted form via the IP network. |
| Traces can be performed as usual, but do not include data in the CorNet NQ container (for example, signaling messages, station number information). |
| • | Encrypted payload from workpoint client to workpoint client and from gateway to workpoint client: CorNet TS is encrypted. |
| The connection setup via CorNet TC is already partially encrypted. The CorNet TS data records contained in this setup are completely encrypted. This means that voice data (including DTMF tones) is transmitted in encrypted form. In the case of data connections, the data is encrypted for transmission. If RFC2833 is activated (this must be activated if security is activated), information about key actions (user input indication) on the workpoint client is also encrypted and transmitted. |
| The rest of the CorNet TC message is not encrypted. Messages that do not contain CorNet TS data records are not encrypted either. |
| During a trace, the RTP data flow can be read out as usual. Voice quality cannot be evaluated due to payload encryption. |
| HiPath 3000/5000 V8, Service Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3580S100017620 | 2011-01-24 |