pln-(i)cvm11-ossv1_01.16

Carrier Voice over IP

Nortel OSS Overview Vol. 1Customer-impacting features

PLN-(I)CVM11-OSSv1

Carrier Voice over IP

Nortel OSS OverviewCustomer-impacting features

Document number: PLN-(I)CVM11-OSSv1Product release: (I)CVM11Document version: Standard 01.16Date: December 2009

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 2009 Nortel Networks, All Rights Reserved

Printed in the United States of America/Canada

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.

* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

Table of Contents 1

Carrier Voice over IPNortel OSS Overview Customer-impacting features

PLN-(I)CVM11-OSSv1 Standard 01.16(I)CVM11 December 2009

Nortel Confidential Copyright © 2009 Nortel Networks

Publication history 3

About this document 7Organization of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Version history (of the source documents) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8IP and ATM Features Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Reference documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

(I)CVM11 Feature Overview 15A00014116, MG4K Automatic Trunk Deload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17A00014277, SIP PBX capacity / scaling development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18A00014278, SIP PBX blind protocol tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20A00014279, SIP PBX Interface Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21A00015652, Inter-Carrier SIP Trunking: Support for Border Control Point Insertion . . . . . . 22A00015719, H.323 Billing Mediation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23A00016277, Flexible endpoints for small line GW and Endpoint utilization improvement 24A00016298, STORM Robustness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25A00016419, SIP Line: GWC line capacity improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26A00016421, AS2K Provisioning and SOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27A00016506, SESM Robustness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28A00016582, CS2K SIP PBX Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29A00016591, PacketCable 1.5 MTA NCS Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31A00016592, CS2K SIP Enabled VoIP VPN - LTID Decoupling . . . . . . . . . . . . . . . . . . . . . . . 32A00016594, CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools . . . . 35A00016595, CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38A00016770, Intergateway Route Identification Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39A00016771, Japan NTC Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42A00017589, Presentation CLI Support For Japan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43A00018187, Support for Cause-of-no-ID on Japan PRI and SIP line Originations . . . . . . . . 44A00018188, JI-ISUP/J-PRI to ETSI ISUP interworking and CgPN NOA Default Change 45A00018189, Japan Call Control Enhancements and CLI Conditional Removal . . . . . . . . . . 46A00018330, Switch wide GWC status report toolg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47A00018518, Flash Ignore with Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48A00018519, Speed Call Short Capacity Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49A00018520, Line Capacity Enhancement - Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50A00018521, LCMINV & MTAVERT Table Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52A00018527, PNSCRN Table Expansion to 24 million tuples . . . . . . . . . . . . . . . . . . . . . . . . 53A00018529, OM Enhancements for MTX (also applies to CVoIP) . . . . . . . . . . . . . . . . . . . . 54A00018579, CLI Blocking Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55A00018680, INAP FCI Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56A00018715, Session Server Trunks (SST) Additional Operational Measurements (OMs) 57A00018730, ISDN Preconf Notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59A00018754, Automatic Collect Call Blocking (ACCB) for Trunk Groups . . . . . . . . . . . . . . . . 60A00018761, Enhancements to the TTP Outpulse Command . . . . . . . . . . . . . . . . . . . . . . . . 62A00018834, NGSS/SS Trunks CSV PM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63A00018837, SPFS CSV PM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64A00018847, Critical Alarm raised when Phase 1 or Phase 2 negotiation fails . . . . . . . . . . . 65

2 Table of contents



Nortel Confidential Copyright © 2009 Nortel Networks

A00018885, Increase SIP Trunks to 150K per Call Server . . . . . . . . . . . . . . . . . . . . . . . . . . 66A00018886, SSL Geographic Survivability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67A00019321, SPFS PM enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70A00019363, INAP Flexible ACN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72A00019365, PNSCRN ONP Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Q01670586, QCUST command behavior for SIP Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

CVM11 Feature Impacts 77CVM11 operational and functional impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77CVM11 feature SOC activation and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80CVM11 feature HMI impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82CVM11 feature hardware impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84CVM11 feature Network Interface impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84CVM11 feature alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

CVM11 OAM&P Summary 87AMA/billing changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Data schema (DS) changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Log changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Operational measurement (OM) changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Office parameter (OPARM) changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Service Order (SO) changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Human-machine interface (HM) changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Software Optionality Control (SOC) changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

3



Copyright © 2009 Nortel Networks

Publication history 1

December 2009

Standard release 01.16 of this document for (I)CVM11 for CR updates. The following changes are made:

• CR Q02091213 created new TRK193 and TRK194 logs.

• Added feature SPFS PM enhancement, A00019321.

July 2009

Standard release 01.15 for CVM11 for CR updates.

• Added information on new log PP396 in OAM&P Summary and related impact tables.

• Added information on IEMS performance files for MG15000/MDM in OAM&P Summary.

March 2009

Standard release 01.14 for CVM11 for CR updates. Added information on OM groups TRK2NET1 and TRK2NET2 in OAM&P Summary.

February 2009

Standard release 01.13 for CVM11 for CR updates. The following changes are made:

• SPBX801 log information is added.

• CICM657 log information is updated in Appendix F.

January 2009

Standard release 01.12 for CVM11 for CR update: SIP PBX alarms information is added to A00016594.

December 2008

Standard release 01.10 and 01.11 for CVM11 for CR updates. The following changes are made:

• Added A00014277, SIP PBX Capacity / scaling development

4




• Added A000 16592, SIP PBX trunk to LTID decoupling

• Changed feature A00016591, PacketCable MTA NCS Loopback with revised FN.

September 2008

Standard release 01.09 for CVM11. Per CR request, added the following features:

• A00018834, NGSS/SS Trunks CSV PM Integration.

• A00018837, SPFS CSV PM Integration

August 2008

Standard release 01.08 for CVM11. The following changes are made:

• Added A00014116, MG4K Automatic Trunk Deload.

• Added A00019365, PNSCRN ONP Activity.

• Per CR update, added information on office parameter ENABLE_10_DIGIT_XLA_FOR_MWT.

• Identified two “missing” office parameters as not applicable for the CVoIP market/solution.

May 2008

Preliminary release 01.07 for CVM11. The following changes are made:

• Added feature ACTIDs per customer request.

• Added A00016298, STORM Robustness

April 2008

Preliminary release 01.06 for CVM11. CR update for “Line Capacity Enhancement - Phase 2” to add SOC warning information.

March 2008

Preliminary release 01.05 for CVM11. The following features have been deleted since the previous release:

• CS2K SIP Enabled VoIP VPN - LTID Decoupling• LTID Decoupling - Get LTID modifications

February 2008

Preliminary release 01.04 for CVM11. The following features have been added since the previous release:

• AS2K Provisioning and SOC• OM Enhancements for MTX (also applies to CVoIP)

5




• Switch Wide GWC Status Report Tool

The following feature has been removed since the previous release as it is not a part of the CVM11 release.

• HTTP Digest

October 2007

Preliminary release 01.03 for CVM11. This release includes updates to the feature “Session Server Trunks (SST) Additional Operational Measurements (OMs).”

October 2007

Preliminary release 01.02 for CVM11. Changes include the release name change to CVM11, updates to Volume 1, and the first release for Volume 2. The following features have been added to Volume 1 since the previous release:

• Speed Call Short Capacity Enhancement

• Increase SIP Trunks to 150K per Call Server

August 2007

Preliminary release 01.01 of this document for (I)SN11. The document covers ATM solutions, IP solutions, and International features.

Note: Starting in CVM11, this document uses the two-volume format of the Wireless delta doc. Volume 1 contains high-level information on new and changed features for the release, with extensive cross-reference tables that identify the content changes and impacts for planners. Volume 2 contains the complete functional descriptions for the features, organized by functional areas.

6




7




About this document 1

Overview 1This document contains delta information for the current software release of Nortel Networks Carrier Voice over IP for (I)CVM11. Delta information means changes to a single software release in relation to the previous software release. The previous software release, in this case, refers to the (I)SN10 release. Changes include new features, modified features, and or deleted features.

Audience for this document 1The primary objective of this document is to provide the information required by those personnel whose job it is to plan and implement upgrades to their system software. The information in this document may be useful to anyone who wants or needs to know what changes are associated with the new software load as it is implemented on the system.

Note: The purpose of this document is to provide information for planning only. Do not attempt to use the information in this document to perform maintenance or operational tasks. Do not use this document as an installation aid; use the appropriate installation methods or methods of procedure instead.

Organization of this document 1This document is split into two volumes. The first volume provides the high-level information of all new features and includes the following sections:

• Feature overview - an introduction of the new features available for the new (I)CVM11 release.

• Feature impacts - any impacts to existing hardware, software and OAM&P functions.

• OAM&P summary - high-level lists of impacts to operations, administration, maintenance, and performance-related information.

• Additional (I)CVM11 impacts - any impacts made by patch or other non-feature-related information.

8




The second volume contains the more technical information for our users. In volume two, the information has been segregated under common chapters. The information for each feature has been divided into the following “functional” chapters:

• Functional Descriptions

• Planning and Engineering

• Upgrades

• Configuration Management

• Maintenance

• Administration and Security

• Fault Management

• Performance Management

• Accounting

This information has been mapped to various functions so that someone who is interested in planning and engineering only has to look in one chapter for information on all applicable features rather than find all the planning and engineering information spread throughout the entire book.

Version history (of the source documents) 1The following table lists the version number of the Functional Descriptions (FNs) used to create this version of the NTP

Table 1-1 FD Version History

Feature FN version used in this NTP version

MG4K Automatic Trunk Deload AA23

SIP PBX capacity / scaling development AB08

SIP PBX blind protocol tunneling AB08

SIP PBX Interface Services AB03

Inter-Carrier SIP Trunking: Support for Border Control Point Insertion

AA21

H.323 Billing Mediation AA04

Flexible endpoints for small line GW and Endpoint utilization improvement

--

(Sheet 1 of 3)

9




SIP Line: GWC line capacity improvement AA19

AS2K Provisioning and SOC AA26

SESM Robustness --

CS2K SIP PBX Provisioning AA13

PacketCable MTA NCS Loopback AA37

CS2K SIP Enabled VoIP VPN - LTID Decoupling AA25

CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools

AA29

CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component

AA05

LTID Decoupling - Get LTID modifications AA38

Intergateway Route Identification Support AA06

Japan NTC Enhancements AB08

Presentation CLI Support For Japan AA03

Support for Cause-of-no-ID on Japan PRI and SIP line Originations

AA06

JI-ISUP/J-PRI to ETSI ISUP interworking and CgPN NOA Default Change

AA03

Japan Call Control Enhancements and CLI Conditional Removal

AA06

Switch wide GWC status report tool AA11

Flash Ignore with Call Waiting AA07

Speed Call Short Capacity Enhancement AA11

Line Capacity Enhancement - Phase 2 AA08

LCMINV & MTAVERT Table Expansion AA06

PNSCRN Table Expansion to 24 million tuples AA07



(Sheet 2 of 3)

10




IP and ATM Features Lists 1This section consists of two tables: Features for IP solution, and Features for ATM solutions. The first table shows all features in numeric order by ACTID that are applicable to the various VoIP solutions:

• PT-IP

• UA-IP

• IAW

• IAC

OM Enhancements for MTX (also applies to CVoIP) AA06

CLI Blocking Enhancements AA07

INAP FCI Enhancement AA14

Session Server Trunks (SST) Additional Operational Measurements (OMs)

AA08

ISDN Preconf Notify AA04

Automatic Collect Call Blocking (ACCB) for Trunk Groups AA07

Enhancements to the TTP Outpulse Command AA09

Critical Alarm raised when Phase 1 or Phase 2 negotiation fails

--

Increase SIP Trunks to 150K per Call Server --

SSL Geographic Survivability --

INAP Flexible ACN AA08

PNSCRN ONP Activity AA04

QCUST command behavior for SIP Lines --

NGSS/SS Trunks CSV PM Integration 1.01

SPFS CSV PM Integration, A00018837 1.01

SPFS PM enhancement 0.2



(Sheet 3 of 3)

Features for IP solutions 11




• DMS

• MCS

• CHS

• Converged Core

Features for IP solutions

ACTIDHTTP-Digest IP

Sol’n Product

A00014116 MG4K Automatic Trunk Deload PT-IP CS2000

A00014277 SIP PBX capacity / scaling development CHS CS2000, AS5200/SSL

A00014278 SIP PBX blind protocol tunneling CHS CS2000, GWC, WT, AS5200/SSL

A00014279 SIP PBX Interface Services CHS CS2000, GWC, WT, AS5200/SSL

A00015652 Inter-Carrier SIP Trunking: Support for Border Control Point Insertion

CHS CS2M, GWC, CS2000

A00015719 H.323 Billing Mediation CHS CS2000, GWC

A00016277 Flexible endpoints for small line GW and Endpoint utilization improvement

PT-IP CS2M

A00016298 STORM Robustness Intl PT-IP

Intl UA-IP

STORM

A00016419 SIP Line: GWC line capacity improvement CHS, IAC, Intl IAC

CS2000, GWC, CS2M

A00016421 AS2K Provisioning and SOC CHS CS2000

A00016506 SESM Robustness PT-IP CS2M

A00016582 CS2K SIP PBX Provisioning CHS GWC, CS2M, AS5200/SSL

A00016591 PacketCable MTA NCS Loopback IAC CS2000, GWC, WT

A00016592 CS2K SIP Enabled VoIP VPN - LTID Decoupling CHS CS2000, GWC, WT, AS5200/SSL

12 Features for IP solutions




A00016594 CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools

CHS CS2M, GWC, AS5200/SSL

A00016595 CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component

CHS GWC, AS5200/SSL

A00016770 Intergateway Route Identification Support Intl PT-IP CS2000, GWC, WT

A00016771 Japan NTC Enhancements Intl PT-IP WT

A00017589 Presentation CLI Support For Japan Intl PT-IP WT

A00018187 Support for Cause-of-no-ID on Japan PRI and SIP line Originations

Intl PT-IP WT, CS2000

A00018188 JI-ISUP/J-PRI to ETSI ISUP interworking and CgPN NOA Default Change

Intl PT-IP WT

A00018189 Japan Call Control Enhancements and CLI Conditional Removal

Intl PT-IP WT

A00018330 Switch wide GWC status report tool DMS GWC, CS2000

A00018518 Flash Ignore with Call Waiting DMS CS2000, WT

A00018519 Speed Call Short Capacity Enhancement DMS CS2000, WT

A00018520 Line Capacity Enhancement - Phase 2 DMS CS2000

A00018521 LCMINV & MTAVERT Table Expansion DMS CS2000

A00018527 PNSCRN Table Expansion to 24 million tuples DMS WT

A00018529 OM Enhancements for MTX (also applies to CVoIP) DMS GWC, CS2000

A00018579 CLI Blocking Enhancements DMS CS2000, WT

A00018680 INAP FCI Enhancement DMS WT

A00018715 Session Server Trunks (SST) Additional Operational Measurements (OMs)

