The
Unable to show "metadata-from": No such page "_space_variables"
supports enhanced Preconditions Interworking to support interworking functionality on just one leg of a call instead of both legs. To use this functionality, preconditions interworking is triggered based on the presence/absence or value of a SIP information element (for example, a proprietary header or parameter). The message content is based on IP Trunk Group configurables on the ingress leg.
For in-depth details of
Unable to show "metadata-from": No such page "_space_variables"
preconditions interworking and preconditions profile flags interactions, refer to
Reserving Network Resources.
IP Signaling Profile - Common IP Attributes - Preconditions
The following are the parameter descriptions:
Preconditions Profile Parameters
Parameter | Range | Description |
---|
State | N/A | Enable this flag to activate the Preconditions Profile configuration. NOTE: The remaining Preconditions Profile configuration options (listed below) are available once this preconditions State flag is enabled. |
Support If Egress IPTG | N/A | Enable this flag during session offer processing to have the Unable to show "metadata-from": No such page "_space_variables" assume preconditions support for entities on the egress trunk group.NOTE: The SBC does not associate semantics with this field from the ingress IPTG perspective. |
Strength Mandatory Policy | N/A | Enable this flag for the Unable to show "metadata-from": No such page "_space_variables" to determine whether preconditions interworking is required on the ingress leg.NOTE: The precondition strength is mandatory in the precondition attribute and the Support If Egress IPTG flag is disabled. |
Strength Optional Policy | N/A | Enable this flag to determine whether precondition inter-working is required on the ingress leg. NOTE: The precondition strength is optional in the precondition attribute and the SupportIfEgressIPTG flag is disabled. |
UPDATEPreconditions Policy | NA | Enable this flag for the Unable to show "metadata-from": No such page "_space_variables" to indicate whether local preconditions are met with the initial INVITE or with a subsequent UPDATE on the egress leg.NOTE: This flag is significant when egress leg supports precondition based on the configuration. |
Strength Mandatory Priority | 1-100 | (Default = 1) Enter a value to specify the priority assigned to a call leg. This fields helps in resolving conflicts with selecting the policy. If the StrengthMandatoryPriority flag is enabled on one call leg, but disabled on the other call leg, the Unable to show "metadata-from": No such page "_space_variables" considers the priority assigned to the policy on each call leg to select the policy and selects the policy with the higher priority.When the two call legs have the same priority, the Unable to show "metadata-from": No such page "_space_variables" selects the policy on the ingress leg.NOTE: Priority is inversely proportional to the value of digit. Lower the digit value, higher the priority. For example, priority 1 takes precedence over priority 2. |
Strength Optional Priority | 1-100 | (Default = 1) Enter a value to specify the priority assigned to a call leg. This parameter helps in resolving conflicts with selecting the policy. If the StrengthOptionalPolicy flag is enabled on one call leg but disabled on the other call leg, the Unable to show "metadata-from": No such page "_space_variables" accounts the priority assigned to policy on each call leg to select the policy. The Unable to show "metadata-from": No such page "_space_variables" selects the policy which has higher priority.When the two call legs have the same priority, the Unable to show "metadata-from": No such page "_space_variables" selects the policy on ingress leg.NOTE: The priority is inversely proportional to the value of digit. The lower the digit value, the higher the priority. For example, priority 1 takes precedence over priority 2. |
UPDATEPreconditions Priority | 1-100 | (Default = 1) Enter a value to specify the priority assigned to a call leg. This field helps in resolving the conflicts with selecting the UPDATE policy. If the UPDATE policy is enabled on one call leg, but disabled on the other call leg, the Unable to show "metadata-from": No such page "_space_variables" considers the priority assigned to each UPDATE policy to select the UPDATE policy. In such cases, the Unable to show "metadata-from": No such page "_space_variables" selects the UPDATE policy with higher priority.When the two call legs have the same priority, the Unable to show "metadata-from": No such page "_space_variables" selects the policy on ingress leg.NOTE: The priority is inversely proportional to the value of digit. The lower the digit value, the higher the priority. For example, priority 1 takes precedence over priority 2. |
Make the required changes and click
Save to save the changes made.