Skip Headers
Oracle® Communications Billing and Revenue Management Telco Integration
Release 7.5

E16721-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

18 About Managing Prepaid Services and Extended Rating Attributes

This chapter describes how to set up prepaid services, supplementary services, and extended rating attributes (ERAs) in your Oracle Communications Billing and Revenue Management (BRM) system.

For background information about wireless services, see "About Integrating Wireless Services".

About BRM Prepaid Services

A BRM service is the mechanism by which services are managed in BRM. They are identified by classes and objects, such as /service/telco/gsm/telephony.

Telco services are the services that are provisioned on a telco network. There are groups of telco services, such as telephony, data, and fax. For example, with GSM services, there are multiple varieties of GSM service in each GSM service group: the voice service group includes normal voice telephony service (T11) and emergency-only telephony service (T12).

A single service can be used to offer multiple types of a service. For example, the BRM /service/telco/gsm/telephony service is used for GSM normal voice service and emergency-only voice service. When you create products in Pricing Center, you use provisioning tags to assign different types of telco services to them. For more information, see "About Provisioning Tags for Telco Services".

The services in Table 18-1 are used to offer telco services:

Table 18-1 Services for Telco

Service Description

/service/telco/gsm/telephony

Supports GSM voice services.

/service/telco/gsm/fax

Supports GSM fax services.

/service/telco/gsm/data

Supports GSM Internet access for corporate access or WAP access.

/service/telco/gsm/sms

Supports GSM Short Message Service (SMS).


Your price list can include deals for one or more services. For example, you might have a plan that includes just the GSM telephony service (/service/telco/gsm/telephony) and a plan that includes all BRM GSM services. You can create different usage and subscription rates for different services. For more information, see "Setting Up GSM Wireless Pricing".

About Telco Service Logins and Passwords

When you create an account that uses telco services, the customer ID and password are generated automatically. Therefore, a CSR does not need to enter an ID and password at account creation or when adding a telco service.

Note:

Internally, the customer ID is the same as the login name.
  • To ensure that a unique ID is generated, the default ID is a unique string composed of the following elements:

    • A timestamp generated by the Connection Manager (CM) that was used for creating the account.

    • The process ID (PID) of the CM.

    • The thread ID of the CM (always 1).

    • The CM host name.

    For example:

    269-20011128-095216-7-22493-1-host_name

    When an ID is needed: for example, for Web-based account management: the customer enters their MSISDN or IMSI. Applications can retrieve the MSISDN or IMSI from the customer's service objects. (Customers can also enter the ID.)

    Note:

    When using an MSISDN or IMSI as a login, the customer must enter the full number with no punctuation, such as 014085551212.

    To customize how IDs are generated, you customize the PCM_OP_CUST_POL_PREP_LOGIN policy opcode.

  • The default password is password. You cannot change the password when a service is being added, but you can change it later in either Customer Center or Self-Care Manager.

    To customize how passwords are generated, you customize the PCM_OP_CUST_POL_PREP_PASSWD policy opcode.

About Associating SIM Cards and Numbers with Services

Use Customer Center to associate SIM cards and telephone numbers with telco services and to change the SIM card and number for a customer's service.

SIM cards and telephone numbers are not associated with each other. Instead, you associate SIM cards and telephone numbers with the appropriate service, as shown in Figure 18-1:

Figure 18-1 SIM Card to Service Association

Description of Figure 18-1 follows
Description of "Figure 18-1 SIM Card to Service Association"

You can associate SIM cards and numbers in a variety of ways. For example, a customer can own multiple services, SIM cards, and numbers.

Figure 18-2 shows associations for three services, each with its own SIM card and number:

Figure 18-2 Three SIM Cards to Services Associations

Description of Figure 18-2 follows
Description of "Figure 18-2 Three SIM Cards to Services Associations"

You can also associate SIM cards and numbers with multiple services as shown in Figure 18-3:

Figure 18-3 SIM Card to Multiple Services Associations

Description of Figure 18-3 follows
Description of "Figure 18-3 SIM Card to Multiple Services Associations"