Intl PT-IP, PT-IP

CS2000, SST

A00018730 ISDN Preconf Notify DMS WT

A00018754 Automatic Collect Call Blocking (ACCB) for Trunk Groups

DMS WT

A00018761 Enhancements to the TTP Outpulse Command DMS CS2000, GC, WT

A00018834 NGSS/SS Trunks CSV PM Integration PT-IP, UA-IP, IAC, IAW

IEMS

A00018837 SPFS CSV PM Integration PT-IP, UA-IP, IAC, IAW

IEMS

ACTIDHTTP-Digest IP

Sol’n Product

Features for ATM solutions 13




Acronyms used

Features for ATM solutionsThis table shows all features in numeric order by ACTID that are applicable to the various VoATM solutions:

• PT-AAL1

• UA-AAL1

A00018847 Critical Alarm raised when Phase 1 or Phase 2 negotiation fails

Intl PT-IP, Intl UA-IP, PT-IP, UA-IP

GC

A00018885 Increase SIP Trunks to 150K per Call Server UA-IP SST

A00018886 SSL Geographic Survivability MCS AS5200/SSL

A00019321 SPFS PM enhancement UA-IP SPFS, CS2000

A00019363 INAP Flexible ACN Intl Hybrid WT

A00019365 PNSCRN ONP Activity DMS CS2000

Q01670586 QCUST command behavior for SIP Lines -- CS2000

Acronym Related Product

AS5200 Application Server 5200

CA Call Agent Card (for Compact CS2000)

CS2M GWC Manager & OSSGate

CS2000 Communication Server 2000

CS2000-c Communication Server 2000-Compact

GWC Gateway Controller

MCS AS5200/SSL

SSL CS 2000 Session Server Lines

SST Session Server Trunks

ACTIDHTTP-Digest IP

Sol’n Product

14 Features for ATM solutions




• PT-AAL2

1Reference documents 1

More detail about the features that are outlined in this document can be found in Nortel OSS Overview: Customer-impacting features Volume 2 (PLN-(I)CVM11-OSSV2).

ACTID Feature TitleATM Sol’n Product

A00014116 MG4K Automatic Trunk Deload PT-AAL1 CS2000

15




(I)CVM11 Feature Overview 1This chapter outlines the new features associated with the (I)CVM11 software release and documents high-level overviews of the following features:

1. A00014116, MG4K Automatic Trunk Deload2. A00014277, SIP PBX Capacity / scaling development

3. A00014278, SIP PBX blind protocol tunneling

4. A00014279, SIP PBX Interface Services

5. A00015652, Inter-Carrier SIP Trunking: Support for Border Control Point Insertion

6. A00015719, H.323 Billing Mediation

7. A00016277, Flexible endpoints for small line GW and Endpoint utilization improvement

8. A00016298, STORM Robustness

9. A00016419, SIP Line: GWC line capacity improvement

10. A00016421, AS2K Provisioning and SOC

11. A00016506, SESM Robustness

12. A00016582, CS2K SIP PBX Provisioning

13. A00016591, PacketCable MTA NCS Loopback

14. A00016592, CS2K SIP Enabled VoIP VPN - LTID Decoupling

15. A00016594, CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools

16. A00016595, CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component

17. A00016770, Intergateway Route Identification Support 18. A00016771, Japan NTC Enhancements

19. A00017589, Presentation CLI Support For Japan

16




20. A00018187, Support for Cause-of-no-ID on Japan PRI and SIP line Originations

21. A00018188, JI-ISUP/J-PRI to ETSI ISUP interworking and CgPN NOA Default Change

22. A00018189, Japan Call Control Enhancements and CLI Conditional Removal

23. A00018330, Switch wide GWC Status Report Tool

24. A00018518, Flash Ignore with Call Waiting

25. A00018519, Speed Call Short Capacity Enhancement26. A00018520, Line Capacity Enhancement - Phase 2

27. A00018521, LCMINV & MTAVERT Table Expansion

28. A00018527, PNSCRN Table Expansion to 24 million tuples

29. A00018529, OM Enhancements for MTX (also applies to CVoIP)

30. A00018579, CLI Blocking Enhancements

31. A00018680, INAP FCI Enhancement

32. A00018715, Session Server Trunks (SST) Additional Operational Measurements(OMs)

33. A00018730, ISDN Preconf Notify

34. A00018754, Automatic Collect Call Blocking (ACCB) for Trunk Groups

35. A00018761, Enhancements to the TTP Outpulse Command

36. A00018834, NGSS/SS Trunks CSV PM Integration

37. A00018837, SPFS CSV PM Integration

38. A00018847, Critical Alarm raised when Phase 1 or Phase 2 negotiation fails

39. A00018885, Increase SIP Trunks to 150K per Call Server

40. A00018886, SSL Geographic Survivability

41. A00019321, SPFS PM enhancement

42. A00019363, INAP Flexible ACN

43. A00019365, PNSCRN ONP Activity

44. Q01670586, QCUST command behavior for SIP Lines

17




A00014116, MG4K Automatic Trunk Deload 1Automatic Trunk Deload (ATD) is a robustness feature which alerts the crafts person as well as interested layers of software of a pending issue when a resource is driven close to or beyond its capability to process call traffic.

Overload indications allow software to take action to reduce call initiation attempts through an overloaded resource to prevent the unwanted effects.

18




A00014277, SIP PBX capacity / scaling development 1Description

The interface between Communication Server 2000 (CS2K) and Private Branch Exchange (PBX) has traditionally been Primary Rate Interface (PRI) or H.323. With the advancement of Voice over Internet (VoIP) and Succession networks, the Session Initiation Protocol (SIP) is becoming a dominant protocol for VoIP.

To migrate the interface between CS2K and PBX to VoIP, a SIP-enabled VoIP virtual private network (VPN) architecture is being proposed to provide SIP-based PBX access to CS2K. The SIP PBX will communicate with CS2K via the Session Server Lines (SS-L). It will allow SIP Lines solution to co-exist with SIP based PBX. Figure 1, "CS2K SIP Enabled VoIP VPN Solution" shows the architecture.

Figure 1 CS2K SIP Enabled VoIP VPN Solution

The salient features of the SIP enabled VoIP VPN architecture are:

19




• It evolves CS2K Primary Rate Interface (PRI) and International Telecommunication Union (ITU) Specification Q signalling (Q.SIG) trunks to SIP Enabled VoIP VPN.

• It leverages and expands on the SIP Lines design and program.• It re-uses the Session Server Lines (SS-L) platform developed for the SIP

Lines program, and the gateway controller (GWC). However it uses the PRI/Q.SIG implementation from the core.

• Supports the both Nortel’s North American (NTNA) and International (INTL) Q.SIG variant used for H.323.

• De-couples LTID from PRI TRKGRP to allow scaling.

This architecture has the following additional advantages for the customers:• It provides simplified enterprise site interconnect and topology

management- traffic engineering simplification and greater efficiency- reduces cost of expensive leased lines- deployment flexibility to add/remove sites or even individuals

• It allows CS2K hosted private dial plan management thereby reducing dial plan complexity for the enterprise, and allowing PBX and Centrex inter-operability

• Centralized Billing for the Enterprise• Investment Protection; CPE re-use and Carrier Support for existing PBX

- inter site MCDN feature transparency- support for SIP-enabled PBX Gateways

• Inter site next-generation PBX feature transparency via SIP thereby allowing enterprise customer access to all the evolving SIP-based multimedia applications being deployed via the Carrier and providing VoIP VPN Services.

• It allows enterprise networks to migrate from PRI and/or H.323 to SIP.

20




A00014278, SIP PBX blind protocol tunneling 1This feature makes use of the SIP PBX messaging to transport the tunnel data across the CS2K. This tunneling capability is supported for the Call Associated Signaling (CAS) and Non-Call Associated Signaling (NCAS) on both NTNA PRI and QSIG. It also involves tunnelling the data across 2 CS2K nodes over ISUP/SIPT trunks.

Purpose and synopsisA SOC is used to enable this Tunneling functionality, with the following SOCID:

• SIP PBX Blind Tunneling, with MCDN data - VPNG0001

Refer to activity A00016582 (CS2K SIP PBX Provisioning) for SOC details.

21




A00014279, SIP PBX Interface Services 1The scope of this activity in CVM11 will be implementing and verifying the Services components for the SIP interface to PBX

Purpose and synopsisThis activity will be providing support to following services in the CVM11 release.

• NCAS Framework for NTNA and QSIG SIP PRI variants for supporting non call associated messages across the SIP PRI interface.

• Support for MWI notification feature with NTNA SIP PRI.

• Presentation and Screening services for NTNA and QSIG variants:

— Calling Number Presentation and Screening

— Called Number Presentation and Restrictions

— Redirection and Original Called Number Presentation

— Connected Number Presentation

— Name Display Services - Calling Party, Called Party, Connected Party, Redirection Party and Original Called Party.

• Support for DUAL CLI service with SIP PBX interface for International market (QSIG). The existing support for Dual CLI allows the assignment on the terminating QSIG PRI on the CS2000 Core in Table LTDATA. The same provisioning will be available for the QSIG SIP PRI.

• Support for LTID and DN based surveillance ordering and processing for International market (QSIG)

• Support for DMS-100 Core based NTNA and QSIG variant services.

• Support for CORE based service interactions with SIP-PBX interface.

22




A00015652, Inter-Carrier SIP Trunking: Support for Border Control Point Insertion 1

This SN11 activity improves the control of the BCP usage for the interdomain SIP trunks. Prior to SN11, it was only possible to define SIP trunks as either intra_domain or inter_domain.

Purpose and synopsisThis activity, while obsoleting intra_domain and inter_domain attributes of the SIP trunks, introduces the following new attributes:

• Location

• NATid

• ForceBCP

• BCPList Location, NATid, ForceBCP and BCPGroupId will be datafilled in the TRKOPTS DPT tuple, both for NGSS and VRDN SIP trunks.

Location attribute of the SIP trunks will have the following possible values:

• Intradomain

• Private

• Public

• NATted

• Unknown Total of 20 BCP ids will be datafillable for a SIP trunk.

With the introduction of these new attributes, BCPs for the SIP trunk calls will be inserted according to the established BCP insertion rules.

23




A00015719, H.323 Billing Mediation 1This feature provides end-to-end billing capabilities for an H.323-based carrier-carrier interconnect network by extending the existing QoS reporting framework within CS2K.

Purpose and synopsisThis activity extends the QoS support to H323 GWCs by enhancing three areas:

• Modify QoS interface from H.323 protocol driver, which will be used by H.323 application to report the H323 parameters namely - H323 CallID and H323 ConferenceID parameters to CB by unsolicited QoS messages through callback.

• Implement the Qos data collect functionality in H.323 application and fill these parameters in the QoS data structure

• Implement SOC (Software Optionality Control) functionality in core to enable/disable the feature for specified customers.

24




A00016277, Flexible endpoints for small line GW and Endpoint utilization improvement 1

This feature is to let customers have the ability to specify the name of a small line during line provisioning.

Purpose and synopsisCustomers can define the endpoint name in NEW/EST/ADD commands through ServOrd+. Once commands are issued, provisioning changes are made through the GWCEM GUI.

This feature also lets customers have the ability to configure what percentage of LENs under one LGRP to be reserved for unused ports of small line gateways so that a compromise can be reached between the functionality of small line gateway capacity changing and the utilization rate of LGRP. This capability is available through the SESM configure tool.

25




A00016298, STORM Robustness 1

The purpose of this activity is enhancing robustness and alarm capabilities of the STORM server.• The STORM-IA component is enhanced to include detection of Ethernet

link failures and alarm them.

• STORM-IA is enhanced to output logs with the required IEMS field data.

• STM302 alarm is raised when power fails.

Refer to the Fault Management section of this feature for details.

26




A00016419, SIP Line: GWC line capacity improvement 1This activity doubles the SIP lines capacity of a Lines GWC. This increased capacity configuration is referred to as “double density” configurations as opposed to “single density” configurations previously available.

Purpose and synopsisThis increased capacity will reduce GWC ownership in provisioning, management and maintenance due to the fact that fewer GWCs will be required.

To allow the customers to provision and activate this new larger capacity, changes in the following components are required:• CS2000 Management Tool--Two new GWC high density SIP profiles are

created to support NA and INTL market respectively. The new profiles are required to provision the double density GWC which will support 27,621 endpoints. The new profiles are added in the Add Gateway Controller GUI to support support 27k SS-Ls; one for North American market and one for International.

• XA-Core-- introduces a new USAGE based SOC option, CS2B0013, on the Core. This SOC option will assist in controlling the number of existing GWCs which can be extended to the double density GWC capability. The capability being extended is the additional (doubling) of the GWC capacity. The SOC allows a per switch limit on the number of GWC, which can be extended to this double density capability, to be defined in the CS2000 complex when the feature is purchased.

27




A00016421, AS2K Provisioning and SOC 1This feature, A00016421 - AS2K Provisioning and SOC, introduces a new SERVORD option AGeNT ProtoCoL (AGNTPCL), to provide the provisioning functionality for ISC SIP Lines. This new option also distinguishes between IETF SIP Lines and ISC SIP Lines on the AS2000 Core by means of PROTOCOL and VARIANT fields provided by this feature. This feature also introduces a new usage SOC AS2K0002 on AS2000 (similar to the existing CS2C0005 - Number of SIP Client) to track and limit the number of ISC SIP Lines that can be provisioned on the AS2000.

This feature also provides a new trunk option to provision IMS Service Control (ISC) compliant trunk groups (i.e the network side interface for the AS2000). The ISC network interface is similar to SIP-T DPT provisioning. The Session Server for Trunks (SST) platform is used for the provisioning of ISC network interface. An ISC Trunk is provisioned with the existing trunk option DPT, but with the new DPT Protocol type, ISC, introduced by this feature.

28




A00016506, SESM Robustness 1This feature is to increase SESM robustness and optimize software processes to support a line sizes for 180,000 IAD and cable lines.

Purpose and synopsisChanges are made to the Line Audit GUI and the Batch Provisioning Tool (BPT).

The Line audit component checks data integrity of Line-specific data shared between the XA-Core and the GWCEM in the SESM database. In this feature, the XA-Core table download commands and comparison algorithm between XA-CORE and GWCEM data are updated.

The Line Audit GUI is also changed. To make the audit functionality more clear to customers, “Select All” is changed to “Integrity Audit”. Customers can choose whether the DN data will be audited or not.

The Batch Provisioning Tool (BPT) is a command line user interface. It uses OSSGate as the backend to perform all batch operations. In this feature, BPT will support Gateway and Carrier XML provisioning. For the gateway provisioning, only bulk small line and trunk gateway and carrier’s association, disassociation and change behaviour are supported.

29




A00016582, CS2K SIP PBX Provisioning 1This feature delivers the ability to provision the CS2K (Call Server 2000) SIP (Session Initiation Protocol) Enabled Carrier Hosted VoIP (Voice over Internet Protocol) VPN (Virtual Private Network) product.

