In this section:

Overview


IMPORTANT

Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.

Refer to the SBC SIP Transparency Implementation Guide for additional information.

The E-CSCF functionality can be used when SBC acts as Proxy Call Session Control Function (P-CSCF). Therefore, the SBC acts as a combined P-CSCF and E-CSCF (P+E-CSCF).

The SBC as (P+E-CSCF) receives an emergency session establishment request from user equipment (UE) or a Serving Call Session Control Function (S-CSCF) and applies the following functionality as E-CSCF in addition to the normal P-CSCF functionality.

  • SBC as E-CSCF forwards the session establishment request to the Emergency Access Transfer Function (EATF) in the serving IMS network for anchoring to support Single Radio Voice Call Continuity (SRVCC).
  • SBC as E-CSCF requests Location Retrieval Function (LRF) to retrieve location information and proper routing information/PSAP destination, based on the configuration,
  • SBC as E-CSCF routes the call to the destination Public Safety Answering Point (PSAP) returned by LRF and sends the location information and correlation information (ESQK in PAI header) to PSAP.
  • SBC as E-CSCF sends the call to PSAP based on the routing information returned by LRF and PSX configuration by using any of the following:
    • Directly
    • Through Interconnection Border Control Functions (IBCF) to the IP-PSAP
    • Through Breakout Gateway Control Function (BGCF) to the PSTN PSAP

Figure 1: E-CSCF in IMS architecture


The ATCF is generally co-located with an existing functional element in the IMS architecture, such as the P-CSCF, IBCF, or MSC server. The most likely option for ATCF co-location is the P-CSCF as it is already in the path of all UE signaling with IMS. The IBCF is only in the path for a session when the UE is roaming, and the MSC server is only involved in a session during and after SRVCC. Thus, the IBCF and MSC server are not co-located with the ATCF. The E-CSCF may reside within the P-CSCF to support IMS Emergency procedures.

In the case of ATCF and E-CSCF integrated with P-CSCF, IMS-AGW acts as ATGW.

The E-CSCF is responsible for routing emergency call requests to the nearest PSAP based on the callers location information, as well as other information, such as the type of emergency service being requested.  E-CSCF receives from the P-CSCF request for emergency session establishment, and if required, contacts the LRF to validate the location information given by the UE and routes the request to the appropriate destination.

Figure 2: SBC as P-CSCF along with co-located ATCF and E-CSCF


At a high level, the functions performed by the ATCF are:

  • Allocates a STN-SR.
  • Includes itself for the SIP sessions.
  • Instructs the ATGW to anchor the media path for originating and terminating sessions.
  • Keeps track of sessions (either in pre-alerting state, alerting state, active or held) to perform Access Transfer of the selected session.
  • Performs the Access Transfer and updates the ATGW with the new media path for the (CS) access leg, without requiring to update the remote leg.
  • After Access Transfer, updates the SCC AS for which Access Transfer takes place. This ensures that the T-ADS have the information on the currently used access.
  • Handles failure cases during the Access Transfer.

At a high level, the functions performed by the E-CSCF are:

  • Receives an emergency session establishment request from a P CSCF or an S-CSCF.
  • If location information is not included in the emergency request or additional location information is required, the E CSCF requests the LRF to retrieve location information.
  • If required, the E-CSCF requests the LRF to validate the location information included by the UE.
  • Determines or queries the LRF for the proper routing information/PSAP destination.
  • Route emergency session establishment requests to an appropriate destination including anonymous session establishment requests.
  • Subject to local regulation, the E-CSCF may send the contents of the P-asserted ID or UE identification to the LRF.
  • Based on operator policy, the E-CSCF may route the emergency IMS call to ECS for further call process.
  • For supporting SRVCC, the E-CSCF forwards the session establishment request to the EATF in the serving IMS network for anchoring.

Deployment Scenario