You can customize the SIM card and number policy opcodes, PCM_OP_SIM_POL_DEVICE_ASSOCIATE and PCM_OP_NUM_POL_DEVICE_ASSOCIATE, to customize how services, SIM cards, and numbers can be associated. By default, the following business policies are used:

  • Each account can have one or more SIM cards and one or more telephone numbers.

  • You can use one SIM card and number for all services, or you can use multiple SIM cards and numbers; for example, you can use a separate SIM card and number for each service.

  • A SIM card can be associated with multiple services only if the services are of different types, such as fax and telephony, and each service must belong to the same network element. For example, two /service/telco/gsm/telephony services can be associated with the same SIM card to support dual lines on one SIM card.

  • A number can be associated with multiple services, with the following restrictions:

    • All services must belong to the same account.

    • All services must belong to the same network element.

    • Each service must be of a different type. For example, you cannot associate one number with two telco services. To do so, you need to customize the policy opcode for the device type, PCM_OP_SIM_POL_DEVICE_ASSOCIATE or PCM_OP_NUM_POL_DEVICE_ASSOCIATE.

  • With the exception of the telephony service, a SIM card can share a service association with only one telephone number. For example, if you associate a SIM card with a fax service and a data service, the phone number must be the same for the fax service and the data service.

    If you associate a SIM card with two telephony services, you must associate a different number for each of the telephony services.

  • A SIM card and number associated with the same service must have the same network element.

  • A SIM card and number associated with the same service must belong to the same brand.

For more information, see "How Accounts Are Created and Managed".

About Assigning SIM Cards

When assigning SIM cards in Customer Center:

  • You can manage SIM cards by brand.

  • You cannot change the IMSI number, network element, or status.

For information about managing SIM cards in Customer Center, see information about GSM accounts in the Customer Center Help.

For information about managing your SIM card inventory, see "About Managing SIM Card Inventory".

About Assigning Numbers

When assigning numbers in Customer Center:

  • You can manage numbers by brand.

  • You cannot change the network element, number category, vanity flag, or status.

  • If an account has more than one telephone number, you can specify one of them as the primary number. If Pipeline Manager processes an event that includes the IMSI, and if the IMSI is the same for multiple telephone numbers, Pipeline Manager uses the primary number to look up the service.

    Note:

    Customer Center does not support adding more than one number to an account, but you can create a custom application to do this.
  • You can assign an IMEI number, but it is not required.

  • You can assign vanity numbers to charge a different amount for specific numbers.

For information about managing your telephone number inventory, see "About Managing Telephone Numbers".

About Provisioning Tags for Telco Services

To implement supplementary services, service extensions such as bearer services, and extended rating attributes (ERAs) for telco services, you define provisioning tags. You then use Pricing Center to include provisioning tags in products. A tag becomes available to an individual account and service when a product containing the tag is purchased. This is also known as product-level provisioning.

Use one of these methods to define provisioning tags for telco services:

Use these methods for provisioning tags for telco services, except for the following cases:

  • For a provisioning tag that creates an ERA or other type of profile that you want to associate with a discount. Services Framework Manager does not process provisioning tags associated with discounts.

  • For a provisioning tag that populates default values to a profile when creating it. Services Framework Manager cannot populate default values to the profiles.

In both of these cases, use the provisioning tag framework to create provisioning tags. See "Using the Provisioning Tag Framework" in BRM Setting Up Pricing and Rating.

Service-level provisioning tags are stored in service-specific /config/telco objects, such as /config/telco/gsm/telephony.

You can also use the pin_telco_tags_service file to create account-level ERAs, which do not depend on a specific service. These ERAs are stored in /config/account_era objects.

Important:

You cannot use the Provisioning Tags application to add account-level ERAs to provisioning tags.

For more information, see:

Some provisioning tags are available by default when you install GSM Manager. For a list of these tags, see "Default Account-Level ERAs" and "Default Service-Level ERAs".

For information on creating provisioning tags for non-telco services, see "Working with Provisioning Tags" in BRM Setting Up Pricing and Rating.

About the Provisioning Tags Application

You can create provisioning tags for telco services in the Provisioning Tags application, which is part of Pricing Center.

