Downloads |
 Feedback
|
Table Of Contents
Related Features and Technologies
Supported Standards, MIBs, and RFCs
PRI Tariff Table Provisioning Examples
Tariff Rate Selection Provisioning Restrictions
Provisioning PRI AOC Supplementary Services
Adding Elements to the PRI Charge Table
Modifying Elements from the PRI Charge Table
Deleting Elements from the PRI Charge Table
Retrieving an Element from the PRI Charge Table
Adding Elements to the PRI Tariff Table
Modifying Elements in the PRI Tariff Table
Retrieving an Element from the PRI Tariff Table
Deleting Elements from the PRI Tariff Table
Verifying Tariff Table Entries
AOC-D Tariff Provisioning Example
Verifying the Platform State of the Cisco MGC Hosts
Verifying That Processes Are Running
Invoking AOC Supplementary Services
Populating Table Data for AOC Supplementary Services
Adding, Editing, Retrieving, and Deleting AOC Properties
PROV-ADD—Add a Provisioning Component
PROV-ADD:PRICHARGE—Adds an Entry to the PRI Charge Table
PROV-ADD:PRITARIFF—Adds an Entry to the PRI Tariff Table
PRI AOC Service Activation (Tag: 4221)
PRI AOC Invoke Type (Tag: 4222)
PRI AOC—S-Charge Information (Tag: 4223)
PRI AOC—D-Charge Information (Tag: 4224)
PRI AOC—E-Charge Information (Tag: 4225)
PRI AOC Invoke Failure (Tag: 4226)
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
AOC Generation for PRI
Document Release History
Feature History
This document describes the AOC Generation for PRI feature. This feature is described in the following sections:
•
Supported Standards, MIBs, and RFCs
•
•
•
Feature Overview
The Advice of Charge (AOC) Generation over PRI feature enables the Cisco Media Gateway Controller (MGC) 2200 to support the Advice of Charge Supplementary Service as a charge determination point for phones that are connected to Private Branch Exchange (PBX) switches. The MGC determines the applicable tariff rates and sends AOC-S, AOC-D, and/or AOC-E messages over Primary Rate Interface (PRI) links, as defined in ETS 300 182.
AOC is a group of supplementary services that provides the served user with usage-based charging information. The MGC supports all three AOC supplementary services:
•
•
•
When the AOC Generation for PRI feature is enabled in the MGC, AOC is applicable only for the user or subscriber when that person is connected to the originating network. Also, if AOC is enabled and configured, the charging information for any of the three supplementary services can be provided for:
•
or•
The MGC activates an AOC supplementary service on a per call basis when the user has included in the SETUP message a Facility Information element containing a ChargingRequest invoke component. The ChargingRequest invoke component indicates the AOC supplementary service to activate. Each AOC supplementary service is activated independently. Thus, one, two, or three AOC activations can occur in the same SETUP message.
Upon receiving the ChargingRequest invoke component (depending on the parameters configured), the MGC activates the requested AOC supplementary service and acknowledges the request by returning a ChargingRequest return result component within a Facility Information element in a subsequent call control message to the subscriber or user indicating that "chargingInfoFollows."
If a proper per call configuration does not exist for the call requesting an activation, and the MGC cannot activate the requested AOC supplementary service, the MGC sends a Facility Information element. The element includes the requested type of AOC supplementary service (AOCSCurrency, AOCDChargingUnit, AOCEChargingUnit, and so on), the invoke component indicating that "NoChargingInfoAvailable" or another error from the General Error list to the subscriber or user.
The MGC continues processing the call normally, even if the AOC supplementary service requested was not activated. The subscriber or user must take the action that is suitable for the call.
Additionally, AOC over PRI can be configured to charge rates for a specified duration of the call, followed by a flat rate charged for the remaining call duration. This change to AOC allows for tariff changes during the call that are based on the duration of the call. For example, support for one tariff rate charge rate for the first 2 minutes of the call (that is, 40 units for the first 2 minutes or less), followed by a standard tariff rate of 10 units per minute for the remaining call duration. The remaining call tariff rate may or may not change based on the time of day or day of week.
Benefits
The AOC Generation for PRI feature provides the following benefits.
Flexible Charge Determination
Advice of Charge is an ETSI PRI Supplementary Service that allows service providers to define tariff rates for users connected over PRI/DSS1 links, as defined in ETS 300 182. Availability of the service on the MGC allows service providers to offer the service over IP-enabled voice networks.
Accurate Charge Information
AOC is a PRI supplementary service, which when activated on the MGC, provides the subscriber or user with charging information for the specific call at the beginning of the call, during the call, or at the end of the call.
Selective Supplementary AOC Services
Enables setup of all or any of the AOC supplementary services for all calls or on a per-call basis as requested by the subscriber.
Selective Tariff Rates Based on Call Duration
Enables setup of tariff rates for all calls, based on the duration of the call (that is flat-rate) or based on a specified time duration.
Restrictions
The AOC Generation for PRI feature is available on the Cisco MGC Software Release 9.5(2) Patch gs035/nn029, and above.
The number of tariff rate changes per day is 10, for a total of 11 different tariff rates in one day.
Related Features and Technologies
The AOC Generation for PRI feature provides functions for PRI AOC capabilities on the MGC (that is the PGW 2200).
Related Documents
This document contains information on the AOC Generation for PRI feature and the AOC Over PRI Tariff Changes Based on Call Duration feature. The documents that contain additional information related to the Cisco MGC are listed below:
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Release Notes for Cisco Media Gateway Controller Software Release 9.5(2).
Supported Standards, MIBs, and RFCs
Standards
The AOC Generation for PRI feature is based on the following standards:
•
•
•
•
MIBs
No new or modified MIBs are supported by this feature.
For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Management Information Base Guide.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
There are no prerequisites for the AOC Generation for PRI feature.
AOC Data Structure
The following sections describe the AOC data structure, the PRI Charge table and the PRI Tariff table (both shown in Figure 1. They also show how the provisioned information is accessed.
PRI Charge Table
The PRI Charge table can be accessed by using the following keys:
•
•
•
The PRI Charge table (shown in Figure 1) contains the tariff descriptors for each of the three AOC supplementary services that are applied (determined by identifiers and separated by a semicolon). The resultant tariff descriptor for each AOC supplementary service is in a string format and can contain either a single tariff ID to be applied for the entire day or a list of different tariffs and the time at which each tariff is applied (delimited by spaces).
If the tariff descriptor for each AOC supplementary service is a list of different tariffs and the time at which each tariff is applied, the initial entry is the tariff rate to be applied from 0000 hour until the next specified time period, at which time the tariff ID following the time switch is applied. A maximum of 10 tariff changes is allowed for one day. For example, a day can contain a total of 10 different tariff rates. That is, the starting (default) tariff rate and 10 tariff rate changes, for a total of 11 tariff rates.
A tariff descriptor time period value of 0000 indicates the end of time-dependent tariff data and the last found (previous) tariff ID continues until midnight.
The charge origin can be defaulted (a value of 0) when the charging tariff rates are not origin dependent. The day of the week can be defaulted (a value of 0) by the craftperson when the same tariff rate is to be applied to more than one day of the week.
The Holiday table allows you to specify days of the year that are charged differently from the actual day of the week on which the holiday occurs.
Figure 1 PRI Charge Table Access
In the sample PRI Charge table (shown in Figure 1), the charge origin and charge destination combination have three entries: 1,1,0 in the first row, 1,1,8 in the second row, and 1,1,5 in the third row. The second entry (1,1,8) defines a split-day holiday tariff for AOC-S and AOC-E, and a fixed-day tariff for AOC-D supplementary service. The third entry (1,1,5) defines a split-day tariff for day 5 (Friday) for only the AOC-S supplementary service. The default entry (1,1,0) defines the fixed tariff for the day to be applied for all other days that are not configured (Monday through Wednesday, Saturday, Sunday, and the remaining holiday days 9 and 10) for AOC-S, AOC-D, and AOC-E supplementary service.
The split-day tariff (the second entry) is charged as follows:
•
•
•
•
•
Note
PRI Tariff Table
The PRI Tariff table is indexed using the tariff identifier (TariffID) retrieved from the PRI Charge table. The PRI Tariff table supports a maximum of 9999 (values from 1 to 9999) distinct tariffs with user-defined tariff identifiers.
Table 1 lists the PRI Tariff table fields and a description of each field.
PRI Tariff field explanations:
Note
•
•
•
PRI Tariff Table Provisioning Examples
If AOCDMinPeriodicTimerDuration is set to 30 seconds, the time length value is 7, the timescale is 1 second, the granularity is 1, and the granularity scale is 1second, the DTariffPeriodicTimer is set to 35 seconds.
Similarly, if AOCDMinPeriodicTimerDuration is set to 30 seconds, the time length value is 70, the timescale is 1 second, the granularity is 1, and the granularity scale is 1second, the DTariffPeriodicTimer is set to 70 seconds.
Note
CLI Charge Origin Table
The CLI Charge Origin table is accessed during generic analysis. The CLI Charge Origin table is referenced after A-number digit tree analysis when AOC is enabled against the incoming trunk group or sigPath. Valid CLI Charge Origin table values are 1 through 9999. Table 2 provides a visual indication of the information present in the CLI Charge Origin table.
Table 2 CLI Charge Origin Table Sample
02087568791
2
01711234567
2
0403123456
3
...
...
Tariff Rate Types
When the combination of tariff type, duration, and rate type is used, there are effectively four types of tariffs:
•
•
•
•
Tariff Rate Selection
The following sequence of events occurs when you select a tariff rate:
Upon call connect, the MGC determines the current Tariff ID for this call from the priCharge table (based on Charge Origin, Charge Destination, Day of Week, and Time of Day).
The MGC then looks up this Tariff ID in the priTariff table and reads in the tariff information.
If there is an initial tariff descriptor defined, the MGC first applies the initial tariffs.
After the initial tariffs have been applied, the MGC applies the specified tariff. For example, if Tariff ID 3 has an initial tariff defined as "5 7", then it first applies tariff 5, then applies tariff 7, and then applies tariff 3.
The tariff remains in effect until a Time of Day or Day of Week tariff switchover (same as the current behavior).
Initial tariffs are used only at the beginning of a call. If a tariff is switched into during the call, the initial tariff is not used.
Tariff Rate Selection Provisioning Restrictions
The following provisioning restrictions are enforced by the MGC:
•
•
•
PRI Charge Operation
When you are provisioning the PRICHARGE component, all tariffs described here must have duration set to 0, which means you cannot specify a tariff that will expire after a duration.
The tariff rates can have initial tariffs that are applied at the beginning of the charging (specified in the PRITARIFF component).
The following is an example of an entry in the priCharge table:
ORIG DEST DOW S-TARIFFDESC D-TARIFFDESC E-TARIFFDESC---------------- ---- ---------- ------------- -------------- -----------------All Originations 1 Default 1 0900 2 1500 3 2000 4From the priCharge table example, the AOC-D tariff descriptor indicates that the following four tariff IDs are to be used:
•
•
•
•
PRI Tariff Operation
Figure 2 provides an example of the elements present in the priTariff table for the following MML command:
mml> prov-add:pritariff:tariffid=1,drecchrg=1,currency="dollars",amount=1,mtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=50, duration=0,ratetype=1,initialtariff="8 5 6"Figure 2 priTariff Table Example
TARIFF CHRG SCA SREC DREC EREC CURRENCY AMT AMT TIME TIME GRANUL GRAN VOL SCU BILL CHRG DURATION RATE INITIALID ITEM CHRG CHRG CHRG MULT LEN SCALE SCALE ID UNITS TYPE TARIFF------ ---- --- ---- ---- ---- ----------- -------- ---- -------- ----- ------- ------ --- ----- ---- ----- -------- ---- -------1 - - - 1 - dollars 10 3 60 2 1 2 - - 0 50 0 1 "8 5 6"2 - - - 1 - dollars 10 3 60 2 1 2 - - 0 20 0 1 ""3 - - - 1 - dollars 10 3 60 2 1 2 - - 0 60 0 1 "5 7"4 - - - 1 - dollars 10 3 120 2 1 2 - - 0 40 0 0 ""5 - - - 1 - dollars 10 3 60 2 1 2 - - 0 60 60000 0 ""6 - - - 1 - dollars 10 3 120 2 1 2 - - 0 40 120000 0 ""7 - - - 1 - dollars 30 3 60 2 1 2 - - 0 60 60000 1 ""8 - - - 1 - dollars 10 3 60 2 1 2 - - 0 50 60000 0 ""Table 3 lists the tariff IDs from the PRI Tariff table shown in Figure 2 and provides a description of the associated tariff behavior.
Provisioning Tasks
The AOC Generation for PRI feature is controlled by the ingress trunk group property AOCInvokeType, which specifies if the feature is invoked on a per call basis or for all calls. The AOCInvokeType property specifies if the AOC Generation for PRI feature is invoked based on the subscription (per call) from the user or is invoked automatically for all the calls (all calls). For all calls, a default configuration in the Tariff table is used (TariffID = 0). If AOCInvokeType is configured for all calls, then the default is required to prevent no charge generation being set up and invoked.
Provisioning PRI AOC Supplementary Services
PRI AOC supplementary services provisioning is accomplished in following stages:
•
•
•
•
•
•
•
•
•
What to Provision
The following sections describe what to provision for the PRI AOC supplemental services. The provisioning order is:
•
•
•
•
Charge Origins (Optional)
Charge origins are integer values (1-9999) that are assigned as a property against the trunk group or signaling path, a result type in the A-number analysis, or an entry in the CLI Charge Origin table. These values can be assigned incrementally during planning or you can assign any valid value at any time.
Trunk Group or Signaling Path Property
The ChargeOrigin property can be assigned to trunk groups or to signaling paths. For example, TG-2.ChargeOrigin=123.
A-Number Result
The ChargeOrigin result type has been created for AOC. Only the first data word is significant (carries the charge origin value). This result type is assignable against the ADIGTREE component only and is treated as an intermediate result (digit analysis can continue past this result type). For example,
mml> numan-add:resultset:custgrpid="t002",name="settwo"mml> numan-add:resulttable:custgrpid="t002",name=result2",resulttype="chargeorigin", dw1="1",setname="settwo"CLI Charge Origin Table
Dial plan component ACHGORIGIN has been created. This component is provisionable using the following generic format of the MML dial plan commands:
NUMAN-<verb>:ACHORIGIN:CUSTGRPID=<customer group ID>,CLI=<cli>,CORIGIN=<charge origin>The following MML commands provide an example of provisioning the ACHORIGIN result type:
mml> numan-add:achgorigin:custgrpid="t001",cli="02087568000",corigin=1Charge Destinations
CHARGE Result Type
The CHARGE result type can return a charging destination for the Metering Pulse Tariff table. This is achieved by setting dataword3 to a value of 5 for the ChargeDataDiscriminator field. The CHARGE result type is assigned against the BDIGTREE component only and is treated as an intermediate result. The values of the accompanying data is listed in Table 4.
An MML provisioning example for the CHARGE result type is:
mml> numan-add:resultset:custgrpid="t001",name="setone"mml> numan-add:resulttable:custgrpid="t001",name=result1",resulttype="charge",dw1="1", dw3="2",setname="setone"Charge Mode Indicator Result Type
The Charge Mode Indicator (CHARGE_MODE_IND) result type indicates how the metering pulses generated by the MGC are applied in relation to other possible other metering pulses (pulses generated by some other node). The CHARGE_MODE_IND result type is assignable against the ADIGTREE or BDIGTREE component and it is treated as an intermediate result. The values of the accompanying data is listed in Table 5.
Table 5 Data Values for the CHARGE_MODE_IND Result Type
1
Charge Mode Indicator
Charge Mode Indicator
1—Add on charge
2—Replace charge
3—Free of charge
Charge Indication Result Type
The Charge indication result type indicator (CHARGE_IND) indicates if the MGC should change the value of the charge indicator. The CHARGE_IND result type is assignable against the ADIGTREE or BDIGTREE component and it is treated as an intermediate result. The values of the accompanying data is listed in Table 6.
Table 6 Data Values for the CHARGE_IND Result Type
1
Charge Indicator
Charge Indicator
0—Leave as it is (default)
1—Charge
2—No charge
Holiday Table (Optional)
You can create a Holiday table, and you can add, edit, and delete rows within the table. The MML provisioning commands (PROV-ADD, PROV-RTRV, and so on), can be used to access these tables. Each row is referenced by the DATE (STRING value), broken down into three integers that represent the year, month, and day of week (yy.mm.dd). The corresponding holiday (HDAY) row entry is HOL1, HOL2, or HOL3.
An example adding a holiday for December 25, 2005:
mml> prov-add:holiday:date="041225",hday="hol1"PRI Charge Table
You can create a PRI Charge table, and you can add, edit, and delete rows within the table. The provisioning commands (PROV-ADD, PROV-RTRV, and so on) are used to access these tables, as listed in Table 7. Each row is referenced by means of three keys:
•
•
•
Note
Note
PRI Tariff Table
You can create a PRI Tariff table. The provisioning commands (PROV-ADD, PROV-RTRV, and so on) are used to access this table. Each row is referenced by a tariff ID that call processing obtains from the Charge table. The retrieved row entry contains the tariff rate and other required information for generating the charging information.
PRI Tariff table example:
mml> prov-add:pritariff:tariffid=2,schargeditem=1,sca=1,srecchrg=1,drecchrg=1,erecchrg=1, currency=USD,amount=1,amtmult=3,timelen=1,timescale=2,granularity=1,granularityscale=2, vol=1,scu=1,billingid=1Activation Type for AOC Supplementary Services/AOCInvokeType
The AOC Generation for PRI feature is controlled by the ingress trunk group property AOCInvokeType, which specifies if the feature is invoked on a "PER CALL" basis or for "ALL CALLs" received on the ingress trunkgroup. It is controlled by the AOCInvokeType Property in the properties.dat file (1=PER CALL, 2=ALL CALL). If the feature defined as "PER CALL" the MGC expects to receive the invoke component from the subscriber. If it is defined as "ALL CALL", the MGC generates the charging information and sends it to the subscriber.
Note
Note
AOCInvokeType example:
mml> prov-add:trnkgrpprop:name="3333",custgrpid="1111",AOCInvokeType=1Default Tariff for AOC Supplementary Service/AOCDefaultTariffId
If the AOCInvokeType is configured as "ALL CALL" (that is, AOCInvokeType = 2) and there is no entry for the Charge Destination, the default tariff is used to set up the charge. This default tariff value is configured in the PRI Tariff table. It is controlled by the AOCDefaultTariff property in the properties.dat file. Value range: 1 (default) through 9999.
AOCDefaultTariff example:
mml> prov-add:trnkgrpprop:name="101",custgrpid="ABC234",AOCDefaultTariffId=99Default Charging Unit Duration for AOC-D Supplementary Service/AOCDMinPeriodicTimerDuration
The MGC periodically sends accumulated charging units to the subscriber. The MGC controls the rate of sending charging information, so charging information is not sent more frequently than the configured value or after accumulation of at least one charging unit, whichever is later. The sending rate is controlled by the AOCDMinPeriodicTimerDuration signalling path property, in the properties.dat file. Value range is 5 - N seconds.
AOCDMinPeriodicTimerDuration example:
mml> prov-add:sigsvcprop:NAME="ABCNET1",AOCDMinPeriodicTimerDuration="5"
Note
PRI AOC Supplementary Services Activation
The AOC Generation for PRI feature is controlled by the AOCEnabled property in the properties.dat file (1—enabled or 0—disabled).
Note
AOCEnabled example:
mml> prov-add:trnkgrpprop:name="2000",aocenabled="1"When to Provision
Charging data should be defined during installation (after the creation of each customer dial plan). More charging data can be added at any time.
Use the following suggestions to avoid alarms being generated because of inconsistent data for calls in progress while charging data is being added or modified:
•
•
Planning for Provisioning
When planning for provisioning the AOC Generation for PRI feature, collect the information listed in the following paragraphs to populate the data tables.
Collecting PRI Charge Data
CHORIG:
CHDEST:
DOW:
STARIFFDESC:
DTARIFFDESC:
ETARIFFDESC:
Collecting PRI Tariff Data
TARIFFID:
SCHARGEDITEM:
DCALLSTATE:
ECALLSTATE:
SCA:
SRECCHRG:
DRECCHRG:
ERECCHRG:
CURRENCY:
AMOUNT:
AMTMULT:
TIMELEN:
TIMESCALE:
GRANULARITY:
GRANULARITYSCALE:
VOL:
SCU:
BILLINGID:
CHARGINGUNITS:
DURATION:
RATETYPE:
INITIALTARIFF:
For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Provisioning Procedures
Provision the AOC Generation for PRI feature of the Cisco PGW 2200 by performing the procedures contained in the following sections.
This section covers the following provisioning topics:
•
•
•
•
•
•
•
•
Provisioning Basics
Use the procedures in this section to start a provisioning session and to save and activate the changes you have made.
•
•
•
•
•
•
•
•
For more detailed information about provisioning your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You might need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-sta::srcver="curr_ver",dstver="mod_ver"Where:
•
–
–
Note
Note
•
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you enter the following command:
mml> prov-sta::srcver="ver1",dstver="ver2"Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML commands to add, modify, and delete components on your system. This document describes how to add, modify, and delete AOC components. For more information on provisioning other components on your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes, as described in the "Saving and Activating Your Provisioning Changes" section, or ending your provisioning session without saving and activating your changes, as described in the "Ending a Provisioning Session Without Activating Your Changes" section.
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.
Caution
Use the prov-cpy MML command to save and activate your changes on the active Cisco MGC. This command is typically used to save and activate changes on a Cisco MGC in a simplex configuration. However, you can use the prov-cpy MML command on Cisco MGCs in a high-availability or continuous-service configuration to save and activate your changes on the active Cisco MGC. If you choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your changes saved and activated on the standby Cisco MGC.
Note
Caution
Note
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in high-availability or continuous-service configurations. This command should not be used on a Cisco MGC in a simplex configuration.
Note
Ending a Provisioning Session Without Activating Your Changes
You may find that you want to end a provisioning session without saving and activating the changes you have entered during your session. If this is the case, you can enter the prov-stp MML command. This command ends your current provisioning session and your changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning settings. The ways in which you can use this command to retrieve provisioning data are described in the following sections:
•
•
•
•
•
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:component:name=MML_nameWhere:
•
•
For example, to view the provisioning data for an IUA signaling service called iua1, you would enter the following command:
mml> prov-rtrv:sigsvcprop:name="iua1"Retrieving Data for Select Components
You can retrieve data on select components provisioned on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:all
Note
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:component:"all"Where component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Note
prov-rtrv:propComp:name="compName" | name="ss7famName"
Where:
propComp—MML component name appropriate to the property type you want to retrieve, as listed below:
sigsvcprop—Provides maintenance access to the properties of signaling services.
trnkgrpprop—Provides maintenance access to the properties of trunk groups
lnksetprop—Provides maintenance access to the properties of linksets.
compName—MML name of a previously provisioned signaling service or trunk group.
ss7famName—MML name of the SS7 family associated with the desired linkset.You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:component:"all"Where component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
For example, to view the provisioning data for all SS7 signaling services, enter the following command:
mml> prov-rtrv:ss7path:"all"Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:sessionThe system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2004-07-17 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = jtest*/Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:variantsFor more information on provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Adding Elements to the PRI Charge Table
Step 1
Step 2
mml> prov-add:pricharge:chorig=10,chdest=15,dow="MONDAY",stariffdesc="tariff 1 timeChange 1",dtariffdesc="tariff 1 timeChange 1",etariffdesc="tariff 1 timeChange 1"
Note
Note
Step 3
Note
Step 4
Modifying Elements from the PRI Charge Table
Step 1
Step 2
mml> prov-ed:pricharge:chorig=11,chdest=15,dow="MONDAY",stariffdesc="tariff 1 timeChange 1",dtariffdesc="tariff 1 timeChange 1",etariffdesc="tariff 1 timeChange 1"Step 3
Step 4
Deleting Elements from the PRI Charge Table
Step 1
Step 2
mml> prov-dlt:charge:pricharge=11,chdest=15,dow="MONDAY"Step 3
Step 4
Retrieving an Element from the PRI Charge Table
Step 1
Step 2
mml> prov-rtrv:charge:chorig=10,chdest=15,dow="monday"
Adding Elements to the PRI Tariff Table
Step 1
Step 2
mml> prov-add:pritariff:tariffid=2,schargeditem=1,sca=1,srecchrg=1,drecchrg=1,erecchrg=1, currency=USD,amount=1,amtmult=3,timelen=1,timescale=2,granularity=1,granularityscale=2, vol=1,scu=1,billingid=1Step 3
Step 4
For the preceding MML command, the priTariff.dat entry appears as:
2 0 1 1 1 1 USD 1 4 1 4 1 4 0 1 1For the following MML commands,
mml> prov-add:pritariff:tariffid=3,schargeditem=2,sca=1,srecchrg=3,drecchrg=2,erecchrg=2, currency=USD,amount=1,amtmult=3,timelen=1,timescale=2,granularity=1,granularityscale=2, vol=0,scu=1,billingid=1mml> prov-add:pritariff:tariffid=4,schargeditem=0,sca=2,srecchrg=2,drecchrg=2,erecchrg=2, currency=USD,amount=1,amtmult=3,timelen=1,timescale=2,granularity=1,granularityscale=2, vol=0,scu=1,billingid=1The corresponding priTariff.dat entries appear as:
3 1 1 3 2 2 USD 1 4 1 4 1 4 0 1 14 0 2 2 2 2 USD 1 3 1 2 1 2 0 1 1As another example, the following MML command
mml> prov-add:pritariff:tariffid=99,schargeditem=0,sca=2,srecchrg=2,currency=Dollars,amount=1, amtmult=3,timelen=1,timescale=2adds an entry that appears in the priTariff.dat entry as:
99 0 2 2 255 255 Dollars 1 3 1 2 1677216 255 255 255 255
Modifying Elements in the PRI Tariff Table
Step 1
Step 2
mml> prov-ed:pritariff:tariffid=9,chargeditem=<AocSChargedItemRange>, dcallstate=<AocDCallStateRange>,ecallstate=<AocECallStateRange>,sca=<AocSSCArrRange>, srecchrg=<AocSRecordedChrgRange>,drecchrg=<AocDRecordedChrgRange >, erecchrg=<AocERecordedChrgRange>,currency=<IA51-10>,amount=<0-16777215>, amtmult=<AmountMultiplierRange>,timelen=<0-16777215>,timescale=<TimeScaleRange>, granularity=<0-16777215>,granularityscale=<GranularityTimeScaleRange>,vol=<VolumeRange>, scu=<1-10>,billingid=<BillingIdRange>,chargingunits=<0-16777215>,duration=<0-16777215>, ratetype=<0-1>,initialtariff=<up to 3 tariffs>
Retrieving an Element from the PRI Tariff Table
Step 1
Step 2
mml> prov-pritariff:tariffid=9
Note
mml> prov-rtrv:pritariff:"all"
Deleting Elements from the PRI Tariff Table
Step 1
Step 2
mml> prov-dlt:pritariff:tariffid=9Step 3
Step 4
Verifying Tariff Table Entries
To verify PRI Tariff table entries, use the rtrv-all MML command. You can verify the returned values against the input values.
Step 1
Step 2
mml> prov-rtrv:pritariff:tariffid=<range 1-9999>Step 3
mml> prov-rtrv:pritariff:"all"
AOC-D Tariff Provisioning Example
The following MML commands are an example of AOC-D tariff provisioning. Figure 2 shows the priTariff table entries that result from the following provisioning commands:
mml> prov-add:pritariff:tariffid=1,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=50, duration=0,ratetype=1,initialtariff="8 5 6"mml> prov-add:pritariff:tariffid=2,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=20, duration=0,ratetype=1,initialtariff=""mml> prov-add:pritariff:tariffid=3,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=60, duration=0,ratetype=1,initialtariff="5 7"mml> prov-add:pritariff:tariffid=4,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=120,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=40, duration=0,ratetype=0,initialtariff=""mml> prov-add:pritariff:tariffid=5,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=60, duration=60000,ratetype=0,initialtariff=""mml> prov-add:pritariff:tariffid=6,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=120,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=40, duration=120000,ratetype=0,initialtariff=""mml> prov-add:pritariff:tariffid=7,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=60, duration=60000,ratetype=1,initialtariff=""mml> prov-add:pritariff:tariffid=8,drecchrg=1,currency="dollars",amount=1,amtmult=3, timelen=60,timescale=2,granularity=1,granularityscale=2,billingid=0,chargingunits=50, duration=60000,ratetype=0,initialtariff=""AOC-D Use Case Examples
The following use case examples are based on the AOC-D provisioning examples. A call flow diagram is also provided for each use case.
Use Case 1
Scenario: Use 3 flat rate and then an ongoing rate.
Call Information
Charge Origin: Default
Charge Destination: 1
Day: Monday
Time of Day: 080000 (HHMMSS)
Call Duration: 5 minutes and 10 seconds
|<------------- SETUP ---------------||-------------- SETUP ACK ---------->||-------------- CALL PROC ---------->||-------------- ALERTING ----------->||-------------- CONNECT ------------>||----- FAC w/ AOC-D (CU = 0) ------>|080000 |<--------- CONNECT ACK ------------|080000 |----- FAC w/ AOC-D (CU = 50) ----->| Tariff Applied = ID 8080100 |----- FAC w/ AOC-D (CU = 110) ----->| Tariff Applied = ID 5080200 |----- FAC w/ AOC-D (CU = 150) ----->| Tariff Applied = ID 6080400 |----- FAC w/ AOC-D (CU = 150) ----->| Tariff Applied = ID 1080500 |----- FAC w/ AOC-D (CU = 200) ----->|080510 |<--------- DISCONNECT ------------||---- RELEASE w/ AOC-E (CU = 208) -->||<------- RELEASE COMPLETE ---------|Use Case 2
Scenario: Call hung up during initial flat rate.
Call Information
Charge Origin: Default
Charge Destination: 1
Day: Monday
Time of Day: 080000 (HHMMSS)
Call Duration: 0 minutes and 10 seconds
|<------------- SETUP ---------------||-------------- SETUP ACK ---------->||-------------- CALL PROC ---------->||-------------- ALERTING ----------->||-------------- CONNECT ------------>||----- FAC w/ AOC-D (CU = 0) ------>|080000 |<--------- CONNECT ACK ------------|080000 |----- FAC w/ AOC-D (CU = 50) ----->| Tariff Applied = ID 8080010 |<--------- DISCONNECT ------------||---- RELEASE w/ AOC-E (CU = 50) --->||<------- RELEASE COMPLETE ---------|Use Case 3
Scenario: Call starts during a continuous flat rate period, then rolls into ongoing duration based rate.
Call Information
Charge Origin: Default
Charge Destination: 1
Day: Monday
Time of Day: 235930 (HHMMSS)
Call Duration: 3 minutes and 10 seconds
|<------------- SETUP ---------------||-------------- SETUP ACK ---------->||-------------- CALL PROC ---------->||-------------- ALERTING ----------->||-------------- CONNECT ------------>||----- FAC w/ AOC-D (CU = 0) ------>|235930 |<--------- CONNECT ACK ------------|235930 |----- FAC w/ AOC-D (CU = 40) ----->| Tariff Applied = ID 4| |240000 | ** Switchover based on DoW, but || not applied, flat rate ongoing || |000130 |----- FAC w/ AOC-D (CU = 40) ------>| Tariff Applied = ID 1000230 |----- FAC w/ AOC-D (CU = 90) ------>|000240 |<--------- DISCONNECT ------------||---- RELEASE w/ AOC-E (CU = 98) --->||<------- RELEASE COMPLETE ---------|Use Case 4
Scenario: Call starts during continuous flat rate period.
Call Information
Charge Origin: Default
Charge Destination: 1
Day: Monday
Time of Day: 230000 (HHMMSS)
Call Duration: 3 minutes and 10 seconds
|<------------- SETUP ---------------||-------------- SETUP ACK ---------->||-------------- CALL PROC ---------->||-------------- ALERTING ----------->||-------------- CONNECT ------------>||----- FAC w/ AOC-D (CU = 0) ------>|230000 |<--------- CONNECT ACK ------------|230000 |----- FAC w/ AOC-D (CU = 40) ----->| Tariff Applied = ID 4230200 |----- FAC w/ AOC-D (CU = 80) ----->| Tariff Applied = ID 4230310 |<--------- DISCONNECT ------------||---- RELEASE w/ AOC-E (CU = 80) --->||<------- RELEASE COMPLETE ---------|Use Case 5
Scenario: Call starts during tariff 3 and then switches over into tariff 4.
Call Information
Charge Origin: Default
Charge Destination: 1
Day: Monday
Time of Day:195730 (HHMMSS)
Call Duration: 5 minutes and 10 seconds
|<------------- SETUP ---------------||-------------- SETUP ACK ---------->||-------------- CALL PROC ---------->||-------------- ALERTING ----------->||-------------- CONNECT ------------>||----- FAC w/ AOC-D (CU = 0) ------>|195730 |<--------- CONNECT ACK ------------|195730 |----- FAC w/ AOC-D (CU = 60) ----->| Tariff Applied = ID 5195830 |----- FAC w/ AOC-D (CU = 60) ----->| Tariff Applied = ID 7195930 |----- FAC w/ AOC-D (CU = 120) ----->| Tariff Applied = ID 3200000 |----- FAC w/ AOC-D (CU = 190) ----->| Tariff Applied = ID 4 (Time of day switchover)200200 |----- FAC w/ AOC-D (CU = 230) ----->| Tariff Applied = ID 4200240 |<--------- DISCONNECT ------------||---- RELEASE w/ AOC-E (CU = 230) -->||<------- RELEASE COMPLETE ---------|Troubleshooting Tips
In the event of errors, verify that all of the required properties and tables are configured properly.
For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Monitoring and Maintaining
For more information on operational tasks for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
"Daily Tasks" section contains the procedures required for proper monitoring and maintenance of this feature.
For more information on operational tasks for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Daily Tasks
The following sections describe procedures performed on a daily basis on the Cisco MGC. These procedures call for Man-Machine Language (MML) and UNIX commands. You can also perform these procedures using the optional Cisco MGC Node Manager (MNM) application. For more information on using the Cisco MNM to operate the Cisco MGC, refer to the Cisco Media Gateway Controller Node Manager User's Guide.
The tasks you should perform on a daily basis are found in the following sections:
•
•
•
Verifying the Platform State of the Cisco MGC Hosts
You can determine which of your Cisco MGC hosts is the active Cisco MGC and which is the standby Cisco MGC. If your system uses a Cisco MGC in a simplex configuration, the single Cisco MGC host is always active. To verify the MGC host state, complete the following steps:
Step 1
mml> rtrv-neThe system should return a message, similar to the following, if it is currently the active Cisco MGC:
Media Gateway Controller 2004-07-17 14:15:22M RTRV"Type:"MGC"""Hardware platform:sun4u sparc SUNW,Ultra-5_10""Vendor:"Cisco Systems, Inc."""Location:Media Gateway Controller""Version:"9.5(2)"""Platform State:ACTIVE"The valid values for the Platform State field are ACTIVE, STANDBY, and OOS.
Step 2
mml> rtrv-neThe system should return a message that indicates that it is in either the active or standby platform state.
If the Cisco MGC hosts have changed their platform states, determine why the switchover occurred by searching the contents of the active system log file.
Under normal operations, one Cisco MGC host is active and the other Cisco MGC host is standby.
If the platform state of either Cisco MGC host is out of service (OOS), check the alarms and take the actions necessary to correct the condition that caused the associated alarm(s). The alarms that require you to take corrective action and their associated actions can be found in the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.
If the platform state of both Cisco MGC hosts is active, proceed to Step 4.
Step 3
cd /opt/CiscoMGC/etcls -lThe system returns a response similar to the following:
total 35350-rw-r--r-- 1 mgcusr mgcgrp 38240 May 8 10:46 02.trigger-rw-rw-r-- 1 mgcusr mgcgrp 20488 May 10 2004 64eisup.batlrwxrwxrwx 1 mgcusr mgcgrp 43 Aug 1 18:55 active_link -> /opt/CiscoMGC/etc/CONFIG_LIB/CFG_pol-addipl-rw-rw-rw- 1 mgcusr mgcgrp 30907 Jul 24 15:29 alarmCats.dat-rw-rw-rw- 1 mgcusr mgcgrp 2064 Jun 4 10:57 alarmTable.dat-rw-rw-rw- 1 mgcusr mgcgrp 0 Jun 4 10:57 auxSigPath.datIdentify the active_link file. The previous listing indicates which configuration is currently active. The active configuration in the example is CFG_pol-addipl.
If everything is normal, this procedure is complete. However, if the configuration has changed, you might want to compare the active configuration to the previous configuration and proceed to Step 4.
Step 4
Verifying That Processes Are Running
To verify that the processes on your Cisco MGC are running, perform the following steps:
Step 1
mml> rtrv-softw:allThe system returns a response similar to the following:
Media Gateway Controller - MGC-04 2004-07-17 08:06:03M RTRV"CFM-01:RUNNING ACTIVE""ALM-01:RUNNING ACTIVE""MM-01:RUNNING ACTIVE""AMDMPR-01:RUNNING ACTIVE""CDRDMPR-01:RUNNING ACTIVE""DSKM-01:RUNNING IN N/A STATE""MMDB-01:RUNNING IN N/A STATE""POM-01:RUNNING ACTIVE""MEASAGT:RUNNING ACTIVE""OPERSAGT:RUNNING ACTIVE""PROVSAGT:RUNNING ACTIVE""MGCP-1:RUNNING IN N/A STATE""Replic-01:RUNNING ACTIVE""ENG-01:RUNNING ACTIVE""IOCM-01:RUNNING ACTIVE""TCAP-01:RUNNING IN N/A STATE""FOD-01:RUNNING IN N/A STATE""EISUP-1:RUNNING IN N/A STATE""SS7-A-1:RUNNING IN N/A STATE"
Note
Step 2
If any of the processes are stopped, contact the Cisco TAC for assistance. Refer to the "Obtaining Documentation" section for more information on contacting the Cisco TAC.
Understanding Processes
The Cisco MGC software contains processes and process groups that perform various functions. These functions include managing the I/O channels; generating alarms, call detail records (CDRs), and logs; and performing signal conversion. All of these processes are managed by the process manager of the Cisco MGC software.
Three different monitoring levels are offered:
•
•
•
Table 8 shows the system processes and process groups controlled by the process manager.
AOC Supplementary Operations
The following are AOC supplementary services:
•
•
•
The MGC acts as the charge determination point, gets the tariff rate, and generates AOC-S or AOC-D, depending on the state of the call. The AOC-S or AOC-D are sent out to the ingress side in a Facility message. The AOC-E, which is sent at the call termination, is generated in either a Disconnect or a Release message that is sent out to the ingress side. The MGC also processes the appropriate response.
Invoking AOC Supplementary Services
The MGC is required to act as a charge determination point for ETSI PRI calls. The AOC supplementary services are invoked as determined by the AOC_INVOKE_TYPE trunk group property setting. The AOC supplementary services are either invoked on receipt of the subscription (per call basis) or generally available (for all calls). AOC services will be made available for any call based on the configured (AOC_ENABLED) value.
Upon receiving the call origination, Generic Analysis obtains the Charge Origin and Charge Destination information from the dial plan, based on the number analysis. The charge information is stored in the Call Context and the AOC supplementary services are invoked.
If AOC_INVOKE_TYPE is configured for all calls, then the default tariff value is retrieved from the PRI Tariff table and AOC supplementary services are invoked. The AOC type invoked depends on the default configured value. For example, if the MGC receives the AOC invoke component, the MGC overrides the AOC component and invokes the charges as it would for per calls.
If AOC_INVOKE_TYPE is configured for per call, then the AOC supplementary services are not invoked until the AOC invoke component is received from the user.
On receipt of the invoke component, the PRI retrieves the tariff value from the PRI Tariff table, based on the stored Charge Origin and Charge Destination information, and the AOC supplementary services are invoked. The type of AOC invoked depends on the invoke component received from the user.
If the user invokes the AOC supplementary services (for example, AOC-S) and no AOC information is provided with the AOC invocation, the attempt to invoke the AOC service is rejected, and the user is informed of the reason for the rejection.
If the user invokes the supplementary AOC services and the information related to the call is not available or is incomplete, the attempt to invoke the services is rejected and the reason is made known to the subscribed user.
If a proper all calls configuration does not exist for the call requesting an activation, and the MGC cannot activate the requested AOC supplementary service, the MGC sends a Facility Information element. The element includes the requested type of AOC supplementary service (AOCSCurrency, AOCDChargingUnit, AOCEChargingUnit, and so on), the invoke component indicating that "chargeNotAvailable" or another error from the General Error list to the subscriber or user.
If the MGC receives a request to activate the AOC supplementary service in any call control message other than a SETUP message, the MGC sends a ChargingRequest return error component indicating "invalidCallState" to the subscriber or user.
Tariff information is determined, based on a combination of:
•
•
•
or
•
•
•
•
When there is a change in the charging rate during the call, due either to the configured tariff rate (split tariff) or the change in date, the MGC sends information about the new charging rate to be applied for the call to the requesting user.
If the MGC determines the charge is free-call, then free-of-charge information is sent once to the subscribing user.
Populating Table Data for AOC Supplementary Services
Two tables, PRI Charge table and PRI AOC Tariff table, have been added. These tables are in a flat-file format and are loaded at startup. These tables must be reloaded in the event of craft update.
Access to the charge table is gained by using a combination of three keys: charge origin, charge destination, and the day of the week (DOW). The charge origin and charge destination values are retrieved by the analysis function while it is reading the dial plan data and are passed on to the charging function. The holiday table is used to get the DOW and corresponding holiday. The charge table provides the charge descriptor that is applied for the call in progress.
The resultant tariff descriptor is used to set up the different AOC charging mechanisms. The tariff descriptor consists of the tariff identifier and the time of day when the tariff identifier is applied to a call. The tariff identifier is used to get the charging rate information for the invoked AOC supplementary services. The values obtained from the PRI Tariff table and PRI Charge table complete the data required for generating the required AOC.
The format for the PRI AOC Tariff table is shown in Table 2. Table 2 indicates which data is mandatory and which is optional for the different AOC supplementary services.
Invoking AOC-S Charging
The AOC-S supplementary services are invoked at call establishment. If the invoke component is received after call establishment, the call attempt is discarded and the reason is made available to the subscribing user.
On successful charge establishment due to user invocation or the MGC configuration, the charging information is sent to the subscribing user at call establishment or at the latest by call connection. Additional information is sent to the user whenever there is a change in the charging rate.
Invoking AOC-D Charging
The AOC-D supplementary services are invoked at call establishment. If the invoke component is received after call establishment, the call attempt is discarded, and the reason is made available to the subscribing user.
On successful charge establishment due to user invocation or the MGC configuration, the charging information is sent to the subscribing user during the active phase of the call. For AOC-D, the total charge is recorded until the charging information is sent to the user.
On call release, the total charge is sent to the subscribing user in a call control message that clears the call. The total accumulated charge is sent to the user at regular 15-minute intervals. On call release, the total charge accumulated is sent to the subscribing user in a backward call control message clearing the call.
Invoking AOC-E Charging
The AOC-E supplementary services are invoked at call establishment. If the invoke component is received after call establishment, the attempt is discarded and the reason is made available to the subscribing user.
On successful charge establishment due to user invocation or by the MGC configuration, the total charge is sent to the subscribing user in a call control message that clears the call.
Provisioning Example
Step 1
(Optional)—Create Charge Holiday Data.
mml> prov-add:holiday:date="04.07.04",hday="hol1"mml> prov-add:holiday:date="04.12.25",hday="hol2"mml> prov-add:holiday:date="04.05.01",hday="hol3"Step 2
The following example assigns charge origins from the newly introduced CLI charge origin table:
mml> numan-add:achorigin:custgrpid="pstn"mml> numan-add:achorigin:custgrpid="pstn",cli="91234567",corigin=1mml> numan-add:achorigin:custgrpid="pstn",cli="501234567",corigin=2Step 3
mml> prov-add:charge:chorig=1,chdest=1,stariffdesc="3 0700 4 1800 3", dtariffdesc="3 0700 5 1800 3",etariffdesc="3 0700 6 1800 4"mml> prov-add:charge:chorig=1,chdest=1,dow=saturday,stariffdesc="4", dtariffdesc="3",etariffdesc="4"mml> prov-add:charge:chorig=1,chdest=1,dow=sunday,stariffdesc="2", dtariffdesc="2",etariffdesc="2"mml> prov-add:charge:chorig=1,chdest=1,dow=hol1,stariffdesc="3 0700 4 1800 3",dtariffdesc="3",etariffdesc="4"mml> prov-add:charge:chorig=1,chdest=1,dow=hol2,stariffdesc="3",dtariffdesc="3", etariffdesc="3"mml> prov-add:charge:chdest=1,stariffdesc="1",dtariffdesc="1",etariffdesc="1"In the preceding PRI Charge table example, calls from charge origin 1 to charge destination 1 on Monday to Friday use a tariff ID of 3 from 0000 to 0700, a tariff ID of 4 from 0700 to 1800, and then a tariff ID of 3 again from 1800 to 2400, if AOC-S supplementary service is activated. The MGC uses tariff ID 3 from 0000 to 0700, tariff ID 5 from 0700 to 1800, and tariff ID 3 again from 1800 to 2400, if AOC-D supplementary service is activated. The MGC uses tariff ID 3 from 0000 to 0700, tariff ID 6 from 0700 to 1800, and then uses tariff ID 3 again from 1800 to 2400, if AOC-E supplementary service is activated.
Calls from charge origin 1 to charge destination 1 on Saturday use tariff ID 4 from 0000 to 2400, if AOC-S supplementary service is activated. Calls use tariff ID 3 from 0000 to 2400, if AOC-D supplementary service is activated. The MGC uses tariff ID 4 from 0000 to 2400, if AOC-E supplementary service is activated.
Calls from charge origin 1 to charge destination 1 on Sunday use tariff ID 2 from 0000 to 2400, if AOC-S supplementary service is activated. The MGC uses tariff ID 2 from 0000 to 2400, if AOC-D supplementary service is activated. The MGC uses tariff ID 2 from 0000 to 2400, if AOC-E supplementary service is activated.
Calls from charge origin 1 to charge destination 1 on HOL1 use tariff ID of 3 from 0000 to 0700 and tariff ID 4 from 0700 to 1800, and then uses tariff ID 3 again from 1800 to 2400, if AOC-S supplementary service is activated. The MGC uses tariff ID 3 from 0000 to 2400, if AOC-D supplementary service is activated. The MGC uses tariff ID 4 from 0000 to 2400, if AOC-E supplementary service is activated.
All other calls to charge destination 1 (charge origin <> 1) on any day use a tariff ID of 1 from 0000 to 2400, if AOC-S supplementary service is activated. It uses tariff ID 1 (flat rate) from 0000 to 2400, if AOC-D supplementary service is activated. It uses tariff ID 1 (flat rate) from 0000 to 2400, if AOC-E supplementary service is activated.
Step 4
mml> prov-add:pritariff:tariffid=1,schargeditem=1,sca=1,srecchrg=1,drecchrg=1,erecchrg=1, currency=USD,amount=1,amtmult=3,timelen=600,timescale=1,granularity=1,granularityscale=2, vol=1,scu=1,billingid=1mml> prov-add:pritariff:tariffid=2,schargeditem=1,sca=1,srecchrg=1,drecchrg=1,erecchrg=1, currency=USD,amount=1,amtmult=3,timelen=30,timescale=2,granularity=1,granularityscale=2, vol=1,scu=1,billingid=1Step 5
mml> numan-add:resulttable:customergrpid="pri",name="aoccharge1",resulttype="charge", dw1="10",dw2="10",dw3="2",setname="privoipcall"Step 6
mml> prov-add:trnkgrpprop:name="pri",custgrpid="aoccharge1",aocinvoketype=1Step 7
mml> prov-add:trnkgrpprop:name="pri",custgrpid="aoccharge1",aocdefaulttariffid=1Step 8
mml> prov-add:sigsvcprop:name="pri",aocdminperiodictimerduration="30"Step 9
mml> prov-add:trnkgrpprop:name="2000",aocenabled="1"
Adding, Editing, Retrieving, and Deleting AOC Properties
The following MML provisioning commands are examples of adding, editing, retrieving, and deleting AOC properties.
AOCEnabled Provisioning
mml> prov-add:trnkgrpprop:name="2000",aocenabled="1"MGC-01 - Media Gateway Controller 2004-07-17 15:30:22.471 EDTM COMPLD"trnkgrpprop";mml> prov-ed:trnkgrpprop:name="2000",aocenabled="0"MGC-01 - Media Gateway Controller 2004-07-17 15:30:46.350 EDTM COMPLD"trnkgrpprop";mml> prov-rtrv:trnkgrpprop:name="2000"MGC-01 - Media Gateway Controller 2004-07-17 15:30:58.869 EDTM RTRV"session=test:trnkgrpprop"/*AOCEnabled = 0AOCDefaultTariffId Provisioning
mml> prov-add:trnkgrpprop:name="2000",aocdefaulttariffid="1"MGC-01 - Media Gateway Controller 2004-07-17 15:33:43.610 EDTM COMPLD"trnkgrpprop";mml> prov-ed:trnkgrpprop:name="2000",aocdefaulttariffid="2"MGC-01 - Media Gateway Controller 2004-07-17 15:33:54.267 EDTM COMPLD"trnkgrpprop";mml> prov-rtrv:trnkgrpprop:name="2000",aocdefaulttariffid="2"MGC-01 - Media Gateway Controller 2004-07-17 15:34:00.556 EDTM RTRV"session=test:trnkgrpprop"/*AOCDefaultTariffId = 2AOCInvokeType Provisioning
mml> prov-add:trnkgrpprop:name="2000",aocinvoketype="1"MGC-01 - Media Gateway Controller 2004-07-17 15:34:42.169 EDTM COMPLD"trnkgrpprop";mml> prov-ed:trnkgrpprop:name="2000",aocinvoketype="2"MGC-01 - Media Gateway Controller 2004-07-17 15:35:32.943 EDTM COMPLD"trnkgrpprop";mml> prov-rtrv:trnkgrpprop:name="2000",aocinvoketype="2"MGC-01 - Media Gateway Controller 2004-07-17 15:35:41.888 EDTM RTRV"session=test:trnkgrpprop"/*AOCInvokeType = 2AOCDMinPeriodicTimerDuration Provisioning
mml> prov-add:sigsvcprop:name="bh2055ess",aocdminperiodictimerduration="30"MGC-01 - Media Gateway Controller 2004-07-17 15:36:53.374 EDTM COMPLD"sigsvcprop";mml> prov-ed:sigsvcprop:name="bh2055ess",aocdminperiodictimerduration="25"MGC-01 - Media Gateway Controller 2004-07-17 15:37:04.904 EDTM COMPLD"sigsvcprop";mml> prov-rtrv:sigsvcprop:name="bh2055ess",aocdminperiodictimerduration="25"MGC-01 - Media Gateway Controller 2004-07-17 15:37:09.327 EDTM RTRV"session=test:sigsvcprop"/*AOCDMinPeriodicTimerDuration = 25Command Reference
This section documents Man-Machine Language (MML) commands added to support the AOC Generation for PRI feature. All other commands are documented in the Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide.
New MML Commands
This section contains the MML commands added for the AOC Generation for PRI feature.
The following MML commands were added to support the PRI Charge table and the PRI Tariff table for the AOC Generation for PRI feature:
•
•
•
•
•
•
•
•
The following MML commands were added to support the AOCInvokeType and the AOCDefaultTariffId trunkgroup properties for the AOC Generation for PRI feature.
•
•
•
•
PROV-ADD—Add a Provisioning Component
PROV-ADD:PRICHARGE—Adds an Entry to the PRI Charge Table
PROV-ADD:PRITARIFF—Adds an Entry to the PRI Tariff Table
Reference Information
The following sections contain reference material related to this feature:
Alarms
This section lists the alarms that were added to support this feature.
PRI Tariff Table Load Failure
Description This alarm is raised in case of failure to load the PRI Tariff table.
Severity Major.
Cause Table access failed.
Type 2 (Service affecting).
Action No action required.
PRI Charge Table Load Failure
Description This alarm is raised in case of failure to load the PRI Charge table.
Severity Major.
Cause Table access failed.
Type 2 (Service affecting).
Action No action required.
PRI Tariff Charging Unit Table Load Failure
Description This alarm is raised in case of failure to load the PRI Tariff Charging Unit table.
Severity Major.
Cause Table access failed.
Type 2 (Service affecting).
Action No action required.
For information on the other alarms for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.
Billing Interface
The tags shown in Table 9 through Table 14 have been added to support the AOC Generation for PRI feature.
PRI AOC Service Activation (Tag: 4221)
PRI AOC Invoke Type (Tag: 4222)
PRI AOC—S-Charge Information (Tag: 4223)
PRI AOC—D-Charge Information (Tag: 4224)
PRI AOC—E-Charge Information (Tag: 4225)
PRI AOC Invoke Failure (Tag: 4226)
For billing interface information for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide.
Components
The components described in the following sections are added for this feature.
PRICHARGE
The PRI charge component is used to create entries in the PRI Charge table. The PRICHARGE component MML name is as follows:
•
The structure of this component is shown in Table 15.
PRITARIFF
The PRI Tariff component is used to create entries in the PRI Tariff table. The PRITARIFF component MML name is as follows:
•
The structure of this component is shown in Table 16.
Properties
The trunk group properties added for the AOC Generation for PRI feature are listed in Table 17 through Table 19.
Table 18 Provisionable Properties
AOCInvokeType
Yes
AOCDefaultTariffId
Yes
The following MML commands are used to change the configuration value for the AOCInvokeType property:
mml> prov-ed:trnkgrpprop:name="100",custgrpid="ABC123",AOCInvokeType=2mml> prov-ed:trnkgrpprop:name="101",custgrpid="ABC234",AOCDefaultTariffId=99For information on other properties of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Provisioning Worksheets
Table 20 and Table 21 are for planning your provisioning session associated with the AOC Generation for PRI feature.
For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 22 contains definitions of acronyms used in this feature module.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCSP, the Cisco Square Bridge logo, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0406R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