The SBC acting as an E-CSCF can interact with a third-party LRF. An LRF is responsible for retrieving the location information of the UE that has initiated an IMS emergency session. An LRF can interact with a location service to manage ESQK allocation. The ESQK is used by the PSAP to query the LRF for location information and optionally a callback number. Information provided by the LRF to the E‑CSCF includes the routing information to the appropriate PSAP and other parameters necessary for emergency services, which is forwarded to the PSAP by SBC as E-CSCF.

Some regions, such as North America, may require the ability to provide the PSAP with an accurate initial and updated location estimate for the UE. In such cases, the LRF stores a record of the emergency session including all information provided by the E‑CSCF, and releases the record when informed by the E‑CSCF that the emergency session has terminated. The information provided by the LRF to the E‑CSCF (for example, ESQK) then includes correlation information identifying both the LRF and the emergency session record in the LRF. This correlation information is transferred to the PSAP by the SBC as E-CSCF during session establishment. The PSAP can use this information to request an initial location estimate from the LRF and/or to request an updated location estimate.

Figure 3: Deploying E-CSCF with LRF


Call Flows

Figure 4: Call flow for a multi mode UE with LRF deployment


Global Configuration

set global signaling srvcc stnSr +1-237-555-3333 atcfUri atcf.visisted2.net callLingerTimer 32 
set addressContext default zone ZONE_ACCESSNW dialogTransparency enabled
set addressContext default zone ZONE_ACCESSNW disableZoneLevelLoopDetection disable 

Attaching ATCF Profile to IPSP

  1. Select ATCF profile from the Access Transfer Policy Type option.
    Figure 5: Selecting ATCF Profile


  2. Attach the ATCF profile to the IP SIGNALING PROFILE of a Trunk Group.
    Figure 6: Attaching ATCF profile to the IPSP Trunk group


Configuring SBC Towards UE

The following profiles are configured:

Configuring Transparency Profile

set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader To
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader From
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Path
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Accept
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Reason
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Server
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Warning
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Call-Info
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Alert-Info
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Error-Info
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader User-Agent
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Referred-By excludedMethods register,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Request-URI
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Accept-Language
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader Contact
set profiles services transparencyProfile TRANS_PROF_ACCESS sipHeader P-Called-Party-Id
commit
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/rlmi+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody message/external-body
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/cpim-pidf+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/pidf-diff+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/dialog-info+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/simple-filter+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/resource-lists+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/conference-info+xml
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/simple-message-summary
set profiles services transparencyProfile TRANS_PROF_ACCESS sipMessageBody application/vnd.3gpp.srvcc-ext ignoreTransparency yes
commit
set profiles services transparencyProfile TRANS_PROF_ACCESS  state enabled
commit
set addressContext default zone ZONE_ACCESSNW sipTrunkGroup TG_TOWARDS_UE services transparencyProfile TRANS_PROF_ACCESS
commit

Configuring Zone Index Profile

The following flags must be configured:

  • Zone Index Profile
  • Description
  • Zone Index

Figure 7: Configuring Zone Index Profile


Configuring IP Signaling Profile

The following parameters are configured :

Configuring Common IP Attributes

The following must be enabled in PSX under IP SIGNALING PROFILE:

  • No Port Number 5060
  • Reject REFER
  • ReQuery PSX on REGISTER Refresh
  • Disable Host Translation
  • End to End BYE
  • End to End re-INVITE
  • End to End UPDATE
  • End to End PRACK
  • Minimize Relaying Of Media Changes From Other Call Leg
  • Store P-Charging-Vector
  • Validate Access Nw Info Header

Figure 8: Configuring Common IP Attributes


Configuring Relay Flags

The following Relay Flags must be enabled under IP SIGNALING PROFILE:

  • Dialog Event Package
  • Info
  • Options
  • Select Reject the REFER request if no match is found from Refer To Header Relay option.

Figure 9: Configuring Relay Flags


Configuring Egress IP Attributes