You can use this application to do the following:

  • Create new provisioning tags or search for, display, and edit existing provisioning tags for telco services as shown in Figure 18-4:

Figure 18-4 Provisioning Tags Application

Description of Figure 18-4 follows
Description of "Figure 18-4 Provisioning Tags Application"

  • Add or delete service extensions, such as bearer services, and features for new or existing provisioning tags as shown in Figure 18-5:

Figure 18-5 Service Extensions Window

Description of Figure 18-5 follows
Description of "Figure 18-5 Service Extensions Window"

  • Add or delete ERAs and ERA labels for new or existing provisioning tags as shown in Figure 18-6. An ERA label is an individual ERA list. An ERA can have multiple lists:

You can include only ERAs that already exist in the BRM database, although you can add new label names. To create custom ERAs, see "Defining ERAs for Telco Services" and "Creating ERAs" in BRM Setting Up Pricing and Rating.

Note:

The ERA names and descriptions displayed in Provisioning Tags are from the era_descr.locale file. See "Customizing ERA Names and Descriptions for Client Applications" in BRM Setting Up Pricing and Rating.

For more information, see Provisioning Tags Help.

Examples of Provisioning Tags for Prepaid Services

You can create different types of provisioning tags; for example:

  • A provisioning tag for a single bearer service, such as a type of voice service.

  • A provisioning tag for one or more supplementary services without a bearer service. A product with this type of provisioning tag is typically included in an add-on plan because the customer must have the service already before adding the supplementary services.

  • A provisioning tag for one or more service-level ERAs. This type of provisioning tag can be used only in an add-on plan.

  • A provisioning tag can include combinations of a bearer service, supplementary services, and service-level ERAs.

For example, you might include two different provisioning tags for a GSM telephony service product:

  • The VoicePremium provisioning tag implements the following:

    • A voice bearer service

    • The Call Forwarding supplementary service

    • The Home Cell Assignment service ERA

  • The VoiceFamily provisioning tag implements the following:

    • A voice bearer service

    • The Caller ID supplementary service

    • The Friends and Family service ERA

You might also create products such as these:

  • A product that implements a voice bearer service.

  • An add-on product that implements Call Forwarding and the Home Cell Assignment ERA.

  • An add-on product that implements Caller ID and the Friends and Family ERA.

    Important:

    You cannot directly change the status of supplementary services. Instead, you change the status by changing the status of the products that they were purchased with.

    For example, to inactivate a Call Forwarding supplementary service, you inactivate its product. However, when you do so, you inactivate all other products, supplementary services, and service-level ERAs that were purchased with that product.

    Therefore, you should create products that allow you to manage services after the products are purchased. For more information, see the Customer Center Help.

About GSM Supplementary Services

GSM supplementary services are features such as call forwarding and call blocking. They are not implemented as BRM services. Instead, they are implemented by using product-level provisioning.

For example, you might have a product in your price list that includes the GSM telephony service and a provisioning tag that implements the call forwarding supplementary service.

Note:

Supplementary services can be used only with GSM services.

Value-added services, such as voice mail, are similar to supplementary services. The difference is that value-added services are not part of the GSM network standard.

Note:

In Customer Center, and in this documentation, supplementary services and value-added services are referred to collectively as supplementary services.

You include supplementary services in products by using provisioning tags. You can create products that add supplementary services to an existing account; for example, a product that adds call forwarding.

You cannot activate supplementary services in Customer Center. After BRM provisions a supplementary service, a customer usually activates the supplementary service using the telephone keypad. For example, a customer can define a number to use for call forwarding.

For more information, see "About Provisioning Tags for Telco Services".

How Supplementary Services Are Stored in BRM

A customer's supplementary services are defined in the service objects owned by the customer's account. For more information, see /service/telco/gsm.

You define system-wide supplementary services in /service/telco/gsm objects. For example, supplementary voice telephony services are defined in /service/telco/gsm/telephony.

About Extended Rating Attributes for Telco Services

Extended rating attributes (ERAs) provide discounts and promotions based on a specific attribute, such as a telephone number. For example, you use ERAs to offer special friends and family rates or a birthday discount.

