Release Notes for Cisco Billing and Measurements Server Software Release 3.30 and Related Patches

Table Of Contents

Release Notes for Cisco Billing and Measurements Server Software Release 3.30 and Related Patches

Contents

Platform Support

Software Compatibility

New Features

Modifications in Cisco BAMS 3.30

Related Documentation

Installation Notes

Upgrading to Cisco BAMS 3.30

Cisco BAMS 3.30 Patch 308 Information

Caveats Resolved by Cisco BAMS 3.30 Patch 308

CSCta19898

CSCta25143

Cisco BAMS 3.30 Patch 307 Information

Caveats Resolved by Cisco BAMS 3.30 Patch 307

CSCsz31323

Cisco BAMS 3.30 Patch 306 Information

Caveats Resolved by Cisco BAMS 3.30 Patch 306

CSCsw25065

CSCsv06648

Cisco BAMS 3.30 Patch 305 Information

Caveats Resolved by Cisco BAMS 3.30 Patch 305

CSCsr36965

Cisco BAMS 3.30 Patch 304 Information

Caveats Resolved by Cisco BAMS 3.30 Patch 304

CSCsq91400

Cisco BAMS 3.30 Patch 303 Information

Caveats Resolved by Cisco BAMS 3.30 Patch 303

CSCsj95215

CSCsl41843

CSCsj98950

CSCsi11511

CSCsi14942

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Billing and Measurements Server Software Release 3.30 and Related Patches

---

Revised: March 11, 2011, OL-11619-08

Contents

Platform Support

Software Compatibility

New Features

Modifications in Cisco BAMS 3.30

Related Documentation

Installation Notes

Upgrading to Cisco BAMS 3.30

Cisco BAMS 3.30 Patch 308 Information

Cisco BAMS 3.30 Patch 307 Information

Cisco BAMS 3.30 Patch 306 Information

Cisco BAMS 3.30 Patch 305 Information

Cisco BAMS 3.30 Patch 304 Information

Cisco BAMS 3.30 Patch 303 Information

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Obtaining Documentation and Submitting a Service Request

Platform Support

Cisco BAMS Release 3.30 runs on the Sun Solaris 10 operating system. For installation and platform information, refer to Chapter 1, "Introduction to Cisco BAMS," of the Cisco Billing and Measurements Server User Guide.

Cisco BAMS Release 3.30 operates on Sun Netra 210, Sun Netra 240, and Sun Netra T5220 platforms.

Software Compatibility

Cisco BAMS Release 3.30 interoperates with release 9.7(3) and earlier releases of the Cisco Media Gateway Controller software (which runs on the Cisco PGW 2200 Softswitch). To enable all of the features introduced by Cisco BAMS 3.30, the Cisco PGW 2200 Softswitch must be running release 9.7(3) or later.

New Features

BAMS 3.30 supports all of the features and output formats that were supported in prior versions of BAMS. The BAMS 3.30 package supports all of the BAMS 3.20 features and output formats. The following new features and output formats are provided in BAMS 3.30:

•Support for Solaris 10 operating system

•Support for new fields/CDR in MGC Release 9.6 and 9.7

•Support for trunk group measurements such as total seizures on a trunk group during a measured period and total answered calls on a trunk group during a measurement period; answer seizure ration (ASR) value during a measurement period; and peak traffic carried by each trunk group in Erlangs.

•New Measurements reported in the Daily file, based on current and new stored values, requiring new captured data and non-integer measurements

•Support for BAMS software licensing

•New alarms related to license failures

•Support for new QoS output

See the Cisco Billing and Measurements Server User's Guide, Release 3.30, Chapter 11, "Configuring BAMS for QoS Output"

•SFTP File Transfer Support

•Generic Error Handling

•New PGW CDE tags—Table 1 lists new CDE tags introduced in BAMS 3.30.

Table 1 New CDE Tags 