Purpose and synopsisThis feature delivers the ability to commission and provision the CS2K SIP Enabled Carrier Hosted VoIP VPN product on the CS2K Core, GWC (Gateway Controller) and Session Server. You commission and provision the “SIP PBX interface” on the CS2K Session Server and the PRI “pipe” on the CS2K Core and GWC.

The provisioning interfaces on the CMT (CS2K Management Tools) server and the CS2K Core are used to configure a PRI trunk group on the Core and GWC. The OSSGate XML interface of the CMT server is also expanded to configure and provision SIP PBX node and related data on Session Server. The configuration and provisioning interfaces of the CS2K Session Server have been expanded to configure and provision SIP PBX interfaces.

The new CMT gateway profile VoIP VPN can be selected via the CMT GUI. The existing “Associate Gateway” dialog box is launched to select the VoIP VPN gateway profile. The ISA selector in the routing tables is enhanced to include a new private ISA TON value. The refinement for the ISA selector is going to be the same as refinement of PVT ISA calltype.

This activity implements a Dual - State and Usage Controlled - SOC feature to enable the SIP Enabled VoIP VPN product on the CS2K. The new SOC option CS2B SIP PBX enables the provisioning of the PRI_IP_PROT option with the SIP protocol of table LTDATA. The new SOC option also controls the number of trunk members that can be provisioned with the PRI_IP_PROT option with the SIP protocol.

This activity implements a State SOC feature for basic “blind tunneling” for the SIP Enabled VoIP VPN product. The SIP PBX Blind Tunneling SOC capability includes the Nortel proprietary protocol MCDN (Meridian Customer Defined Networking).

GUI clients are used to commission the required nodes on the CS2K to enable the SIP PBX interface on the Session Server. The nodes that are required to be added to the CS2K components to support the SIP VPN service include: VoIP VPN enabled GWCs, VoIP VPN VMGs (Virtual Media Gateways) and SIP PBXs.

TRKMEM update for SIP PBXWith this activity, there is support for up to 2046 B-Channels for both North American and International markets. For this purpose TRKGRSIZ in table

30




CLLI is increased to 2046. To allow more than 671 B-Channels, the limit for GWC type node is changed to 2046 for SIP PBX only.

CMT GUIThe “Add Gateway Controller”, “Associate Media Gateway” and “Add Carrier” operations display and configure GWCs, VMGs and virtual carriers by using the configuration menu from the main CMT (CS2K Management Tools) GUI. The “Associate Media Gateway” operation can also be selected by the “Associate” button from the Gateway panel of a GWC.The “GWC Profile” and “Gateway Profile” fields of the dialog boxes have been updated to include the new VoIP VPN capability and gateway profile. The “Add Carrier” dialog has been updated with the VoIP VPN carrier type.

Table 1 Modified CMT GUI

Operation Name NEW, CHANGED, or DELETED

Add Media Gateway Controller Changed by adding the VoIP VPN capability to the existing gateway controller profiles LINE_TRUNK_AUD _NA, LINE_TRUNK_AUD_INTL.

Changed by adding optional “Flow through” checkbox to dialog box.

Delete Media Gateway Controller

Changed by adding optional “Flow through” checkbox to dialog box.

Associate Media Gateway Changed by adding gateway profile VoIP VPN.

Add Carrier Changed by adding VoIP VPN carrier type.

31




A00016591, PacketCable 1.5 MTA NCS Loopback 1

Purpose and synopsisThe CS 2000 MTA NCS Network Loopback feature, in conjunction with third party test equipment, instructs a PacketCable-compliant NCS MTA to loop-back the speech path for the purpose of creating a test call. This helps MSO technicians determine whether customer trouble reports are network-related or whether a field technician needs to be dispatched. Loopback connection modes help assess if an NCS MTA is functioning properly prior to dispatching personnel to the customer premise, reducing the MSO’s customer support costs. Loop back testing can be used for both reactive and proactive voice quality testing.

The PacketCable-defined NCS protocol supports MTA loop-backs via two connection modes NETWLOOP and NETWTEST.

NETWLOOP - network loop-back mode. In this mode, the signals received from the connection are echoed back by the MTA on the same connection. The network loop-back mode operates as a simple RTP packet reflector.

NETWTEST - network continuity test mode. This mode is used for continuity checking across the IP network. An audio signal is encoded by a test device originator and sent over the IP network to the NCS endpoint under test. The endpoint must echo the signal back over the IP network after passing it through the MTA’s internal equipment to verify proper operation. The signal must go through internal decoding from Packet to Analog voice and re-encoding back to Packetized voice prior to being sent back towards the test originator. PacketCable’s NCS specification dictates that the analogue signal must not be passed on to a telephone connected to the analog access line, regardless of the current hook-state of that handset, i.e., on-hook or off hook.

Test calls are originated by non-Nortel provided third party external test equipment. That external test equipment must appear to the CS 2000 as a (PacketCable-compliant) NCS gateway, supporting up to 64 (PacketCable-compliant) NCS lines, called “test head originators”. The external test equipment is responsible for all test monitoring, result capture and analysis.

32




A00016592, CS2K SIP Enabled VoIP VPN - LTID Decoupling 1Description

Introduction

SIP PBX is a CS2K SIP Enabled Carrier Hosted VoIP VPN product.

The interface between Communication Server 2000 (CS2K) and Private Branch Exchange (PBX) is traditionally Primary Rate Interface (PRI). With advancement of Voice over Internet (VoIP) and succession networks, the Session Initiation Protocol (SIP) is becoming dominant protocol for the VoIP.

To migrate the interface between CS2K and PBX to VoIP, a SIP enabled VoIP VPN architecture is being proposed to provide SIP based PBX access to CS2K. The SIP based PBXs will communicate with CS2K via the Session Server. It will allow SIP Lines solution to co-exist with SIP based PBXs. The following are the benefits for the carrier and the enterprise customers• It provides simplified enterprise site interconnect and topology

management - traffic engineering simplification and greater efficiency - reduces cost of expensive leased lines - deployment flexibility to add/remove sites or even individuals.

• Allows service providers to offer a value-added set of new hosted services.• Maximizes market potential for new service offerings by enabling call

Management, Video etc. to the existing customers.• Provides a wide range of telephony and multimedia applications

irrespective of workplace location, office, home etc.• Provides a radian for convergence by merging new and traditional media

on a unified interface.

The CS2K SIP enabled VoIP VPN is an evolution from wireline VPN access solution PRI/QSIG. This gives a good feature transparency with existing PRI/QSIG functionality.

Figure 1, “Nortel’s SIP Enabled Carrier Hosted VoIP VPN Solution,” on page 33 provides a high level view of Nortel’s SIP Enabled Carrier Hosted VoIP VPN Solution.

33




Figure 1 Nortel’s SIP Enabled Carrier Hosted VoIP VPN Solution

The primary goal of “LTID Decoupling Phase -2” feature is to remove one-to-one relationship between the LTID and the trunk group for supporting SIP PBX. In doing so other challenges related to translation and routing is addressed. The following consideration is necessary to achieve the scaling desires

— Need to allow all the SIP PBXs for a single enterprise into a same single trunk group.

— If SIP PBX within an enterprise wish to receive differentiated services then additional trunk group will be added.

— Having a number of SIP PBXs for a single enterprise into a same single trunk group reduces the number of CS2K routes.

— Need to support very large VPNs and to the other extreme a support for small VPNs.

— Additionally need to increase the number of routes across CS2K as there is a limitation of only 8000 route list in North American (NA) configuration. International market does not have this problem as there are over 90000 routes already available.

CS2K SIP Enabled VoIP VPN solution

=

IPCore

CS 2000

GK

PBX

GW

PBX

GWSIPPBX

PVG

H.323 SIP

SS

SIP

SIP Enabled VoIP VPNNEW for SN11

PBX

TDM PSTN Network

ISUP

ILEC or IXC

PRI

34




This feature is based on PRI interface and enhances the capability of PRI to support SIP PBX. Currently, each PRI (Primary Rate Interface) trunk group can be assigned only one LTID. There are a maximum of 32,000 LTIDs. This would require up to 32,000 trunk groups. However, the CS2K only supports 4000 trunk groups. To meet this requirement • The LTID must be decoupled - breaking the one-to-one relationship

between a LTID and a PRI trunk group. Allow several LTIDs to subscribe to the same trunk group.

• Additionally there arises a need to allow core translations to route based on LTID.

• Increase the number of route list beyond 8000 for NA market.• Enhance Logs, OMs, Audits and tools• Billing on a Per LTID basis.

35




A00016594, CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools 1

This activity encompasses OAM activities implemented in the CM, GWC, CMT, and Session Server required to provide a comprehensive level of maintainability for the CS2K Hosted SIP Enabled VoIP VPN application. The maintenance of the application is distributed over these platforms to achieve efficiencies of operation realized by having the maintenance capabilities in close proximity (logically) to the resources or data representing the resources being maintained instead of trying to maintain the maintenance state of the far-end PBXs completely through the path of devices up to the CORE.

Purpose and synopsisThe intent of SIP Enabled VoIP VPN OAM features is to:

• Reuse as much as possible the framework created by the PRI maintenance model in the CORE and GWC that is used by Succession Carrier Hosted H323 but with some slight modifications made for efficiency and scale necessitated by the increased size of trunk groups.

• Provide a mechanism for invocation of maintenance capabilities for CORE SIP PBX trunks in the CMT via the TMM CLUI.

• Provide a mechanism for invocation of maintenance actions in the CMT via the TMM CLUI in the Session Server for the SIP PBXs.

Core and GWC SIP PBX Trunk BehaviorFor SIP PBX trunk, the D-channel is tied to a trunk group which maps to a VMG (Virtual Media Gateway) on the Session Server. We treat the trunk group as a large pipe of resources to the Session Server that can go INSV as soon as communication with the Session Server (for that VMG) is established. If the D-channel for the SIP PBX is busied, then call processing service is impacted to potentially many SIP PBXs. Similarly, the BUSYing of B-channels affects the overall call capacity of the SIP PBXs that share the trunk group. But the capacity of B-channels allowed per PBX is controlled in the CORE by a capacity value that is tied to the LTID.

Session Server SIP PBX BehaviorThe Session Server System Management Console maintains three states for each SIP PBX configured there: Adimistrative, Operational and Registration. The Administrative state represents the desired state of the “link” between the Session Server and the SIP PBX. The Operational state of the PBX is relevant only if the PBX is configured to be audited via the AYT audit. The Registration state of the PBX will show REGISTERED or NOT REGISTERED.

36




Console Enhancements A new dialog box within the System Management Console is provided to allow the display and manipulation of the maintenance states of the SIP PBXs.

AuditsThe GWC initiated SIP call processing audit exchanges messages containing SIP callids over the message link between the GWC and Session Server to detect any discrepancy of SIP Enabled VoIP VPN calls between both platforms.

The Session Server’s Are You There (AYT) audit uses the SIP OPTIONS message to detect the loss of communication to the SIP PBX server. The AYT audit is enabled on a per-PBX basis via the SM Management Console.

Session Server initiated call processing audits exist and exchange messages containing SIP callids over the message link between the GWC and Session Server to detect any discrepancy of SIP Enabled VoIP VPN calls between both platforms.

The GWC data, VMG data, LTID data, VMG capacity and LTIDs capacity data exist in CMT, Core and SS-EM. Use “CS2K Data Integrity Audit” to ensure that data are in sync.

GWC is provisioned in CMT with minimal flowthru passing of data to the SS-EM database. Auditing this data ensures that data is in sync between the CMT and SS-EM.

VMG data (vmg name) is provisioned in the GWC via CMT with minimal flowthru passing of data to the SS-EM database or provisioned in the SS-EM database via SS-EM Provisioning Mgr Auditing (in some form) of this data ensures that data is in sync between the GWC and SS-EM.

A Route Audit checks the validity of the SSL's PBX Route datafill. A PBX Route on the SSL is an association between a SIP PBX, a VMG and an LTID.

CMT TMM CLUI Maintenance Of SIP PBXs and Core Trunk GroupsA new component “TMM CLUI” will be introduced in this feature to support SIP PBX. And part of the TMM GUI function also will be introduced into TMM CLUI to provide the machine interfaces to maintain the trunk info of SIP PBX on Core.

The TMM CLUI is only invoked via OSSGate. It includes SIP PBX and SIP PBX trunk maintenance commands. The QSIP command is introduced into TMM CLUI to support querying the SIP PBX info. The TRAVER command is introduced into TMM CLUI for user to run it on CMT side.

37




New logsThis activity introduces 11 new XPKT logs. The existing core TRK, AUDT and TRKT logs do not contain enough information to discern to which SIP PBX the log is associated. These new XPKT logs contain LTID and correlation id, which will help in debugging.

Except XPKT353, each of these new logs is similar and corresponds to an existing TRK, TRKT and AUDT log. They are generated whenever the legacy logs are generated. The log type will match that of the existing log.

This activity also introduces new log SPBX801, generated when the VMG state is changed.

New SIP PBX alarmsThe following new alarms are introduced:

• SPBX101--The "SIP PBX Unreachable" alarm indicates that the AYT audit is failing for a specific SIP PBX. It is a major alarm as CallP will reject calls while the AYT audit is failing.

• SPBX802--The "SIP PBX MANBSY" alarm is a warning-level alarm that reminds the operator that the PBX cannot accept new calls while in MANBSY state.

• SPBX803--The "VMG Provisioning Mismatch" alarm is warning level alarm. It is raised when the GWC and Session Server disagree about their provisioned VMGs.

• SPBX804--The "Missing LTID Capacity Value" alarm is another warning level alarm. It is raised when the Session Server hasn't received a LTID capacity value from the GWC.

Tools enhancementsWith LTID decoupling, each LTID will represent a SIPPBX. The following tools are enhanced on the CS2K Core to include LTID as parameter or output information based on LTID.

• QSIP

• TRAVER

• CALLTRAK

• CALLDUMP

• AMADUMP

• PMIST/XPMIST

• DISPCALL

• LTIDCI

38




A00016595, CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component 1

From the CS2K’s perspective, calls to and from SIP PBX will function in the same manner that calls to and from standard PRI trunks. Additional capabilities are added specifically for SIP PBX.

Purpose and synopsisThe additional capabilities are added specifically for SIP PBX are as follows:

• Support for CDP calls

• SIP PBX Module Code 260

• SIP PBX Module Code 611

Support for CDP callsTo support the private UDP and CDP dial plans, additional datafill is required to explicitly set the private TON value on a route basis on the CS2K Core.The existing ISA selector of the routing tables has been updated to configure the private TON value. This activity adds an optional parameter to the existing ISA selector. The private TON value, Level 0(CDP), Level 1(UDP) and SPECIFIC will be included as an optional field.

Support for private dial plans (CDP/UDP) - NA market onlyTo support the private UDP(Uniform Dial Plan) and CDP(Coordinated Dial Plan) dial plans, additional datafill is required to explicitly set the private TON value on a route basis on the CS2K Core.The existing ISA selector of the routing tables has been updated to configure the private TON value for the North American market only.