A friends and family ERA type can have multiple lists. Each individual list is identified as an ERA label. During rating, BRM can apply different rates based on the label.

For general information about ERAs, see "About Extended Rating Attributes".

BRM contains default ERAs for telco services. For lists of default ERAs, see "Default Account-Level ERAs" and "Default Service-Level ERAs". Default ERAs are loaded when you install a telco service manager, such as GSM Manager.

To create ERAs for telco services, see "Defining ERAs for Telco Services".

For more information, see:

About Configuring ERAs for Individual Customers

When a customer purchases a product that uses telco provisioning tags, the primary telco service is provisioned. You then use the Customer Center Promotion tab to configure the customer's ERAs. For more information, see the Customer Center Help.

Note:

  • ERA codes are defined in Pipeline Manager configuration files. When you enter ERA data in Customer Center, the data you enter depends on how you configure the ERAs in Pipeline Manager. For example, you might enter a number in an ERA. That number is mapped to a value in ERA configuration.

  • When configuring ERAs in Customer Center, use only uppercase letters, ASCII 7-bit punctuation, and no spaces.

You do not configure any primary services or supplementary services after an account is created. The customer usually performs this type of configuration using the handset. For example, a customer might define call forwarding numbers.

How ERAs for Telco Services Are Stored in BRM

A customer's ERA configurations are stored in profile objects:

  • The /profile/serv_extrating object, which stores the service-level ERA configuration, is linked to the telco service objects owned by the customer's account.

  • The /profile/acct_extrating object, which stores the account-level ERA configuration, is linked to the account object that owns the telco services.

You define system-wide definitions for service-level ERAs in /config/telco/service objects. For example, supplementary voice telephony services are defined in /config/telco/gsm/telephony. Account-level ERAs are defined in /config/account_era objects. See "About Provisioning Tags for Telco Services".

Defining Provisioning Tags for Telco Services by Using the pin_telco_tags file

This section describes defining provisioning tags through the pin_telco_tags file for a specific telco service. For example, you use pin_telco_tags_gsm for GSM provisioning tags.

You can include service-level ERAs, supplementary services, and service extensions in a provisioning tag defined in a pin_telco_tags file.

You can use the Provisioning Tags application in Pricing Center instead of the pin_telco_tags file to define provisioning tags for telco services. But you cannot create custom ERAs using Provisioning Tags. For information, see "About the Provisioning Tags Application" and Provisioning Tags Help.

To define provisioning tags using the pin_telco_tags file:

You can also define account-level ERAs in the pin_telco_tags file. See "Defining Account-Level ERAs in the pin_telco_tags File"

Configuring Provisioning Tags in the pin_telco_tags File

To configure a provisioning tag in the pin_telco_tags file:

  1. Open the pin_telco_tags_service file. For example, use pin_telco_tags_gsm for GSM services.

    The default pin_telco_tags files are in BRM_Home/sys/data/config. They include examples and instructions.

  2. Use this syntax to add a provisioning tag:

provisioning_tag  "Class" "ProvTag" "PTDescription" "DelayedProvReqd"
service_extn      "Extension Type Name" "Extension Value" 
features          "One Or More Feature Name String Values" 
service_era       "ServiceERA" "StringIdERA" "StringIdServiceERADesc" "ProvBool" "ERALabel"

Enter each value in quotation marks.

A provisioning tag can be any combination of service extensions, features, and service-level ERAs. You do not need to include all three types of data in a tag.

Table 18-2 describes the provisioning tag syntax:

Table 18-2 Provisioning Tag Syntax

Tag Element Value Description

provisioning_tag

Class

The object that stores the tag. For example:

"/config/telco/gsm/telephony"

provisioning_tag

ProvTag

The name of the provisioning tag. For example:

"DataPremium"

provisioning_tag

PTDescription

The description of the provisioning tag. For example:

"Premium Data Service"

provisioning_tag

DelayedProvReqd

