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

Compare with Current View Page History

« Previous Version 2 Next »

Back to Table of Contents

Back to Configuration

Back to Configuration - System Provisioning

Back to Category - Trunk Provisioning

Back to System Provisioning - Trunk Group

Back to Trunk Group - Sip Trunk Group

Back to Sip Trunk Group - Signaling

This section helps you to understand what SIP headers may be used when determining the Calling Party information.

To View and Edit Calling Party

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Trunk Group > Sip Trunk Group > Signaling > Calling Party. The Calling Party window is displayed.

The Calling Party can be checked for each Address Context, for each Zone, for each Sip Trunk Group created or for all the Address Contexts, Zones and Sip Trunk Groups created. Use the drop-down box to select the desired Address Context, Zone and Sip Trunk Group.

The Edit Calling Party window is displayed.

Sip Trunk Group - Signaling - Calling Party

 

 

The following fields are displayed:

Sip Trunk Group - Signaling - Calling Party parameters

 

Parameter

Description

Pai For Calling Party

If enabled, the PAI header (if present) will be accepted to form the Calling-Party-ID. 

  • disabled 
  • enabled (default)

Ppi For Calling Party

If enabled, the PPI header (if present) will be accepted to form the Calling-Party-ID. 

  • disabled 
  • enabled (default)

Rpi For Calling Party

If enabled, the RPI header (if present) will be accepted to form the Calling-Party-ID. 

  • disabled 

  • enabled (default)

Both Ppi For Calling Party and Rpi For Calling Party options are not applicable in Q.1912.5 SIP-I to SIP-I scenarios. Based on the Q.1912.5 recommendation, the mapping to calling party number only occurs if a PAI header containing valid address digits (0-9) are received.

From Hdr For Calling Party

If enabled, the FROM header will be used to form the Calling-Party-ID provided no allowed PAI/PPI/RPI header is present. 

  • disabled 
  • enabled (default)

Cpc Param From Header

IP Mapping CPC parameter from incoming call to outgoing call.

  • default (default)
  • fromHeader
  • paitel

Trusted Source For Isup

Used to indicate if the message came from a trusted source and the FROM header can be used to map into ISUP parameters. 

  • disabled
  • enabled (default)

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

 

  • No labels