Billing Module code changes for SIP PBXSIP PBX AMA billing Module 260 captures originating and terminating agent component and protocol information for packet network agents. The Record_MC260 option in table AMAOPTS shall be used to activate and deactivate Module 260 inclusion for SIP PBX along with SIP lines. If the option is set to ON, module 260 is appended.

This activity appends Module code MC611 to the existing Module code 104 in the AMA record. A new context id 80150 is added to Module code 611 to contain the LTID information. MC611 is appended in AMA record.

39




A00016770, Intergateway Route Identification Support 1This feature supports ‘Intergateway Outgoing Route Identification’ on CS2Kc on ISN11 release.

CS2Kc which acts as international gateway can route the traffic to another international gateway through inter-gateway trunk based on the datafill defined on CS2Kc. It is called ‘overflow’. ‘Intergateway Outgoing Route Identification’ is the information about the situation when overflow happens, including the following:

— Route type that indicates the outgoing route.

— Trunk CLLI number of the outgoing trunk group on the international gateway that directly routes the call out to oversea carrier or toll switch.

— Gateway ID of the international gateway that directly routes the call out to oversea carrier or toll switch.

For any call coming from another international gateway and going out to the oversea carrier or toll switch, the ‘Intergateway Outgoing Route Identification’ should be sent backward to that international gateway with ORI (Outgoing Route Identification) parameter in ACM. The first international gateway where overflow occurs stores the ‘Intergateway Outgoing Route Identification’ that is carried by ACM ORI parameter into AMA record. The following call scenarios are supported by this feature.

• TS -> INT1 -> INT2 ->OC• TS -> INT1 -> INT2 -> INT3 -> OC• OC -> INT1 -> INT2 -> TS• OC -> INT1 -> INT2 -> INT3 -> TS• OC -> INT1 -> INT2 -> OC• OC -> INT1 -> INT2 -> INT3 -> OC• IBN/RES/M5216 Line -> INT1 -> INT2 -> OC• IBN/RES/M5216 Line -> INT1 -> INT2 -> INT3 -> OC• IBN/RES/M5216 Line -> INT1 -> INT2 -> TS• IBN/RES/M5216 Line -> INT1 -> INT2 -> INT3 -> TS

Note: Only CICM line and SIP line are tested for IBN/RES/M5216 line in the IT stage of this feature.

This feature provides the ISUP message support and AMA support after call overflow occurs between international gateway switches. CS2Kc acts as an international gateway.

New ISUP parameter ORI (Outgoing Route Identification) is introduced in ACM message for ETSI ISUP V2 base. The generation, tandem and reception of ORI parameter is supported by this feature.

40




The following interworkings are supported by this feature:• For ORI reception switch

— Taiwan ISUP -> ETSI ISUP V2 base

— Taiwan ISUP -> SIP-T (ETSI ISUP V2 base)

— SIP-T (Taiwan ISUP) -> ETSI ISUP V2 base

— SIP-T (Taiwan ISUP) -> SIP-T (ETSI ISUP V2 base)

— ETSI ISUP V2 base -> ETSI ISUP V2 base

— ETSI ISUP V2 base -> SIP-T (ETSI ISUP V2 base)

— SIP-T (ETSI ISUP V2 base) -> ETSI ISUP V2 base

— SIP-T (ETSI ISUP V2 base) -> SIP-T (ETSI ISUP V2 base)

— SIP trunk -> ETSI ISUP V2 base

— SIP trunk -> SIP-T (ETSI ISUP V2 base)

— IBN/RES/M5216 line -> ETSI ISUP V2 base

— IBN/RES/M5216 line -> SIP-T (ETSI ISUP V2 base)

• For ORI tandem switch.



— SIP-T (ETSI ISUP V2 base) <-> ETSI ISUP V2 base

— SIP-T (ETSI ISUP V2 base) <-> SIP-T (ETSI ISUP V2 base)

• For ORI generation switch.

— ETSI ISUP V2 base -> Taiwan ISUP

— ETSI ISUP V2 base -> SIP-T (Taiwan ISUP)

— SIP-T (ETSI ISUP V2 base) -> Taiwan ISUP

— SIP-T (ETSI ISUP V2 base) -> SIP-T (Taiwan ISUP)



— SIP-T (ETSI ISUP V2 base) -> ETSI ISUP V2 base

SIP-T (ETSI ISUP V2 base) -> SIP-T (ETSI ISUP V2 base) .

New option TWXRI of table ISERVOPT is introduced. There are two fields in this option:• ORI_ACTIVATE: the trigger of whole feature.

• GATEWAY_ID: 0 ~ 255. The gateway ID that is defined for this switch.

41




A new trunk option TOINTLGW in table TRKOPTS is introduced to indicate that the trunk group on this international gateway is connected to another international gateway.

A new option, ORI_Billing, is introduced in table AMAOPTS. This option allows the operator to enable or disable the capturing of ORI in the AMA record.

42




A00016771, Japan NTC Enhancements 1This feature enhances the Notification of Time & Charge (NTC) function to work under the length limit of H.248 message for MS2000, restores the missing linking phrases of the NTC announcement, and enhances the callback function for operation on CS2000/CS2000-Compact with USP signaling. A new CLBK600 log reason is also introduced to indicate a phrase must be datafilled in table ANNAUDID.

Purpose and synopsisJapan NTC enhancements provides the following functionality:• Breaking one audio request into multiple pieces

• MCMP message enhancement for compound phrases

• Support NTC callback on Japan Interconnect ISUP (JI-ISUP)* on CS2000/CS2000-Compact

• New CLBK600 log reason for datafill missing

• Support multiple cycles and multiple languages for MS2000/UAS

• Support SIP-T (JI-ISUP payload) as the incoming trunk of the original callNote: The term ‘JI-ISUP' as used in the document means legacy JI-ISUP, other than SIP-T (JI-ISUP payload).

43




A00017589, Presentation CLI Support For Japan 1In this activity, feature AJ5284 “Presentation CLI Support” is extended to JPRI to JI-ISUP interwoking. Presentation Number is sent in GNP parameter in IAM. Moreover, the default number of JPRI is inserted into Calling Party number parameter (CgPN).

Purpose and synopsisThe purpose of this activity is to support interworking of Generic Number parameter (GNP) for the below three call scenarios:• JPRI to JI-ISUP

• JI-ISUP to JI-ISUP

• JI-ISUP to JPRI

This activity is deployed on ISN11 for CS2Kc systems.

In order to implement the above functionalities, the following parts are required:

• Table LTDATA enhancement

— DEFLTPN and DFLTCGN for JPRI in table LTDATA. DEFLTPN is supported for JPRI in this activity to provide default PN.

— The activity provides SCRNPN option to JPRI in table LTDATA, then DID number can be treated as PN.

• Call processing support for JPRI to JI-ISUP interworking.

• Support PN captured in AMA.

• Keep GNP for JI-ISUP to JI-JISUP

• PN mapping for JI-ISUP to JPRI

44




A00018187, Support for Cause-of-no-ID on Japan PRI and SIP line Originations 1

The Cause-of-no-ID supplementary service complements the CLIP supplementary service by providing the called party with a displayed indication (a reason) that the calling party number is not available for delivery.

Purpose and synopsisIn this feature, the support of Cause-of-no-ID is extended to the following interworkings:

• Japan PRI (INS1500) to Japan Interconnect ISUP (JI-ISUP)

• Japan PRI to SIP-T with encapsulation of JI-ISUP

• SIP line to Japan Interconnect ISUP.

Note: SIP-T(JI-ISUP) is short for JI-ISUP encapsulation in SIP-T.

45




A00018188, JI-ISUP/J-PRI to ETSI ISUP interworking and CgPN NOA Default Change 1

Japan market is implementing CS2000 as a replacement for old international gateways. The decommissioning of the international gateways will allow traffic to be sent directly over ETSI ISUP V1/V2 trunks from CS2000 nodes connected to the domestic network via Japan ISUP and Japan PRI trunk. This interworking is already supported but needs to be enhanced.

This feature is implemented on CS2000 (CS2K) in ISN11.

Purpose and synopsisThe following items are addressed by this feature:

• ANM No Charge Mapping for JI-ISUP/Japan PRI ->ETSI ISUP

• UUI Blocking/Forwarding for ETSI ISUP <-> JI-ISUP

• ACM Charge Indicator & IAA for JI-ISUP -> ETSI ISUP payphone calls

• Carrier Name Notification Fast Answer for JI-ISUP -> ETSI ISUP

• Japan PRI Backward Voice Path Solution for Japan PRI -> ETSI ISUP

• Mapping of CgPN NOA Indicator for ETSI ISUP <-> JI-ISUP and ANSI ISUP -> JI-ISUP interworking

• Mapping of the CPC parameter for JI-ISUP -> ETSI ISUP

46




A00018189, Japan Call Control Enhancements and CLI Conditional Removal 1

This feature extends the screening capabilities of the Call Control & Universal Screening feature and allows for conditional removal of the CLI based on the outcome of a set of screening conditions. This will prevent call spoofing (calls with a fake or dummy Caller ID) on inbound international calls.

Purpose and synopsisTwo functional components are implemented to address compliance with Japan Telecommunications Carriers Association (TCA) recommendations:• Japan Call Control enhancements (FCICI and PI screening)

• CLI conditional removal by table CLICNTL from call control or CLISERV translations according to the outcome of the screening.

Japan Call Control EnhancementsCall control framework is enhanced to support two new screening functions, FCICI (FCI Call Indicator) and PI (Presentation Indicator).

Table CALLCNTL is enhanced to support the new screening option, FCICI. A new table FCICISCR is created to support the screening function. The TRAVER tool is also enhanced to display the data met during the call control translation for the new screening table FCICISCR.

Table CALLCNTL is enhanced to support the new screening option, PI. A new table PISCRN is created to support the screening function. The TRAVER tool is also enhanced to display the data met during the call control translation for the new screening table PISCRN.

CLI Conditional Removal for Call Control and CLI Service TranslationThe CLI removal function is activated by option CLIDELV set as “N” in table CLICNTL entered from table CALLCNTL or from table CLISERV. The CLICNTL index is selected by table CALLCNTL or table CLISERV during translations. If the CLIDELV option specified by the index is datafilled as “N”, the CLI is removed from the outgoing trunk.

47




A00018330, Switch wide GWC status report toolg 1This feature was initially requested by CDMA to improve the time to assess the status of all the GWCs in a PMSC solution when they are responding to a service degradation or outage situation. But feature is designed to be a generic tool, not specific to CDMA.

Purpose and synopsisThis feature introduces two new user interfaces on CORE to make OA&M easy for Gateway Controllers on Packet solution.

GWCSTAT is a new CI level and has sub commands on CORE to give the ability of querying switch wide GWC status information in a clean, easy to read format, and store it into a file if necessary.GWCALL is another new level under MAPCI;MTC; PM, GWC directory. It continuously monitors and displays operational and activity status of GWCs.

48




A00018518, Flash Ignore with Call Waiting 1This activity provides a new interaction of FIG (Flash Ignore) & CWT (Call Waiting) options when both of these options are assigned to the same line.

Purpose and synopsisNormally, CWT and FIG are incompatible with each other. This activity provides compatibility of CWT and FIG line options.

This feature will only work for IBN lines on both TDM and CS2K for International market.

To assign FIG & CWT to an existing line, use the ADO (add option) command in ServOrd.

49




A00018519, Speed Call Short Capacity Enhancement 1

Purpose and SynopsisCurrently, the limit for Speed Call Short (SC1 and SCS) option is 65,520. The CS 2000 supports a capacity of 180,000 lines now and there are plans to increase line capacity to 300,000 (Please refer to A00018520). The purpose of this feature is to implement an architecture that allows expansion of Speed Call Short provisioning up to 300,000 lines. 300,000 lines will be available with the activity A00018520 and before that 180,000 lines will be available with Speed Call Short option. This feature applies to both CS 2000 and CS 2000 - Compact and provides an increase in the limit of the number of CS 2000 lines with Speed Call Short feature.

50




A00018520, Line Capacity Enhancement - Phase 2 1Total line capacity is increased to 300,000 in both the North American and International markets and this feature includes expansion of individual line limits of RES, IBN, V5.2, H.248 and MGCP line types to 300,000. Furthermore, an increase in NCS lines to 300,000, but not NCS gateways when a RMGC GWC is used, is also provided by this activity.

There is no further increase in the TDM line (ENET and ABI-based), MG 9000 or CICM line capacities (Refer to A00018521 which is expanding total TDM and MG 9000 ABI-based lines to 180,000.). VoIP lines behind H.323 gateways and gatekeepers are not included as part of line capacity.

OverviewThis activity only includes Core enhancements for line capacity increase of CS2000 and CS2000 - Compact. The other necessary enhancements to perform line capacity increase apply on:

• SESM/CS2M: Increase SESM robustness and performance and optimize software processes.

• IEMS:

— Memory reclamation to improve performance of IEMS.

— Enhancements to the IEMS overload control algorithm.

— Enhancements to IEMS performance monitoring.

Purpose and synopsisThis feature increases provisioning limits for lines from its current limit to 300,000 total. This activity verifies following items in order to achieve 300,000 line support:

• The total line capacity supported is increased to 300,000.

• The supported capacity of IBN lines is increased to 300,000.

• The supported capacity of RES lines is increased to 300,000. The maximum value for office parameter MAX_RES_LINES (in Table OFCOPT) is increased to 3000 to yield support for capacity increase of RES lines.

• A mix of RES, IBN and POTS lines are allowed provided the individual line limit for any specific type is not exceeded.

• A mix of TDM, MGCP, V5.2, H.248, MG9000, CICM, NCS and SIP lines are allowed provided the individual line limit for any specific type is not exceeded and provided the total of all line types does not exceed total line capacity.

• The supported capacity of MGCP IAD lines is increased to 300,000. (Refer to section 2.5 for RMGC limitations)

51




• With the exception of offices that use a RMGC for NCS and/or MGCP lines, it is possible using small line GWC service profiles, to assign 1-port gateways to every line up to the maximum number of lines supported for the associated line type and protocol (i.e. 300,000 lines with 300,000 gateways). In an office that uses an RMGC, the total number of small line gateways is 180,000 whether they utilize the RMGC or not.

• The supported capacity of V5.2 IBN lines is increased to 300,000.

• The supported capacity of H.248 lines is increased to 300,000.

• The supported capacity of NCS (cable) lines is increased to 300,000. (Refer to section 2.6 for RMGC limitations)

A new controlled usage SOC, CS2N0004, is created to monitor North American non-SIP IBN and RES lines. MG 9000 ABI, SIP and IMS packet lines are excluded from this control. Existing mechanisms are used to allow provisioning of IBN lines to these new limits.

Line provisioning is supported using the OSSGATE (SESM) provisioning interface.

52