Whether the tag is unprovisioned when the product containing the tag is canceled. The possible values are:

  • "y" specifies that cancellation triggers unprovisioning. In most cases, use this setting.

  • "n" specifies that cancellation does not trigger unprovisioning.

    Use this setting to leave a customer's service configuration unchanged. For example, you might want to leave a voice mailbox intact.

service_extn

Extension Type Name

The type of service extension. For example:

"BEARER_SERVICE"

service_extn

Extension Value

The code for a GSM bearer service or other service extension. For example:

"B46"

Codes are defined in the GSM specification. You must use the exact code that the network requires.

features

One or More Feature Name String Values

The GSM supplementary services that are provisioned when this product is purchased. The services are entered as codes, in one line. For example:

"CLIP" "CW"

These codes are defined in the GSM specification. You must use the exact code that the network requires. For a list of codes, see "Supported Supplementary Services".

service_era

ServiceERA

The service ERA code. For example:

"FRIENDS_FAMILY"

service_era

StringIdERA

StringIdServiceERADesc

The IDs for the ERA name and description. For example:

"12"  "13"

You define a localized name and description for these IDs in the era_descr.localefile. These names and descriptions appear in Customer Center. See "Customizing ERA Names and Descriptions for Client Applications" in BRM Setting Up Pricing and Rating.

service_era

ProvBool

Whether or not provisioning is required. The possible values are:

  • "y" specifies that provisioning is required.

  • "n" specifies that provisioning is not required.

service_era

ERALabel

The name of a list within the ERA. An ERA can have one or more lists. For example:

"MYFRIENDS"

Note: You cannot localize the ERA label. You cannot have duplicate label names associated with the same ERA code.


This example shows a provisioning tag for a telephony product that includes a bearer service, call waiting and voice mailbox supplementary services, and friends and family service-level ERAs:

# Standard Telephony Package 
provisioning_tag  "/config/telco/gsm/telephony”  "Voice Standard" "Voice Standard Service package with Called ID, Call Waiting, Voice mail and Friends and Family" "y"
service_extn      "BEARER_SERVICE" "T11"
features          "CLIP" "CW" "VMBOX" 
service_era       "FRIENDS_FAMILY" 12 13 "n" "MYFRIENDS"
service_era       "FRIENDS_FAMILY" 12 13 "n" "MYFAMILY"

Loading the pin_telco_tags File

Run the load_pin_telco_tags utility to load the contents of the pin_telco_tags_service file: for example, the pin_telco_tags_gsm file: into the BRM database. This utility creates or updates /config/telco/service and /config/account_era objects.

Caution:

By default, the load_pin_telco_tags utility appends telco provisioning tags and account-level ERAs to the BRM database. But if you use the -x parameter, this utility overwrites existing telco provisioning tags and account-level ERAs. Do not use the -x parameter unless you are certain you want to overwrite existing objects.

Important:

The load_pin_telco_tags utility requires a configuration file. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Note:

You cannot create ERAs for individual brands. All ERAs can be used by any brand.
  1. Edit the pin_telco_tags_service file to add the custom account-level ERAs. The default pin_telco_tags_gsm file in BRM_Home/sys/data/config includes examples and instructions.

  2. Save the pin_telco_tags_service file.

  3. Use the following command to run the load_pin_telco_tags utility:

    load_pin_telco_tags pin_telco_tags_service 
    

    For the complete command syntax, see "load_pin_telco_tags".

  4. Restart the Connection Manager (CM). See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

  5. Restart Pricing Center.