CDE Tag	Tag Name	Minimum Length	Maximum Length
4227	RO/PR Executed	1	1
4228	RO/PR Other Call Ref	8	8
4229	RO/PR Replacement TRK group	2	2
4230	RO/PR Replacement Chan ID	2	2
4231	RO/PR Switchover Timestamp	4	4
4232	Rejecting Location Label	1	20
4233	Rejecting Location Label Direction	1	1
4236	H323 Destination	1	29
4237	Ingress Redirecting Number	1	16
4239	Service Usage Data	2	2
4242	Terminating Remote SIP Host	1	256
4243	Terminating Local SIP Host	1	256
4244	License Reject License Reason	1	20
4245	License Rejecting Direction	1	1
4013	LRN number	1	96
2018	ANSI Egress Calling Number Nature of Address	1	1
2019	ANSI Egress Redirecting Number Nature of Address	1	1
2020	ANSI Egress Original Called Number Nature Of Address	1	1
3018	ITU Egress Calling number Nature of Address	1	1
3019	ITU Egress Redirecting number Nature of Address	1	1
3020	ITU Egress Original Called Number Nature Of Address	1	1

•Changed PGW CDE tags—Table 2 lists CDE tags for which the maximum length is increased.

Table 2 Changed CDE Tags

CDE Tag	Tag Name	Minimum Length	Maximum Length
4215	Charge Tariff Info	8	68
4223	PRI AOC-S Charge Info	6	66
4224	PRI AOC-D Charge Info	10	70
4225	PRI AOC-E Charge Info	10	70
4098	Originating Leg DSP Statistics	280	794
4099	Terminating Leg DSP Statistics	280	794

•New CDE fields for Binary 1110 Output—See the Cisco Billing and Measurements Server User's Guide, Release 3.30, Chapter 10, "1110 Binary Output"

•New CDE fields for Extendable ASCII Output—See the Cisco Billing and Measurements Server User's Guide, Release 3.30, Chapter 7, "Extendable ASCII Output"

•New measurements—See the Cisco Billing and Measurements Server User's Guide, Release 3.30, Chapter 12, "Obtaining Measurements"

•PGW_DYNAMIC_UPDATE flag setting—For BAMS Release 3.30, the PGW_DYNAMIC_UPDATE flag is always set to TRUE. To migrate to BAMS 3.30, BAMS 3.20 configurations in which the PGW_DYNAMIC_UPDATE flag is set to FALSE will be changed so that the field is set to TRUE. BAMS 3.30 does not support the utility for changing the PGW_DYNAMIC_UPDATE flag setting.

•New NODEPARMS table parameter—BAMS Release 3.30 adds the parameter "qosoutput" to support the new QoS output.

•New POLL table parameter—BAMS Release 3.30 adds the parameter "protocol" for specifying the protocol (FTP or SFTP) for transferring files between the Cisco PGW and Cisco BAMS.

Modifications in Cisco BAMS 3.30

The Cisco Billing and Measurements Server (BAMS), for Release 3.30 software is modified to provide the following:

•Support for all the feeds and capabilities that are available in BAMS 3.20 release.

•Support for any new fields/CDRs that are supported in the Cisco Media Gateway Controller software, Releases 9.6(1) and 9.7(3), which runs on the Cisco PGW 2200.

•Support for any fields/CDRs that were changed after the release of Cisco BAMS 3.20.

•Support for the following Trunk Group measurements. Traps must be supported that notify when a configured threshold is crossed.

–Total seizures on a trunk group during a measured period—BAMS counts the call attempts (seizures) on a trunk group (IAM/SETUP in TAG 4003), over a defined period of time. The measured period must be configurable (1 hour is the default duration).

–Total answered calls on a trunk group during a measurement period—BAMS counts the receipt of ANM/ANSWER messages (TAG 4005) on a trunk group, over a defined period of time. The measured period must be configurable (1 hour is the default duration).

–Answer Seizure Ration (ASR) value during a measurement period—Information is derived using the measurements in A and B above (B ÷ A). The measured period must be configurable (1 hour is the default duration). The measurement threshold on ASR is crossed when the value drops below a specified value.