A00018521, LCMINV & MTAVERT Table Expansion 1This feature expands tables LCMINV and MTAVERT.

Purpose and synopsisThis feature expands table LCMINV from 256 to 512 tuple and expands the total number of supported TDM lines (MG 9000 ABI-based and/or ENET-based) from 150k to 180k which is required to address additional VoIP office collapse opportunities. In addition to table LCMINV, current MTAVERT table limit is also expanded from 1024 to 2040 within this activity.

53




A00018527, PNSCRN Table Expansion to 24 million tuples 1This feature expands PNSCRN table size up to 24M tuples.

Purpose and synopsisThis feature expands PNSCRN table size up to 24M tuples without changing the customer visible view of the table. The capacity expansion of the table is allowed using a usage-controlled SOC option with hard-limit. The new capacity of the table can be expanded with 4M tuples block (8M +4M +4M +4M +4M) up to 24M tuples as one of 12M - 16M - 20M - 24M upper-bounds.

This feature provides up to 24M tuples via the new XLAS0059 usage-controlled SOC option. The current capacity is allowed to be expanded with 4M tuple increments using the usage-controlled SOC option. The new capacity of the table must be one of 12M - 16M - 20M - 24M. Here there are a few requirements when using this SOC:

• The new usage-controlled SOC option depends on XLAS0006/IXLS0002 (activation of PNRF option presented by AU2848), meaning that this new feature cannot be active unless one of these SOCs is turned on.

• The new SOC is usage-controlled and hard-limited, in increments of 4M tuples block, with default of 0. Usage limit must be set up to only increment by 4 such that 8M +4M, +8M, +12M, +16M up to 24M tuples.

• When changing size of the usage limit, it can only be increased. The usage limit cannot be decreased.

• During ONP; If pre-source patch to expand PNSCRN to 24M tuples (PTA33) is active in active side then max tuple count is set to 24M tuples. If patch is not active then the current tuple count limit is set to 8M tuples.

54




A00018529, OM Enhancements for MTX (also applies to CVoIP) 1This feature provides more accurate tracking of number of calls shed by GWC, during a nodal GWC overload event, through registers PTRMMSG and PORGMSG of XPMOVLD2 OM group.

This feature implements a new OM group, ISUPSOC OM, to keep track of the number of origination attempts shed by the GWC during a core overload event, for ISUP terminals. The registers in this OM group provide the following information.

1. Total number of origination attempts shed by GWC on core overload event.

2. Total number of origination attempts abandoned by user.

During core overload, GWC will not report origination attempts to core immediately. The origination attempts will be queued and then reported later. This causes a delay in applying dial tone to the user and the user may abandon the call attempt.

3. Total number of call originations reported to an overloaded core without being queued, because of queue overflow.

55




A00018579, CLI Blocking Enhancements 1This activity provides CLI (Calling line identification) delivery control via universal translations tables, which is determined per destination and source. It enhances previous activities about CLI transfer. This activity is developed in CS2K&TDM for Israel ISN market.

Purpose and synopsisBLOCKCLI enhances previous activities, CLI Delivery Control and Calling Line Identity. CLI delivery can be controlled via trunk group basis. One method is to address CLICNTL table. A tuple in CLICNTL table has a CLIDELV field which allows CLI delivery if the value is ‘Y’, or blocks it when it is ‘N’. If the CLIDELV field is set to ‘N’, then the CLI parameter is not sent over the terminating trunk. In such a case, a null parameter is sent in the outgoing message. A tuple in CLICNTL can be addressed from TRKOPTS with CLICNTL option for originator, per trunk group.

CLIDELV option in TRKOPTS also supplies TRKGRP basis CLI blocking but for terminating trunks. One can give CLIDELV option with ‘Y’, ‘N’ or SCRN_PI value, which determines CLI to be allowed, blocked or determined according to Presentation indicator respectively.

This activity provides CLI (Calling line identification) delivery control via universal translations tables(XXHEAD, XXCODE), which is determined per destination and source. It is possible to block CLI in initial setup messages of both TDM and IP Network protocols, per trunk group basis when CLI blocking framework exists.

This feature enhances the existing functionality by providing it per route, getting use of the existing framework. A new option (BLOCKCLI) is introduced in universal translation tables. BLOCKCLI provides to block CLI in initial setup message when it is set to ‘Y’. If BLOCKCLI is set to ‘N’ or it doesn’t exist, there is no effect to block CLI information in initial setup message.

56




A00018680, INAP FCI Enhancement 1This feature enhances IN framework in CS2K to provide support for Nortel proprietary FREEFORM FCI operation to extend the maximum FCI data size and the number of Module Code:199 (MC-199) modules being appended to the AMA billing record. In addition, this feature enhances the FCI message decoding to enable the decoding of an FCI message received with SEQUENCE parameter.

Feature synopsisINAP FCI Enhancement consists of three design improvements:

• Extending Nortel proprietary FREEFORM FCI maximum data size: FREEFORM FCI maximum data size is extended from 200 octets to 286 octets, which increases the maximum allowed MC-199 module codes received in a single FREEFORM FCI message for a single call from 5 to 10.

• Extending the maximum number of MC-199 modules being appended to the AMA billing record: The maximum number of MC-199 modules being appended to the AMA billing record is increased from 10 to 20.

• FCI Decoding Enhancement: Nortel SSP handles the FCI message including FCIBCC parameters under SEQUENCE tag. DMS SSP only decodes FCIServiceKey parameter and does not decode the other sub-parameters.

57




A00018715, Session Server Trunks (SST) Additional Operational Measurements (OMs) 1

This feature shall enhance the scope of Performance Measurements on the SST and Core that are relevant to DPT traffic and various capacity/engineering needs.This capability focus is on some of the gaps related to Session Server Trunks application and CS2k Core, with respect to the content of the Performance Measurements.

This activity shall enhance the SST related Operational Measurements (OM) application in SN11.This activity covers the following areas:• MAXBU Register in TRK OM Group in CS2K core to be enabled for

SIPT DPT Trunks

• Creation of new Registers in Existing OM Groups

— New register DPT_TID_OVFL is created in SIPGW_CALLP OM Group to keep track of incoming call failures due to the non availability of TIDs in GWC.

— New register CDB_OVFL is introduced in SIPGW_ETC OM Group to keep track of incoming call failures due to the non availability of CDBs in SST.

— The existing register HWM_INUSE_CDB in the SST OM group SIPGW_STACK_STATS is re-named as SIMULTANEOUS_CALL_HWM. This register will provide the maximum simultaneous calls in OM collection period.

— New registers are introduced in SIPGW_OVERLOAD. These OM registers are Set Registers.– TLS_SIMULTANEOUS_CONNECTION_HWM: This High

Water Mark register updates when the number of TLS connections at an instance is greater than the previous value.

– MEM_USAGE: This register contains average percentage memory usage of the SST over a OM collection period.

– DISKSPACE_USAGE: This register contains the average of percentage disk space available for the application over OM cycle period

• Creation of new SST OM Groups based on SIPT DPT traffic and SIP Transactions.

— SIPGW_REJECT_SIPMSG: Provides the count of number of rejected message for each message type on a per SIPLINK basis

— SIPGW_TRANSACTION_IC: Provides count of number of transactions created by incoming messages per message type

58




— SIPGW_TRANSACTION_OG: Provides count of number of transactions created by outgoing messages per message type.

— SIPGW_TRANSACTION_USAGE: Provides count of the number of active Transactions per message type

— SIPGW_RESPONSE_IC: Provides count of number of incoming response messages received.

— SIPGW_RESPONSE_OG: Provides count of number of outgoing response messages received.

All the OM groups in SST will report via both 5 min and 15/30 min CSV files.

59




A00018730, ISDN Preconf Notify 1When a PRECONF is invoked within the DMS100, the DMS100 shall include in the outgoing ISDN call setup message a Notify IE, which reuses the ETSI defined value ‘ Conference established’.

This feature will also provide supporting Notification indicator ’ Conference Established ’ using Generic Notification parameter, to be sent to ETSI BRI conferees over either ETSI ISUP V2 or intra call.

Purpose and synopsisThe existing Preset activity allows an ETSI BRI (p-to-mp) station or ETSI ISUP V2 trunk to set up a preset conference with up to 35 conferees by dialing a specific directory number. This invokes simultaneous ringing of preselected conference members.

The originator of a preset conference (served user) which has AFC & HOLD line options, is able to add on additional local conferees once the conference is established.The maximum index of Preconf Table is increased up to1024 conference, according to the new Preset SOC option is turned on.

60




A00018754, Automatic Collect Call Blocking (ACCB) for Trunk Groups 1

This feature provides the ability to prevent ACC calls from Brazil ISUP to FST R2 Brazil Variant, FDCP R2 Brazil Variant and ETSI PRI trunks. This functionality is provided by means of a new trunk option, ACCB – ACC Blocking. ACC calls routing to trunk with ACCB datafilled in TRKOPTS table.

Purpose and synopsisAn Automatic Collect Call in Brazil is a direct dialled call, local or national long distance , placed with in the public network using a special dialing sequence and completed without operator assistance , where the charges for the call are applied to the called party upon acceptance for the called party. Announcement signal the called party that the call is a collect call. The called party signifies acceptance by staying off-hook longer than a pre-limited period (e.g 5 seconds) after answer.

Billing for an ACC call begins at the conclusion of the defined period. Billing is terminated when either party of the call hangs up.

All automatic collect calls, whether they are local or national long distance, are routed via the controlling switch, in this case a DMS-100 (Digital Multiplex Switch Multi-100) switch, which has control of the connection.(in addition to the originating party control at the originating local switch)

ACC calls may originate from any of the following sources:

• Brazilian Integrated Services Digital Network (ISDN) User Part (ISUP)

• Brazilian Telephone User Part (TUP)

• Brazilian Register Signalling #2 (R2)

• European Telecommunications Standards Institute (ETSI) Primary Rate Interface

• Lines (via Brazil ISUP looparounds)

ACC calls may terminate to any of the following destinations:

• Brazilian ISUP

• Brazilian TUP

• Brazilian R2

• ETSI PRI

• Lines (via Brazil ISUP looparounds)

Note that the ACC feature can only be invoked between two trunk interfaces, it cannot be invoked directly from a line. As a result, Brazil ISUP

61




looparounds must be used when attempting to originate an ACC call from a line or terminate an ACC call to a line.

The feature provides the ability to prevent ACC calls before routing to terminating switch. This functionality is provided by means of new trunk option, ACCB-ACC Blocking. ACC calls routing to a trunk with ACCB datafilled.

62




A00018761, Enhancements to the TTP Outpulse Command 1This activity enhances the Outpulser (OP) tool which is used to establish a connection to a distant office by outpulsing a given called number over a ETSI ISUP v1 or ETSI ISUP v2 trunk posted in the TTP level of MAPCI.

Purpose and synopsisThis feature gives the craftsperson more options to specify the content of selected ISUP IAM parameters in the test call via the OP command. These ISUP parameters of IAM are as follows:

• NOA Field and Digits of CdPN--an optional parameter is added, with settings of “national number” or “international number.”

• NOA Field and Digits of CgPN--an optional parameter is added, with settings of “national number” or “international number.”

• TMR/USI--an optional parameter is added, with settings of “64 kbit/s unrestricted”, “speech” or “3.1 kHz audio.”

• CPC--an optional parameter is added. CPC values are supported from 0 to 15. If the user does not enter a value then the default value for CPC is “test call” except if the TMR is specified as “64kbit/s unrestricted”, in which case the default value for CPC is “data call.”

• FCI Natl/Intl Call Indicator--an optional parameter is added, with settings of “national call” or “international call.”

• NOC Echo Suppression Indicator--set as specified in table TRKSGRP for the trunk under test. This default value used to be set as “no_half_echo_sup” independent from the market before this feature was implemented. Note, when the TMR is specified as “64Kbit/s unrestricted, ” the Echo Suppression Indicator will be set to “no_half_echo_sup” regardless of the provisioning in table TRKSGRP.

The first five parameters, CdPN NOA, CgPN NOA, TMR, CPC and FCI CI are new parameters introduced in this feature and can only be used for ETSI ISUP v1 and ETSI ISUP v2 trunks. The Echo Suppression setting is based on the datafill in table TRKSGRP, otherwise the original behaviour of the “OP” command remains the same as before.

63




A00018834, NGSS/SS Trunks CSV PM Integration 1Solution: PT-IP, UA-IP, IAC, IAW

This feature implements the IEMS handling of SS Trunks CSV-formatted metrics data and disables the SNMP interface. Customers wil be able to configure a CSV-based performance interface for SS Trunks devices, and to configure CSV-based collection and report jobs.

If an SST is up-versioned from an SST version that uses the SNMP interface to one that uses the CSV interface, that SST MO has to be deleted and re-added to IEMS, at which time the new CSV performance interface is configured.

Configuraton details are in Volume 2 of this document.

64




A00018837, SPFS CSV PM Integration 1Solution: PT-IP, UA-IP, IAC, IAW

This feature implements the IEMS handling of SPFS CSV-formatted metrics data and disables the SNMP interface. Customers wil be able to configure a CSV-based performance interface for SPFS platform devices and to configure CSV-based collection and report jobs.

If SPFS is up-versioned from an SPFS version that uses the SNMP interface to one that uses the CSV interface, that SPFS MO has to be deleted and re-added to IEMS, at which time the new CSV performance interface is configured.

Configuraton details are in Volume 2 of this document.

65




A00018847, Critical Alarm raised when Phase 1 or Phase 2 negotiation fails 1

A Critical alarm needs to be generated when IKE Phase1 or Phase 2 fails, and alarms should be cleared when IKE negotiations are successful.

Purpose and synopsisIn the current implementation, a major alarm is raised whenever phase 1 or phase 2 negotiation fails, and it is cleared when negotiation successful. This feature changes the severity from major to critical.

66




A00018885, Increase SIP Trunks to 150K per Call Server 1

Purpose and SynopsisWith succession, trunk engineering is greatly simplified due to dynamic nature of DPT trunks. Unlike TDM trunks where circuits consume more bandwidth when not in use, DPTs only consume bandwidth when in use. Therefore for maximum operational efficiency in lower cost, the aim is to provision all DPTs to the maximum. This feature enhances CS2K to support up to 150K SIP trunk ports for a SIP trunk group. Hence this feature ensures the possibility of maximum of 150,000 simultaneous calls over a SIP trunk-group in CS2K.

67




A00018886, SSL Geographic Survivability 1

As depicted in the figure above, the CS2000 Compact Call Agent (CCA) has multiple redundant network communication paths between its active/standby components in geographically separated sites. These redundant paths prevent single failures from resulting in complete isolation of the two sites from each other. This enables the CCA to maintain a single active component in network failure scenarios that would otherwise result in active components in both sites at the same time. In this scenario, it is necessary to choose one site (referred to as the surviving site) from which to provide service. To this end, dynamic routing protocols are updated so that all remote messages destined for addresses in the geographically distributed LAN are routed to the site collocated with the active CCA component. In network deployments using the ERS8600 router, the inactive CCA in the non-surviving site automatically updates the dynamic routing. Otherwise, this action is performed manually in response to an alarm.