To verify that the account ERAs were loaded, you can display the /config objects by using the Object Browser or use the robj command with the testnap utility. (See "Reading an Object and Writing Its Contents to a File" in BRM Developer's Guide.)

Defining ERAs for Telco Services

You can create both service-level and account-level ERAs. This section describes creating service-level ERAs. For more information about account-level ERAs, see "Defining Account-Level ERAs in the pin_telco_tags File".

To create and implement an ERA for a telco service:

  1. Define the ERA in a provisioning tag.

    See "Defining Provisioning Tags for Telco Services by Using the pin_telco_tags file".

    Note:

    To use an ERA already defined in a default provisioning tag, you do not need to define a new provisioning tag, but you must perform the remaining steps.
  2. Define how the ERA is rated. For example:

    • To rate an ERA based on usage type, create a usage type corresponding to the ERA and customize the IRL_UsageType iRule. See information about defining usage types in Pricing Center Help and "Configuring the IRL_UsageType iRule for ERAs" in BRM Setting Up Pricing and Rating.

      The usage type code must match the value in the IRL_UsageType.data file for this type of ERA.

    • To rate an ERA based on the label name, define a price or discount model selector for pipeline rating or a rate plan selector for real-time rating. The rate or discount is based on the label name. See "Using ERAs with Multiple Lists" in BRM Setting Up Pricing and Rating.

  3. Include the provisioning tag when creating or modifying a product based on a telco service or on an account. See information about defining product purchase information in Pricing Center Help.

    Note:

    Although it is possible to include provisioning tags in discounts, BRM does not make use of them for telco services.
  4. Add the names and descriptions to the era_descr.locale file. Names and descriptions from this file are displayed in Customer Center and Provisioning Tags. See "Customizing ERA Names and Descriptions for Client Applications" in BRM Setting Up Pricing and Rating.

  5. Configure the ERA for a specific customer in Customer Center. ERAs are called promotions in Customer Center. ERAs you configure are stored as profiles. For more information, see "About Configuring ERAs for Individual Customers" and the Customer Center Help.

    Note:

    For ERAs based on usage types, CSRs must enter values in Customer Center that exactly match the way values are specified in the ISC_UsageType.isc file. See "Configuring the IRL_UsageType iRule for ERAs" in BRM Setting Up Pricing and Rating.
  6. (Optional) Create a profile sharing group to share the ERA with other accounts. See information about creating a profile sharing group in the Customer Center Help.

    Note:

    • Even though an account is qualified to use ERAs, you do not have to implement them in the account.

    • Service-level ERA profile information is not automatically transferred between plans during plan transition or generation change. If the two plans have some common provisioning tags, the ERA profile information can be reconfigured in the new plan. See information about configuring service-level promotions in the Customer Center Help.

    • BRM does not validate any data entered when configuring ERAs; for example, telephone numbers for the friends and family discount. To create validation rules for these entries, edit the PCM_OP_CUST_POL_VALID_PROFILE policy opcode.

Defining Account-Level ERAs in the pin_telco_tags File

Account-level ERAs apply to any activity in an account no matter which service is involved.

You define account-level ERAs in any pin_telco_tags_service file. You can use the define account-level ERAs in the same file you used for telco provisioning tags.

Note:

You cannot use the Provisioning Tags application for account-level ERAs.

To define an account-level ERA:

  1. Open a pin_telco_tags_service file. You can define an account-level ERA in any pin_telco_tags file, because they are not associated with a particular service.

    The default pin_telco_tags files are in BRM_Home/sys/data/config. They include examples and instructions.

    Account-level ERAs are added in a block at the end of the file.

  2. Use this syntax to add an account-level ERA:

    account_era  "AccountERA" "StringIdERA" "StringIdAccountERADesc" 
    

Table 18-3 describes the account ERA syntax:

Table 18-3 Account ERA Syntax

Value Description

AccountERA

The account ERA code. For example:

"SPECIAL_DAY"

StringIdERA

StringIdAccountERADesc

The IDs for the ERA name and description. For example:

"2"  "3"

You define a localized name and description for these IDs in the era_descr.localefile. These names and descriptions appear in Customer Center. See "Customizing ERA Names and Descriptions for Client Applications" in BRM Setting Up Pricing and Rating.


For example:

account_era "SPECIAL_DAY" "2" "3"

Supported Supplementary Services

Table 18-4 shows the supplementary services supported by GSM Manager. You select from these codes when configuring GSM provisioning tags in Pricing Center.

These codes are defined in the GSM provisioning DTD file (GSM.dtd), which is used by the GSM provisioning components. If you customize the GSM provisioning components to add supplementary services, you must be sure to use the new codes in the provisioning tags.

Table 18-4 GSM Manager Supported Supplementary Services

Supplementary Service Code

Advice of charge (charging)

AOCC

Advice of charge (information)

AOCI

Barring all incoming calls

BAIC

Barring incoming calls when roaming outside the home PLMN country

BAICR

Barring all outgoing calls

BAOC

Barring all incoming calls when roaming outside the home PLMN country

BICRO

Barring all outgoing international calls

BOIC

Barring all outgoing international calls except those directed to the HOME PLMN country

BOICXH

Completion of calls to busy subscribers

CCBS

Call deflection

CD

Call forwarding on mobile subscriber busy

CFB

Call forwarding on mobile subscriber not reachable

CFNRC

Call forwarding on mobile subscriber no reply

CFNRY

Call forwarding unconditional

CFU

Calling line identification presentation

CLIP

Calling line identification restriction

CLIR

Name identification

CNAP

Connected line identification presentation

COLP

Connected line identification restriction

COLR

Call waiting

CW

Explicit call transfer

ECT

Call holding

HOLD

Multicall

MC

Enhanced multilevel precedence

MLPP

Multiparty

MPTY

Support of private numbering plan

SPNP

User-to-user signaling

UUS

Voice/fax mail service

VMBOX


Default Account-Level ERAs

Table 18-5 summarizes the default account-level ERAs:

Table 18-5 Default Account-Level ERAs

Function Name Pipeline Manager Name

Assign an account to a business segment for business intelligence reporting.

Business Intelligence Segment ERA

See information about adding a business intelligence segment promotion in the Customer Center Help.

DATAWAREHOUSE

Assign an account to a customer group, or assign an arbitrary quality level to an account.

Customer type or quality ERA

See information about adding a customer type or quality promotion in the Customer Center Help.

CLASSIFICATION

Assign an account to a group of accounts that share certain telephony properties.

Corporate agreement ERA

See information about adding a corporate agreement promotion in the Customer Center Help.

CORPORATE

Create a closed user group, such as a group of all mobile numbers in a company.

Closed user group ERA

See information about adding a closed user group promotion in the Customer Center Help.

CLOSEDUSERGROUP

Give a discount for calls made on a specific calendar date.

Special day discount ERA

See information about adding a special day discount promotion in the Customer Center Help.

SPECIAL_DAY

Use a pipeline rate plan.

Pipeline account-level rate plan ERA

See information about adding a pipeline account-level rate plan promotion in the Customer Center Help.

RATEPLAN


Default Service-Level ERAs

Table 18-6 summarizes the default service-level ERAs:

Table 18-6 Default Service-Level ERAs

Function Name Pipeline Manager Name

Specify a discount account that is used for calculating volume discounts for multiple accounts.

Note: You can calculate volume discounts for multiple accounts by creating a discount. Discounts and the DISCOUNTACCOUNT ERA are mutually exclusive. This ERA is supported for batch rating only.

Hierarchical discount account ERA

See information about adding a hierarchical discount account promotion in the Customer Center Help.

DISCOUNTACCOUNT

Assign a Quality of Service to a service.

Service-level agreement ERA

See information about adding a service-level agreement promotion in the Customer Center Help.

SERVICELEVEL

Define the home cells for a customer and allow discounts while calling from this area.

Home cell assignment ERA

See information about adding a home cell assignment promotion in the Customer Center Help.

HOME_CELL

Provide cross-product volume discounts, as defined in pipeline discounts.

Note: You can provide cross-product volume discounts by creating a discount. Discounts and the DISCOUNTACCOUNT ERA are mutually exclusive. This ERA is supported for batch rating only.

Pipeline discount model ERA

See information about adding a pipeline discount model promotion in the Customer Center Help.

DISCOUNTMODEL

Provide discounts to calls made to specific numbers or regions, such as all numbers in a country or area code.

Home region code ERA

See information about adding a home region code promotion in the Customer Center Help.

HOME_REGION

Provide discounts to calls made to specific numbers, such as those for friends and family members.

Friends and family ERA

See information about adding a friends and family promotion in the Customer Center Help.

FRIENDS_FAMILY

Use a pipeline rate plan.

Pipeline service-level rate plan ERA

See information about adding a pipeline service-level rate plan promotion in the Customer Center Help.

RATEPLAN