Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added 2 new mapping flags.
Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

 

Use

...

the callingParty parameter for the

Spacevars
0series4
 to specify which SIP headers are used when determining the Calling Party information.

Info
titleNote

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

Code Block
languagenone
% 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

Caption
0Table
1Calling Party Parameters
3Calling Party Parameters
ParameterDescription
cpcParamFromHeader

Use this parameter to specify how to map the SIP CPC parameter from the incoming to the outgoing call.

  • default (default)
  • fromHeader
  • paitel
fromHdrForCallingParty

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

  • disabled 
  • enabled (default)

mapFromHeaderToIsupGAP

If enabled, the

Spacevars
0product
maps the From header to ISUP GAP parameters.

  • disabled (default) 
  • enabled

NOTE: Refer to SIP-I Support for feature details and example call flow.

mapIsupCgpnToPAI

If enabled, the

Spacevars
0product
maps the ISUP Calling Party Number to SIP From and PAI Headers. 

  • disabled (default) 
  • enabled

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. 

  • disabled 
  • enabled (default)
ppiForCallingParty

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

  • disabled
  • enabled (default)
rpiForCallingParty

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

  • disabled 
  • enabled (default)
trustedSourceForIsup

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)
Pagebreak