The
Unable to show "metadata-from": No such page "_space_variables"
includes a signaling profile, NNI Profile, in support of the Inter-IMS Network to Network Interface (II-NNI) and interworking of charging parameters for SIP to/from SIP-I/T/GWGW/ISUP calls. The NNI Profile is attached to a ingress SIP trunk group. To learn more about how the
Unable to show "metadata-from": No such page "_space_variables"
performs SIP to SIP-I and SIP-I to SIP interworking based on the NNI Profile, refer to
PCV Interworking Enhancement.
To View NNIProfile
On the SBC main screen, navigate to All > Profiles > Signaling > NNIProfile.
The NNIProfile window is displayed.
To Edit NNIProfile
To edit any of the NNIProfile in the list, click the radio button next to the specific NNIProfile name.
The Edit Selected NNIProfile window is displayed.
The NNIProfile Edit Window
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
To Create NNIProfile
To create a new NNIProfile, click New NNIProfile tab on the NNIProfile List panel.
The Create New NNIProfile window is displayed.
The NNI Profile parameters (as displayed in the Copy and Edit tools) are described below:
NNI Profile Parameter Descriptions
Parameter Description | Length/Range | Parameter Description |
---|
Name | 1-23 characters | The name of the NNIProfile used to control Unable to show "metadata-from": No such page "_space_variables" interworking of charging parameters for SIP to/from SIP-I/T, GW-GW and ISUP calls. The NNI Profile is attached to a SIP trunk group. |
Charge Area Information | (ASCII 0-9) | A 5-digit value representing the charge area Information that applies to calls establishing the INVITE. |
Additional Party Category First | N/A | Use this parameter to select one of the following values to specify the first Additional Party Category type. The configured value will be included inside the policy request message sent to the PSX and sent in the ISUP IAM message body of SIP-I/T or over GW-GW message. Fixed_1-1 Fixed_1-2 Mobile_1-1 Mobile_1-2 Mobile_1-3 Mobile_1-4 Mobile_1-5 Mobile_2-1 Mobile_2-2 Mobile_2-3 Mobile_2-4 Mobile_2-5 Mobile_2-6 Mobile_2-7 Mobile_2-8 Mobile_2-9
|
Additional Party Category Second | N/A | Use this parameter to select one of the above values to specify the second Additional Party Category type. The configured value will be included inside the policy request message sent to the PSX and sent in the ISUP IAM message body of SIP-I/T or over GW-GW message. |
Calling Party Category Interworking | N/A | The flag Calling Party Category Interworking has two possible values: Disabled (default)
Enabled
To start Calling Party Category Interworking, set this flag to enabled . When set to enabled , the Unable to show "metadata-from": No such page "_space_variables" populates the parameter Calling Party Category (CPC) with the value 11, on receiving the Resource Priority Header (RPH) in the initial INVITE. Here, the value 11 denotes "Calling Subscriber with priority". When RPH is absent in the initial INVITE, SBC populates the parameter CPC from the PAI Header. |
History Info Interworking | N/A | The flag History Info Interworking has two possible values: Disabled (default)Enabled
To start History Info Interworking, set this flag to enabled . When set to enabled , for the SIP-SIP-I call leg, the Unable to show "metadata-from": No such page "_space_variables" maps History Info Header to ISUP Parameters (Original Called Number, Redirection Number, and Redirection Information). For the SIP-I-SIP call leg, the SBC maps the ISUP parameters in the MIME body to the corresponding History Info Header.
To summarize, when History Info Interworking is enabled, the SBC supports the following mappings:
- History-Info to ISUP parameters (Redirecting Number, Original Called Number, and Redirection Information) for redirection, and the other way for the SIP-I-SIP call leg.
- History-Info to ISUP parameters (Called IN Number and Original Called IN Number) for number translation, and the other way for the SIP-I-SIP call leg.
|
Enable PVCTTCParams | N/A | When disabled, the SBC deactivates the NNI PCV to trigger. The options are: Disabled (default)Enabled
|
Set Hi Presentation Restricted | N/A | The flag Set Hi Presentation Restricted has two possible values: Disabled (default) – When set to disabled , the SBC sends send the Presentation as per privacy information it received.Enabled – When set to enabled , the SBC sends the APRH (Address Presentation Restricted Indicator) as "Presentation Restricted" irrespective of privacy information in the History-Info (HI) header.
If privacy=history, Presentation should be Restricted If privacy=none or not present, Presentation should be allowed |
Add User Equal Phonefor Div Hi Interworking | N/A | To start Add User Equal Phonefor Div Hi Interworking , set this flag to enabled . Disabled (default) – When set to disabled , the SBC will not add user=phone and mp parameter to history-info in Diversion-History-Info interworking.Enabled – When set to enabled, the SBC sends user=phone and the mp parameter to history-info header, but only for Diversion-History-Info interworking.
|
To Copy NNIProfile
To copy any of the created NNIProfile and to make any minor changes, click the radio button next to the specific NNIProfile.
Select the NNIProfile to be Copied
Click Copy NNIProfile tab on the NNIProfile List panel.
The Copy Selected NNIProfile window is displayed along with the field details which can be edited.
Copy Selected NNIProfile Window
NNI Profile Parameter Descriptions
Parameter Description | Length/Range | Parameter Description |
---|
Name | 1-23 characters | The name of the NNIProfile used to control Unable to show "metadata-from": No such page "_space_variables" interworking of charging parameters for SIP to/from SIP-I/T, GW-GW and ISUP calls. The NNI Profile is attached to a SIP trunk group. |
Charge Area Information | (ASCII 0-9) | A 5-digit value representing the charge area Information that applies to calls establishing the INVITE. |
Additional Party Category First | N/A | Use this parameter to select one of the following values to specify the first Additional Party Category type. The configured value will be included inside the policy request message sent to the PSX and sent in the ISUP IAM message body of SIP-I/T or over GW-GW message. Fixed_1-1 Fixed_1-2 Mobile_1-1 Mobile_1-2 Mobile_1-3 Mobile_1-4 Mobile_1-5 Mobile_2-1 Mobile_2-2 Mobile_2-3 Mobile_2-4 Mobile_2-5 Mobile_2-6 Mobile_2-7 Mobile_2-8 Mobile_2-9
|
Additional Party Category Second | N/A | Use this parameter to select one of the above values to specify the second Additional Party Category type. The configured value will be included inside the policy request message sent to the PSX and sent in the ISUP IAM message body of SIP-I/T or over GW-GW message. |
Calling Party Category Interworking | N/A | The flag Calling Party Category Interworking has two possible values: Disabled (default)
Enabled
To start Calling Party Category Interworking, set this flag to enabled . When set to enabled , the Unable to show "metadata-from": No such page "_space_variables" populates the parameter Calling Party Category (CPC) with the value 11, on receiving the Resource Priority Header (RPH) in the initial INVITE. Here, the value 11 denotes "Calling Subscriber with priority". When RPH is absent in the initial INVITE, SBC populates the parameter CPC from the PAI Header. |
History Info Interworking | N/A | The flag History Info Interworking has two possible values: Disabled (default)Enabled
To start History Info Interworking, set this flag to enabled . When set to enabled , for the SIP-SIP-I call leg, the Unable to show "metadata-from": No such page "_space_variables" maps History Info Header to ISUP Parameters (Original Called Number, Redirection Number, and Redirection Information). For the SIP-I-SIP call leg, the SBC maps the ISUP parameters in the MIME body to the corresponding History Info Header.
To summarize, when History Info Interworking is enabled, the SBC supports the following mappings:
- History-Info to ISUP parameters (Redirecting Number, Original Called Number, and Redirection Information) for redirection, and the other way for the SIP-I-SIP call leg.
- History-Info to ISUP parameters (Called IN Number and Original Called IN Number) for number translation, and the other way for the SIP-I-SIP call leg.
|
Enable PVCTTCParams | N/A | When disabled, the SBC deactivates the NNI PCV to trigger. The options are: Disabled (default)Enabled
|
Carrier Information Transfer - Carrier Category And Info | N/A | Use this object to define the carrier poi-category and carrier ID code. Carrier Category – The carrier category type.Olec – The SBC inserts the "olec" in the SIP requests in SIP to SIP-I interworking scenarios.Tlec – The SBC inserts the "tlec" (terminating carrier info) in the SIP responses in SIP to SIP-I interworking scenarios.
Carrier Info - Carrier ID Code – A 4-digit carrier identification code associated with the charge area. Only ASCII characters from 0 to 9 are valid.
NOTE: The following Carrier Category values are not supported in this release: |
Forward Call Indicator | N/A | Use this object to configure forward call indicator settings. National Call Indicator – Choose a National Call Indicator type:Int – International callNat – National call
Originating Isdn Indicator – Choose an Originating ISDN Access Indicator type:
|
Make the required changes to the required fields and click Save to save the changes. The copied NNIProfile is displayed at the bottom of the original NNIProfile in the NNIProfile List panel.
To Delete NNIProfile
To delete any of the created NNIProfile, click the radio button next to the specific NNIProfile which you want to delete.
Select the NNIProfile to be Deleted
Click Delete at the end of the highlighted row. A delete confirmation message appears seeking your decision.
The NNIProfile Delete Confirmation