4 V-Flex Configuration
The V-Flex feature is configured on the EAGLE and on the EPAP. This chapter covers the EAGLE configuration only. The EPAP configuration is covered in Administration Guide.
4.1 Introduction
The V-Flex feature is configured on the EAGLE and on the EPAP. This chapter describes prerequisites and procedures for the EAGLE configuration only. The EPAP configuration is covered in Administration Guide. Refer to Commands User's Guide for complete descriptions of the commands used in the procedures in this chapter.
V-Flex Configuration Procedure lists the steps for enabling and turning on the V-Flex feature, and for the provisioning required for the feature. Each step contains a link or reference to information and procedures to use to complete the step.
The V-Flex feature is optional and must be purchased from Oracle before it can be used in your system. If you are not sure whether you have purchased the feature, contact your Oracle Communications Sales or Account Representative.
4.1.1 EPAP Entity Provisioning
- EPAP-administered entity data can become out-of-sync with the EAGLE MAP table when the creation of Point Codes and/or Subsystem Numbers in the MAP table is performed after EPAP database administration.
- If this mismatch is discovered in real-time operations, a UIM is sent to the EAGLE maintenance terminal. (Example UIMs: SCCP did not route - DPC not in MAP tbl, SCCP did not route - SS not in MAP tbl.)
4.1.2 System Prerequisites
Before any feature that is described in this manual can be enabled, the prerequisites listed in Table 4-1 are required in the system.
Table 4-1 System Prerequisites
Prerequisite | Verification and Provisioning |
---|---|
The system serial number must be correct and locked. For new installations, the system is shipped with an unlocked serial number. The serial number can be changed if necessary and must be locked after the system is on-site. For systems that are being upgraded, the serial number is usually already verified and locked. |
Note: The serial number cannot be changed after it is entered
and locked in the system.
Locate the serial number for the system on a label affixed to the control shelf (1100). Enter the Verify that the displayed serial number is correct for the system. If no
serial number is displayed, enter the Enter the |
A sufficient number of Service Module cards must be equipped. |
Enter the If more cards or cards of a different type are needed, refer to the procedures in Database Administration - GTT User's Guide to add or remove Service Module cards. |
The GTT feature must be on in the system. Some features require an additional GTT-related feature such as EGTT. See the specific feature prerequisites in this section. |
Enter the If the GTT feature is on, the gtt=on entry appears in the output. If the gtt=off entry appears in the output, use the procedures in Database Administration - GTT User's Guide to turn on and provision the GTT feature and any other GTT-related features and functions that will be used in the system. |
4.1.3 V-Flex Feature Prerequisites
Before the V-Flex feature can be enabled, the following prerequisites are required in the system:
Table 4-2 V-Flex Feature Prerequisite
Prerequisite | Verification and Provisioning |
---|---|
The ANSIGFLEX system option cannot be set to Yes. |
Enter the Verify that the ANSIGFLEX entry does not appear in the command output or that the ANSI GFLEX entry shows a value of No. |
The LNP feature cannot be on in the system. |
Enter the If the LNP feature is on, shown with a quantity greater than zero for the LNP ported TNs entry in the command output, features described in this manual cannot be enabled. |
4.2 V-Flex Configuration Procedure
- Verify, and provision if needed, the system prerequisites. See System Prerequisites.
- Verify, and provision if needed, the feature prerequisites. See V-Flex Feature Prerequisites.
- Enable the V-Flex feature, set system STP options, and turn on the V-Flex feature. See Enabling V-Flex, Setting STP Options, and Turning On V-Flex.
-
Refer to the procedures in Database Administration - SS7 User's Guide to change the self identification of the EAGLE node to include true point codes and V-Flex capability point codes.
Messages for the V-Flex local subsystem can arrive Rt-on-SSN or Rt-on-GT. All MSUs must contain the EAGLE true or secondary point code or the V-Flex capability point code in the DPC field of the message.
For the V-Flex subsystem, the EAGLE supports ANSI, ITU-I, ITU-N, ITU-I Spare, and ITU-N Spare capability point code types. including group codes. ITU-N24 capability point codes are not supported.
- Refer to the procedures in Database Administration - GTT User's Guide to provision the following items
- Translation types and mappings
- Mated Application (MAP) table entries for the V-Flex feature that contain the EAGLE true point codes, the V-Flex capability point codes, and the V-Flex subsystem number. Only solitary and dominant loadsharing are supported.
The V-Flex subsystem can have a mate subsystem and a concerned point code group assigned to it in the MAP table.
If multiple point code types for V-Flex are provisioned in the MAP table, then the point code type for the Subsystem Out-of-Service Request message (SOR) is determined using the following order:- ANSI
- ITU-N
- ITU-N Spare
- ITU-I
- ITU-I Spare
- Provision state and subsystem number for the V-Flex local subsystem application. See Adding the V-Flex Subsystem Application.
- Provision final GTT routing to an EAGLE PC and the V-Flex local subsystem.
GTT routing information must be provisioned properly in GTT tables. Refer to the procedures in Database Administration - GTT User's Guide.
Rt-on-GT MSUs can arrive either with SCCP CdPA information that matches an EAGLE service selector, or with a GTA address that has been provisioned to translate to the local V-Flex subsystem.
If the local V-Flex subsystem is online, then it does not matter if the DPC is a CPC or TSPC. The query will be redirected to the local subsystem and processed. Any response MSU will use the TSPC assigned to the destination node as the OPC.
If the local V-Flex subsystem is offline and the mated subsystem is available, the EAGLE will reroute the message to the mated subsystem. In this case, the EAGLE is acting as both STP and SCP, and STPs do reroute messages. If a message arrives Rt-on-GT for the EAGLE TSPC, the EAGLE cannot generate a TFP. The EAGLE will be forced to handle and reroute these messages, instead of forcing the adjacent node to route to the mate. Therefore, nodes that send Rt-on-GT traffic to the EAGLE should use one of the V-Flex CPCs, not the EAGLE TSPC.
See Activating the V-Flex Subsystem.
Note:
Direct DPC/SSN routing to the EAGLE PC and the V-Flex local subsystem (SSN) is handled on the network card. No provisioning is required.Rt-on-SSN MSUs should contain the EAGLE V-Flex Subsystem number in the Called Party Subsystem field of the message.
If the V-Flex local subsystem is online, then it does not matter whether the DPC is capability point code (CPC), or true or secondary point code (TSPC). The message will be processed by the local subsystem. Any required response MSU will use the TSPC assigned to the destination node as the OPC.
If the local V-Flex subsystem is offline and the mated subsystem is available, the EAGLE will not reroute the message to the mate. In this case, the EAGLE is acting as an end node, and end nodes do not reroute. If possible, the EAGLE will generate network management messages to force the network to transition traffic to the mate.
Because the EAGLE cannot generate an SSP when a message arrives Rt-on-SSN for the EAGLE CPC, it is preferred that nodes sending Rt-on-SSN traffic use one of the EAGLE TSPCs.
- Provision the service selector mechanism to route MSUs to the V-Flex subsystem. See Adding a V-Flex Service Selector.
The V-Flex service is vflex.
The Translation Type and Subsystem Number are the values assigned for the V-Flex local subsystem when the MAP table entries were defined. See Step 5 in this procedure.
V-Flex supports ANSI, ITU-I, and ITU-N Global Title Indicators; ITU-N24 is not supported.
The Nature of Address Indicator (NAI or NAIV) and Numbering Plan (NP or NPV) are required when the GTI value is 4, and not allowed when the GTI value is 2.
V-Flex does not support the Service Nature of Address (SNAI) or the Service Numbering Plan (SNP).
- Provision V-Flex options. See Provisioning the V-Flex Options.
- Provision Home Routing Number (HOMERN) prefix entries. See Provisioning HOMERN Entries.
- Provision Voice Mail screening prefix entries. See Provisioning Voice Mail Prefix Entries.
- Provision Voice Mail routing numbers (VM RN) . See Provisioning Voice Mail Routing Numbers.
- Provision Voice Mail Server ID (VMSID) entries. See Provisioning Voice Mail Server ID Entries.
- Provision Call Decision entries. See Provisioning Call Decision Table Entries.
- Activate the V-Flex local subsystem. See Activating the V-Flex Subsystem.
-
Configure the Measurements Platform if measurements are to be collected for V-Flex.
Refer to the procedures in Database Administration - System Management User's Guide for configuring the Measurements Platform feature and the EAGLE OA&M IP Security feature in the EAGLE.
The EAGLE can collect daily and hourly measurements for the V-Flex local subsystem. V-Flex measurements are collected by only the EAGLE Measurements Platform. UI measurements reports are not available for V-Flex.
4.3 Enabling V-Flex, Setting STP Options, and Turning On V-Flex
This procedure is used to enable the V-Flex feature, set the system STP options, and turn on the V-Flex feature in the EAGLE.
The V-Flex feature must be enabled using the V-Flex feature part number 893016701 and a feature access key.
Note:
Controlled features are optional and you must be entitled to use them in your system. If you are not sure whether you are entitled to use a specific feature, contact your Oracle Sales or Account Representative.Note:
The SIP NP feature cannot be enabled if the LNP feature is on. Enter thertrv-ctrl-feat
command to verify whether or not the LNP feature is on. If the LNP feature is on, shown with a quantity greater than zero for the LNP ported TNs field in the command output, this procedure cannot be performed.
When the V-Flex feature is enabled, it is permanently enabled. The V-Flex feature cannot be temporarily enabled. After the V-Flex feature is enabled and turned on, the V-Flex feature cannot be turned off.
When the V-Flex feature has been enabled, the STP options for the default country code and the default network destination code must be changed from NONE to appropriate values for V-Flex. The chg-stpopts
and rtrv-stpopts
commands support the defcc, defndc and dsmaud parameters for the V-Flex feature.
The default country code (defcc) parameter and default network destination code (defndc) parameter can be provisioned for V-Flex after the V-Flex feature is enabled. The defcc and defndc parameter values must be changed from NONE to appropriated values before the V-Flex feature can be turned on in the system.
rtrv-stpopts
command output:
- The defcc and defndc parameters are displayed with value NONE when the V-Flex feature is enabled
- The dsmaud parameter is displayed with value OFF when the V-Flex feature is turned on
After the V-Flex feature has been enabled and the STP options are set, the V-Flex feature status must be set to on (the feature must be “turned on”). Database provisioning for V-Flex can be done after the feature is turned on.
- The defcc and defndc parameter values cannot be set to NONE.
- The DSM audit running state (dsmaud) parameter of the
chg-stpopts
command can be provisioned for V-Flex
4.4 Provisioning V-Flex as a Local Subsystem
The following procedures in this section are used to add or remove a subsystem application.
See the procedures in Changing the State of a Subsystem Application to take the subsystem application online or offline.
Note:
The EAGLE supports the operation of two or more local subsystems for EPAP-related features in the system at one time. For example, V-Flex and ATINP can coexist in the system.4.4.1 Adding the V-Flex Subsystem Application
This procedure is used to define the V-Flex (Voice Mail Router) subsystem application.The subsystem can be placed on-line when it is added or later in the configuration process (see Changing the State of a Subsystem Application).
Before the V-Flex subsystem application can be added to the database, the conditions described in Table 4-3 must exist in the system:
Table 4-3 V-Flex Subsystem Application Prerequisites
Prerequisite | Verification |
---|---|
The V-Flex feature must be enabled and turned on. |
Enter the If the VFLEX entry with Status of on does not appear in the output, see the Enabling V-Flex, Setting STP Options, and Turning On V-Flex procedure. |
The application specified by the appl parameter (vflex) cannot already be in the database. |
Enter the If the VFLEX entry appears in the output, this procedure cannot be performed. |
EAGLE true point codes and V-Flex capability point codes must be defined, and entered in the Mated Application table with a subsystem number to be used for the V-Flex subsystem application. |
Only one subsystem number for the application can be defined, and must be used for all point code types assigned to the local subsystem.. Enter the Enter the |
The examples in this procedure use the subsystem number 100 for the V-Flex application and set the V-Flex application status to online.
4.5 Provisioning the V-Flex Service Selector
The procedures in this section describe how to add, change, and remove a service selector. The information is indicated that is specific to the V-Flex feature. The commands used in these procedures are described briefly in EAGLE Service Selector Commands. Refer to Commands User's Guide for complete descriptions of the commands used in these procedures.
4.5.1 Adding a V-Flex Service Selector
This procedure is used to add a service selector for the V-Flex feature.
The V-Flex feature must be enabled and turned on before a V-Flex service selector can be added.
4.5.2 Removing a Service Selector
This procedure is used to remove a service selector from the database.
To remove a service selector, the GTI, GTII, GTIN, tt, and ssn parameter values must be entered as shown in the rtrv-srvsel
output.
These parameters can also be used to limit the amount of information displayed with the rtrv-srvsel
command.
test
4.5.3 Changing an Existing Service Selector to a V-Flex Service Selector
This procedure is used to change an existing non-V-Flex service selector to a V-Flex service selector.
The only parameters that can be changed using this procedure are:
- :nsnp
- A V-Flex service selector cannot contain an SNP value; if the service selector being changed contains an SNP value, this value must be changed to none with this parameter.
- :nsnai
- A V-Flex service selector cannot contain an SNAI value; if the service selector being changed contains an SNAI value, this value must be changed to none with this parameter.
The chg-srvsel
command requires that the following parameters be specified with the values shown in the rtrv-srvsel
output for the service selector that is being changed. If any of these parameter values need to be changed for a V-Flex service selector, use the the procedure in Removing a Service Selector to remove the existing service selector. Then use the procedure in Adding a V-Flex Service Selector to add the new V-Flex service selector with the new parameter information.
4.6 Provisioning the V-Flex Options
The V-Flex options indicate the contents and required processing of types of information in the MSU.
- The destination routing address (dra) can contain the Routing Number (RN), the Routing Number + Dialed Number (RN + DN), or the Country Code + Routing Number + Dialed Number (CC + DN + RN).
- The Nature of Address Indicator can be specified as a mnemonic (dranai) or an explicit value to indicate a subscriber number, a national significant number, an international number, a network specific number, or an unknown type of number.
- The Numbering Plan can be specified as a mnemonic (dranp) or an explicit value (dranpv) to indicate an ISDN/telephony numbering plan, a data numbering plan, or a telex numbering plan.
- If the Network Query Only option is set to on, the Call Decision table is searched after RTDB lookup, for the specified network entity type: a Voice Mail Server ID (VMSID), a signaling point routing number (SP), or a generic routing number (GRN - the Routing Number provided by the RTDB lookup).
The V-Flex feature must be turned on before this procedure can be completed. See Enabling V-Flex, Setting STP Options, and Turning On V-Flex.
4.7 Provisioning HOMERN Entries
The ent-homern
command is used to provision the prefix RNs in the HOMERN table.
The matching RN is removed in the incoming message as part of the conditioning process.
Any deleted HomeRN digits are omitted from the DN digits encoded in a Connect:DRA parameter.
After HomeRN deletion, the MSISDN with MSISDN_NAI in subscriber format is converted to international format by prepending the STPOPTS defcc value and the STPOPTS defndc value.
After HomeRN deletion, the MSISDN with MSISDN_NAI in national format is converted to international format by prepending the STPOPTS defcc value.
4.8 Provisioning Voice Mail Prefix Entries
A list of up to 100 Voice Mail prefixes can be provisioned, that can be searched against incoming CdPN digits to determine if a direct-dial VM deposit is required.
4.9 Provisioning Voice Mail Routing Numbers
Each VM Routing Number is 1-15 hexadecimal digits and has a VM Routing Number Name. A VM Routing Number Name can be assigned to each of 10 VMRN indices associated with a VMSID. See Provisioning Voice Mail Server ID Entries.
For each VM Routing Number, a reference count is maintained in the database. When a VMSID entry refers to a VM RN entry, the reference count of that VM Routing Number is incremented by 1 in the database. When a VM RN reference to a VMSID entry is removed, the reference count is decremented by 1 in the database. A VM RN entry can be deleted only when the reference count is zero for that VM RN.
4.10 Provisioning Voice Mail Server ID Entries
Up to 10 Voice Mail Routing Number Names (VM RN Names) in the VFLXVID table provide a correlation between the VMSIDs associated to the subscribers from the EPAP, and a list of call-related VMRN indexes and VM Routing numbers to be used by the EAGLE in the IDP response being sent to the MSC. Up to 1000 VMSIDs can be provisioned, including the default VMSID.
Each VM RN name is assigned to a Routing Number Index (0-9). The Routing Number Indexes are used in the Call Decision entries to identify a Routing Number associated with a VMSID.
Note:
It is up to the user to interpret what each index means. V-Flex does not interpret the indexes in any way.- If no specific MSISDN is found for a particular IDP
- If a specific MSISDN is found with no VMSID
- If a specific MSISDN is found with a VMSID in the RTDB, but there is no matching VMSID provisioned in the VFLXVID table.
- If a VMRN index match is found in the Call Decision Table, but there is no corresponding VMRN index provisioned in specific MSISDN’s VMSID.
For each Routing Number, a reference count is maintained in the database. Whenever a VMSID entry refers to a Routing Number, the reference count of that RN will be incremented by 1 in the database. Whenever a VMSID reference to a Routing Number is removed, the reference count of that RN will be decremented by 1 in the database. A Routing Number can be deleted only when the reference count is zero for that Routing Number.
4.11 Provisioning Call Decision Table Entries
- Voice Mail Number/Voice Mail Prefix (1-15 hexadecimal digits)
- INAP/CAP Redirection Indicator (redirected, not redirected)
- INAP/CAP Bearer Capability
- MSISDN/RN status indicator in the database (Found, Not Found, Does not matter -*)
Each Call Decision table entry also contains a VM Routing Number Index (0-9). The VM RN index is used in the VMSID for a specific MSISDN, or in the default VMSID if a specific VMSID is not provisioned.
4.12 Activating the V-Flex Subsystem
The procedure in this section explains how to activate the V-Flex subsystem.
V-Flex operates as a local subsystem in the EAGLE 5 ISS.
When all configuration is complete for the V-Flex feature, the V-Flex subsystem application must taken online and the local subsystem must be activated to allow it to begin operation.
When the local subsystem operating state is Inhibited, the chg-ss-appl:appl=
command can be used to specify the value online or the value offline to control the persistent setting for the local subsystem. The rtrv-ss-appl
command always displays the online or offline provisioned value. When the first Service Module card is loaded, this state tells whether the subsystem should be considered allowed (online) or inhibited (offline). This is a database state. If the command is accepted, then the change is made to the tables and can be read after an init-sys
command is entered to initialize the system.
When the Service Module cards are in-service and the subsystem application is online, the alw/inh-map-ss
commands can be used to change the dynamic operating state of the local subsystem. The inh-map-ss
command does not necessarily force a state change, because it can fail if the mate does not send SOG. The force=yes parameter must be specified to bypass the SOR/SOG exchange and inhibit immediately. (There is no rtrv-map-ss
command.)
The procedures in Changing the State of a Subsystem Application explain how to take a local subsystem online and offline.
Table 4-4 Subsystem Allow/Inhibit
Command\ Subsystem State | Offline | Online |
---|---|---|
alw-map-ss
|
Command is rejected. | Attempts to make the local subsystem active. |
inh-map-ss
|
Command accepted, but no action because offline implies inhibited. | Attempts to inhibit the local subsystem. Use of the force=yes parameter bypasses the SOR/SOG exchange and inhibits immediately. |
chg-ss-appl:appl=vflex :nstat=online
|
Command is rejected, because the subsystem must be online to be in the allowed state. | Changes local subsystem database status to online. |
chg-ss-appl:appl=vflex :nstat=offline
|
Command is rejected because the subsystem must be inhibited to go offline. | Changes local subsystem database status to offline. |
4.13 Changing the State of a Subsystem Application
The procedures in this section are used to set the state of an existing subsystem application to either online or offline.
The online/offline status of the subsystem application is shown in the STAT field of the rtrv-ss-appl
command output.
The rept-stat-sccp
command displays the operating state (in or out of service) of the subsystem.
If the subsystem application is to be taken online, the subsystem application must be offline.
When the subsystem is taken online (regardless of how the subsystem was taken offline), the EAGLE 5 ISS sends SNR/SSA. A UAM is generated, indicating that the subsystem is ALLOWED.
If the subsystem application is to be taken offline, the subsystem application must be online. The subsystem must be taken out of service (OOS-MT-DSBLD) with the inh-map-ss
command before it can be taken offline.
A subsystem application can be taken offline using coordinated state change, or forced offline without using coordinated state change.
When the inh-map-ss
command is entered for the subsystem, a coordinated shutdown is attempted. If the coordinated shutdown fails, a UIM is output indicating the shutdown failed. If the force parameter is specified, the subsystem is forced to shut down; a coordinated shutdown is not performed.
For coordinated state change, SCMG sends an SOR message to the mated subsystem and will start a Tcoord timer (30 seconds). If SCMG receives an SOG message from the mated subsystem before the Tcoord timer expires, SCMG will broadcast SSPs to the concerned point code group, send SBR / SSP, and take the subsystem offline. A UAM is generated, indicating that the subsystem is PROHIBITED. If the SOG is not received before Tcoord expires, then the inhibit request is denied and a UIM is generated.
When the subsystem is taken offline without coordinated state change, the EAGLE 5 ISS sends SBR/SSPs. A UAM is generated, indicating that the subsystem is PROHIBITED.
- The local subsystem is available
- The total load on the DSM subsystem is less than 45% of its capacity
If either of these conditions is not met, the EAGLE 5 ISS will not reply to the SOR message.
4.14 Configuring the Measurements Platform
The EAGLE can collect daily and hourly measurements for the V-Flex service. V-Flex measurements are collected by only the EAGLE Measurements Platform. UI measurements reports are not available for V-Flex.
For information about V-Flex measurements, see V-Flex Measurements in this manual and refer to Measurements Reference. Refer to the procedures in Database Administration - System Management User's Guide for configuring the Measurements Platform feature in the EAGLE.