In this section:
Use the callingParty parameter for the SBC Core to specify which SIP headers are used when determining the Calling Party information.
Note
Both ppiForCallingParty and rpiForCallingParty 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.
Command Syntax
% set addressContext <name> zone <name> sipTrunkGroup <name> signaling callingParty cpcParamFromHeader <default | fromheader | paitel> fromHdrForCallingParty <disabled | enabled> mapFromHeaderToIsupGAP <disabled | enabled> mapIsupCgpnToPAI <disabled | enabled> paiForCallingParty <disabled | enabled> ppiForCallingParty <disabled | enabled> rpiForCallingParty <disabled | enabled> trustedSourceForIsup <disabled | enabled>
Command Parameters
Calling Party Parameters
| Parameter | Description |
|---|---|
cpcParamFromHeader | Use this parameter to specify how to map the SIP CPC parameter from the incoming to the outgoing call.
|
fromHdrForCallingParty | If enabled, the FROM header is used to form the Calling-Party-ID provided no allowed PAI/PPI/RPI header is present.
|
| If enabled, the SBC maps the From header to ISUP GAP parameters.
NOTE: Refer to SIP-I Support for feature details and example call flow. |
mapIsupCgpnToPAI | If enabled, the SBC maps the ISUP Calling Party Number to SIP From and PAI Headers.
NOTE: Refer to SIP-I Support for feature details and example call flow. |
paiForCallingParty | If enabled, the PAI header (if present) will be accepted to form the Calling-Party-ID.
|
ppiForCallingParty | If enabled, the PPI header (if present) will be accepted to form the Calling-Party-ID.
|
rpiForCallingParty | If enabled, the RPI header (if present) will be accepted to form the Calling-Party-ID.
|
trustedSourceForIsup | Used to indicate if the message came from a trusted source and the FROM header can be used to map into ISUP parameters.
|
Overview
Content Tools