The result of this dynamic routing change has an impact on other 1+1 fault tolerant components in the network, including the SS-L components. In the failure scenarios described above, the SS-L components become isolated from their mates, resulting in both instances of each 1+1 SS-L component being active at the same time. However, based on the dynamic routing changes, only one site is able to receive messages from outside the LAN. This implies that when the network failure is corrected, all 1+1 SS-L

CS-LAN CS-LAN

Site A Site B

GWgw

gw

Packet Network

Fiber-Channel

Link

WAN connectivity forgateway to GWC traffic

CS LAN ping traffic

gw

gw

GigE

Backup Path for Mastership Selection - prevents “split brain”

scenario

Optical Transport NetworkOM5200 Mesh

68




components in the site collocated with the active CCA should retain their activity while those in the other site should cede.

This feature requires 1+1 Fault Tolerant SS-L Components to detect the site isolation scenario, and specifically to detect which site is the surviving site. The purpose of detecting this condition is to make sure that a Fault Tolerant component that was completely isolated from the network does not take Activity away from its mate when the isolation condition is repaired.

Prior to this feature, SS-L components already support a mechanism to detect one simple scenario of being isolated from the network—network interface failure. SS-L components are able to detect when all network interfaces connecting them to the LAN have failed. When they detect this condition, they ensure that an isolated component does not take Activity away from its mate when the isolation condition is repaired. This existing behavior is exactly consistent with the desired behavior of a Fault Tolerant component that detects itself to be in the non-surviving site of a Geographically Survivable configuration. This is not surprising, because fundamentally network interface failure has the same effect on the SS-L components on the affected host platform that declaration of a non-surviving site by the CS2000 Compact Call Agent has on components existing in the non-surviving site. In both cases, the affected components are completely isolated from the rest of the network, while call processing continues elsewhere.

Accordingly, this feature introduces a new mechanism to detect the condition of being in the non-surviving site. However, the behavior upon detecting this condition is not new. SS-L components that detect themselves to be in the non-surviving site of a Geographically Survivable configuration behave exactly as they behave upon detecting network interface failure. For completeness, the behavior of an SS-L component that detects itself to be network isolated—either due to network interface failure or to existence in the non-surviving site of a Geographically Survivable configuration—is explained in detail.

The mechanism introduced by this feature to detect existence in the non-surviving site of a Geographically Survivable configuration involves periodically and continuously sending ICMP Echo Request (ping) messages to the Active IP Address of the CS 2000 Compact Call Agent in order to assess its reachability. SS-L Components that detect this IP Address to be unreachable consider themselves to be in the non-surviving site. Accordingly, they consider themselves to be network isolated.

The basic behavior of a Fault Tolerant network isolated component depends on whether it is Active at the time it detects this condition. A component that is not Active immediately shuts itself down and enters a state in which it

69




waits for the network isolation condition to clear. Once this is detected, the component restarts itself.

If a Fault Tolerant component is either Activating or Active at the time it detects itself to be network isolated, it remains Active. However, the periodic messages it exchanges with its mate as part of the 1+1 Fault Tolerance mechanism communicates to its mate the fact that it considers itself to be network isolated. When an Active component receives contact from its Active mate, the fact that the mate is also network isolated is used in the decision process about which of the two Active mates should retain activity and which should restart.

This feature removes one existing alarm and adds three new Alarms. The names of the new alarms:

• Interface 1 LAN Failure

• Active CS 2000 Call Agent Unreachable

• Network Isolated

70




A00019321, SPFS PM enhancement 1This feature provides a set of performance measurements that monitor in near real-time for any performance degradation or pending issues related to SPFS platform exhaustible resources. It enables users to isolate the issue to a specific application.

Typically, the feature is enabled automatically by the SSPFS installation and runs by itself to collect PM data for the IEMS to transfer. Defined PMs are collected as 15-minute PMs and 30-minute PMs. 5-minute PMs can also be collected if configured but are turned off by default at installation for performance reasons. Configured collection settings are maintained over an upgrade. At each collection interval these PMs will be available to be collected by NB system (IEMS). PMs will be stored on SPFS in CSV formatted files at each collection interval available for SFTP pull to IEMS.

Performance ManagementThis feature creates records every 5 minutes (turned off by default), 15 minutes and 30 minutes unless configured otherwise. The filename format of the record files is

succession.sspfs.<unit hostname>.OMs.<interval time>_MIN.<capture time>.csv

Examples:

/export/home/pmcftp/5min/succession.sspfs.ottawa-unit1.OMs.5_MIN.2009-11-24T11:35:51EST.csv