The following parameters must be enabled :

  • Select SIP Only from IP Protocol Type.
  • BCI Interwork Encountered (in BCI option).
  • Transparency (in Privacy option).
  • Merge Received Contacts with Existing Contacts (in Redirect option).
  • Select Include None from Include Charge Information (in SIP Headers and Parameters option).
  • Select None from SIP TO Header Mapping (in SIP Headers and Parameters option).
  • Include OLIP (in SIP Headers And Parameters > Flags option).
  • Transparency For Destination Trunk Group Parameter (in SIP Headers And Parameters > Flags option).
  • End To End Ack (in SIP Headers And Parameters > Flags option).
  • Diversion (in SIP Headers And Parameters > Call Forwarding option).

Figure 10: Configuring Egress IP Attributes


Configuring Ingress IP Attributes

The following parameter is to be enabled:

  • 181 Supported (in Flags option)

Figure 11: Configuring Ingress IP Attributes


Configuring SIP Trunk Group

set addressContext "default" zone "ZONE_ACCESSNW" sipTrunkGroup "TG_TOWARDS_UE"
commit 

The following profiles/fields must be enabled:

  • Zone Index Profile
  • IP Signaling Profile
  • Feature Control Profile
  • Signaling Profile
  • SIP Domain
  • IP Version Preference
  • Use IPTG Routing (Hop By Hop Routing) For Ingress (Ingress > Flags)
  • Do Not Use For Fallback Bearer Capability (Egress > Flags)
  • IP Peer Supported (Egress > IPTG)
  • Egress IP Signaling Profile (Egress > IPTG)
  • Select Traffic Management Options from Trunk Group Reserved Level 1 and Trunk Group Reserved Level 2.
  • Select Services as Not Screened

Figure 12: Configuring SIP Trunk Group


Configuring SBC Towards MSC

The following profiles are configured:

Configuring Transparency Profile

set profiles services transparencyProfile TRANS_PROF_MSC sipHeader To
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader From
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Path
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Accept
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Reason
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Server
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Warning
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Call-Info
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Alert-Info
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Error-Info
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader User-Agent
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Referred-By excludedMethods register,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Request-URI
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Accept-Language
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Contact
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader P-Called-Party-Id
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Require
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Proxy-Require
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Security-Client
set profiles services transparencyProfile TRANS_PROF_MSC sipHeader Security-Verify
commit
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/pidf+xml excludedMethods register,invite,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/rlmi+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody message/external-body
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/cpim-pidf+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/pidf-diff+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/dialog-info+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/simple-filter+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/resource-lists+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/conference-info+xml
set profiles services transparencyProfile TRANS_PROF_MSC sipMessageBody application/simple-message-summary
commit
set profiles services transparencyProfile TRANS_PROF_MSC state enabled
commit
set addressContext default zone ZONE_CORENW sipTrunkGroup TG_TOWARDS_IMSCORE services transparencyProfile TRANS_PROF_MSC
commit

Configuring Zone Index Profile

set addressContext default zone ZONE_CORENW dialogTransparency enabled

set addressContext default zone ZONE_CORENW disableZoneLevelLoopDetection disabled
set addressContext "default" zone "ZONE_CORENW" sipTrunkGroup "TG_TOWARDS_MSC"

The following flags must be configured:

  • Zone Index Profile
  • Description
  • Zone Index

Figure 13: MSC Zone Index Profile


Configuring IP Signaling Profile

The following parameters must be configured under "Ip Signaling Profile".

Configuring Common IP Attributes

The following must be enabled in PSX under IP SIGNALING PROFILE:

  • Add P-Charging Function Addr
  • No Port Number 5060
  • P-Called-Party-Id-Support
  • Create P-Charging-Vector
  • Create P-Visited-Network Id
  • Create Path Header
  • Disable Host Translation
  • Restrict History Info Header
  • End To End BYE
  • End To End re-INVITE
  • End To End UPDATE
  • End To End PRACK
  • Enable Default PUI Procedures
  • Enable Dial String Handling
  • Store P-Charging Vector
  • Store Service -Route Header
  • Validate Access Nw Info Header

