End-to-end secure call indication

Last Updated : Jan 20, 2020 |
Prolog information
Metadata
Keywords:
Avaya endpoints can display an end-to-end secure indicator for calls that use secure protocols for both halves of the call. Avaya SBC provides a Securable field on the Server Configuration page to indicate whether the server is securable. Avaya SBC uses the Securable field to determine whether the trunk and call server can use secure protocols, and sets appropriate values for the Av-Secure-Indication header.
The Av-Secure-Indicator header in the outgoing INVITE message is set to
  • The trunk server and call server are securable.
  • The incoming and outgoing links use TLS and have a secure Audio-Visual Profile (SAVP) or transaction capabilities application part (tcap) messages with an SAVP profile.
  • System Manager sends the Av-Secure-Indication header as
Avaya SBC sets the Av-Secure-Indication header to
  • Any condition required for setting the Av-Secure-Indication header to
  • The Answer message has an AVP profile.
Subsequent messages such as Update without SDP, PRACK without SDP, and ACK must keep the secure indication value from the response of the previous request.
To make the Trunk server unsecured, the corresponding trunk link with Session Manager must also be unsecured.
Note:
Avaya SBC depends on Avaya Aura® 7.0 to support the end-to-end secure indication feature. Avaya Aura® 7.0 makes this feature available to users.