An area of confusion in the industry is whether or not to apply base64 padding (ie 0, 1, or 2 "equals" signs) to inline crypto attributes in the SDP. Example with no padding:
Currently, we have an env var in SBC outbound, PAD_CRYPTO, that globally sets which way to do it. However, we should be able to set this on a sip gateway level. When the user selects "TLS/SRTP" for the protocol for an outbound SIP gateway there should appear a checkbox labeled "Pad crypto attributes". By default it should be unchecked. This setting should define whether or not for any outbound calls made through to gateway padding should be added.
An area of confusion in the industry is whether or not to apply base64 padding (ie 0, 1, or 2 "equals" signs) to inline crypto attributes in the SDP. Example with no padding:
Example with padding:
Currently, we have an env var in SBC outbound, PAD_CRYPTO, that globally sets which way to do it. However, we should be able to set this on a sip gateway level. When the user selects "TLS/SRTP" for the protocol for an outbound SIP gateway there should appear a checkbox labeled "Pad crypto attributes". By default it should be unchecked. This setting should define whether or not for any outbound calls made through to gateway padding should be added.