Figure 14: IP Signaling Profile


Configuring Relay Flags

The following Relay Flags must be enabled under IP SIGNALING PROFILE:

  • Dialog Event Package
  • Info
  • Options
  • Select Reject the REFER request if no match is found from Refer to Header Relay option.

Figure 15: IP Signaling Profile Relays Flags


Configuring Egress IP Attributes

The following parameters are to enabled :

  • Select SIP Only from IP Protocol Type
  • BCI Interwork Encountered (in BCI)
  • Select Use IP Signaling Peer Domain In R-URI (in Domain Name)
  • Select Include npdi from NPDI Options (in Number Portability Attributes option)
  • Select Include Privacy and Do Not Include Tel URI in PAI Header(in Privacy)
  • Select Merge Received Contacts with Existing Contacts from Contact Handling(under Redirect)
  • Select Include None from Include Charge Information (in SIP Headers and Parameters option)
  • Select None from SIP TO Header Mapping (under SIP Headers And Parameters option)
  • Select Include CPC Information(under Flags option)
  • Select Transparency For Destination Trunk Group Parameter(under Flags option)
  • Select End to End Ack (under Flags option)
  • Select Diversion from Redirect Information (under Call Forwarding)

Figure 16: IP Signaling Profile Egress IP Attributes


Configuring Ingress IP Attributes

The following parameter must be enabled:

  • Map Called Party Category In P-Sig-Info Header

Figure 17: IP Signaling Profile Ingress IP Attributes


Configuring SIP Trunk Group

The following profiles/fields must be enabled:

  • Feature Control Profile
  • IP Signaling Profile
  • Signaling Profile
  • SIP Domain
  • Zone Index Profile
  • IP Version Preference

  • Use IPTG Routing (Hop by Hop Routing) For Ingress (Ingress > Flags)

  • Do Not Use For Fallback Bearer Capability (Egress > Flags)
  • IP Peer Supported (Egress > IPTG)
  • Egress IP Signaling Profile (Egress > IPTG)
  • Select Traffic Management Options from Trunk Group Reserved Level 1 and Trunk Group Reserved Level 2.

  • Select Services as Not Screened.

Figure 18: SIP Trunk Group for MSC


Configuring SBC Towards SCCAS or IMS Core

The following profiles are configured:

Configuring Transparency Profile

set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader To
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader From
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Path
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Accept
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Reason
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Server
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Warning
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Call-Info
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Alert-Info
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Error-Info
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader User-Agent
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Referred-By excludedMethods register,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Request-URI
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Accept-Language
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader P-Called-Party-Id
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Require
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Proxy-Require
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Security-Client
set profiles services transparencyProfile TRANS_PROF_CORENW sipHeader Security-Verify
commit
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/pidf+xml excludedMethods register,invite,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/rlmi+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody message/external-body
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/cpim-pidf+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/pidf-diff+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/dialog-info+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/simple-filter+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/resource-lists+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/conference-info+xml
set profiles services transparencyProfile TRANS_PROF_CORENW sipMessageBody application/simple-message-summary
commit
set profiles services transparencyProfile TRANS_PROF_CORENW state enabled
commit
set addressContext default zone ZONE_CORENW sipTrunkGroup TG_TOWARDS_IMSCORE services transparencyProfile TRANS_PROF_CORENW
commit

Configuring Zone Index Profile

set addressContext default zone ZONE_CORENW dialogTransparency enabled
set addressContext default zone ZONE_CORENW disableZoneLevelLoopDetection disabled

The following flags must be configured:

  • Zone Index Profile
  • Description
  • Zone Index

Figure 19: Zone Index Profile for SCCAS


Configuring IP Signaling Profile

