Include Page |
---|
| Transparency_Profile_Note |
---|
| Transparency_Profile_Note |
---|
|
When the
receives When the SBC receives a REGISTER request from the SIP endpoint, it sends a policy request to the ERE (or centralized PSX) for the next-hop route to the SIP Registrar. Before forwarding the REGISTER request, SBC creates the
creates a Path Header containing its own signaling IP address and port number and includes the Path Header in the outgoing REGISTER request. The reg-info parameter is added to the Path Header and used by the SBC to determine the next-hop direction of future INVITE requests.
When the SBC receives
receives a 200-class response to a REGISTER request from the SIP Registrar, the SBC does not include the Path header when it sends the response to the SIP endpoint. SBC has the flexibility to transparently pass a single Path Header towards UE if no interworking is needed.
...
...
Path Header Transparency Flag – When enabled, SBC transparently the
transparently passes the received Path Headers. (default is ‘disable’). Code Block |
---|
% set profiles signaling ipSignalingProfile <profile name> commonIpAttributes transparencyFlags pathHeader <enable|disable> |