–Peak Traffic carried by each trunk group in Erlangs—A measurement is required for each trunk group to determine the Busy Hour (calls that reach the answer state) during a 24-hour period.

Related Documentation

Cisco Billing and Measurements Server User's Guide, Release 3.30

Installation Notes

Refer to the Cisco Billing and Measurements Server User's Guide, Release 3.30 for installation information.

---

Note The filename for the BAMS 3.30 is CSCOcaBAM.pkg.

---

Upgrading to Cisco BAMS 3.30

Refer to Appendix B: "Upgrading to BAMS Release 3.30," in the Cisco Billing and Measurements Server User's Guide, Release 3.30 for complete upgrade information

Cisco BAMS 3.30 Patch 308 Information

This section includes information about caveats resolved by Cisco BAMS 3.30 Patch 308.

Caveats Resolved by Cisco BAMS 3.30 Patch 308

CSCta19898

Version	Severity	Description
3.30	3	Cisco BAMS truncated long nodenames after the 18th character.

Conditions and Symptoms: Cisco BAMS accepts a 30-character string hostname but BAMS truncated the hostname at 18 characters and then did not display the system prompt.

Resolution: The MML program is modified to correctly support and display node names up to 40 characters long. If you attempt to set a nodename longer than 40 characters, Cisco BAMS will issue an error message when you attempt to deploy the nodename:

/* Unable to set node name: size of value is out of range */

   DENY

CSCta25143

Version	Severity	Description
3.30	3	Cisco BAMS must send the redirecting number to NICS output.

Conditions and Symptoms: Prior to this patch, Cisco BAMS did not populate NICS output with the redirecting number.

Resolution: When Cisco BAMS detects that the redirecting number is present, NICs field #10 reads tag 3017 (Redirecting Number NOA) instead of Tag 3003. Also, NICs field #19 reads tag 4060 (Redirecting Number) instead of Tag 4084 or Tag 4010 as it did prior to this patch.

When Cisco BAMS does not detect the redirecting number, BAMS operates as it did before the introduction of this patch.

Cisco BAMS 3.30 Patch 307 Information

This section includes information about caveats resolved by Cisco BAMS 3.30 Patch 307.

Caveats Resolved by Cisco BAMS 3.30 Patch 307

CSCsz31323

Version	Severity	Description
3.30	2	A Cisco BAMS system experienced a core failure in response to the entry of an extremely long MML command.

Conditions and Symptoms: When a user issued a very long MML command, the Cisco BAMS 3.30 system encountered a core failure.

Resolution: The MML program buffer is increased to handle 5000 characters and 300 parameters in a single command.

Cisco BAMS 3.30 Patch 306 Information

This section includes information about caveats resolved by Cisco BAMS 3.30 Patch 306.

Caveats Resolved by Cisco BAMS 3.30 Patch 306

CSCsw25065

Version	Severity	Description
3.30	3	The Cisco CMNM application could not receive SNMP traps from Cisco BAMS 3.30 running on a Sun Netra T2000 platform.

Conditions and Symptoms: Traps obtained from Cisco BAMS 3.30 running on a Sun Netra T2000 could not be displayed in the CMNM.

Resolution: The SNMP Agent has been updated to support e1000g network interfaces. Now traps can be sent successfully to CMNM.

CSCsv06648

Version	Severity	Description
3.30	3	Support BAMS 3.30 on a Sun Netra T2000 platform.

Conditions and Symptoms: Certify that Cisco BAMS 3.30 Patch 306 operates on a Sun Netra T2000 platform.

Resolution: BAMS 3.30 Patch 306 operates on a Sun Netra T2000 platform.

Cisco BAMS 3.30 Patch 305 Information

This section includes information about caveats resolved by Cisco BAMS 3.30 Patch 305.

Caveats Resolved by Cisco BAMS 3.30 Patch 305

CSCsr36965

