...
...
...
Back to Table of Contents
Back to CLI Configure Mode
Back to Profiles - CLI
...
...
Use this object to specify whether to allow processing of destination trunk group and destination trunk context associated with a Feature Control Profile.
Include Page |
---|
| Transparency_Profile_Note |
---|
| Transparency_Profile_Note |
---|
|
Command Syntax
Code Block |
---|
|
% set profiles featureControlProfile <profile_name>
doNotValidateGAP <disable | enable>
ipProtocolFlags |
...
defaultCalledUser <disable | enable>
useIpProtocol <disable | enable>
honorPhoneContextParameter <disable | enable>
processDestinationTgrp <disable | enable>
processDestinationTrunkContext <disable | enable>
processEnumdi <disable | enable> |
Command Parameters
The Feature Control Profile parameters are as shown below:
Caption |
---|
0 | Table |
---|
1 | Feature control parameters |
---|
|
...
|
Parameter | Length/Range | Description |
---|
featureControlProfile
| 1-23 characters | <profile name> – The Feature Control Profile name.
| doNotValidateGAP | N/A | Enable this flag to allow the to skip Generic Address Parameter (GAP) validation.NOTE: This feature will apply to an configured for an external PSX in a future release. | ipProtocolFlags
| N/A | Use this parameter to configure IP protocol flags behavior. |
|
...
- treats called userinfo value as a telephone number.
enable – The
|
|
...
- treats called userinfo value as a user name.
useIpProtocol – Enable flag to use IP protocol flags. honorPhoneContextParameter – When this flag is enabled, PSX globalizes the incoming called number using the phone-context value received in Called-URI. Once the number is globalized using phone-context, the PSX acts as if it received a global number in policy request and use the modified number for further call processing.
|
|
...
NOTE: The useIpProtocol flag must first be enabled in order to enable honorPhoneContextParameter flag. |
|
...
To set phoneContextParameterLength , see |
|
...
...
NOTE: The settings of the above ipProtocolFlags should be based on the settings of the associated flags in the PSX Manager. | processDestinationTgrp
| N/A | Enable flag to process destination trunk group parameters associated with the specified Feature Control Profile. The ERE/PSX performs a light policy lookup and skips all SSG-based services, number translation and routing functions. | processDestinationTrunkContext
| N/A | Enable flag to allow processing of destination trunk context associated with the specified Feature Control Profile. | processEnumdi | N/A | Enable this flag to use the enumdi parameter to indicate when an ENUM query is performed. The |
|
...
can process enumdi indicator received in an ingress INVITE to avoid a redundant query. Likewise, if the ERE/PSX performs an ENUM dip, the SBC can send this parameter in the egress INVITE thus preventing redundant queries further down the network. |
|
...
NOTE: If R-URI transparency is enabled, the |
|
...
does not send enumdi indicator in egress signaling even if an ENUM dip is performed by ERE/PSX. The R-URI transparency flag is controlled using the CLI command: |
|
...
set profiles signaling ipSignalingProfile DEFAULT_SIP commonIpAttributes transparencyFlags requestURI <disable | enable>
|
|
Command Example
Code Block |
---|
|
% show profiles featureControlProfile DEFAULT_IP
processDestinationTgrp enable;
processDestinationTrunkContext disable;
processEnumdi disable;
ipProtocolFlags {
useIpProtocol enable;
defaultCalledUser enable;
honorPhoneContextParameter enable; |