The following parameters must be configured under IP SIGNALING PROFILE:

Configuring Common IP Attributes

The following must be enabled in PSX under IP SIGNALING PROFILE:

  • Add P-Charging Function Addr
  • Create P-Charging-Vector
  • Create P-Visited-Network Id
  • Customized Session Timer Behavior
  • Disable Host Translation
  • End To End BYE
  • End To End re-INVITE
  • End To End UPDATE
  • End To End PRACK
  • Enable Default PUI Procedures
  • Enable Dial String Handling
  • No Port Number 5060
  • P-Called-Party0Id-Support
  • Restrict History Info Header
  • Store P-Charging Vector
  • Store Service-Route Header
  • Validate Access Nw Info Header

Figure 20: Common IP Attributes for SCCAS


Configuring Relay Flags

The following Relay Flags must be enabled under IP SIGNALING PROFILE:

  • Dialog Event Package
  • Info
  • Options
  • Reg Event Package
  • Select Reject the REFER request if no match is found from Refer to Header Relay option.

Figure 21: Relay Flags for SCCAS


Configuring Egress IP Attributes

The following parameters are to enabled :

  • Select SIP Only from IP Protocol Type
  • Select Transit PAI From Unregistered Peer from Flags
  • Select Use IP Signaling Peer Domain In R-URI (in Domain Name)
  • Select Include npdi from NPDI Options (in Number Portability Attributes option)

  • Select P-Preferred-ID from Privacy Information options (in Privacy option)

  • Select Include Privacy (in Privacy)
  • Select Merge Received Contacts with Existing Contacts from Contact Handling(under Redirect)
  • Select Include None from Include Charge Information (in SIP Headers and Parameters option)
  • Select Not Send from Session-Expires Refresher (in SIP Headers and Parameters option)

  • Select None from SIP TO Header Mapping (under SIP Headers And Parameters option)

  • Select Transparency For Destination Trunk Group Parameter(under Flags option)
  • Select End to End Ack (under Flags option)
  • Select Diversion from Redirect Information (under Call Forwarding)

Figure 22: Egress IP Attributes for SCCAS


Configuring SIP Trunk Group

The following profiles/fields must be enabled:

  • Feature Control Profile
  • IP Signaling Profile
  • Signaling Profile
  • SIP Domain
  • Zone Index Profile
  • IP Version Preference
  • Use IPTG Routing (Hop By Hop Routing) For Ingress (Ingress > Flags)
  • Do Not Use For Fallback Bearer Capability (Egress > Flags)
  • IP Peer Supported (Egress > IPTG)
  • Egress IP Signaling Profile (Egress > IPTG)
  • Select Traffic Management Options from Trunk Group Reserved Level 1 and Trunk Group Reserved Level 2.

  • Select Services as Not Screened.

Figure 23: SIP Trunk Group for SCCAS


Configuring SBC Towards IBCF

The following profiles are configured:

Configuring Transparency Profile

request system security generateSipHeaderEncryptionKeys
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Path
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Service-Route
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Feature-Caps
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Accept-Contact
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Alert-Info
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Contact
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader WWW-Authenticate
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Error-Info
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader From
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader History-Info
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader P-Called-Party-ID
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Reason
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Referred-By
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader To
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Accept
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Call-Info
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Warning
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader User-Agent
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Server
set profile services transparencyProfile IBCF_COMMON_HTP sipHeader Accept-Language

Zone Configuration (Towards Peer in External)

 set addressContext default zone ZONE3 id 5 sipSigPort 1 ipInterfaceGroupName LIG3 ipAddressV4 10.4.8.18 ipAddressV6 fd00:10:6b50:248f::c portNumber 5060 
transportProtocolsAllowed sip-tcp,sip-udp,sip-tls-tcp,sip-sctp mode inService state enabled
 set addressContext default zone ZONE_CORENW dialogTransparency enabled

IBCF (Towards Peer IBCF/IPX)

