You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The SBC supports Transit and Roaming Function (TRF) and applies TRF procedures defined for a looped back RAVEL call.

For feature details, refer to OMR and TRF Support

Use this command to configure the preferred Media Resource Broker (MRB) and/or TRF URIs.

Command Syntax

% set profiles signaling ipSignalingProfile <IPSP name> trfParameters 
	preferredMrbUri <string>
	preferredTrfUri <string>

Command Parameters

Parameter

Length/Range

Description

preferredMrbUri

0-512

<URI> (default = <NULL>) – The URI of entity performing the role of Media Resource Broker. The characters #%^&(){}<>,/\;`[]=!$"*?|~ and SPACE are not allowed.

This value is used if the SBC needs to include MRB URI parameter in the SIP Invite request, if the calling party of an originating call is identified to be roaming, and a roaming agreement exists with the home network operator to support local Media Resource Broker.

When this parameter is configured, the SBC does the following:

  • If the ingress SIP request does not contain ‘Feature-Caps’ header if the preferredMrbUri value is configured in egress IPSP of PSX Manager, the SBC creates the header and adds the preferredMrbUri parameter value in the header.
  • If the ingress SIP request contains ‘Feature-Caps’ header without  "+g.3gpp.mrb" parameter value if the preferredMrbUri value is configured in egress IPSP of PSX Manager, the SBC creates the header and adds the preferredMrbUri parameter value in the header.
  • If the ingress SIP request contain ‘Feature-Caps’ header with "+g.3gpp.mrb" parameter value then SBC does NOT overwrite the header field value with the configured preferredMrbUri value. If there is a need to overwrite, use SMM to delete the received TRF parameter.

preferredTrfUri

0-512

<URI> (default = <NULL>) – The URI of the entity performing the role of Transit and Roaming. The characters #%^&(){}<>,/\;`[]=!$"*?|~ and SPACE are not allowed.

The value configured in this parameter is used if the SBC needs to include TRF URI parameter in the SIP Invite request if the calling party of an originating call is identified as roaming, and a roaming agreement exists with the home network operator to support RAVEL.

When this parameter is configured, the SBC does the following:

  • If the ingress SIP request does not contain Feature-Caps header if the preferredTrfUri value is configured in egress IPSP of PSX Manager, SBC creates the header and add the preferredTrfUri parameter value in the header.
  • If the ingress SIP request contain ‘Feature-Caps’ header without  "+g.3gpp.trf" parameter value if the preferredTrfUri value is configured in egress IPSP of PSX Manager, the SBC creates the header and adds the preferredTrfUri parameter value in the header.
  • If the ingress SIP request contain ‘Feature-Caps’ header with "+g.3gpp.trf" parameter value, then the SBC does NOT overwrite the header field value with the configured preferredTrfUri value. If there is a need to overwrite, use SMM to delete the received TRF parameter.


 

  • No labels