Billing Enhancement for Business Digital Voice Subscribers

Table Of Contents

Cisco BTS 10200 Softswitch Billing Enhancement for Business Digital Voice Subscriber Feature, Release 7.0

Contents

Feature Overview

Prerequisites for the Feature

Restrictions for the Feature

How to Provision the Feature

Managing the Feature

Billing Information

Feature Interaction

Additional References

Related Documents

Cisco BTS 10200 Softswitch Billing Enhancement for Business Digital Voice Subscriber Feature, Release 7.0

---

Revised on: July 12, 2010

The Cisco BTS 10200 Softswitch Billing Enhancement for Business Digital Voice Subscriber feature allows the service provider to identify whether a call is generated from a business subscriber or a residential subscriber.

Contents

•Feature Overview

•How to Provision the Feature

•Managing the Feature

•Additional References

Feature Overview

Business digital voice subscribers are billed at a rate that is different from that of residential subscribers. Currently, service providers are unable to determine from billing record whether a call should be billed as a residential call or a business call.

The Cisco BTS 10200 Softswitch Billing Enhancement for Business Digital Voice Subscriber feature enables the service providers to identify whether a call is made from a business subscriber or a residential subscriber.

Prerequisites for the Feature

Internal Components and Functions

•The Call Agent and the Feature Server are provisioned.

•The MGW, terminations, and dial plans are provisioned.

External Components

External network elements that connect subscribers to the Cisco BTS 10200, such as Media Gateways (MGW) and SIP proxies, are installed and operating.

Restrictions for the Feature

When calls are forwarded, the contents of the originating_sub_type field of the forwarded call might not be sufficient to determine whether the call originated from a business subscriber. Therefore, both sub_type and the charge_number are required to determine whether the originator was a business subscriber. See the Billing Information and Feature Interaction for more details on the originating_sub_type field and for feature interaction with forwarded calls.

How to Provision the Feature

This section explains how to provision the Billing Enhancement for Business Digital Voice Subscriber feature. Perform these tasks in the sequence shown in this section.

---

Note Ensure that you have added MGW, terminations, and dial-plan before adding subscriber-profile and subscribers. Refer to the Provisioning Guide, Release 6.0.x for more information about adding subscribers.

---

---

Note The commands shown in this section are examples; you should provision value that are appropriate for your network and service offerings. CLI syntax allows you to enter commands in uppercase or lowercase. It also allows you to enter hyphens (-) or underscores (_) interchangeably in most cases (exceptions, if any, are noted in the procedures).

A complete list of tokens for each CLI table, as well as the allowed values, default values, and detailed descriptions for each token, is provided in the Cisco BTS 10200 Softswitch CLI database.

---

SUMMARY STEPS

1. add subscriber-profile

2. add subscriber

DETAILED STEPS

	Command	Purpose
Step 1	add subscriber-profile id=subpf1; dial-plan-id=dp1; pop-id=1;	Adding subscriber profiles. The Subscriber Profile (subscriber-profile) table groups shared subscriber properties. Because CAs have several points of presence (POPs), and POPs are a subscriber profile token, you must create POP-specific subscriber profiles.
Step 2	add subscriber id=sub1; category=individual; name=Richardson1; term-id=aaln/S1/3/; mgw-id=c2421.192; dn1=4692551231; sub-profile-id=subpf1; SUB_TYPE=BUSINESS	Adding subscribers. The Subscriber (subscriber) table defines subscribers and subscriber groups on a CA. Set the sub_type token to BUSINESS. Default value of this token is RESIDENTIAL.

Managing the Feature

This section provides information that helps you manage the Billing Enhancement for Business Digital Voice Subscriber feature, including

•Billing Information

•Feature Interaction

Billing Information

Two fields in billing record has been added, namely originating_sub_type and terminating_sub_type. The following table provides information about the fields:

Table 1 Call Detail Block Fields

Field Number	Common Name	Field Type	Field Size	Potential Values	Data Source	Field Description
266	Originating Subscriber Type	NUMERIC		0 - Residential 1- Business	Subscriber:: SUB_TYPE	Identifies type of originating subscriber and is used in conjunction with Business Digital Voice subscribers. This will be used to keep the business CDR's separate from residential services. In the case of forwarded calls, the contents of the originating_sub_type of the forwarded call CDR might not be sufficient to determine if the call originated from a business subscriber. Therefore, both sub_type and the billing_charge_number need to be used to determine if the originator was a business subscriber.
267	Terminating Subscriber Type	NUMERIC		0=Residential 1=Business	Subscriber:: SUB_TYPE	Identifies type of terminating subscriber and is used in conjunction with Business Digital Voice subscribers. This will be used to keep the business CDR's separate from residential services.

•The originating_sub_type is derived from the SUB_TYPE field in the subscriber table for the calling party. The terminating_sub_type is derived from the SUB_TYPE field in the subscriber table for the called party.

•If the originating_sub_type field in the CDR is 1, then the report billing_record command displays, ORIGSUBTYPE=BUSINESS. Similarly, if the terminating_sub_type field in the CDR is 1, then report billing_record displays TERMSUBTYPE=BUSINESS.

Feature Interaction

The following feature interactions can have a significant impact on the Billing Enhancement for Business Digital Voice Subscriber feature:

Table 2 Feature Interaction with Call Forwarding Feature

Feature Name

Description

When Call Forwarding feature is active for a subscriber

In case of forwarded calls, contents of the originating_sub_type field of the forwarded call might not be sufficient to determine whether the call originated from a business subscriber. Therefore, both sub_type and the charge_number fields are required to determine whether the originator was a business subscriber. For example, subscriber A and C are residential subscribers, and B is a business subscriber. A calls B, and B forwards the call to C. In this scenario, two billing records are generated with the following subscriber type: CDR 1: Originating_Subscriber_Type: residential subscriber Terminating_Subscriber_Type: business subscriber CDR 2: Originating_Subscriber_Type: business subscriber Terminating_Subscriber_Type: residential subscriber In this example, if CDR 2 is used for billing, the originating_subscriber_type indicates that the call is a business call, when in fact, the call originated from a residential customer. The charge number field (indicates the directory number of the billable party) in CDR needs to be used along with the originating_subscriber_type to determine whether the call originated from a business subscriber.

Additional References

Related Documents

Related Topic	Document Title
Call Forwarding Feature	Cisco BTS 10200 Softswitch Network and Subscriber Feature Descriptions Guide
Call Detail Block Fields and Call Detail Records	Cisco BTS 10200 Softswitch Billing Guide
Reference listing of all CLI tables and tokens	Cisco BTS 10200 Softswitch CLI Database

---

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2010 Cisco Systems, Inc. All rights reserved.

---