Common Configuration
 set addressContext default zone ZONE3 sipTrunkGroup IBCF signaling registration requireRegistration none
 set addressContext default zone ZONE3 sipTrunkGroup IBCF signaling relayNonInviteRequest enabled
 set addressContext default zone ZONE3 sipTrunkGroup IBCF services transparencyProfile IBCF_COMMON_HTP
 set addressContext default zone ZONE3 sipTrunkGroup IBCF media omrAllowed enabled
 set addressContext default zone ZONE3 sipTrunkGroup IBCF media primaryRealmName RealmName2
 set addressContext default zone ZONE3 sipTrunkGroup IBCF media directMediaAllowed disabled
 set addressContext default zone ZONE3 sipRegRelay enabled 
 set addressContext default zone ZONE3 sipTrunkGroup IBCF callRouting useRouteSet received 
 set addressContext default zone ZONE3 sipTrunkGroup IBCF signaling relayNonInviteRequest enabled
 set addressContext default zone ZONE3 sipTrunkGroup IBCF callRouting sendRouteUriToPsx enabled 
 set addressContext default zone ZONE3 sipTrunkGroup IBCF signaling skipDTGLookupForRouteHeader enabled
 set addressContext default zone ZONE3 sipTrunkGroup IBCF services honorSdpClockRate enabled
 set addressContext default zone ZONE3 sipTrunkGroup IBCF transitIoi "IBCF"

Configuring Zone Index Profile

The following flags must be configured:

  • Zone Index Profile
  • Description
  • Zone Index

Figure 24: IBCF Zone Index Profile


Configuring PSX Route URI Based Routing

The following flags must be configured:

  1. Create a Feature Profile.

    1. Enable Perform Route Header Based Routing.
      Figure 25: Route Header Based Routing

    2. On the SIP Trunk Group , select the mapped Feature Control Profile and IP Signaling Profile.
      Figure 26: Ingress SIP TG


  2. Create Call Parameter Filter Profile and set the values for :
    1. Type as "Regex Group". 
    2. Variable Type as "Route URI Host Part".
    3. Configure RouteURI as matching Regex String. 
      Figure 27: Call Parameter Filter Profile


  3. Create Policy Profile.
    1. Enable URI and URI Action as "Override IP Peer with Route URI Host Part".
    2. Map the created Call Parameter Filter Profile.
      Figure 28: Policy Profile


  4. Map the Policy Profile under Policy Profile Group.
    Figure 29: Policy Profile Group



  5. On the SIP Trunk Group under Egress, select the Output Policy Profile Group.
    Figure 30: Egress SIP Trunk Group



  6. For domain based configuration, select UserName Routing.

    1. Select the already mapped Call Parameter Filter Profile and Domain Name from the drop-down.
      Figure 31: Username Routing

Configuring IP Signaling Profile

The following parameters must be configured under IP SIGNALING PROFILE:

Configuring Common IP Attributes

The following Common IP Attributes must be enabled in PSX under IP SIGNALING PROFILE:

  • Add P-Charging-Function Addr
  • Create P-Charging-Vector
  • Create P-Visited-Network Id
  • Create Path Header
  • Customized Session Timer Behavior
  • Disable Host Translation
  • End to End BYE
  • End to End re-INVITE
  • End to End UPDATE
  • End to End PRACK
  • Enable Dial String Handling
  • No Port Number 5060
  • P-Called-Party-Id-Support
  • Restrict History Info Header
  • Store P-Charging Vector
  • Store Service-Route Header
  • Validate Access Nw Info Header

Figure 32: IP Signaling Profile for IBCF


Configuring Relay Flags

The following Relay Flags must be enabled under IP SIGNALING PROFILE:

  • Dialog Event Package
  • Info
  • Options
  • Select Reject the REFER request if no match is found from Refer To Header Relay option.

Figure 33: IP Signaling Profile IP Relay Flags for IBCF