Version	Severity	Description
3.30	3	The MSCmain process restarted and generated a core dump.

Conditions and Symptoms: In rare, unknown circumstances, the MSCmain process restarted in a cycle, creating core dumps under /opt/CiscoBAMS/bin.

Resolution: The BAMS software is modified to eliminate this problem.

Cisco BAMS 3.30 Patch 304 Information

This section includes information about caveats resolved by Cisco BAMS 3.30 Patch 304.

Caveats Resolved by Cisco BAMS 3.30 Patch 304

CSCsq91400

Version	Severity	Description
3.30	3	The size of a buffer size was insufficient to support a CDR with a very tag.

Conditions and Symptoms: The initial buffer size that supported the FMT process was not large enough to support some CDRs.

Resolution: The buffer size is increased to eliminate this problem.

Cisco BAMS 3.30 Patch 303 Information

This section includes information about caveats resolved by Cisco BAMS 3.30 Patch 303.

Caveats Resolved by Cisco BAMS 3.30 Patch 303

The following anomalies identified in the operation of the Cisco BAMS are resolved by BAMS 3.30 Patch 303:

CSCsj95215

Version	Severity	Description
3.30	1	The Cisco BAMS failed and generated a critical COR alarm.

Conditions and Symptoms: When the BAMS 3.30 software was installed without the most recent patch, the software experienced a COR failure.

Resolution: The Cisco BAMS software is modified to eliminate this problem. When you install the base Cisco BAMS 3.30 build, you must also install the most recent patch of the software.

CSCsl41843

Version	Severity	Description
3.30	3	BAMS did not poll CDRs via the second PGW interface.

Conditions and Symptoms: With a primary and secondary interface configured on the PGW 2200, BAMS polled CRDs from the primary interface but failed to poll CDRs from the secondary interface if the primary interface became inactive.

Resolution: The BAMS software is modified to poll CDRs from the secondary interface.

CSCsj98950

Version	Severity	Description
3.30	2	BAMS measurements were not generated following the installation of a patch, which was intended to enhance performance.

Conditions and Symptoms: BAMS failed to generate measurements after a patch to improve performance was installed.

Resolution: The BAMS software is modified to generate measurements properly with the introduction of performance improvements.

CSCsi11511

Version	Severity	Description
3.30	3	BAMS performance was not capable of supporting 100 calls per second (cps) when connected to two PGW 2200 nodes running on SunFire V210 platforms in redundant mode.

Conditions and Symptoms: The BAMS could not support traffic of 100 calls per second when connected to two PGW 2200 nodes running on SunFire V210 platforms operating in redundant mode.

Resolution: The BAMS software is modified to support traffic of 100 CPS when connected to two PGW 2200 nodes running on SunFire V210 platforms.

CSCsi14942

Version	Severity	Description
3.30	3	BAMS was not capable of supporting 100 cps when connected to four PGW 2200 nodes running on N240 platforms.

Conditions and Symptoms: The BAMS could not support traffic of 100 CPS when connected to
four PGW 2200 nodes running on N240 platforms.

Resolution: The BAMS software is modified to support traffic of 100 CPS when connected to four PGW 2200 nodes running on N240 platforms.

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/cisco/web/psa/default.html?mode=prod

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/web/siteassets/locator/index.html

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/en/US/docs/general/Illus_process/PDI/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical 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-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support 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, 365 days a year at this URL:

http://www.cisco.com/cisco/web/support/index.html

Access to all tools on the Cisco Technical Support 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

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 automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://tools.cisco.com/ServiceRequestTool/create/launch.do

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 TAC 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 2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/en/US/support/tsd_contact_technical_support.html

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.

•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/pcgi-bin/marketplace/welcome.pl

•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/index.html

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com/index.asp

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/web/about/ac123/ac114/about_cisco_packet_magazine.html

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/web/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

•World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/web/learning/index.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

---

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)

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

© 2011 Cisco Systems, Inc. All rights reserved.