Page History

...

...

• SBC relays REGISTER using the routes from PSX.
• When “Require registration” flag is also enabled, relay functionality takes higher precedence and provisioned value of the “Require registration” flag is ignored.
• Registration message relayed by SBC are NOT subject to any throttling.
  
  • SBC ignores provisioned registration “expires” and “insideExpiresMinimum” values (typically used for registration message throttling for UE behind NAT scenarios).
  • SBC passes the registration expiry value received in the ingress registration message transparently to the egress message. This is applicable to both REGSITER request and 200 OK response messages. 
• SBC as IBCF does NOT add the Path and Service-Route headers included in the emergency registration requests and responses if noServiceRotueHdrForEmergencyRegistration noServiceRouteHdrForEmergencyRegistration is enabled, even if createServiceRouteHeader flag is enabled.
• SBC ignores provisioned “storePathHeader” and “serviceRouteHeader” values (typically provisioned on SBC to act as B2BUA with respect to Path and Service-Route header processing).
• SBC as IBCF supports transparency of the following headers in REGISTER requests and responses if registration relay functionality is enabled.

  • Contact header and parameters (excluding transport parameter).

  • Expires header

    Note
    Since Contact header always points to either UE or P-CSCF included URI passing the transport parameter to next hop with IBCF being in the path may NOT serve any purpose.

...

Emergency Registration

The flag noServiceRotueHdrForEmergencyRegistration is added in this release to control noServiceRouteHdrForEmergencyRegistration controls whether SBC as IBCF adds itself to Service-Route headers in the 200 OK to emergency registration requests.

...