Configuring Egress IP Attributes

The following Egress IP Attributes must be enabled:

  • Select SIP Only from IP Protocol Type.
  • Transit PAI From Unregistered Peer (under Flags)
  • Use IP Signaling Peer Domain In R-URI (under Domain Name)
  • Select Include npdi from NPDI Options (under Number Portability Attributes option).
  • Select P-Preferred-ID from Privacy Information (under Privacy option).
  • Include Privacy (under Privacy > Flags)
  • Merge Received Contacts with Existing Contacts (under Redirect)
  • Select Include None from Include Charge Information option (under SIP Headers and Parameters)
  • Select Not Send from Session-Expires Refresher option (under SIP Headers and Parameters)
  • Select None from SIP TO Header Mapping option (under SIP Headers and Parameters)
  • Transparency For Destination Trunk Group Parameter (under SIP Headers and Parameters > Flags)
  • End To End Ack (under SIP Headers and Parameters > Flags)
  • Diversion (under SIP Headers and Parameters > Call Forwarding)
  • Select Retry Without ETS from the Action For ETS 400 Responses With 417 Reason Code drop-down box (under SIP RPH ETS)
  • Set ETS Default Priority Value as 0  (under SIP RPH ETS)

Figure 34: IP Signaling Profile Egress IP Attributes for IBCF


Configuring SIP Trunk Group

The following profiles/fields must be enabled:

  • Zone Index Profile
  • IP Signaling Profile
  • Feature Control Profile
  • Signaling Profile
  • SIP Domain
  • IP Version Preference
  • Use IPTG Routing (Hop By Hop Routing) For Ingress (Ingress > Flags)
  • Do Not Use For Fallback Bearer Capability (Egress > Flags)
  • Select Traffic Management Options from Trunk Group Reserved Level 1 and Trunk Group Reserved Level 2.
  • Select Services as Not Screened.

Figure 35: SIP Trunk Group for IBCF


Configuring SBC Towards E-CSCF

The following profiles are configured:

Configuring Transparency Profile

set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader To
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader From
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Path
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Accept
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Reason
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Server
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Warning
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Call-Info
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Alert-Info
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Error-Info
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader User-Agent
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Referred-By excludedMethods register,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Request-URI
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Accept-Language
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader P-Called-Party-Id
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Require
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Proxy-Require
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Security-Client
set profiles services transparencyProfile TRANS_PROF_ECSCF sipHeader Security-Verify
commit
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/pidf+xml excludedMethods register,invite,subscribe,info,publish,message,options,update,bye
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/rlmi+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody message/external-body
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/pidf+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/cpim-pidf+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/pidf-diff+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/dialog-info+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/simple-filter+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/resource-lists+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/conference-info+xml
set profiles services transparencyProfile TRANS_PROF_ECSCF sipMessageBody application/simple-message-summary
commit
set profiles services transparencyProfile TRANS_PROF_ECSCF state enabled
commit
set addressContext default zone ZONE_ECSCF sipTrunkGroup TG_TOWARDS_ECSCF services transparencyProfile TRANS_PROF_ECSCF
commit

Configuring Emergency Calls

set profiles services sipResourcePriorityHeaderProfile "RPH-1" rphEmergencyMatchingConfig "esnet" "1"
commit
set profiles services sipResourcePriorityHeaderProfile "RPH-1" sendEgressRphForEmergency esnet 1
commit
set profiles services emergencyCallProfile "EMG-ECSCF" resPriorityHeaderProfile "RPH-1" sosInContactOfRegister "enable"
commit
set profiles services emergencyCallProfile EMG-ECSCF prefix 911
comm
set profiles services emergencyCallProfile EMG-ECSCF urnPrefix service:sos.fire
comm
set profiles services emergencyCallProfile EMG-ECSCF sosInContactOfRegister enable
comm

Configuring Zone Index Profile

