Page History

The

• Spacevars
  0 product

   processing/forwarding REGISTER requests without creating any RCB (registration control block).
• Passing of Path and Service-Route headers (included in REGISTER request and response messages) end to end with support for encryption for topology hiding purpose. "Via" headers are handled in a B2BUA role (i.e

• . the

  Spacevars
  0 product

   stores the incoming Via and inserts its URI in outgoing messages).
• Decryption of Route headers in non-REGISTER requests (in an IMS deployment, Route headers are formed based on Path and Service Route headers included in REGISTER request and response message.

• the

  Spacevars
  0 product

   must decrypt them for routing purpose).
• IBCF continues to act as a B2BUA with respect to non-REGISTER message processing, so topology revealing headers encryption is NOT applicable to non-REGISTER messages.
• Registration rate limit CAC related enhancements in the context of registration relay support on IBCF.

Overview

At a high-level, the following steps are needed for

the

• Transparently pass the received headers
• Insert itself on top of the received headers
• Perform encryption

The

When registration relay functionality is enabled, the following behavior applies:

• The

  Spacevars
  0 product

   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

• the

  Spacevars
  0 product

   are NOT subject to any throttling.

• 
  
  • The

    Spacevars
    0 product

     ignores

• • provisioned registration “expires” and “insideExpiresMinimum” values (typically used for registration message throttling for UE behind NAT scenarios).

• • The

    Spacevars
    0 product

     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. 

• The

  Spacevars
  0 product

   as

• IBCF does NOT add the Path and Service-Route headers included in the emergency registration requests and responses if

• noServiceRouteHdrForEmergencyRegistration is enabled, even if createServiceRouteHeader flag is enabled.

• The

  Spacevars
  0 product

    ignores provisioned “storePathHeader” and “serviceRouteHeader” values (typically provisioned on SBC to act as B2BUA with respect to Path and Service-Route header processing).

• The

  Spacevars
  0 product

   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.

    
    

The

IBCF can route non-REGISTER requests based on the received route set.

Options include:

• routing the message based on PSX username/standard routing provisioning if NO route headers are received in the incoming message.

• The

  Spacevars
  0 product

   inserts the next-hop as the top-most Route header based on (existing) configuration.

• routing the message based on PSX username/standard routing provisioning if there is one Route header and that points to IBCF.

• The

  Spacevars
  0 product

   inserts the next-hop as the top-most Route header based on (existing) configuration.

• The

  Spacevars
  0 product

   copies any parameters present in the received ingress Route header (pointing to itself) in the egress Route header (pointing to next-hop).

The

IBCF can prevent the addition of Service-Routes pointing to IBCF (both internal and external interface IP addresses) in 200 OK response.

• This behavior is controlled by provisioning flag associated with egress TG with respect to message direction.
• If this flag is enabled then provisioned values of “createServiceRouteHeader” and “addPathServiceRoute” is ignored.

Network Topology Hiding Support

The

The

• upon receiving an outgoing request/response from the trusted/hiding network

• ,

• upon receiving and incoming requests/response towards the trusted/hiding network.

Header transparency is controlled using the dynamic header Transparency Profile (Note that contact and expires headers are transparently passed by default).

The

• When the request/response traverses from trusted network to untrusted network, encryption is performed.
• When the request/response traverses from untrusted network to trusted network, encryption is not performed.

Emergency Registration

The flag

noServiceRouteHdrForEmergencyRegistration controls whether the

Encryption/Decryption Enhancements

The

• Encryption of Path headers included in REGISTER requests.
• Encryption of Path and Service-Route headers included in the 200 OK to REGISTER message.
• Decryption of Path headers included in the 200 OK to REGISTER message.
• Decryption of Route headers included in the non-REGISTER requests such as dialog creating INVITE and OOD non-INVITE messages such as SUBSCRIBE, OOD MESSAGE, OPTIONS, REFER etc.

The

The

IBCF supports the encryption of the topology revealing headers

using the following logic:

• Copy all headers considered for encryption from ingress SIP message towards the egress SIP message. This behavior is controlled by transparency flag pertaining to the header to be encrypted.

• Insert own URI(s) before the headers entries to be considered for encryption.

• Encrypt the headers based on encryption logic discussed in subsequent requirements.

The Global command generateSipHeaderEncryptionKeys generates header encryption keys for AES encryption. The

CAC Control on Register Relay Messages

Since the