Note: If the SPFS unit is managed by IEMS and it is configured to collect SPFS performance data, the files would be available to OSSs from its northbound directories: /data/oms/longinterval/1 for 15/30 minute files and /data/oms/shortinterval/1 for 5 minute files. Once IEMS collects the SPFS performance files from the /export/home/pmcftp/*min directories, it changes the filename extension from .csv to .processed.

Data is collected every minute and compiled at the end of the interval at which time tables are built.

This feature collects a set of new PMs: 5 single values and 6 data tables (7 in SPFS 12 and up)

71




Five single values are listed in the following table:

Six (or 7 in SPFS 12 and up) data tables are described as follows:

cpuUsage table reports the Mean/Minimum/Maximum values over the past PM interval.

memoryUsage table reports the Mean/Minimum/Maximum values over the past PM interval.

diskUsage table reports the complete output from Solaris utility “df –k”, used and available disk space on each file system. It is captured at the end of each PM interval.

traffic table reports the number of packets passing through each network interface over the past PM interval. Typically uplink0, uplink1 and lo0 are network interfaces for SPFS.

diskIO table reports the disk io statistics over PM interval. (x) is for the Max value and (a) is for the Average value.

ApplicationPMs data table reports performance data grouped with applications. This table content is configurable and an application is defined as a list of running processes provided with a configuration file.

ONLY VISIBLE IN SPFS12 and up:In SPFS 12, data is collected for LWPs as well (Light Weight Processes).

SystemLWP data table reports the number of processes and LWP processes running on the system. It provides the mean, minimum and maximum for the processes and LWPs.

PM Description

HAstatus “active” or “inactive” for SPFS cluster “active” for SPFS simplex

1minLoadAvg Average system load for the past 1 minute



Alarm350 Number of SPFS 350 alarms

72




A00019363, INAP Flexible ACN 1This activity provides flexibility in ACN (Application Context Name) handling, by enabling the customers to datafill the ACN value to be used in a new table INAPACN for the INAP operations that can include ACN in TCAP dialogue portion.

A new table INAPACN is created in order to provision any ACN value for any of the following operations:

• IntialDp

• CallGap

• ActivateServiceFiltering

• ActivateServiceFilteringResponse

• InitiateCallAttempt

Table INAPACN has the following fields:

• INAPACNX

• OPTIONS

73




A00019365, PNSCRN ONP Activity 1This feature reduces the table transfer time for table PNSCRN prior to ONPs. This applies to both BRISC processors which are limited to 8M entries and to XA-Core/PPC processors which are limited to 24M entries.

74




Q01670586, QCUST command behavior for SIP Lines 1Starting in CVM11, output for the QCUST command no longer produces a Boolean indicator (Y/N) at the end of the DPL option line.

The output of QCUST in CVM11:

>qcust len SS 00 0 00 90

0 57 Y 4 Y N

99

18 ISDN

18 FUSS

18 BURG

18 FRNK

18 RODP

18 SCRIPT

18 GUI

18 SODP

18 QSIG

18 ISDN1

18 ISDNPRI

18 V5BRI

18 MANTST

18 TTF

18 MEHO

18 QNSX

99

19 PUBLIC 0

19 TRAF_DPNSS 1

19 TTFNET 2

19 FUSS_NET 3

19 CBTELNET 4

19 RAGNTWK 5

19 CUST783 6

19 QUEENSNET 7

19 KINGSNET 8

75




19 SIPPBX 9

99

1 SS 00 0 00 90 IBN PKNIL GWLPOT N

2 5420090 CUST542 0 0 216

9 DGT $

10 0 DPL Y 10 <-------------------- No Y after 10.

10 0 CND NOAMA ACT 0 0 0 0

99

@

>

76




77




CVM11 Feature Impacts 1The following feature to function impacts are broken down into the following sections:

• CVM11 operational and functional impacts on page 77 (data schema, logs, OMs, office parameters, and changes to the CDR)

• CVM11 feature SOC activation and prerequisites on page 80

• CVM11 feature HMI impacts on page 82

• CVM11 feature hardware impacts on page 84

• CVM11 feature Network Interface impacts on page 84

• CVM11 feature alarms on page 85

Note: If the feature does not have an impact to a particular table, the feature will not be listed. Only features that impact a table will be listed. Links in the tables are cross referenced to the feature summaries in the first chapter.

CVM11 operational and functional impacts 1This section outlines operational measurements (OMs), logs/alarms, data schema (DS), office parameter, billing (CDR), and ServOrd (SO) changes.

Table 2-1 CVM11 operational and functional impacts

Feature Name OMs Logs DS OParms CDR SO

MG4K Automatic Trunk Deload, A00014116

No Yes, 3 new Yes, 1 changed

Yes, 1 new

No No

SIP PBX capacity / scaling development, A00014277

Yes, 1 new

No No No No No

SIP PBX Interface Services, A00014279

No No Yes, 1 changed

No No No

(Sheet 1 of 4)

78




Inter-Carrier SIP Trunking: Support for Border Control Point Insertion, A00015652


No No No

Flexible endpoints for small line GW and Endpoint utilization improvement, A00016277

No No No No No Yes, 3 changed

STORM Robustness, A00016298

No Yes, 2 changed

No No No No

PacketCable MTA NCS Loopback, A00016591


No No No

CS2K SIP Enabled VoIP VPN - LTID Decoupling, A00016592

No Yes, 2 new No No No No

AS2K Provisioning and SOC, A00016421


No No Yes, 1 new

SIP PBX OAM, A00016594 No 11 new logs, 4 new alarms

No No No No

CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component, A00016595

No No Yes, rout-ing tables changed

No Yes, 2 changed

No

Intergateway Route Identification Support, A00016770

No No Yes , 3 changed

No Yes, 1 changed

No

Japan NTC Enhancements, A00016771

No Yes, 1 changed

Yes , 2 changed

No No No

Presentation CLI Support For Japan, A00017589

No No Yes ,1 changed

No No No

Japan Call Control Enhance-ments and CLI Conditional Remova, A00018189l

No No Yes , 1 changed, 2 new

No No No

Flash Ignore with Call Waiting, A00018518

No No No No No Yes, 1 changed

Table 2-1 CVM11 operational and functional impacts (Continued)


(Sheet 2 of 4)

79




Speed Call Short Capacity Enhancement, A00018519

(Refer to Line Capacity Enhancement - Phase 2)

Line Capacity Enhancement - Phase 2, A00018520

No No No Yes, 1 changed

No Yes, several changed

LCMINV & MTAVERT Table Expansion, A00018521


No No No

PNSCRN Table Expansion to 24 million tuples, A00018527


No No No

OM Enhancements for MTX, A00018529

Yes, 1 changed and 1 new group with 6 registers

No No No No No

CLI Blocking Enhancements, A00018579

No No Yes, several changed

No No No

INAP FCI Enhancement, A00018680

No No No No Yes, 1 changed

No

Session Server Trunks (SST) Additional Operational Measurements (OMs), A00018715

Yes, 6 new groups; 6 new registers added in existing groups

No No No No No

Automatic Collect Call Blocking (ACCB) for Trunk Groups, A00018754


No No No

NGSS/SS Trunks CSV PM Integration, A00018834

Yes, changes SS-T OMs

No No No No No



(Sheet 3 of 4)

80




CVM11 feature SOC activation and prerequisites 1Table 2-2 identifies the changes to the SOC activation by new features. The table also displays the prerequisites (hardware or software) associated with the features where applicable.

SPFS CSV PM Integration, A00018837

Yes, changes SPFS OMs

No No No No No

SPFS PM enhancement, A00019321

Yes, adds SPFS PMs: 5 single values & 6 data tables

No No No No No

INAP Flexible ACN, A00019363

No No Yes, 1 new No No No

PNSCRN ONP Activity, A00019365

No No No Yes (1 new)

No No

Table 2-2 CVM11 feature SOC activation and prerequisites

Feature Name SOC Activation SERVORD information

Prerequisites/Description

SIP PBX blind protocol tunneling, A00014278

VPNG0001, SIP PBX Blind Tunneling

N/A SIP PBX Blind Tunneling SOC can only be turned ON, if the CS2B SIP PBX SOC is already turned ON.

H.323 Billing Mediation, A00015719

Implemented in the Core

N/A N/A

(Sheet 1 of 3)



(Sheet 4 of 4)

81




SIP Line: GWC line capacity improvement, A00016419

CS2B0013, GWC Double Density usage SOC

N/A There are no technical dependencies on any other SOCs. However, there is an indirect dependency on CS2B0002. CS2B0002 controls how many GWCs can be purchased (regardless of “type”) in a CS2000 Complex. Just for clarity, CS2B0013 determines how many of those GWCs can be double density. CS2B0013 can not be larger than the current setting for CS2B0002.

AS2K Provisioning and SOC, A00016421

AS2K0002 Controls the number of AS2K Lines and is a Usage type SOC.

There is a corresponding new line option (AGNTPCL) which allows distinguishing between IETF SIP Lines and ISC SIP lines using in the IMS network on the AS2K.

AS2K0002 SOC is commercially dependent on the AS2K0001 TRAK SOC and technically dependent on no other SOCs. However, this AS2K0002 SOC will be implicitly dependent on the CS2B0005 SOC which controls the usage of DPT TIDs for BICC and SIP-T currently on CS2000.

CS2K SIP PBX Provisioning, A00016582

CS2B0012, CS2B SIP PBX

VPNG0001, SIP PBX Blind Tunneling

N/A SIP PBX Blind Tunneling SOC can only be turned ON, if the CS2B SIP PBX SOC is already turned ON.

PNSCRN Table Expansion to 24 million tuples, A00018527

XLAS0059 XLAS0059 depends on XLAS0006/IXLS0002 (activation of PNRF option presented by AU2848); this new feature cannot be active unless one of these SOCs is turned on. The new SOC is usage-controlled and hard-limited, in increments of 4M tuples block

Table 2-2 CVM11 feature SOC activation and prerequisites (Continued)



(Sheet 2 of 3)

82




CVM11 feature HMI impacts 1This section summarizes the impacted human-machine interfaces required to configure and manage the new features.

Line Capacity Enhancement - Phase 2, A00018520

CS2N0004 N/A CS2N0004 controls usage of CS2000 and CS 2000 - Compact non-SIP, IBN and RES lines for North American applications. MG 9000 ABI, SIP and IMS packet lines are excluded from this control. Line protocols controlled by SOC CS2N0004 include H.248, NCS and MGCP.

ISDN Preconf Notify, A00018730

MDC00080 N/A N/A

Table 2-3 CVM11 feature HMI impacts

Feature Name MAPCI GUI usage

Flexible endpoints for small line GW and Endpoint utilization improvement, A00016277

Yes Yes

SIP Line: GWC line capacity improvement, A00016419

No Yes

SESM Robustness, A00016506 Yes Yes

CS2K SIP PBX Provisioning, A00016582 No Yes

CS2K SIP PBX OAM (Operations, Adminis-tration, Maintenance) & Tools, A00016594

Yes Yes

Switch wide GWC status report tool, A00018330 Yes No

NGSS/SS Trunks CSV PM Integration, A00018834

No Yes

SPFS CSV PM Integration, A00018837 No Yes

Enhancements to the TTP Outpulse Command, A00018761

Yes No

(Sheet 1 of 2)

Table 2-2 CVM11 feature SOC activation and prerequisites (Continued)



(Sheet 3 of 3)

83




SSL Geographic Survivability, A00018886 No Yes

QCUST command behavior for SIP Lines, Q01670586

Yes No

Table 2-3 CVM11 feature HMI impacts (Continued)

Feature Name MAPCI GUI usage

(Sheet 2 of 2)

84




CVM11 feature hardware impacts 1Table 2-4 outlines the hardware impacts of the features. This table will identify any new/modified or removed hardware resulting from the implementation of the new CVM11 features.

CVM11 feature Network Interface impacts 1Table 5 identifies whether each feature has an impact on ANSI-41 and IS41P network messages or NOIS/IOS networking messages.

Table 2-4 CVM11 feature hardware dependencies

Feature Details

Increase SIP Trunks to 150K per Call Server, A00018885

This feature enhances CS2K to support up to 150K SIP trunk ports for a SIP trunk group. Hence this feature ensures the possibility of maximum of 150,000 simultaneous calls over a SIP trunk-group in CS2K.

Table 5 CVM11 feature Network Interface impacts

Feature Network message

Independent

SIP PBX Interface Services, A00014279 Yes No

Intergateway Route Identification Support, A00016770

Yes

Presentation CLI Support For Japan, A00017589

Yes No

Support for Cause-of-no-ID on Japan PRI and SIP line Originations, A00018187

Yes No

JI-ISUP/J-PRI to ETSI ISUP interworking and CgPN NOA Default Change, A00018188

Yes No

INAP FCI Enhancement, A00018680 Yes No

ISDN Preconf Notify, A00018730 Yes No

SSL Geographic Survivability, A00018886 Yes

INAP Flexible ACN, A00019363 Yes No

85




CVM11 feature alarms 1Table 2-6 identifies the changes to alarms by new features.

Table 2-6 CVM11 feature alarms

Feature Name Details

SIP PBX OAM, A00016594 Four new alarms added.

Critical Alarm raised when Phase 1 or Phase 2 negotiation fails, A00018847

2 changed

SSL Geographic Survivability, A00018886

Removes one existing alarm and adds three new Alarms

86




87




CVM11 OAM&P Summary 1This chapter contains high-level OAM&P (Operations, Administration, Maintenance and Performance) delta information for the CVM11 software release. Delta information is defined as changes to a single software release in relation to the previous software release. Changes include added, modified, or deleted features. Sections are covered in this order:

• AMA/billing changes on page 88

• Data schema (DS) changes on page 89

• Log changes on page 92

• Operational measurement (OM) changes on page 93

• Office parameter (OPARM) changes on page 98

• Service Order (SO) changes on page 99

• Human-machine interface (HM) changes on page 101

• Software Optionality Control (SOC) changes on page 103

Product-impact mapppingIn the tables that follow, the parenthetical information after the ACTID indicates the affected product, for example, A00018680 (WT). This mapping table shows explanations for the acronyms used within the parentheses.


AS5200 Application Server 5200

CA Call Agent Card (for Compact CS2000)

CS2M GWC Manager & OSSGate

CS2000 Communication Server 2000

CS2000-c Communication Server 2000-Compact

GWC Gateway Controller

88




AMA/billing changes 1This section lists any new, modified or deleted AMA/billing related information associated with this release. For more detailed information on these changes, refer to the “Accounting” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

MCS AS5200/SSL

SSL CS 2000 Session Server Lines

SST Session Server Trunks

Table 3-1New and modified AMA information for CVM11

Field name Status Feature title and description of change

Module Code:199 Changed INAP FCI Enhancement, A00018680 (WT)

The maximum number of MC-199s appended to the AMA billing record is increased from 10 to 20. Hence, the total number of octets that can be captured in MC-199 modules for a single call increased to 400 octets vs current 200 octets. To append 20 MC-199s to the AMA billing record, 20 FCI messages can be send one by one consecutively, also by appending up to 10 MC-199s in one FCI message.

Module Code 260 Changed CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component, A00016595 (GWC, AS5200/SSL)

Tuple RECORD_MC260 in AMAOPTS activates/deactivates inclusion for SIP PBX along with SIP lines. The option activates recording of packet client involvement for both originating and terminating SIP PBX agents. This option does not force billing; it collects the additional information for existing billable scenarios.

Module Code:611 Intergateway Route Identification Support, A00016770 (CS2000, GWC, WT)

A new context ID 80300 of module code 611 is introduced. When ACM message with ORI parameter is received in an ORI reception switch, ORI information is stored in AMA record if the ‘ORI_BILLING’ option is set to ‘ON’. Option ori_billing in Table AMAOPTS must be set to 'on'.


89




Data schema (DS) changes 1This section lists any new, modified or deleted Data schema (DS) related information associated with this release. For more detailed information on these changes, refer to the “Configuration Management” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

Table 3-2New and modified DS for CVM11

Table name Status Feature title and change description

TRKOPTS Changed MG4K Automatic Trunk Deload, A00014116(CS2000)

New option ATD is added, valid only for TDM ISUP trunk groups. The ATD option marks a trunk group as available for deloading.

LTDATA Changed SIP PBX Interface Services, A00014279 (CS2000, GWC, WT, AS5200/SSL)

Modified to support Dual CLI for the QSIG SIP PRI.

TRKOPTS Changed Inter-Carrier SIP Trunking: Support for Border Control Point Insertion, A00015652 (CS2M, GWC, CS2000)

The fields Location, NATid, ForceBCP and BCPGroupId are datafilled in the TRKOPTS DPT tuple, both for NGSS and VRDN SIP trunks.

IBNFEAT

TRKOPTS

DPTRKMEM

SIPLINK

Changed AS2K Provisioning and SOC, A00016421 (CS2000)

Table IBNFEAT has been enhanced to provide support for the new Agent Protocol (AGNTPCL) Line Option.

Table TRKOPTS has been enhanced to support for the new DPT Protocol Type ISC, for the provisioning of ISC trunks.

Table DPTRKMEM has been enhanced to support for the new Dynamic Signalling Type ISC for the provisioning of ISC trunks.

Table SIPLINK has been enhanced to support for the new Siplink Connection Type AS2IMS for the provisioning of ISC trunks.

IBNXLA Changed PacketCable MTA NCS Loopback, A00016591 (CS2000, GWC, WT)

The two Feature Access Codes (FACs) required by the NCS MTA Loopback capability are provisioned in table IBNXLA. The FTR translation selector is used to implement the capability. A new feature type LOOPTEST is available in IBNXLA. LOOPTEST prompts for MODETYPE. The two supported MODETYPEs are LOOPBACK and CONTINUITY. LOOPBACK and CONTINUITY correspond to the PacketCable-defined NCS connection modes NETWLOOP and NETWTEST, respectively.

(Sheet 1 of 4)

90




Routing tables Changed CS2K Hosted SIP Enabled VoIP VPN Solution - Call Processing Phase 2 Component, A00016595 (GWC, AS5200/SSL)

To support the private UDP and CDP dial plans, additional datafill is required to explicitly set the private TON value on a route basis on the CS2K Core.The existing ISA selector of the routing tables has been updated to configure the private TON value.

ISERVOPT

TRKOPTS

AMAOPTS

Changed Intergateway Route Identification Support, A00016770 (CS2000, GWC, WT)

New option TWXRI of table ISERVOPT is introduced. There are two fields in this option:

• ORI_ACTIVATE: the trigger of whole feature.

• GATEWAY_ID: 0 ~ 255. The gateway ID that is defined for this switch.

New trunk option TOINTLGW in table TRKOPTS is introduced to indicate that the trunk group on this international gateway is connected to another international gateway. This option is used to identify the role of the switch for the ORI transmission.

A new option is introduced in table AMAOPTS. This option allows operator to enable or disable the capturing of ORI in AMA record.

ANNAUDID

ANNPHLST

Changed Japan NTC Enhancements, A00016771 (WT)

On IP side, table ANNAUDID stores datafills for mapping simple phrases to MS2000 announcement IDs. While trying to play a tuple in ANNPHLST, all its simple phrases should be datafilled in ANNAUDID.

To break one long audio request into multiple short pieces, a marker NTCMARKER in table ANNPHLST is defined to indicate the break point of an announcement. It is datafilled in the same way as the other simple phrases.

LTDATA Changed Presentation CLI Support For Japan, A00017589 (WT)

Modified DEFLTPN, DFLTCGN and SCRNPN options to support JPRI trunks. SCRNPN and DEFLTPN are assigned against the CLI selector. DFLTCGN is assigned against the DN selector.

CALLCNTL Changed Japan Call Control Enhancements and CLI Conditional Removal, A00018189 (WT)

Enhanced to support the new screening options, FCICI and PI.

Table 3-2New and modified DS for CVM11 (Continued)


(Sheet 2 of 4)

91




FCICISCR

PISCRN

New Japan Call Control Enhancements and CLI Conditional Removal, A00018189 (WT)

New table FCICISCR is created to support the FCICI screening function. New table PISCRN is created to support the PI screening function.

LCMINV

MTAVERT

Changed LCMINV & MTAVERT Table Expansion, A00018521 (CS2000)

The size for table LCMINV is increased from 256 to 512 and the size of table MTAVERT is increased from 1024 to 2040.

PNSCRN Changed PNSCRN Table Expansion to 24 million tuples, A00018527 (WT)

Expands PNSCRN table size up to 24M tuples without changing the customer visible view of the table. The capacity expansion of the table is allowed using a usage-controlled SOC option with hard-limit. The new capacity of the table can be expanded with 4M tuples block (8M +4M +4M +4M +4M) up to 24M tuples as one of 12M - 16M - 20M - 24M upper-bounds.

XXHEAD

XXCODE

Changed CLI Blocking Enhancements, A00018579 (CS2000, WT)

Enhances the universal translation tables with new option (BLOCKCLI), allowing CLI blocking per route, getting use of the existing framework. BLOCKCLI provides to block CLI in initial setup message when it is set to ‘Y’. If BLOCKCLI is set to ‘N’ or it doesn’t exist, there is no effect to block CLI information in initial setup message.

TRKOPTS Changed Automatic Collect Call Blocking (ACCB) for Trunk Groups, A00018754 (WT)

Modified with new trunk option, ACCB-ACC Blocking.



(Sheet 3 of 4)

92




Log changes 1This section lists any new, modified or deleted logs related information associated with this release. For more detailed information on these changes, refer to the “Fault Management” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

INAPACN New INAP Flexible ACN, A00019363 (WT)

Provides flexibility in ACN (Application Context Name) handling, by enabling the customers to datafill the ACN value to be used in a new table INAPACN for the INAP operations that can include ACN in TCAP dialogue portion.

New table INAPACN is created in order to provision any ACN value for any of the following operations:

• IntialDp

• CallGap

• ActivateServiceFiltering

• ActivateServiceFilteringResponse

• InitiateCallAttempt

Table 3-3New or modified logs for CVM11

Log number Status Feature title and description of change

NWM900 NWM901 NWM902

New MG4K Automatic Trunk Deload, A00014116(CS2000)

• Log NWM900 is generated when a request to block/unblock trunks is initiated.

• Log NWM901 is generated when a mismatch is found between the actual node state and the state of node entered in the ATD database.

• Log NWM902 is generated when a trunk state mismatch is found.

STM302, STM303

Changed STORM Robustness, A00016298 (STORM)

STM302 alarm and log is raised when power fails. All missing IEMS event label fields are set to “Equipment malfunction” in hardware related alarms, such as STM302 or STM303.

(Sheet 1 of 2)



(Sheet 4 of 4)

93




Operational measurement (OM) changes 1This section lists any new, modified or deleted Operational measurements (OM) related information associated with this release. For more detailed

XPKT350 XPKT351 XPKT352 XPKT600 XPKT601 XPKT602 XPKT603 XPKT604 XPKT605 XPKT606 XPKT353

New CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools, A00016594 (CS2M, GWC, AS5200/SSL)

These new XPKT logs contain LTID and correlation id to identify with which SIP PBX the log is associated. Except XPKT353, each of these new logs corresponds to an existing TRK, TRKT, or AUDT log. They are generated whenever the legacy logs are generated. The log type will match that of the existing legacy log. XPKT353 is a new log which will be generated on call failures due to Invalid LTID or no LTID on the incoming side.

SPBX801 New CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools, A00016594 (CS2M, GWC, AS5200/SSL)

This log is generated when the VMG state is changed.

CLBK600 Changed Japan NTC Enhancements, A00016771 (WT)

A new CLBK600 log reason is introduced to indicate a phrase must be datafilled in table ANNAUDID.

XTS309 XTS609

Deleted CR activity

XTS309 and XTS609 are being removed from customer documentation since these logs are never generated by the SST product and can only be generated manually with a debug test tool.

CICM657 Changed CR activity

CR Q01793472 changed the Specific Problem field value to add this statement: IP Address = X.X.X.X:yyyy, where X.X.X.X is the IP address of the terminal and yyyy is the port number. This change was introduced into CICM release 10.1 MR2. At this time, CICM10.1 applies to SN10, CVM11, CVM12 and CVM13.

PP396 New CR Activity

CR Q01906401 created the PP396 log in IEMS11 for the ERS8600 to notify when SLPP detected a loop on a port and the ERS8600 port is thus going to shut down. It was patched back to IEMS10.

Table 3-3New or modified logs for CVM11

Log number Status Feature title and description of change

(Sheet 2 of 2)

94




information on these changes, refer to the “Performance Management” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

Table 3-4New or modified OMs for CVM11

OM group Feature title OM change

LTID1

LTID2

SIP PBX capacity / scaling development, A00014277

This activity introduces two new OM groups called ‘LTID1’ and ‘LTID2’ for SIPPBX. These OM groups use the existing registers in TRK OM, pegged based on LTID.

SIPPBXCallMgmtInstance

CS2K SIP Enabled VoIP VPN - LTID Decoupling, A00016592

A new OM group, SIPPBXCallMgmtInstance, is introduced in the Session Server. These OMs can be turned on or off, per-PBX, via the MCP System Management Console under the dialog box at Network Data and Mtc/Call Server 2000 Integration/CS2K SIP PBX. OMs can also be turned on or off via the CMT interface. The name on each OM row will correspond to the SIP PBX’s configured “shortname”.

XPMOVLD2 OM Enhancements for MTX (also applies to CVoIP), A00018529 (GWC, CS2000)

XPMOVLD2 adds new registers PTRMMSG and PORGMSG to provide more accurate tracking of number of calls shed by GWC during a nodal GWC overload event.

ISUPSOC OM Enhancements for MTX (also applies to CVoIP), A00018529 (GWC, CS2000)

New OM group ISUPSOC has 6 registers to keep track of the number of origination attempts shed by the GWC during a core overload event for ISUP terminals.

TRK

SIPGW_STACK_STATS

Session Server Trunks (SST) Additional Operational Measurements (OMs), A00018715 (CS2000, SST)

MAXBU of the OM group TRK is enabled for SIPT DPT trunk group.

Existing register HWM_INUSE_CDB in SIPGW_STACK_STATS is re-named as SIMULTANEOUS_CALL_HWM

SS-T OM groups NGSS/SS Trunks CSV PM Integration, A00018834 (Product = IEMS)

Implements the IEMS handling of SST CSV-formatted metrics data. Also obsoletes existing SNMP-based PMs for the SST.

SPFS OM groups SPFS CSV PM Integration, A00018837 (Product = IEMS)

Implements the IEMS handling of SPFS CSV-formatted metrics data. Also obsoletes existing SNMP-based PMs for SPFS.

(Sheet 1 of 5)

95




TRK2NET1, registers NVFLATB and CNCTAT

TRK2NET2 register CNCTAT2

Split Trunk Group Engineering Enhancement, Q01956016-01, CS2000 patch TNS29

The formulas for how registers NVFLATB and CNCTAT of CS2000 OM group TRK2NET1 and register CNCTAT2 of OM group TRK2NET2 have changed. This change is enacted through CS2000 patch TNS29. This patch affects the TL22 software layer and thus CVoIP releases SN09U and higher. These registers are pegged now as follows:

• TRK2NET1.NVFLATB: The NVFLATB will peg against the like fabric tuple of the Trunk Group in the TRK2NET1 OM group whenever:

— there are no idle trunk members on either fabric, in which case the call will overflow to another trunk group or treatment. In this scenario NVFLATB will be pegged against like fabric. NVFLATB register will not be pegged against non-like fabric.

— -there is no idle trunk member on the like fabric but an idle trunk is found on the non-like fabric to complete the call. Again, NVFLATB against like fabric will be pegged.

• TRK2NET1.CNCTAT: CNCTAT counts outgoing seizure attempts on the trunk group that appear to result in successful connection. The register increases before the system recognizes whether the seizure is successful. A glare or seize failure does not decrease the count by 1. This behavior is different than the OM group TRK register CONNECT.

• TRK2NET2.CNCTAT2: CNCTAT2 counts outgoing seizure attempts on the trunk group that appear to result in successful connection. The register increases before the system recognizes whether the seizure is successful. A glare or seize failure does not decrease the count by 1. This behavior is different than the OM group TRNK2 register CONNECT2.



(Sheet 2 of 5)

96




SIPGW_REJECT_SIPMSG

SIPGW_TRANSACTION_IC

SIPGW_TRANSACTION_OG

SIPGW_TRANSACTION_USAGE

SIPGW_RESPONSE_IC

SIPGW_RESPONSE_OG

SIPGW_CALLP

SIPGW_ETC

SIPGW_OVERLOAD

Session Server Trunks (SST) Additional Operational Measurements (OMs), A00018715 (CS2000, SST)

Six new SST OM groups are created:

• SIPGW_REJECT_SIPMSG: Provides the count of number of rejected message for each message type on a per SIPLINK basis with 9 registers.

• SIPGW_TRANSACTION_IC: Provides count of number of transactions created by incoming messages per message type with 10 registers.

• SIPGW_TRANSACTION_OG: Provides count of number of transactions created by outgoing messages per message type with 10 registers.

• SIPGW_TRANSACTION_USAGE: Provides count of the number of active Transactions per message type with 10 registers.

• SIPGW_RESPONSE_IC:Provides count of number of incoming response messages received with 10 registers.

• SIPGW_RESPONSE_OG:Provides count of number of outgoing response messages received with 10registers.

OM Group SIPGW_CALLP adds register DPT_TID_OVFL.

OM Group SIPGW_ETC adds register CDB_OVFL.

OM Group SIPGW_OVERLOAD adds the following registers:

• TLS_SIMULTANEOUS_CONNECTION_HWM

• MEM_USAGE

• DISKSPACE_USAGE



(Sheet 3 of 5)

97




Refer to the Change column

SPFS PM enhancement, A00019321 (CS2000, SPFS)

Collects a set of new PMs: 5 single values and 6 data tables (7 in SPFS 12 and up). The single values are:

• HAstatus

• 1minLoadAvg

• 5minLoadAvg

• 15minLoadAvg

• Alarm350

The data tables are:

• cpuUsage table reports the Mean/Minimum/Maximum values over the past PM interval.

• memoryUsage table reports the Mean/Minimum/Maximum values over the past PM interval.

• diskUsage table reports the complete output from Solaris utility “df –k”, used and available disk space on each file system. It is captured at the end of each PM interval.

• traffic table reports the number of packets passing through each network interface over the past PM interval. Typically uplink0, uplink1 and lo0 are network interfaces for SPFS.

• diskIO table reports the disk io statistics over PM interval. (x) is for the Max value and (a) is for the Average value.

• ApplicationPMs data table reports performance data grouped with applications. This table content is configurable and an application is defined as a list of running processes provided with a configuration file.

• SystemLWP data table (for SPFS12 and up) reports the number of processes and LWP processes running on the system. It provides the mean, minimum and maximum for the processes and LWPs.



(Sheet 4 of 5)

98




1Office parameter (OPARM) changes 1

This sections list any new, modified or deleted Office parameters (OPARMS) related information associated with this release. For more detailed information on these changes, refer to the “Configuration Management” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

IEMS performance files for MG15000/MDM

CR Q02007416-01 CR Q02007416-01 changed the TableId value in IEMS10 xml/csv performance files for MDM/MG15000 from the "-officeid" parameter of the MDM's pmsp process to be "<ActiveMDMManagedObjectName>_<ShelfId>". <ShelfId> is the name of the MG15000 which is being reported on in the performance file and <ActiveMDMManagedObjectName> is a name of the MDM from which the performance files are currently being retrieved from. For a detailed description of <ActiveMDMManagedObjectName>, a definition can be found in Chapter 2: IEMS Functionality under IEMS Northbound Performance File Format 2.

Table 3-5New or modified Oparms for CVM11

Parameter name Status Feature title and description of change

ATD_CONFIG New MG4K Automatic Trunk Deload, A00014116(CS2000)

ATD_CONFIG in OFCENG controls the trunk deload process on MG4K nodes with 5 sub-fields:

• ATD_ACTIVE

• TIMER T1

• INITIAL_BLOCK_PERCENTAGE

• TIMER T1

• SUBSEQUENT_BLOCK_PERCENTAGE

(Sheet 1 of 2)



(Sheet 5 of 5)

99




Service Order (SO) changes 1This section lists any new, modified or deleted Service order (SO) related information associated with this release. For more detailed information on these changes, refer to the “Configuration Management” section in Volume 2

MAX_RESLINES Changed Line Capacity Enhancement - Phase 2, A00018520 (CS2000)

The maximum value for office parameter MAX_RESLINES is increased to 300,000 to yield support for capacity increase of RES lines.

XAC_FAST_ONP_ENABLED New PNSCRN ONP Activity, A00019365 (CS2000)

This parameter in OFCENG is used to enable/disable the Fast XA-Core TABXFER method which speeds up table PNSCRN transfer.

ENABLE_10_DIGIT_XLA_FOR_MWT New Per CR Q01811457, ENABLE_10_DIGIT _XLA_FOR_MWT allows the user to choose the translation type (7-digit or 10-digit translation) that controls how messages are retrieved from the Voice Mail Server (VMS). When there is a message left at the VMS, the user enters the MWT key to retrieve messages from the VMS.

ANN_CONF_CODECGRP New N/A for CVoIP; CDMA only.

BEARER_ENCRYPTION_CONTROL New N/A for CVoIP; Enterprise only.

Table 3-5New or modified Oparms for CVM11

Parameter name Status Feature title and description of change

(Sheet 2 of 2)

100




of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

Table 3-6New or modified SERVORD commands/options for CVM11

SERVORD command/option Status Feature title and change description

NEW/EST/ADD Changed Flexible endpoints for small line GW and Endpoint utilization improvement, A00016277 (CS2M)

NEW/EST/ADD commands for small lines must be issued in Servord+ format, i.e., using gateway endpoint name pairs instead of LENs. Establishing the relationship between the LEN and the gateway endpoint is done at service creation time thru NEW/EST/ADD/CLN commands. Once this relationship is established, other line provisioning commands (e.g., ADO, OUT, DEL, etc) can contain either LENs or gateway endpoint name pairs.

AGNTPCL New AS2K Provisioning and SOC, A00016421 (CS2000)

SERVORD+ will accept the new AGNTPCL option during DPL lines provisioning: When provisioning an IETF/ISC SIP line, both the DPL and AGNTPCL options must be present in the SERVORD+ NEW/ADD/EST command. They can not be added later via ADO.

However for IETF SIP Lines, this format will not be made mandatory since it will impact the existing IETF SIP line provisioning format & hence the 3rd party OSS applications. So, when the DMS Core receives DPL option with no AGNTPCL option, the latter will be added automatically by the DMS core and the PROTOCOL sub-field will be set to SIP and VARIANT as IETF.

The new SERVORD option AGNTPCL will support a limited set of SERVORD commands. Refer to the table at the end of the Functional Description of this feature (in Vol. 2) for a complete list.

ADO Changed Flash Ignore with Call Waiting, A00018518 (CS2000, WT)

ADO is used to assign FIG & CWT to an existing line.

101




Human-machine interface (HM) changes 1This section lists any new, modified or deleted Human-machine interface (HM) related information associated with this release. For more detailed information on these changes, refer to the “Configuration Management” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)SN11-OSSV2).

(Various) Changed Line Capacity Enhancement - Phase 2, A00018520 (CS2000)

The OSSGATE (SESM) provisioning interfaceis used to increase line limits from 180,000 to 300,000.

Table 3-7New or modified HM commands for CVM11

HM command or GUI Status Feature title and change description

GWCEM GUI Changed Flexible endpoints for small line GW and Endpoint utilization improvement, A00016277 (CS2M)

The Line Tab window is used to retrieve all small lines which wer added by NEW/EST/ADD-ed by Servord+ command.

Add Gateway Controller GUI Changed SIP Line: GWC line capacity improvement, A00016419 (CS2000, GWC, CS2M)

Two new GWC profiles can be selected from this GUI when the customer adds a GWC: SIP_LINENA or SIP_LINEINTL.

Line Audit GUI

Batch Provisioning Tool (BPT)

Changed SESM Robustness, A00016506 (CS2M)

To make the audit functionality more clear to customers, “Select All” is changed to “Integrity Audit”. Customers can choose whether the DN data will be audited or not.

BPT is modified to support Gateway and Carrier XML provisioning.

Table 3-6New or modified SERVORD commands/options for CVM11

SERVORD command/option Status Feature title and change description

102




CMT GUI Changed CS2K SIP PBX Provisioning, A00016582 (GWC, CS2M, AS5200/SSL)

The CMT GUI is modified as follows:

• Add Media Gateway Controller--Changed by adding the VoIP VPN capability to the existing gateway controller profiles. Options are LINE_TRUNK_AUD _NA or LINE_TRUNK_AUD_INTL. Also added optional “Flow through” checkbox to dialog box.

• Delete Media Gateway Controller --Changed by adding gateway profile VoIP VPN.

• Associate Media Gateway--Changed by adding gateway profile VoIP VPN.

• Add Carrier--Changed by adding VoIP VPN carrier type.

TMM CLUI Changed CS2K SIP PBX OAM (Operations, Administration, Maintenance) & Tools, A00016594 (CS2M, GWC, AS5200/SSL)

“TMM CLUI” is introduced to support SIP PBX.

Part of the TMM GUI function is introduced into TMM CLUI to provide the machine interfaces to maintain the trunk info of SIP PBX on the Core.

GWCSTAT

GWCALL

New Switch wide GWC status report tool, A00018330 (GWC, CS2000)

GWCSTAT is a new CI level and has sub commands on CORE to give the ability of querying switch wide GWC status information in a clean, easy to read format, and store it into a file if necessary.

GWCALL is another new level under MAPCI;MTC; PM, GWC directory. It continuously monitors and displays operational and activity status of GWCs.

OP Command Changed Enhancements to the TTP Outpulse Command, A00018761 (CS2000, GC, WT)

Enhances the OP command by adding an optonal parameter to five ISUP parameters of IAM.



103




Software Optionality Control (SOC) changes 1For information on new, modified or deleted Software Optionality Control related information associated with this release, refer to “Software Optionality Control (SOC) changes” on page 103 of this document.

For more detailed information on these changes, refer to the “Configuration Management” section in Volume 2 of the Nortel OSS Overview: Customer-impacting features (PLN-(I)CVM11-OSSV2).

SS Trunks Performance Interface panel, Collection Job

panel, and Report Job panel

Changed NGSS/SS Trunks CSV PM Integration, A00018834 (Product = IEMS)

For SS TRUNKS devices, the Performance Interface panel now contains a selector for the collection type. The choices are SNMP or CSV.

The Collection Job panel now supports CSV in the Collection Type drop-down list.

In the Report Job panel, if the selected collection job is CSV-based, then the “Report Type” list is updated to contain RAW as the only choice. If the selected collection job is SNMP-based, then the “Report Type” list will continue to contain XML and CSV as the choices.

SPFS Performance Interface panel, Collection Job

panel, and Report Job panel

Changed SPFS CSV PM Integration, A00018837 (Product = IEMS)

For SPFS devices, the Performance Interface panel now contains a selector for the collection type. The choices are SNMP or CSV.

The Collection Job panel and Report Job panel changes are identical to those for A00018834.



104




Family Product Manual Contacts Copyright Confidentiality Legal

Carrier Voice over IPNortel OSS OverviewCustomer-impacting features

Copyright © 2009 Nortel Networks, All Rights Reserved

Document number: PLN-(I)CVM11-OSSv1Product release: (I)CVM11Date: December 2009

To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback

This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components asprogress in engineering and manufacturing may warrant.

Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, and Unified Networks are trademarks of Nortel Networks.

Printed in the United States of America/Canada

pln-(i)cvm11-ossv1_01.16

Documents

trademarks of nortel

nortel networks logo

property of nortel networks

nortel confidential

cs2k sip pbx provisioning

cs2k hosted sip

unified networks

confidential information