The following fields must be configured:

  • Zone Index Profile
  • Description
  • Zone Index

Figure 36: E-CSCF Zone Index Profile


Configuring IP Signaling Profile

The following parameters must be configured under IP SIGNALING PROFILE:

Configuring Common IP Attributes

The following Common IP Attributes must be enabled in PSX under IP SIGNALING PROFILE:

  • Disable Host Translation
  • End to End BYE
  • End to End re-INVITE
  • End to End UPDATE
  • End to End PRACK
  • Insert Peer Address As Top Route Header
  • No Port Number 5060
  • ReQuery PSX on REGISTER Refresh
  • Store P-Charging-Vector
  • Validate Access Nw Info Header

Figure 37: IP Signaling Profile Common IP Attributes for E-CSCF


Configuring Relay Flags

The following Relay Flags must be enabled under IP SIGNALING PROFILE:

  • Conference Event Package
  • Dialog Event Package
  • Info
  • Message
  • Options
  • PUBLISH
  • REFER
  • Reg Event Package
  • Status Code 4XX-6XX
  • Select Reject the REFER request if no match is found from Refer To Header Relay option.

Figure 38: IP Signaling Profile Relay Flags for E-CSCF


Configuring Transparency Flags

The following Transparency Flag must be enabled under IP SIGNALING PROFILE:

  • Request-URI

Figure 39: IP Signaling Profile Transparency Profile for E-CSCF


Configuring Egress IP Attributes

The following Egress IP Attributes must be enabled:

  • Select SIP Only from IP Protocol Type.
  • Disable 2806 Compliance (under Flags)
  • Transit PAI From Unregistered Peer (under Flags)
  • Add Loop Back Route Header (under Flags)
  • Select Include npdi from NPDI Options (under Number Portability Attributes option).
  • Select P-Preferred-ID from Privacy Information (under Privacy option).
  • Merge Received Contacts with Existing Contacts (under Redirect)
  • Select Include None from Include Charge Information option (under SIP Headers and Parameters)
  • Select Original Called Number (OCN) from SIP TO Header Mapping option (under SIP Headers and Parameters)
  • Include CPC Information (under SIP Headers and Parameters > Flags)
  • Transparency For Destination Trunk Group Parameter (under SIP Headers and Parameters > Flags)
  • End To End Ack (under SIP Headers and Parameters > Flags)
  • Diversion (under SIP Headers and Parameters > Call Forwarding)
  • Select Retry Without ETS from the Action For ETS 400 Responses With 417 Reason Code drop-down box (under SIP RPH ETS)
  • Set ETS Default Priority Value as 0  (under SIP RPH ETS)

Figure 40: IP Signaling Profile Egress IP Attributes for E-CSCF


Configuring Ingress IP Attributes

The following Ingress IP Attributes must be enabled:

  • 181 Supported (under Flags option)

Figure 41: IP Signaling Profile Ingress IP Attributes for ECSCF


Configuring SIP Trunk Group

set addressContext default zone ZONE_ECSCF sipTrunkGroup TG_TOWARDS_ECSCF
set addressContext default zone ZONE_ECSCF sipTrunkGroup TG_TOWARDS_ECSCF services emergencyCallProfile EMG-ECSCF
commit

The following profiles/fields must be enabled:

  • Zone Index Profile
  • IP Signaling Profile
  • Feature Control Profile
  • Signaling Profile
  • SIP Domain
  • IP Version Preference
  • Use IPTG Routing (Hop By Hop Routing) For Ingress (Ingress > Flags)
  • Do Not Use For Fallback Bearer Capability (Egress > Flags)
  • IP Peer Supported (Egress > IPTG)
  • Egress IP Signaling Profile (Egress > IPTG)
  • Select Traffic Management Options from Trunk Group Reserved Level 1 and Trunk Group Reserved Level 2.
  • Select Services as Not Screened.

Figure 42: SIP Trunk Group for ECSCF



  • No labels