packetstar psax h.248, user guide - nokia

Doc. No.: 255-700-368

PacketStar®

H.248 Media Gateway Control User Guide for the PacketStar PSAXPacketStar® PSAX Multiservice Media Gateways

Issue 1, July 2002

System Software Release 8.0.0

Navis™ AQueView® EMS Release 6.0

Copyright © 2002 by Lucent Technologies. All rights reserved.

For trademark, regulatory compliance, and related legal information, see the "Copyright and Legal Notices" section.

PacketStar® H.248 Media Gateway Control User Guide, Issue 1 Release 8.0.0

255-700-368 i

Copyright and Legal Notices

Copyright

Copyright © 2002 by Lucent Technologies. All rights reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fash-ion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of the originating organization and the business management owner of the material.

This document was prepared by the Information Design and Development Team of Lucent Technologies, PacketStar PSAX products. Offices are located in Landover, Maryland, USA.

Trademarks

PacketStar, Lucent, Lucent Technologies, and the Lucent Technologies logo are registered trademarks of Lucent Technologies in the USA. Other product and brand names mentioned in this guide are trademarks or registered trade-marks of their respective owners.

Chapter Trademarks

ii 255-700-368

H.248 Media Gateway Control User Guide, Issue 1 Release 8.0.0

255-700-368 iii


Contents

Copyright and Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

1 H.248 Media Gateway Control Protocol Overview . . . . . . . . . . . . . . . . . 1-1H.248 Terms Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Applicable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Purpose and Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

How PRI Data Offload Eases Overworked PSTN Networks . . . . . . . . . . . . . . . . . . . . . . . . .1-1

H.248 Media Gateway Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

2 H.248 Media Gateway Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . 2-1PSAX System Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Setup Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Terminations Supported by the PSAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

PSAX System Modules Supported on Intermachine Machine Trunk (IMT) Terminations 2-2

PSAX System Modules Supported on TDM Terminations Over ISDN PRI . . . . . . . . . . . .2-3

SIGTRAN Support to Transport ISDN D-channel messages to the MGC . . . . . . . . . . . .2-3

ATM Ephemeral Terminations Over AAL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

ATM Ephemeral Terminations Over AAL2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

Naming of Terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

H.248 Commands Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Subtract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Audit Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

Service Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Transaction Re-try . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

PSAX System H.248 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Primary MGC and Backup MGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

Call Processing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

Package Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9

SDP Support Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

Interaction with Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10.2-10

.2-10

.2-9

.2-7

.2-6

.2-6

.2-6

.2-6

.2-6

.2-6

.2-5

.2-5

.2-5

.2-5

.2-5

.2-5

.2-4

.2-4

.2-3

.2-3

.2-3

.2-3

2-2

.2-2

.2-1

.2-1

2-1

.1-2

.1-1

.1-1

.1-1

.1-1

1-1

i

Contents

iv255-700-368


H.248 and CGAPI Protocol Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

H.248 and ATM Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

ISDN PRl and ISDN PRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

IUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

SCTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

OAM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Configuration Management Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Performance and Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

PSAX System Software Fault Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Stable Call Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

IUA/SCTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

IUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

SCTP Interface and Stream Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

PSAX System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

3 Services Supported for the H.248 Media Gateway Control Protocol . . .3-1ITU-T H.248 Media Gateway Control Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

How H.248 Contexts Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Modules Supporting the H.248 Media Gateway Control Protocol . . . . . . . . . . . . . . . . . . 3-3

AAL1 and AAL2 Configuration Scenarios in this User Guide. . . . . . . . . . . . . . . . . . . . . . . 3-3

Document and Text Entry Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

AAL1 TDM-to-ATM-to-TDM Traffic on an ATM UNI 4.0 Interface . . . . . . . . . . . . . . . . . . . 3-4

Turning On the H.248 Media Gateway Control Protocol Feature . . . . . . . . . . . . . 3-5

Configuring the H.248 Media Gateway Control Parameters . . . . . . . . . . . . . . . 3-10

Enabling Channelization and the Signaling Gateway Feature . . . . . . . . . . . 3-14

Configuring the Originating and Terminating Media Gateway Master ATM Addresses . . 3-20

Configuring the Originating Media Gateway and the Terminating Media Gateway for ATM UNI 4.0 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Configuring SVC Routing for the Data Traffic on the OMG and TMG Sides . . . . . . . . . . 3-24

Creating IISP VBR Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Adding NSAP Address Entries 24

Configuring the Voice CBR Traffic for SVC Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

Creating IISP CBR Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

Creating Entries in the IISP CBR Routing Table 26

AAL1 TDM-to-ATM-to-TDM Call Setup Scenario Using the PNNI Interface . . . . . . . . . . . 3-28

Configuring an OMG ATM Module for the PNNI Interface . . . . . . . . . . . . . . . . . . . . 3-29

PNNI Interface Configuration, TMG Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

Saving the System Configuration and Logging Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

4 H.248 Protocol and AQueView® EMS Configuration . . . . . . . . . . . . . . . .4-1 Setting the Call Control Value for H.248 Media Gateway Control Protocol . . . . . . . . 4-24-2

4-1

3-34

3-30

3-29

3-28

3-26

3-26

3-24

3-24

3-22

3-20

3-14

3-10

3-5

3-4

3-3

3-3

3-3

3-2

3-1

3-1

3-1

2-13

2-13

2-12

2-12

2-12

2-11

2-11

2-11

2-11

2-11

2-10

2-10

Contents

255-700-368 v


Saving Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17.4-17

Contents

vi255-700-368



255-700-368 1-1

1 H.248 Media Gateway ControlProtocol Overview

H.248 Terms DefinedThe terms used in this guide to describe the functionality of the hardware and software are:

• A Media Gateway refers to the PSAX system.

• A Media Gateway Controller refers to the system (hardware and software) providing call control funtionality (for example, the ConnectStar system).

• Media Gateway Control Protocol is used to communicate between the Media Gateway and the Media Gateway Controller.

Applicable Specifications

The following specifications apply to the hardware and software functionality described in this guide:

ITU-T H.248, Audiovisual and Multimedia Systems Infrastructure of audiovisual ser-vices– Communication procedures: Gateway control protocol. June 2000.

Purpose and AudienceThis user guide is for network engineers desiring to configure PRI offload functions.

How PRI Data Offload Eases Overworked PSTN Networks

Note: The application described below requires the ISDN Q.921 User Adaptation Layer Configuration protocol to be enabled at the sys-tem-wide level. This feature is planned for a future release.

The H.248 Media Gateway Control protocol enables more efficient use of PRI ports and intermachine trunks (IMTs) when internet data traffic is transmit-ted through the PSTN network. The volume of internet data traffic consumes excessive PSTN resources for two reasons:

1. PSTN trunks, optimized for voice services, become quickly saturated with internet data traffic for time periods much longer than voice traffic con-sumes.

2. Because data cannot be compressed, the PSTN trunks cannot be opti-mized for data traffic as voice traffic can.

The PSAX and the MGC solution accepts the PRI data traffic from the over saturated PSTN CO trunks. The PSAX, under the direction of the MGC, then sends the data traffic to ISP RAS switch networks outside of the PSTN switches, thus freeing PSTN resources for voice traffic. The MGC takes over the function of SS7, and the PSAX takes over the function of the PSTN CO (see Figure 1-1).

Chapter 1 H.248 Media Gateway Control Protocol OverviewH.248 Media Gateway Protocol Overview

1-2 255-700-368


H.248 Media Gateway Protocol Overview

The PacketStar PSAX Media Gateway product line supports the ITU-T Stan-dard H.248, Audiovisual and Multimedia Systems. H.248 is a communications control protocol for convergent networks that separates call control and media- and bearer-control functions.

After the call control and media- and-bearer control functions are separated, they are transmitted over different network elements. The advantage gained by separation is to decentralize control from the SS7 network to local net-works. Decentralization enables transmission cost savings resulting from enabling gateway peripherals from a central controller to terminate trunking circuits near the circuit switches from which they originate.

The PacketStar PSAX Media Gateway supports these H.248 functions:

• PSTN terminations (see Glossary) to PSTN terminations

• Transcoding of media streams between ATM network and ATM packet net-works

• Terminations processed:

~ PSTN-to-PSTN terminations

~ PSTN-to-ATM terminations

• Control the media streams per the controller’s request

• Apply signals (tone and/or announcement) to the terminations

Figure 1-1. H.248 PRI Offload Solution

Multiservice Media Gateways

ISP InternetISP

RASRAS

Offload from ILECTandem Offices

Direct Offloadfrom End Offices

Ingress Switches

SS7 Network

IMT

IMT

Media Gateway Controller

RAS RAS

PSTN

EgressSwitches

PRI/DS-3PRI/DS-3

InternetUser

InternetUser

255-700-368 1-3



• Detect media stream events (tone, continuity check, digits, fax modem) per the controller’s request

• Extract CAS signal from the media stream

• Extract D-channel signaling messages and transport to controller

• Collect, match, and report in-band (MF/DTMF) digits per MGC request

• Create and destroy terminations per MGC request

• Manage ATM resources


1-4 255-700-368



255-700-368 2-1

2 H.248 Media Gateway ProtocolSupport

PSAX System Hardware RequirementsThis feature is supported on all PSAX Multiservice Media Gateways with redundant CPU2 or CPU3L modules.

The H.248 protocol can be configured on the modules on the bullet list below on the CE and PRI interfaces, with the following constraint:

~ For the 6-Port Enhanced E1 Multiservice and the 21-Port High-Density E1 Multiservice modules, if the SG Feature field is Enabled and the MG control protocol type is H.248, the PRI interface cannot be configured.

• 6-Port Enhanced DS1/T1 Multiservice

• 6-Port Enhanced E1 Multiservice

• 3-Port Channelized DS3/STS-1e CES

• 3-Port Channelized DS3/STS-1e CES Protection

• 1-Port Channelized DS3 CES

• 1-Port Channelized STS-1e T1

• 1-Port Channelized OC-3/STM-1 CES Single-Mode

• 1-Port Channelized OC-3/STM-1 CES Multimode

• 12-Port Medium-Density DS1 Multiservice

• 21-Port High-Density E1 Multiservice

For modules other than the ones listed above, the SG Feature field on the Port and Channel Configuration window cannot be Enabled if the MG con-trol protocol type is H.248.

The user should consult the appropriate module user guide for configuration specifics for each module.

Setup SummaryThe following steps are a task summary to set up connections using the H.248 protocol:

1. Decide what H.248 application you want to use.

2. Identify the capabilities of your MGC and your Media Gateway. This guide provides guidance for configuration of the certified modules (see the PSAX Hardware Requirements) for H.248 setup. For the MCG that you are using, see the vendor literature for configuration instructions.

3. Design your call flow(s). This guide provides sample call flows for AAL1 and AAL2 ISUP CES-to-ATM AAL1 SVC Call Setup and Call Clearing, and PRI Offload (IPO).

4. Configure your MGC hardware and software. Your MGC must support your call flow design.

Chapter 2 H.248 Media Gateway Protocol SupportTerminations Supported by the PSAX

2-2 255-700-368


5. Setup your primary and backup physical configuration for the PSAX sys-tem and your MCG. For PSAX system chassis configuration, see your PSAX User Guide, Chapter 4 for the console interface. For AQueView EMS configuration, see Chapter 4 of the appropriate user guide. For your MGC, see the vendor literature.

6. Configure your MGC IUA.

7. Send test messages between terminations through your MGC.

Terminations Supported by the PSAXThe PSAX system supports the following services:

• PSTN-to-ATM calls originated from PSTN TDM terminations, usually con-trolled by SS7/ISUP, and terminated to an ATM network, on an SVC usu-ally using UNI 4.0 or PNNI 1.0 (on AAL1 and AAL2).

• ATM-to-PSTN calls originated from an ATM network, on an SVC usually using UNI 4.0 or PNNI 1.0 (on AAL1 and AAL2), and terminated to PSTN TDM terminations, usually controlled by SS7/ISUP.

• PSTN-to-PSTN calls originated from PSTN TDM terminations, usually con-trolled by SSTISUP, and terminated to another PSTN TDM interface, usu-ally also controlled by SS7/ISUP.

• Single-stage dialing, or calls whose called party numbers are dialed directly in the beginning of the call origination by the initiating subscriber (Party A).

• Transparent Fax/Modem calls. The PSAX system provides transparent transcoding between TDM network and packet (ATM or IP) network for fax/modem calls.

• Internet call diversion (ICD, or Internet Offload) services. The PSAX system terminates internet remote access call via ISDN PRI terminations to a PBX and RAS. The PSAX system supports TDM terminations on the PRI inter-face at DS0 level.

• Two-stage dialing services (calling cards). Two-stage calling final called party number is dialed in on network request. The PSAX system plays announcements and detect/collect dialed digits, and reports them to the MGC. The PSAX system detects and reports new call attempts as indicated by the ‘#’ digit.

PSAX System Modules Supported on Intermachine Machine Trunk (IMT) Terminations

The PSAX system supports TDM terminations over IMT termination types and will assign EC to TDM TDM terminations on MGC request. The PSAX system supports the A-law and mu-law DS0-based PSTN TDM terminations at 64 Kbps and 56 Kbps on these modules:





255-700-368 2-3


Chapter 2 H.248 Media Gateway Protocol SupportTerminations Supported by the PSAX





PSAX System Modules Supported on TDM Terminations Over ISDN PRI

The PSAX system supports the A-law and Mu-law DS0-based PRI TDM ter-minations on these modules:









The time slot for the D-channel is not provisioned as a TDM termination. Instead, the PSAX system processes the data and/or passes the data to the MGC.

SIGTRAN Support to Transport ISDN D-channel messages to the MGC

The PSAX system supports these signal transmission protocol RFCs:

• IUA per IETF-RFC 3057

• SCTP per IETF-RFC 2960

• SIGTRAN per IETF-RFC 2719, for the part relating to IUA/SCTP architec-ture

ATM Ephemeral Terminations Over AAL1

The PSAX system supports ATM AAL1 terminations on all ATM interface modules, as well as ATM AAL1 calls created and/or released by MGC request. On ATM network failure, the MG notifies the MGC of such an event. The PSAX system does not notify the MGC when the bearer connection associ-ated with the ephemeral termination is released from the ATM network with cause due to “Normal”, or “Normal, Unspecified”. Otherwise, the MG notifies the MGC.

ATM Ephemeral Terminations Over AAL2

The PSAX system supports ephemeral ATM AAL2 terminations on all ATM interface modules according to standard atmf vtoa-113 under these condi-tions:

• If calls are SVC VCCs terminations

• If a separate AAL5 signaling VCC carries channel signaling messages; the AAL5 VCC is created in the same way as the associated AAL2 VCC

• If UNI 4.0/Q.2931 is used for AAL2 channel setup and release

Chapter 2 H.248 Media Gateway Protocol SupportH.248 Commands Supported

2-4 255-700-368


• If channels are created by MGC request to add an ATM ephemeraltermination

• If the MGC requests channel release

• If the ATM network fails, the PSAX system notifies the MGC of such an event

• If the PSAX system requires more AAL2 VCC bandwidth, when such band-width is not already allocated, the PSAX system establishes it; otherwise, an existing VCC is re-used regardless of which MG established it

• If multiple VCCs exist, the channel is established on any VCC as long as the CAC allows it

The PSAX system does not notify the MGC when an ephemeral termination is released from ATM network with cause “Normal,” or “Normal, Unspeci-fied.” Otherwise, the MG notifies the MGC.

Naming of Terminations

• The PSAX system allows for flexible TDM termination naming:

~ io module location and slot number

~ io port number (physical and logical) within the module

~ Time slot number in the port

• The PSAX system supports “sectioned” termination ID naming. Termina-tion ID can be divided into sections by the slash ‘/’ character. The semantics of each section is to be defined and interpreted by the user

• The PSAX system supports the wildcard naming mechanism:

~ The wildcard “ALL” asterisk ‘*’ character is supported; the ‘*’ will match all termination IDs

~ The wildcard “CHOOSE” ‘$’ character is supported; the `$' will match one (any) termination ID

~ The `*' and `$' characters are limited within the section where either searches. For example, the search string “T/1 */123” finds “T/12/123” but does not find “T/1/2/123”, except when the search looks at the begin-ning of the string, for example “T*” finds “T/1”, “TDM/l”, and “T/1/2”.

Note: For more information on naming conventions, see the Field Description Table for the Termination ID Slot Configuration Win-dow in Chapter 3 of this guide.

• The PSAX system supports ROOT Terminations as described by ITU-T H.248 section 6.2.5.

• The PSAX system supports termination IDs up to 32 characters long

H.248 Commands SupportedThe PSAX system complies with ITU-T H.248, section 7 for the command syntax and procedures in general. This section describes all commands to be implemented for the services described in the Services Supported by the PSAX:

255-700-368 2-5


Chapter 2 H.248 Media Gateway Protocol SupportH.248 Commands Supported

Add

The PSAX system supports the Add command from the MGC and the fol-lowing reply types and error conditions:

• The PSAX system creates ephemeral terminations and new contexts on request.

• The PSAX system replies to Add commands under these conditions:

~ Only after all terminations and contexts are created and allocated

~ When terminations added to a context, with the exception of “Early Reply to Add Command” described below:

• After Early Reply is sent and after the EECID is requested

• Early reply includes early ATM termination ID before the ATM ephem-eral connection is created

• The PSAX system supports these error conditions:

~ When the maximum number of terminations is exceeded

~ When resources are unavailable

~ If ATM network failure occurs

Modify

The PSAX system supports the Modify command from the MGC and replies to the Modify command after all modifications are done.

Subtract

The PSAX system supports the Subtract command from the MGC under these conditions:

• If an ephemeral termination is subtracted, the PSAX system releases all allocated resources.

• If the context has no remaining termination, the PSAX system releases all allocated resources.

• The PSAX system moves permanent terminations to the NULL context when subtracted

• The PSAX system replies to the Subtract command, but if the termination is not found, the PSAX system replies with an error message.

Move

The PSAX system supports the Move command from the MGC.

Audit Value

The PSAX system supports and replies to the media descriptor Audit Value command from the MGC.

Notify

The PSAX system notify MGC when certain events occur, but the MGC must request notification of such events.

Chapter 2 H.248 Media Gateway Protocol SupportPSAX System H.248 Requirements

2-6 255-700-368


Service Change

The PSAX system notifies the MGC when the service status of termination(s) has changed, as described by ITU-T H.248, Section 7.2.8.

Pending

The PSAX system sends up to two Pending messages when the MGC transac-tion cannot be completed before time out occurs. On the third transaction time-out, the transaction fails. Failure is initiated by the PSAX.

Transaction Re-try

The PSAX system will retry once on transaction time-out. One retry is required.

After one retry with the same outcome, the transaction fails. On such failure, the PSAX system terminates the transaction and releases the resources allo-cated to the particular transaction.

PSAX System H.248 RequirementsThe PSAX system supports the following H.248 interfaces with the MGC:

• Transport H.248 over TCP

• SDP for ATM bearer connection (a subset of IETF RFC 3108) is used as a stream description

• Text encoded operation is supported (port number 2944); H.248 text encoded messages can be case insensitive, except in SDP section

• The PSAX system supports single transactions per H.248 message

• Multiple commands within one single transaction are supported

• Multiple commands within one single action are supported

• The PSAX system supports the Cold Start procedure

The PSAX system supports the Three-Way Handshake (Transaction-Response-Acknowledgement). Regardless of whether TCP, and/or SCTP is used to transport the H.248 messages, the PSAX system implements the Transaction-Response-Acknowledgement parameter and 3-way handshaking described in ITU-T H.248 D.1.2.2.

This preceding procedure confirms the receipt of the Reply to Transactions, in addition to the expiration of a LONG timer.

Primary MGC and Backup MGC

The PSAX system supports up to four MGCs.

Security

See the OAM Requirements section for security requirements.

255-700-368 2-7


Chapter 2 H.248 Media Gateway Protocol SupportCall Processing Requirements

Call Processing RequirementsThis section identifies the call flow requirements: echo cancellation, tones, and announcements.

• The PSAX system supports Continuity Test procedures.

~ The PSAX system supports loopback mode on TDM terminations on MGC command

~ The PSAX system applies continuity test tone on TDM termination on MGC command (continuity test package required)

~ The PSAX system detects and reports the completion of continuity test tone for TDM termination on MGC request (continuity test package required)

• The PSAX system sets up ATM SVCs for ATM ephemeral connection on MCC request

• All of the following conditions must exist before the PSAX system initiates the SVC setup for the ephemeral termination:

~ The local media “bearerType” attribute is SVC ON

~ The remote media “eecid” attribute is provided by MGC

~ The remote ATM NSAP address is provided by MGC

After the above conditions are met, the PSAX system initiates the setup of the ATM SVC for the creation of the ATM ephemeral connection.

• The PSAX system assigns an EECID on MCC request

~ The PSAX system replies to the MGC command immediately without waiting for the creation of the connection

~ The PSAX system replies after the ATM connection is established if the EECID is NOT requested by the MGC

• The PSAX system assigns an ATM NSAP Address on MCC request

~ Whether the PSAX system replies to the MGC command immediately or not depends on the EECID, NOT the NSAP address

• The PSAX system creates / releases AAL1 VCC for ATM ephemeral termi-nations:

~ The PSAX system uses PNNI 1.0 and UNI 4.0

~ EECID encodes in the GIT (as in ITU-T Q.2941.1)

~ Remote NSAP address is in the called party number

• The PSAX system creates / releases AAL2 VCC Channels for ATM ephem-eral terminations by means of PNNI 1.0 or UNI 4.0

• An AAL2 VCC is created when a new ephemeral termination is needed while:

~ No AAL2 VCC is available to the remote MG (as indicated by the NSAP address)

~ All AAL2 channels in the existing VCC are busy

~ CAC failure over the existing VCC

~ The PSAX system AAL2 VCC supports ITU profile 3 and profile 7

• AAL2 VCC is released when:

Chapter 2 H.248 Media Gateway Protocol SupportCall Processing Requirements

2-8 255-700-368


~ Multiple AAL2 VCC available to the same remote MG

~ All CID within that VCC are free

• AAL2 channels are set up and released when:

~ For setup, by MGC request with Add command see other requirements

~ For release, by MGC request with Subtract command see other require-ments

• The PSAX system creates AAL5 Signaling VCC for ATM Ephemeral Termi-nations

• AAL5 VCC is created when new ephemeral termination is needed while:

~ No AAL5 VCC is available to the remote MG (as indicated by the NSAP address;)

~ The PSAX system uses PNNI 1.0 or UNI 4.0 to do so

• The PSAX system support FAX/Modem call by detecting fax/modem tone

~ The PSAX system is able to detect fax/modem tone (ANS and ANSAM) and adjust the codec algorithm accordingly with or without MGC com-mand;

~ On detecting fax/modem tone, the PSAX system removes echo canceller without MGC intervention

~ On detecting fax/modem tone, the PSAX system changes the CODEC mode to the mode that allows fax/modem to pass through (G.711 for modem; G.726 ADPCM–32 Kbps or higher for fax).

~ For AAL2, the VCC supports the profile that allows adjustment

~ The PSAX system supports fax tone modem detection package

• On MGC prior request, the PSAX system notifies the MGC on detecting fax/modem tone, only if such event is requested and pending

• The PSAX system can remove ATM connections allocated for ephemeral termination when subtracted by MGC

~ The PSAX system initiates release of allocated ATM resources

• On ATM connection release, the PSAX system notifies MGC with Service Change Command

~ For normal release, the PSAX system does not notify MGC;

~ For lower layer failure (such as AIS, RDI), the Service Change causes "906–Loss of Lower Layer Connectivity."

• The PSAX system is able to reply to ADD command immediately or delayed

• The ADD command will be replied immediately when any of the follow-ings is true:

~ Local EECID attribute is requested ($) by MGC

~ Otherwise, the ADD command responds with pending and reply delayed until the ephemeral termination is created.

• The PSAX system will select the SDP parameters of the local media stream on MGC request

• The PSAX system is able to select the following:

~ A list of supported profile, in the order of local preference, is supported; The first on the list that is supported by PSAX, then will be used until MGC specific modification;

255-700-368 2-9


Chapter 2 H.248 Media Gateway Protocol SupportPackage Implementation

~ A list of supported CODEC algorithms, in the order of local preference, is supported; The first on the list then will be used until MGC specific mod-ification;

• The PSAX system supports Digit Maps

~ The PSAX system accepts unnamed digit maps from the MGC

• The PSAX system manages the Bearer Path According to the Local Control Mode

• MGC is able to control the Bearer Path configuration by changing the Mode of the local media:

~ The PSAX system cuts through both ways if any termination is in Mode=SendOnly or SendReceive and the other is in Mode=Receive-dOnly or SendReceive; otherwise, removes the connections;

• The PSAX system supports the following Test Calls

~ 102 test call origination and termination is supported;



Package ImplementationThis section lists the packages to be implemented.

• The PSAX system supports Generic Package (g), as described by ITU-T H.248 Annex E.1.

• The PSAX system supports Base Root Package (root), as described by ITU-T H.248 Annex E.2.

~ Maximum number of contexts are read only for MGC

~ Maximum Terminations Per Context is read only for MGC;

~ Normal MG Execution Time is read and write by MGC;

~ Normal MGC Execution Time is read and write by MGC;

~ MG Provisional Response Timer Value is for read and write by MGC;

~ MGC Provisional Response Timer Value is for read and write by MGC;

• The PSAX system supports Tone Detection Package (tonedet), as described by ITU-T H.248 Annex E.4.

~ All events are supported for TDM terminations;

• The PSAX system supports Basic DTMF Detection Package (dd), as described by ITU-T H.248 Annex E.6.

~ The PSAX system detect DTMF digit (through digit map but not toneId) from TDM terminations

~ The PSAX system supports digit map specified in the event descriptor by MGC

~ The PSAX system detects digit map completion event and report to MGC

• PSAX system support Basic Continuity Package (ct), as described by ITU-T H.248 Annex E.10. The PSAX system supports all mandatory events and signals on TDM terminations;

Chapter 2 H.248 Media Gateway Protocol SupportSDP Support Requirements

2-10 255-700-368


• The PSAX system supports TDM Circuit Package (tdmc) as described by ITU-T H.248 Annex E.13. The PSAX system supports echo cancellation for TDM terminations.

• The PSAX system supports Fax/Textphone/Modem Tone Detection Package (ftmd), as described by ITU-T H.248 Annex F.6. The PSAX system detects and reports the following tones on TDM termination:

~ ANS

~ ANSAM

• The PSAX system supports the Generic Announcement Package, as described in ITUH-T H.248 Annex K - Generic Announcement Package.

~ Fixed announcement play

• TDM termination

• ATM termination

• The PSAX system supports Line Test Calls Packages for 102, 105, and 108 Test Calls

SDP Support RequirementsThe PSAX system and MGC use SDP to describe the nature of ATM connec-tions. SDP is defined in IETF–RFC3108. However, only a small subset of SDP is required to support the services intended.

• The PSAX system supports the following SDP parameters:

~ V-version parameter;

~ C-could be used to transport ATM NSAP address;

~ M-media, which may contain a list of profile for PSAX system to choose;

~ A-eecid: the EECID attribute;

~ A-bearerType: SVC – bearer type attribute, could be SVC ON , SVC OFF

~ A-vsel: the VSEL attribute, could contain a list of CODEC algorithms for the PSAX system to choose;

~ A-uiLayer1_prot: the PCM A-law and PCM Mu-law attribute

Interaction with Other Features

H.248 and CGAPI Protocol Controller

This section lists all requirements for interactions between MGC with an H.248 and MGC with CGAPI.

• The PSAX system supports multiple NSAP Address Assignment.

~ You can configure multiple NSAP addresses to associate with a H.248 MGC interface (primary MGC plus backup MGC) so that the PSAX sys-tem is able to tell the ATM termination is controlled by which MGC

H.248 and ATM Signaling

The H.248 command triggers ATM call control activities, such as:

255-700-368 2-11


Chapter 2 H.248 Media Gateway Protocol SupportOAM Requirements

• AALI connection set up and release may be triggered by the H.248 com-mand

• AAL5 connection set up and release may be triggered by the H.248 com-mand

• AAL2 VCC setup and release may be triggered by the H.248 command

• AAL2 channel setup and release may be triggered by the H.248 command

ISDN PRl and ISDN PRA

ISDN PRI/PRA B channels are managed in the same way as other TDM ter-minations. ISDN D channels are transported to the MGC and are transparent to H.248. However, the ISDN PRA service is for future support of interna-tional applications.

IUA

IUA is used by the PSAX system to transport ISDN D channel messages and is independent of H.248.

SCTP

SCTP may be used to transport H.248 and/or ISDN messages, but they are all independent features of one another other than the primitive invocations.

OAM Requirements

Configuration Management Requirement

The PSAX system allows the flexible termination ID assignment at the fol-lowing levels:

• Termination ID assignments are allowed at the I/O module level. All termi-nations created (both permanent and ephemeral, except those IDs gener-ated before the creation) within that module have the same ID structure.

• Termination ID assignments are allowed at I/O port level. All terminations created (both permanent and ephemeral, except those IDs generated before the creation) within that port have the same IDs structure.

• ATM Termination ID assignment are allowed at VPC level. All terminations created (both permanent and ephemeral, excepted those IDs generated before the creation) within that VPC have the same ID structure.

• ATM Termination ID assignments are allowed at VPC level. All termina-tions created (both permanent and ephemeral, excepted those IDs gener-ated before the creation) within that VPC have the same ID structure.

• ATM Termination ID assignments are allowed at VCC level. All termina-tions created (both permanent and ephemeral, except those IDs generated before the creation) within that VCC have the same ID structure.

• TDM Termination ID assignments are allowed at time slot level. All termi-nations created (both permanent and ephemeral, excepted those IDs gen-erated before the creation) within that time slot have the same ID struc-ture.

Chapter 2 H.248 Media Gateway Protocol SupportOAM Requirements

2-12 255-700-368


• When termination ID structure assignment is done at multiple levels, the lower level structure prevails.

Currently, the above naming mechanism is only applicable to TDM termina-tions.

• The PSAX system supports H.248 software optioning:

~ The PSAX system is able to load the H.248 specific software into memory if the feature is needed

~ The PSAX system is able to unload the H.248 specific software from memory if the feature is NOT needed

~ The PSAX system reboots the system when such change is needed. Dur-ing this process, all active connections will be lost.

Performance and Capacity

The PSAX system supports 800 H.248 transactions per second:

~ Each transaction may contain multiple actions

~ Each action may contain multiple commands

The PSAX system supports:

~ 4000 contexts simultaneously

~ 8000 TDM terminations, permanent only

~ 4000 ATM terminations, permanent or ephemeral

PSAX System Software Fault Tolerance

The PSAX system has the following fault tolerance features:

• Stable calls are preserved on CPU software failure causing CPU switchover;

• Stable calls are preserved on CPU software upgrade

• A stable call is defined as the call that has the bearer path established in any fashion

Stable Call Retention

Stable calls are able to survive through certain faults and OAM activities.

The PSAX system retains stable calls through CPU switchover:

~ Stable calls are defined to include stable ephemeral terminations and the stable contexts.

~ A stable ephemeral termination is defined to be the ephemeral termina-tion with the underlying packet resource allocated (i.e., ATM connection set up complete).

~ A stable context is defined to be a context with terminations in cut through mode

~ A stable ephemeral termination is retained through CPU switchover for any reason.

~ Stable contexts are retained through CPU switchover for any reason.

255-700-368 2-13


Chapter 2 H.248 Media Gateway Protocol SupportIUA/SCTP

IUA/SCTPAlthough these features are not directly related to H.248, they are used in conjunction with each other to implement the desired service. In most cases, IUA and SCTP could be used to backhaul ISDN messages without H.248. SCTP could be used to backhaul other signaling protocols without IUA or H.248. H.248 could be used between the MGC and the MG even when IUA/SCTP is not used.

IUA

IUA is needed to backhaul Q.931 messages between a PRI D-channel and the MGC. To support ISDN PRI interfaces and related services, the PSAX system implements IUA and the following IUA requirements.

General Configuration

The PSAX system supports and implements IETF-RFC3057 IUA

The MGC is expected to implement the ASP and the AS

• The PSAX system LAPD configuration remains working as before the IUA support

~ The PSAX system can be the network side or the user side for backhaul-ing.

~ The PSAX system supports the provision of point-to-point signaling con-nections only as specified in Annex A of Q.921. That is, only a value of 0 for TEI and a value of 0 for SAPI are supported.

• The PSAX system ISDN configuration remains working as before the IUA support

~ The type of physical interface supporting ISDN PRI is transparent to IUA

~ The type of ISDN features supported by the PRI interface is transparent to IUA

• The PSAX system can turn on and turn off the IUA feature

~ The feature is turned on or off before system re-boot.

~ When turned off, this feature does NOT occupy the PSAX system primary memory at the .bss nor the .data level.

• The PSAX system IUA can be configured as the server side or as the client side

~ The PSAX IUA is configured as the server side

~ The PSAX IUA is configured as the client side - to be responsible for initi-ating the SCTP association.

PRI Interface

The PSAX system IUA maintains the association between the Interface ID (IID) and the PRI Interface. The IID is NOT configurable by the operator.

• The mapping between the IID and the AS/ASP-list is configurable as well

The PSAX system IUA dynamically maps an IID to an SCTP association and its stream:

Chapter 2 H.248 Media Gateway Protocol SupportIUA/SCTP

2-14 255-700-368


~ Mapping complies to section 1.5.1 of IETF-RFC3057

~ The mapping is between the IID <–> AS <–> ASP (active and idle)

~ The association is done only upon the reception of an ASP Active mes-sage for that IID

AS and ASP Status

The PSAX system IUA maintains the status of the ASP by using the SCTP association to identify the related ASP.

• The PSAX system IUA may maintain the ordered list of ASPs within an AS:

~ The first active ASP on the list associated with the AS is the primary SAP to serve the ISDN message

~ The PSAX system supports one single AS

• The PSAX system IUA supports traffic mode of ASP operation within an AS in override mode.

SCTP Interface and Stream Management

The PSAX system IUA uses a separate SCTP stream for each D channel. (The IID associated with the D channel is carried in the IUA message header). The IUA does NOT limit the maximum number of D channels that a PSAX system supports. Currently, the PSAX system has a limit (250) on the number of LAPD interfaces by the Telenetwork software.

250 PRI interfaces will support at least 23 * 250 TDM B channels, which is enough for PSAX system TDM termination capacity.

SCTP multiplexes the signaling streams of multiple users into a single trans-port session

Each stream is independent of each other; the outage/blockage of one does NOT block the sending and receiving of the others.

Multi-homing is supported in SCTP.

PSAX System Requirements

The PSAX system H.248 feature uses 16 Mb memory or less.

The PSAX system supports 4000 contexts simultaneously.

PacketStar® PSAX Multiservice Media Gateways H.248 Media Gateway Control User Guide Issue 1

255-700-368 3-1

3 Services Supported for the H.248Media Gateway Control Protocol

ITU-T H.248 Media Gateway Control Protocol

The PacketStar PSAX Media Gateway product line supports the ITU-T Stan-dard H.248, Audiovisual and Multimedia Systems. H.248 is a communications control protocol for convergent networks that allows calls to be physically “decomposed” into separate call control and media- and bearer-control func-tions This protocol enables more efficient use of PRI ports and intermachine trunks when internet data traffic is transmitted.The decomposed transit gate-way architecture distributes the call control functionality and the media pro-cessing functionality over different network elements. The advantage gained by decomposition is to decentralize control from the SS7 network to local networks. Decentralization enables transmission cost savings resulting from enabling gateway peripherals from a central controller to terminate trunking circuits near the circuit switches from which they originate.

The PacketStar PSAX Media Gateway supports a variety of network topologies for a termination, (see Glossary) including, but not limited to:

• PSTN terminations (see Glossary) to PSTN terminations

• PSTN terminations to ATM terminations

• One-stage (1+) toll tandem dialing services over ATM

• Fax/modem services (transcoding between TDM network and ATM packet networks)

How H.248 Contexts Work

The H.248 protocol model routes media flows between terminations indi-rectly, by associating them with a common context. In the H.248 Media Gateway protocol, a context is an association of not more than two termina-tions. The context ends when the contained terminations end. A context is modeled as a common pathway to which all the terminations within the con-text are connected. The life span of a context is measured from the occur-rence of the first termination addition, and ended when the last termination is removed. A termination can belong to only one context at a time. The MGC assigns each termination an ID, which is used by the MGC to track its status. A null context holds all terminations not currently engaged in a call.

For example, in a transmission that is bidirectional TDM to ATM, the H.248 protocol designates the TDM-end of a transmission as persistent (perma-nent). The ATM-end is ephemeral (can be set up and torn down). While such a connection is active, it exists in one context.

In bidirectional flows, the TDM part of the transmission is user-created, therefore, the termination ID (TID) is user-created. The ATM-end is dynami-cally set up and torn down. The PSAX user has no control or flexibility in

Before You Begin

3-2 255-700-368

H.248 Media Gateway Control User Guide Issue 1

regard to the ATM-end of the connection. Nor does the user have any control or flexibility in creating the TIDs for the ATM end, which are generated and assigned dynamically during call setup. Figure 4 shows a point-to-point SVC context between the Enhanced DS1 and an OC-3c module. The context cut-through occurs through the backplane.

PSAX H.248 Base Root Package Support

The PacketStar PSAX Multiservice Media Gateway supports the H.248 Base Root Package as described in ITU-T H.248 Annex E.2. All associated parame-ters can be configured by the user using the H.248 screens.

Before You Begin

Before attempting the H.248 Media Gateway Control Protocol configuration, users should be thoroughly familiar with basic configuration of channelized DS1 and channelized DS3 modules, the call control resource allocation pro-cedure, and the chassis reboot procedure. See these procedures in the appro-priate PacketStar PSAX Multiservice Media Gateway user guide. For module port, channel, and interface configuration on DS1 or DS3 modules, see the appropriate module guides.

Ensure that your PSAX is configured to support TCP or SCTP. The PSAX does not support UDP.

We recommend that a primary and backup IP addresses be configured on your MGC and PSAX. Instructions are provided later in this chapter.

Figure 4. A Sample CES-to-ATM AAL1 SVC Showing Decomposed Calling Control Through the Media Gateway Controller

Media Gateway Controller

PSAX Backplane

DS1(Up to 144 Connections)

To/From Local Switch To/From Local Switch

OC

-3c

Enh

DS

1

OC

-3c

Enh

DS

1

ATM

PSAX Backplane

DS1(Up to 144 Connections)

255-700-368 3-3


Modules Supporting the H.248 Media Gateway Control Protocol

Modules Supporting the H.248 Media Gateway Control Protocol

This feature is supported on all PSAX Multiservice Media Gateways with redundant CPU2 or CPU3L modules.

The H.248 protocol can be configured on these modules on the CE and PRI interfaces:





• 3-Port DS3/E3 ATM Protection







AAL1 and AAL2 Configuration Scenarios in this User GuideThis User Guide shows three call setup configurations:

• AAL1 TDM-to-ATM-to-TDM Traffic on an ATM UNI 4.0 Interface

• AAL1 TDM-to-ATM-to-TDM Traffic on a PNNI Interface

• AAL2 TDM-to-ATM-to-TDM ATM UNI 4.0

Document and Text Entry Conventions

This guide uses a different typeface to denote text displayed on console inter-face windows and equipment, as well as data you enter. Table 1 shows how each typographical convention is used.Table 1-2 shows how each typograph-ical convention is used.

Table 1. Text Conventions

Appearance How it is used

SANS SERIF BOLD, ALL CAPS Labels on module panels, chassis faceplates, or other hardware

Fixed-width normal Message text displayed on the user interface window

AAL1 TDM-to-ATM-to-TDM Traffic on an ATM UNI 4.0 Interface

3-4 255-700-368



The steps below are a summary of the AAL1 TDM-to-ATM-to-TDM Traffic configuration on an ATM UNI 4.0 Interface. The procedures outlined in the summary begin with the Turn On the H.248 Gateway Control Protocol Feature Pro-cedure.

1 Ensure that your PSAX is not using H248/UDP/IP to interface with the MGC. The PSAX supports only H248/TCP/IP and H248/STCP/IP.

2 We recommend a primary and at least one backup IP addresses for your PSAX. See your PSAX system chassis user guide for details.

3 Turn On the H.248 Media Gateway Control Protocol by performing the Turn On the H.248 Gateway Control Protocol Feature procedure.

4 Set the call control setting to Explict Cut-Through by performing the Configuring Call Control for the H.248 Media Gateway procedure. The total number of calls allowed explicit cut-through is equal to the number of TIDs, calls, and number of ATM terminations.

5 Reboot your chassis by performing the Steps to Reboot the PSAX System Hardware Chassis procedure in Chapter 5 of this user guide.

6 Set the parameters for the H.248 Media Gateway Control protocol on the H.248 Configuration window. Such parameters as the maximum number of contexts and various timer values are set on this window by performing the Configuring the H.248 Media Gateway Control Protocol Parameters procedure.

7 Enable Channelization and the Signaling Gateway on the module(s) you are using by performing the Enabling Channelization and Signaling Gate-way Feature procedure.

8 Configure the module slot or port for the H.248 Protocol by performing the Configuring the Module Slot or Module Port for the H.238 Protocol proce-dure.

Serif bold • Button name (GUI interface) or command name (console interface) on the user interface window

• Literal text for values that the user types or selects from predefined sets of values for fields

• Commands or literal argument values

Fixed-width bold System prompts displayed on the user interface window

Serif italics • A variable name or string for which you will substi-tute your own information

• An argument or parameter on a command line for which you will substitute your own information

Table 1. Text Conventions (Continued)

Appearance How it is used

255-700-368 3-5



9 Generate the Logical Termination Identifier by performing the Generating the Logical Termination ID procedure.

10 Set the Originating Media Gateway device master node address on the Site Specific Configuration window and apply the configuration.

11 Set the Terminating Media Gateway device master node address on the Site Specific Configuration window and apply the configuration. On your terminating modules, the hex address must end in “FD” for H.248 routing.

12 Configure SVC routing for the data traffic on the OMG and TMG sides.

Turning On the H.248 Media Gateway Control Protocol Feature

The first procedure is to turn on the H.248 Media Gateway Protocol feature on the Site Specific Menu.

Begin

Turning On the H.248 Gateway Control Protocol Feature

1 On the Console Interface Main Menu window, select the Site-Specific Configuration option and press Enter.

The Site-Specific Menu window (Figure 5) is displayed.

2 On the Site-Specific Menu window, select the Feature Turn ON/OFF option and press Enter.

The Feature Turn ON/OFF window is displayed (see Figure 6).

Figure 5. Site-Specific Menu Window


3-6 255-700-368


The commands on this window have the following functions:

Additional information for the fields on the window are in the table below:

Figure 6. Feature Turn ON/OFF Table, H. 248 Selected

Command Function

Page Up Scrolls up one page.

Page Down Scrolls down one page.

Top Displays entries at the top of the table.

Bottom Displays entries at the bottom of the table.

Find . . . . . Feature ID: This command is currently not supported.

Go Back to Site-Specific Menu

Redisplays the Site-Specific Menu win-dow.

255-700-368 3-7



3 Select the H.248 in the Feature Id column and press Enter. This changes the desired status of H.248 to Enable.

The following message is displayed in the status line:

New configuration will take affect only after chassis reboot

4 Do not reboot your chassis at this time; you will do so later on.

5 Select the Go Back to the Site Specific Menu command, and press Enter.

Table 2. Field Descriptions for the Feature Turn On/Off Table

Field Name Field Values Description

Total: 0/0 Default: N/A

Range: 1–6

Format: numeric

First number: Indicates which Feature ID is cur-rently selected in the table.

Second number: Indicates the total number of Feature IDs in the table.

Feature ID(display only)

Default: N/A

Range: N/A

Format: predefined alphanumeric

Displays the PSAX system features that you can enable or disable.

H248 H.248 Media Gateway Control protocol feature.

space memory(display only)

Default: N/ARange: N/A

Format: numeric (bytes)

Displays the amount of system memory allocated to the selected feature.

desired status Default: N/A

Range: N/A


Specifies whether the feature is to be made oper-ational or not.

Note: On the Site-Specific Menu window, the feature options that are displayed between brack-ets [ ] are disabled.

Disable Indicates that the selected enabled feature is to be made not operational. After selecting this value, you must reboot the PSAX system to make this change take effect. After the system reboots, Disabled is displayed in the current status field.

Enable Indicates that the selected disabled feature is to be made operational. After selecting this value, you must reboot the chassis to make this change take effect. After the system reboots, Enabled is dis-played in the Current Status field.

current status(display only)

Default: N/A

Range: N/A


Indicates the current operational status of the feature.

Disabled Indicates that the selected feature is currently not operational.

Enabled Indicates that the selected feature is currently operational.


3-8 255-700-368


6 Proceed with the Configuring Call Control for the H.248 Media Gateway procedure.

Begin

Configuring the Call Control for the H.248 Media Gateway

1 On the Site-Specific Menu window, select the Call Control Resource Allocation Configuration option and press Enter.

The Call Control Resource Allocation Configuration window is displayed (see Figure 7). On this window, the following fields correspond to these H.248 components:

~ sgApiCirEmEndPts = number of TIDs

~ sgApiAtmSvcEndPts = number of ATM terminations

~ sgApiPtToPtSvcCalls = number of calls

2 On this window, change the cgSvcCutThroughOption field value to CgS-vcCgExplicitCutThrough, as shown in Figure 7.

Note: All applications using the H.248 protocol must use the CgSvcCgEx-plicitCutThrough value.

3 Select the Apply Configuration command and press Enter.

4 Press Ctrl+G to return to the Console Interface Main Menu.

5 Select the Save Configuration option and press Enter.

Figure 7. Call Control Resource Allocation Configuration Window

255-700-368 3-9



6 Proceed with the procedure, “Rebooting the PSAX System Hardware Components.”

End

Begin

Rebooting the PSAX System Hardware Components

The Remote Reboot Configuration window is displayed (see Figure 8 for PSAX 1000, PSAX 1250, PSAX 2300, or PSAX 4500).

7 Select the appropriate command shown in the following table as needed and press Enter. For the H.248 feature, select the Reboot Chassis com-mand (or press Ctrl+T).

Figure 8. Remote Reboot Configuration Window


3-10 255-700-368


End

Configuring the H.248 Media Gateway Control Parameters

In the next procedure, you will set the H.248 protocol parameters such as the number of contexts, terminations, timer values, and execution times.

Command Function

Reboot the I/O Card in Slot:__

Reboots the I/O or server module in the slot you designate.

This command is the equivalent to physi-cally deinserting the module from and then reinserting it into the chassis.

Reboot All I/O Cards Reboots all I/O and server modules in the chassis, without affecting the primary CPU module or backup (standby) CPU module (if one is present).

This command is the equivalent to physi-cally deinserting the modules from and then reinserting them into the chassis.

Reboot Primary CPUWARNING:!

Rebooting the PSAX system with a sin-gle (nonredundant) CPU module or component will interrupt all traffic run-ning through the PSAX chassis.

This command also reboots all I/O and server modules in the chassis, as instructed by the system software initial-ization process.

Reboot ChassisWARNING:!

Rebooting the PSAX system with the Reboot Chassis command will interrupt all traffic running through the PSAX chassis.

This command is equivalent to a system cold start, that is, removing the power from the chassis and then reapplying the power.

Use this command:

Go Back to Diagnostics Menu

Displays the Diagnostics Menu window.

255-700-368 3-11



Steps to Configure the H.248 Media Gateway Control Protocol

Begin

Parameters

1 From the Site-Specific Menu, select the H.248 Configuration com-mand (or press Ctrl+O).

The H.248 Configuration window is displayed (see Figure 9).

The commands on this window perform the following functions:

2 Select the values for the fields on this window from the following table:

Figure 9. H.248 Configuration Window

Command Function

Apply Configuration Applies the configuration parameters.

Reset Display Resets the fields to the last set of saved values.




3-12 255-700-368


Table 3. Field Descriptions for the H.248 Configuration Window


MGC IP Address Panel

Transport Protocol Type

Default: tcp

Range: As noted below

Format: Predefined

Specifies which type of IP transport protocol is used.

tcp Transfer control protocol. Select this value for H.248 applications.

sctp This option is currently not supported.

Stream control transmission protocol. Select this value for PRI offload.

MGC IP Address1 through MGC IP Address4

Default: 0Range: 4

Format: Numeric

A Media Gateway Controller (MGC) controls the parts of the call state that pertain to connection control for media channels in a media gateway. Enter up to 4 IP addresses. The MG will connect with the first MGC IP address that responds to a ping, starting with Address1. The MGC must be configured to respond to a ping request.

Base Root Package Panel

Maximum Number of Contexts

Default: 4000

Range: 10–4000

Format: Numeric

A context is an association between a collection of terminations. This value indicates the maxi-mum number of contexts that can exist simulta-neously. As one context is always the null con-text, 3999 contexts are possible for contexts other than null. Each time you change this value and apply the configuration, you must perform a chassis reboot.

[Maximum Termi-nations Per Con-text] (display only)

Default: 2

Range: N/A

Format: Numeric

A termination is a logical entity on a media gate-way that sources and/or sinks media and/or con-trol streams.

Currently, this field value cannot be changed.

Normal MG Execu-tion Time

Default: 1000

Range: 0 or 100–9999

Format: Msec

A value set by the MGC to indicate the interval within which the MGC expects a response to any transaction from the MG (exclusive of the net-work delay).

If this value is set to 0, no pending ACK is sent by the MG.

For values between 100 and 9999, if the MG does not respond in the specified time, a Pending Response is sent. The value represents millisec-onds.

[Normal MGC Exe-cution Time]

Default: 1000

Range: 100–9999

Format: Msec

This value is settable by the MGC that interfaces with the PSAX system to indicate the interval within which the MG expects a response to any transaction from the MG (exclusive of the net-work delay). The value represents milliseconds.


255-700-368 3-13



3 After selecting your values, select the Apply Configuraton command (or press Ctrl+A).

End

[MG Provisional Response Timer Value]

Default: 1000

Range: 100–9999

Format: Msec

The time within which the MGC should expect a Pending Response from the MG if a Transaction cannot be completed. Initially set to Normal MG Execution Time, plus network delay, but may be lowered. The value represents milliseconds.


MGC Provisional Response Timer Value

Default: 0

Range: 0 or 100–9999

Format: Msec

The time within which the MG should expect a Pending Response from the MGC if a Transaction cannot be completed. Initially set to Normal MGC Execution Time, plus network delay, but may be lowered. If no reply response or pending response is received by the MG within the time period specified, the MG will resend the transa-tionc one more time.

If the value is set to 0, the transaction will never by resent. The value represents milliseconds

Maximum Number of Terminations

Default: 02000

Range: 1–8000

Format: Numeric

Specifies the maximum number of terminations permitted in a context. Each time you change this value and apply the configuration, you must per-form a chassis reboot.

ACK from MG Default: DisabledRange: As noted below

Format: Predefined

Specifies whether the MG acknowledges transac-tion replies from the MGC.

Disabled The MG does not send Tranaction ResponseAck messages upon receiving a reply from the MGC.

Enabled The MG sends Tranaction ResponseAck messages upon receiving a reply from the MGC.

Media Gateway Control

Default: CGAPI

Range: N/A

Format: Predefined

The Media Gateway Control protocol allows an external device to interconnect to the PacketStar Multiservice Media Gateway systems and act as an adjunct processor to handle IDSN, SS7 signal-ing, and other call control functions.

CGAPI The Connection Gateway API protocol will be used as the control interface between the incom-ing signal and the PSAX system.

H248 The H.248 protocol will be used as the control interface between the incoming signal and the PSAX system.

Note: You must select this value to enable the H.248 gateway protocol on this PSAX system.

Table 3. Field Descriptions for the H.248 Configuration Window



3-14 255-700-368


Enabling Channelization and the Signaling Gateway Feature

The H.248 configuration procedures from this point forward all use the Enhanced DS1 module as an sample configuration. See the Modules Support-ing the H.248 Media Gateway Control Protocol section for a module list (at the beginning of the H 248 Configuration section for other resources that can be used).

Begin

Steps to Enable Channelization and the Signaling Gateway Feature

1 From the Console Interface Main Menu, select the Equipment Configu-ration command (or press Ctrl+E). (This window is not shown).

2 On the Equipment Configuration window, select a module supporting the H.248 gateway control protocol and press Enter.

3 On the module’s Configuration window, select a port and press Enter.

The module’s Port and Channel Configuration window is displayed (see Figure 10).

4 On this window, change the default setting Disabled for the Channel-ization field to Enabled.

5 Change the signaling gateway (SG) Feature setting from the default set-ting Disabled to Enabled.

6 Select the Apply Port Configuration command (or press Ctrl+A).

Figure 10. Enhanced DS1 Port and Channel Configuration Window

255-700-368 3-15



With the enablement of channelization and the Signaling Gateway fea-ture, you can proceed with Configuring the Slot or Port for the H.248 Protocol procedure (below).

End

At this point, go to the PacketStar® PSAX Connections Provisioning Guide for PacketStar® PSAX Central Office Multiservice Media Gateways and configure a CE-to-ATM VCC PVC interface on the DS1 or DS3 module you are using. After you have done so, continue with the procedure below.

Configuring the Slot or Port for the H.248 Protocol

Steps to Configure the Module Slot or Module Port for the H.248

Begin

Protocol

1 On the Port and Channel Configuration Window of the module you just conf0igured for circuit emulation-to-ATM (see Figure 10), select the Go to H.248 TID Configuration command. The Termination ID Configu-ration window is displayed (see Figure 11).

Note: The trunk name shown in Figure 11 is for sample purposes only.

The commands on this window perform the following functions:

Figure 11. Termination ID Configuration Window (Before TID Configuration Applied)

Command Function

Apply TID Applies the Termination ID configuration.

Apply ACTIVATION Applies the Enabled or Disabled value you selected in the H.248 Activation field.


3-16 255-700-368



Reset the Termination ID configuration

Resets the fields to the last set of saved values.

Go Back to Port Level Redisplays the H.248 Configuration win-dow.

Command Function

Table 4. Field Descriptions for the Termination ID Slot Configuration (Slot) Window


Pseudo Termination ID

Default:

Range: 1–32.

Format: Alphanumeric:Trunk_Name/<pp>/<lp>/<ch>

See Rules for Assigning Termination IDs in the last row below of this table.

A “template” used to automatically generate and assign logical termination IDs to all channels on this slot or port. In this instance, the template takes the form of a 32-character user-assigned trunk name, followed by a literal string for physi-cal port <pp>, logical port <lp> and channel <ch>, separated by slash boundary characters (see the format in the Field Values column). This value can be configured at the slot or port level.

H.248 Activation(displayed only if you are configur-ing a channel for any interface type other than the Cir-cuit Emulation)

Default: Disable

Range: N/A

Format: Predefined

Indicates whether H.248 MGC protocol is acti-vated for this module.

Disable The value Disable is the current and desired state. For an explanation, see the Note in the description of the value Enable below.

Enable The value Enable setting enables all ready termi-nations associated with this slot.

Note: The value Enable is a transient action state. After the Apply ACTIVATION command is applied, this value reverts back to Disable, which is the current and desired state.

Rules for Assigning Termination IDs:

1. A TID is a string of 32 characters or less, consisting of any or all of these characters types:

a. Alphabetic characters A–Z and/or a–z

b. Numeric characters 0–9

c. Special characters: slash (/) and underscore (_)

d. The < and > characters are allowed if they are part of the three generators <pp>, <lp>, and <ch>.

2. TIDs are case-insensitive. For example, Trunk001/6/12 and TRUNK001/6/12 are the same TID.

3. All TIDs must have unique ID strings in order to be valid.

4. The TID “root” is reserved and cannot be used.

255-700-368 3-17



3 In the Pseudo Termination ID field, type your trunk name and the literal string as instructed on the Pseudo Termination ID field (see Table 4 and Figure 11). The string instructs the H.248 system software to assign the physical port on this slot to the H.248 protocol.

4 At this time in the configuration, the H.248 Activation field should say Disable. If it says Enable, follow the instructions for this field in the Commands table above.

5 Select the Apply TID command (or press Ctrl+T).

In this example, after the TID command is applied, the Pseudo Termina-tion ID field will display: Client_Trunk001/2/<lp>/<ch> (see Figure 12). Note that the <pp> variable string has been replaced by “2”. This means that the media gateway controller (MGC) now recognizes the slot physical port 2.

6 Select the Apply ACTIVATION command (or press Ctrl+A).

This command activates the H.248 protocol for the selected slot and port (see Figure 12).

In Figure 12, note the [Port: 02] field has been added to the display after TID configuration. This is a local configuration on the PSAX. The MGC cannot “see” this configuration, as the logical port and associated chan-nels are yet to be generated.

The commands and field descriptions for this window are the same as for Figure 11.

7 Press Ctrl+B to return to the port and channel configuration window.

Figure 12. Terminal ID Configuration Window (After TID Configuration Applied)


3-18 255-700-368


8 Select an available channel and proceed with generating the Logical Ter-mination ID procedure (below).

End

Generating the Logical Termination ID Begin

Steps to Generate the Logical Termination ID

1 From the port and channel configuration window, press Enter on the selected available channel. The Enhanced DS1 Configuration window is displayed (see Figure 13).

2 Select CircuitEmulation in the Interface field.

3 Select the Apply Configuration command (or press Ctrl+A).

Note: Leave the Signaling field at the default Disabled setting.

4 Select the Go to H.248 TID Configuration command, (or press Ctrl+I)

The Terminal ID Configuration window is redisplayed, with additional information, (see Figure 14:


255-700-368 3-19



On this window, note that the Logical Termination ID field now shows the logical port 1 and channel 01 in addition to the physical port 2 shown on the pseudo Termination ID screen (see Figure 12).

Also note that this configuration only applies to one channel, 01 in the Logical Termination ID field. The configured channel also shows in the [Channel:] display-only field under the window title.

The PSAX cannot simultaneously configure all channels on a port for H.248 at this time. If you want to configure other channels for H.248 at this point, you must return to the Port and Channel Configuration win-dow of the module you are using and select another port to be config-ured for circuit emulation and apply the configuration. At the port level, this action will automatically apply H.248 to all channels on the port. At the slot level, this action will automatically apply H.248 to all ports. (On the Enhanced DS1, this action cannot be done at the slot level). You can verify additional configurations by using the Go to H.248 TID Config-uration command.

Bulk configuration options are available through the AQueView Element Management System (EMS). Using the EMS, on a DS1 module, you can configure up to 144 channels. On a channelized DS3 module, you can configure up to 672 channels. Slots, ports, and channels configured for H.248 can only be changed by deleting the interface before applying another configuration to it.

The commands on this window in Figure 14 perform the following func-tions:


Configuring the Originating and Terminating Media Gateway Master ATM Addresses

3-20 255-700-368


End


The following procedures are a sample configuration for AAL1 TDM-ATM-TDM over ATM UNI Call Setup.

In the following procedure, set the master node address for the Originating Media Gateway (OMG) and the Terminating Media Gateway (TMG), and apply the configuration for each.

Command Function


Apply ACTIVATION Applies the Enabled or Disabled value you selected in the H.248 Activation field.

Reset the Termination ID configuration

Resets the fields to the last set of saved values.

Go Back to Port Level Redisplays the H.248 Configuration win-dow.

Table 5. Field Descriptions for the DS1 CE H.248 Termination ID Configuration Window


[Slot] (display only)

Range: Chassis dependent

Format: Numeric

The module slot where a termination exists.

[Port] (display only)

Range: Module dependent

Format: Numeric

The module port assigned to the pseudo termina-tion ID.

[Channel] (display only)


Format: Numeric

The DS1 CE module channel assigned to the pseudo termination ID.

Logical Termination ID

Default:


Format:

A unique identifier used by the MGC to refer to a specific termination. A logical termination ID can be assigned either manually or automatically through a pseudo termination ID specified at a higher level (slot, physical port or logical port).

H.248 Activation Default: Disable

Range:

Format:

Specifies the last setting of the pseudo termina-tion ID before H.248 was activated.

Disable The last setting of the pseudo termination ID before H.248 was activated was Disable.

Enable The termination is currently enabled.

255-700-368 3-21



To configure your system, perform the steps in the following procedure.

Begin

1 On the Console Interface Main Menu window, select the Site-Specific Configuration command.

The Site-Specific Menu window is displayed.

2 On the Site Specific Menu window, select the Site-Specific Configura-tion option.

The Site-Specific Configuration window is displayed (see Figure 15).

Note: The system performs error checking on each field by highlighting any field containing an incorrect value. Use the system message displayed in the information line to help you correct any errors.

End

The commands on this window have the following functions:

Figure 15. Site-Specific Configuration Window

Command Function

Configure TCP Server Displays the TCP Server Configuration window.

Apply Site-Specific Configuration

Applies the values you enter on this win-dow.

Configuring the Originating Media Gateway and the Terminating Media Gateway for ATM UNI 4.0 Interface

3-22 255-700-368



The next procedure is to configure your originating media gateway (OMG) and terminating media gateway (TMG) ATM modules for ATM UNI 4.0. See the Configuring the Ports and Channels chapter in your ATM module User Guide for details on accessing the window in Figure 8.

Reset Site-Specific Configuration

Sets the values in this window to the last saved (applied) set of values.



Command Function

Table 6. Field Descriptions for Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window


Master Node Addr Default: 0000.0000.0000.0000.0000.0000.0000.0000.0000.0000

Range: N/A

Format: hexadecimal

Indicates the master node address where the SNMP traps will be sent (20 octets).

Address Type Default: Nsap

Range: N/A


Nsap, E164, E164nsap

Indicates the type of address used for the master node ATM address.

Loopback Location ID

Default: FFFF.FFFF.FFFF.FFFF.FFFF.FFFF.FFFF.FFFF

Range: N/A

Format: hexadecimal

Indicates the unique identifier of the ATM node where the loopback is to occur (8 octets).

Loopback Location ID is the location identifier of the local switch. It is used as the “Source Location Id” in all the outgoing OAM loopback cells and will be compared with the “Destination Location Id” of a received OAM loopback cell to decide if the received OAM loopback cell should be looped back by this switch or not. You must enter a unique value in the Loopback Location ID field to perform OAM loopback tests.

Debouncing Period (msecs)

Default: 2000

Range: 1000–300000

Format: numeric (msec)

Indicates the maximum time for clearing OAM AIS and RDI alarms.

255-700-368 3-23



1 Configure the OMG side for:

On the module Port and Channel Configuration window (see Figure 8), enter ATM UNI 4.0 in the Interface Type field.

2 Select the Apply the Configuration command.

• On the ATM UNI 4.0 Interface Configuration window, enter these values:

• ATM Signaling Enabled

• Interface Type User

3 Select the Apply the Port and Channel Configuration command

4 Select the Bring the Interface Into Service command.

On the TMG side (windows not shown), enter the same values as on the OMG side for the module Port and Configuration window, and the values below for the ATM UNI Interface Configuration window:

• ATM Signaling Enabled

• Interface Type Network

5 Select the Apply the Port and Channel Configuration command

6 Select the Bring the Interface Into Service command.

End

Figure 3-7. Sample Module Configured for AtmUni4-0.

Configuring SVC Routing for the Data Traffic on the OMG and TMG Sides

3-24 255-700-368



After completing the ATM UNI 4.0 configuration, you will need to configure settings for the data VBR traffic on the SVC routing windows. See your chas-sis user guide for instructions on accessing the screens to configure the basic system. When you perform the Adding NSAP Address Entries procedure, at a minimum supply values for the 3 fields listed below. You will need to enter values for the fields below for both the OMG and TMG sides. Perform the procedure for the OMG side, then for the TMG side. In Figure 4, enter the values below for both the TMG side and the OMG side for all fields except the Vuni ID field.

OMG Side

• Address (Hex) field: Enter the TMG’s master ATM address entered previ-ously on the Site Specific Configuration window

• # Bits field: Enter 152

• Sl Pt Chn field: Enter the slot, port and channel of the TMG’s ATM UNI 4.0’s ATM module (see Figure 4).

TMG Side

• Address (Hex) field: Enter the OMG’s master ATM address entered previ-ously on the Site Specific Configuration window

• # Bits field: Enter 152• Sl Pt Chn field: Enter the slot, port and channel of the OMG’s ATM UNI

4.0’s ATM module (see Figure 4)

Creating IISP VBR Entries

Use the steps in the following procedure to add an entry to the VBR routing table, starting at the Connection Configuration Menu window.

Begin

Adding NSAP Address Entries

1 On the Connection Configuration Menu window, select the IISP VBR Routing Table option and press Enter.

The IISP VBR Routing Table window is displayed (see Figure 4).

255-700-368 3-25



Commands The commands on this window have the following functions:

2 Select the Add an Entry field, and press Enter.

a. Type a network service access point (NSAP) address in hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 characters each), and press the Tab key.

b. In the # Bits field, type a value from 1–152 for the NSAP address mask, and press the Tab key.

c. In the Sl Pt Chn field, type the slot, port, and channel values for the ATM-cell-bearing I/O module that has a configured ATM IISP (User or Network) interface.

d. If applicable to your configuration, enter a value for the Vuni ID field.

e. Press Enter to add the entry to the table.

3 Repeat step 2 as many times as needed to add entries to the table.

4 To permanently save these table entries, press Ctrl+G to return to the Console Interface Main Menu window.

Figure 4. IISP VBR Routing Table Window

Command Function

Find Finds the routing entry with the specified NSAP address.

Go Back to Connection Menu→

Redisplays the Connection Configuration window.

Configuring the Voice CBR Traffic for SVC Routing

3-26 255-700-368


5 Select Save Configuration, and press Enter to store the values to the Multiservice Media Gateway system database.

End

Configuring the Voice CBR Traffic for SVC RoutingAfter you have configured SVC routing for the data traffic on the OMG and TMG sides, you will need to configure the voice CBR traffic for SVC routing. On the window (see Figure 5) below, use these values:

OMG Side

• Address (Hex) field: Enter the TMG’s master ATM address entered previ-ously on the Site Specific Configuration window

• # Bits field: Enter 152

• Sl Pt Chn field: Enter the slot, port and channel of the TMG’s ATM UNI 4.0’s ATM module (see Figure 4).

TMG Side

• Address (Hex) field: Enter the OMG’s master ATM address entered previ-ously on the Site Specific Configuration window

• # Bits field: Enter 152• Sl Pt Chn field: Enter the slot, port and channel of the OMG’s ATM UNI

4.0’s ATM module (see Figure 4)

Creating IISP CBR Entries

Note: SVC connections are not supported on the STM-1 or the OC-3c MM/SM Traffic Shaping modules.

Use the steps in the following procedure to add an entry to the CBR Routing table, starting at the Connection Configuration Menu window.

Begin

Creating Entries in the IISP CBR Routing Table

1 On the Connection Configuration Menu window, select the IISP CBR Routing Table option and press Enter.

The IISP CBR Routing Table window will display (see Figure 5).

255-700-368 3-27


Configuring the Voice CBR Traffic for SVC Routing

Commands The commands on this window have the following functions:

2 Select the Add an Entry field, and press Enter.

a. In the Address (Hex) field, type a network service access point address up to 20 bytes (160 bits) long (10 groups of 4 characters each), and press the Tab key. If configuring the OMG side, enter the TMG Master ATM address from the Site Specific Configuration win-dow. If configuring the TMG side, enter the OMG Master ATM address from the Site Specific Configuration window.

b. In the # Bits field, type a value from 1–152 for the NSAP address mask, and press the Tab key. Enter 152.

c. If configuring the OMG side, enter the slot, port, and channel of the TMG’s ATM UNI 4.0 ATM module in the Sl Pt Chn field. If configur-ing the TMG side, enter the slot, port, and channel of the OMG’s ATM UNI 4.0 ATM module in the Sl Pt Chn field.

d. If applicable to your configuration, enter a value in the Vuni ID field. Enter a 0 if configuring H.248.

e. Press Enter to add the entry to the table.

3 Repeat step 2 as many times as needed to add entries to the table.

Figure 5. IISP CBR Routing Table

Command Function

Find Finds the routing entry with the specified NSAP address.

Go Back to Connection Menu→

Redisplays the Connection Configuration window.

AAL1 TDM-to-ATM-to-TDM Call Setup Scenario Using the PNNI Interface

3-28 255-700-368


4 To permanently save these table entries, press Ctrl+G to return to the Console Interface Main Menu window.

5 Select Save Configuration, and press Enter to store the values to the Multiservice Media Gateway system database.

End

This concludes the ATM UNI 4.0 AAL1 sample configuration.


For the AAL1 TDM-to-ATM-to-TDM call setup scenario using the PNNI inter-face, the setup is the same as for the ATM UNI 4.0 setup through the Configur-ing System Values for Your Site procedure. Instead of configuring the ATM UNI 4.0 interface, configure a PNNI Node connection to the OMG side.

Refer to your PSAX System user guide for PNNI node configuration instruc-tions. Enter the following values on the OMG side PNNI Node Configuration window:

• Node Index field: 00001

• ATM Address field: Follow the guidelines in the your PSAX System User Guide. This address must be different from the Master ATM address

1 Select the Apply Configuration command.

2 Select the Bring Node into Service command.

Figure 6 shows a sample PNNI Node Configuration window.

Figure 6. Sample PNNI Node Configuration Window, OMG Side

255-700-368 3-29



After completing the PNNI node creation procedure, configure an OMG side PNNI Route using the procedure in your PSAX System user guide. When per-forming the procedure to set up PNNI routing, enter the following values on the PNNI Route Address Configuration window:

• Node Index field: 00001. This address is the same as the Node Index field on the PNNI Node Configuration window.

• ATM Address field: Follow the guideline in the PSAX System user guide. This address must be same as the Master ATM address

• Prefix length: 152

• Address index: 00001

3 Select the Add Route Address command.

Figure 7 shows a sample PNNI Route Address Configuration window.

Configuring an OMG ATM Module for the PNNI Interface

On your ATM module (for example, an OC-3c MMAQ module), configure a PNNI interface using the procedures found in the module’s user guide.

• Apply the port and channel configuration.

• Bring the interface into service.

Figure 7. Sample PNNI Route Address Configuration Entry, OMG Side

PNNI Interface Configuration, TMG Side

3-30 255-700-368


PNNI Interface Configuration, TMG SideFollow the next three procedure to continue configuring the PNNI node, route address and PNNI interface on the TMG.

Enter these values on the TMG Side PNNI Node Configuration window. Refer to your PSAX System user guide for instructions on accessing PNNI node configuration instructions. Below are sample values used for the TMG side:

• Node Index field: 00001

• ATM Address field: Follow the guidelines in the your PSAX System user guide. This address must be different from the Master ATM address.

1 Select the Apply Configuration command.

2 Select the Bring Node into Service command.

Figure 6 shows a sample PNNI Node Configuration window.

Figure 8. Sample OC-3cMMAQ Port and Channel Configuration on an ATM PNNI Interface, OMG Side

255-700-368 3-31



After completing the PNNI node creation procedure for the TMG Side, con-figure a TMG-side PNNI node using the procedure in your PSAX System user guide. When performing the procedure, enter the following values on the PNNI Node Configuration window:

• Node Index field: 00001. This address is the same as the Node Index field on the PNNI Node Configuration window.

• ATM Address field: Follow the guideline in the PSAX System User Guide. This address must be same as the Master ATM address

• Prefix length: 152

• Address index: 00001

3 Select the Add Route Address command.

Figure 9. Side Sample PNNI Node Configuration, TMG Side


3-32 255-700-368


For the TMG side, configure your ATM module (Sample OC-3c MMAQ), for a PNNI interface, using instructions from Chapter 5 of your ATM Module Guide.

• Select the Apply Port and Channel Configuration command.

• Select the Bring Interface Into Service command. In Figure 11, the command has been applied.

Figure 10. Sample PNNI Route Address Configuration, TMG Side

255-700-368 3-33



Verify the OMG PNNI Route Address Table. If the configuration is done prop-erly, you will see four entries on the OMG PNNI Route Address table (Figure 12):

Figure 11. Sample OC-3c ATM Module Configured for ATM PNNI Interface, TMG Side

Figure 12. Sample OMG PNNI Route Address Table Side

Saving the System Configuration and Logging Off

3-34 255-700-368


Verify the TMG PNNI Route Address Table. If configuration is done properly, you will see four entries on the TMG PNNI Route Address table (Figure 13):

Your must save the configuration or it will be erased during chassis reboot.


After configuring the module ports and channels, the interface types for each port and channel, and the connections, you must save the values to the PSAX system database. It is recommended that you save your values fre-quently as you progress through your work, at a minimum, after finishing each stage of work:

• Configuring each module in your system

• Configuring the connections in your system

• Before exiting your current console session

Perform the following procedure to permanently save the values for your system.

! CAUTION:If your system or location loses power or your current session ends abnormally while you are in the process of configuring the system, and you have not yet saved the values permanently, you will lose all unsaved values you have applied on the various windows.

Figure 13. Sample OC-3c ATM Module Configured for ATM PNNI Interface, TMG Side

255-700-368 3-35



Begin

1 To return to the Console Interface Main Menu window, press Ctrl+G.

On the Console Interface Main Menu window, [Modified] is displayed next to the Save Configuration command, indicating you have made changes to your system that are not yet saved to the database.

2 Select the Save Configuration command.

Wait a few seconds while the system writes the values to the PSAX sys-tem database. The system displays the following message while it is exe-cuting this command:

Saving the equipment and connection information

When this function is completed, the system displays the following mes-sage:

T-SaveConfiguration: saveConfigurationReasonCode=All-OK

You can now safely exit the current session.

3 Select the Leave Console Interface command.

You are now logged off the PSAX system console interface.

End


3-36 255-700-368



255-700-368 4-1

4 H.248 Protocol andAQueView® EMS Configuration

H.248 Configuration

Enabling H.248 Media Gateway Control Protocol

This feature is supported on all PSAX Media Gateways with redundant CPU2 or CPU3L modules.

The H.248 protocol can be configured on the modules on the bullet list below on the CE and PRI interfaces, with the following constraint:

~ For the 6-Port Enhanced E1 Multiservice and the 21-Port High-Density E1 Multiservice modules, if the SG Feature field is Enabled and the MG control protocol type is H.248, the PRI interface cannot be configured.











For modules other than the ones listed above, the SG Feature field on the Port and Channel Configuration window cannot be Enabled if the MG con-trol protocol type is H.248.

Note: Before attempting the H.248 Media Gateway Control (MGC) Pro-tocol configuration, users should be thoroughly familiar with basic configuration of channelized DS1 and DS3 modules, the call con-trol resource allocation procedure, and the chassis reboot proce-dure. See these procedures in the Configuring the Basic System chap-ter in the appropriate PacketStar® PSAX Multiservice Media Gateway User Guide. For module port, channel, and interface con-figuration on DS1 or DS3 modules, see the appropriate module guides.

Begin

1 In the Device window, click the Site-Specific tab.

Chapter 4 H.248 Protocol and AQueView® EMS ConfigurationH.248 Configuration

4-2 255-700-368


The Site-Specific page is displayed.

2 Click the Feature Turn On/Off tab.

The Feature Turn On/Off Configuration page appears.

3 Select the Feature value H248 on this window.

4 Click the right mouse button and a menu appears.

5 To enable the feature, select Turn On Selected Feature. To disable the fea-ture, select Turn Off Selected Feature.

An informational window appears (see Figure 4-1).

6 Click OK.

The H.248 feature will become enabled upon rebooting the PSAX device.

End

Setting the Call Control Value for H.248 Media Gateway Control Protocol

Perform the steps in the following procedure to configure your call control setting for H.248 MGC.

Begin

1 In the Site-Specific tab, click the Call Control tab.

Figure 4-1. Feature Turn On/Off Confirmation Window

255-700-368 4-3



The Call Control page appears (see Figure 4-2).

2 On this window, change the cgSvcCutThroughOption field value to CgS-vcCgExplicitCutThrough.

3 Click Apply.

An informational window appears (see Figure 4-3).

4 Click OK.

5 In the Provisioning Menu Bar, click Device > Save PSAX Configuration. (See the section, “Saving Configuration Values.”).

End

The next task is to reboot the PSAX device.

Figure 4-2. Call Control Page

Figure 4-3. Call Control Confirmation Window


4-4 255-700-368


Rebooting the PSAX Device

Perform the steps in the following procedure to reboot (initialize) the PSAX device.

Note: Only users with Administrator access privileges can restart hard-ware components.

Begin

1 Click the Diagnostics tab in the Device window.

The Diagnostics page appears.

2 In the Restart Hardware Components panel, select Entire Chassis from the pull-down menu (see Figure 4-4) and click Restart.

3 Click Restart.

A confirmation window appears (see Figure 4-5).

4 Click Yes in the confirmation window to restart the hardware compo-nent. Click No to cancel.

End

Figure 4-4. Restart Button

Figure 4-5. Restart Hardware Component Confirmation Window (Primary CPU Module)

255-700-368 4-5



Setting Site-Specific Values for the H.248 Media Gateway Control Protocol

The H.248 Configuration tab will become enabled only after you have enabled the H.248 feature under the Feature Turn On/Off tab. Otherwise, the H.248 Configuration tab will be disabled. For information on enabling sys-tem-wide features, see the section “Enabling System-Wide Features” in this chapter.

You must also select the CgSvcCgExplicitCutThrough value in the SVC Cut Through Option field on the Call Control Resource Allocation window and reboot the PSAX device. For information on setting call control resource allocation values, see the section “Call Control Resource Allocation” in this chapter.

Perform the steps in the following procedure to configure H.248.

Begin

1 In the Device window, click the Site-Specific tab.

The Site-Specific page appears.

2 Click the H.248 Configuration tab.

The H.248 Configuration page appears (see Figure 4-6).

3 Select the values for the fields on this window as described in Table 4-1.

4 Click Apply.

End


4-6 255-700-368


Buttons The buttons in this window have the following functions:

Field Descriptions

Figure 4-6. H.248 Configuration Page

Button Function

Apply Sets the values selected on this page.

Refresh Updates the values on this page.

255-700-368 4-7



Table 4-1. Field Descriptions for the H.248 Configuration Page

Field Name Field Values DescriptionMGC IP Address Panel

Primary MGC IP Address

Default: 0

Range: 1

Format: numeric

A Media Gateway Controller (MGC) controls the parts of the call state that pertain to connection control for media channels in a media gateway. Enter the IP address of the primary MGC.

Backup MGC IP Address

Default: 0

Range: 1

Format: numeric

Enter the IP address of the backup MGC, if appli-cable.

Base Root Package Panel

Maximum Number of Contexts

Default: 1000Range: N/A


A context is an association between a collection of terminations. This value indicates the maxi-mum number of contexts that can exist at any given time.

Note: Currently, this field cannot be edited.

Maximum Termi-nations Per Context

Default: 2Range: N/A

Format: numeric

A termination is a logical entity on a media gate-way that sources and/or sinks media and/or con-trol streams. Only point-to-point terminations only can be configured.

Note: Currently, this field cannot be edited.

Normal MG Execu-tion Time

Default: 1000Range: 100–9999


A value set by the MGC to indicate the interval within which the MGC expects a response to any transaction from the MG (exclusive of the net-work delay). The value represents milliseconds.

Normal MGC Exe-cution Time

Default: 1000

Range: 100–9999


This value is settable by the MGC to indicate the interval within which the MG expects a response to any transaction from the MG (exclusive of the network delay). The value represents millisec-onds.

MG Provisional Response Timer Value

Default: 1000Range: 100–9999


The time within which the MGC should expect a Pending Response from the MG if a Transaction cannot be completed. Initially set to Normal MG Execution Time, plus network delay, but may be lowered. The value represents milliseconds.

MGC Provisional Response Timer Value

Default: 0

Range: 100–9999


The time within which the MG should expect a Pending Response from the MGC if a Transaction cannot be completed. Initially set to Normal MGC Execution Time, plus network delay, but may be lowered. The value represents milliseconds.


4-8 255-700-368


Enabling Channelization and Signaling Gateway on an I/O Module

Perform the steps in the following procedure to Enable Channelization and the Signaling Gateway feature. The 6-Port Enhanced E1 Multiservice module will is used in this and proceeding examples.

Begin

1 On the Front Panel window, select an unconfigured port of a module that supports the H.248 gateway control protocol.

Gateway Protocol

Default: CGAPI

Range: N/A

Format: predefined

The Media Gateway Control is software that allows an external device to interconnect to the PacketStar Multiservice Media Gateway systems and act as an adjunct processor to handle IDSN, SS7 signaling, and other call control functions.

CGAPI This Connection Gateway API protocol will be used as the control interface between the incom-ing signal and the PSAX system.

H248 The H.248 protocol will be used as the control interface between the incoming signal and the PSAX system.

Note: You must select this value to enable H.248 gateway protocol on this PSAX system.

Table 4-1. Field Descriptions for the H.248 Configuration Page


255-700-368 4-9



The corresponding Port and Channel Configuration window is displayed (see Figure 4-7).

2 Select Enabled in the Channelization field.

3 Select Enabled in the SG Feature (signaling gateway) field.

4 Click Apply.

By enabling channelization and the Signaling Gateway feature, you can proceed to the task of slot and port configuration for the H.248 gateway Control protocol.

End

Configuring a Slot for the H.248 Media Gateway Control Protocol

Begin

1 From the Device Tree, select an unconfigured port of a module that sup-ports the H.248 gateway control protocol.

Figure 4-7. Enhanced E1 Port and Channel Configuration Window


4-10 255-700-368


2 Right-click the mouse and a menu appears (see Figure 4-8). Select Con-figure H248 TID.

The Terminal ID Configuration window is displayed (see Figure 4-12).


4 In the Pseudo Termination ID field, type your trunk name and the literal string as instructed on the Pseudo Termination ID field. The string instructs the H.248 system software to assign the physical port on this slot to the H.248 protocol.

5 At this time in the configuration, the H.248 Activation field should say Disable. If it says Enable, follow the instructions for this field in the Buttons table above.

6 Click Apply TID.

In this example, after the TID command is applied, the Pseudo Termina-tion ID field will display: Client_Trunk001/1/<lp>/<ch>. Note that the <pp> string has been replaced by “2.” This means that the media gateway controller (MGC) now recognizes the slot physical port 2.

7 Click Apply Activation.

Clicking this button activates the H.248 protocol for the selected slot.

8 Click Close.

End

The next task is to select an available channel and configure the channel.

Figure 4-8. Slot Menu (Displaying H.248 Option)

Figure 4-9. Terminal ID Configuration Window (Slot)

255-700-368 4-11



The buttons on this window perform the following functions:

Button Function


Apply Activation Applies the Enabled or Disabled field value in the H.248 Activation field.

Note: If the value after this command says Disable, do nothing. Other-wise, Enable all the ready termi-nations associated with this slot and then reset the H.248 Activa-tion field, using the Reset button. The field wll then display Dis-able.

Reset Resets the fields to the last set of saved values.

Close Closes the H248 Termination ID Configu-ration window.

Table 4-2. Field Descriptions for the Termination ID Slot Configuration (Slot) Window


Pseudo Termination ID

Default:

Range: 1–32.

Format: Alphanumeric:Trunk_Name/<pp>/<lp>/<ch>

See Rules for Assigning Termination IDs in the last row below of this table.

A “template” used to automatically generate and assign logical termination IDs to all channels on this slot or port. In this instance, the template takes the form of a 32-character user-assigned trunk name, followed by a literal string for physi-cal port <pp>, logical port <lp> and channel <ch>, separated by slash boundary characters (see the format in the Field Values column). This value can be configured at the slot or port level.


4-12 255-700-368


Configuring a Port for the H.248 Media Gateway Control Protocol

Begin

1 On the Front Panel, select an unconfigured port of a module that sup-ports the H.248 gateway control protocol.

2 The corresponding Port and Channel Configuration window is dis-played.

3 Click H248 TID.

The Terminal ID Configuration window is displayed (see Figure 4-12).


H.248 Activation(displayed only if you are configur-ing a channel for any interface type other than the Cir-cuit Emulation)

Default: Disable

Range: N/A

Format: Predefined

Indicates whether H.248 MGC protocol is acti-vated for this module.

Disable The value Disable is the current and desired state. For an explanation, see the Note in the description of the value Enable below.

Enable The value Enable setting enables all ready termi-nations associated with this slot.

Note: The value Enable is a transient action state. After the Apply Activation button is applied, this value reverts back to Disable, which is the current and desired state.

Rules for Assigning Termination IDs:

1. A TID is a string of 32 characters or less, consisting of any or all of these characters types:

a. Alphabetic characters A–Z and/or a–z

b. Numeric characters 0–9

c. Special characters: slash (/) and underscore (_)

d. The < and > characters are allowed if they are part of the three generators <pp>, <lp>, and <ch>.

2. TIDs are case-insensitive. For example, Trunk001/6/12 and TRUNK001/6/12 are the same TID.

3. All TIDs must have unique ID strings in order to be valid.

4. The TID “root” is reserved and cannot be used.

Table 4-2. Field Descriptions for the Termination ID Slot Configuration (Slot) Window


255-700-368 4-13



5 In the Pseudo Termination ID field, type your trunk name and the literal string as instructed on the Pseudo Termination ID field. The string instructs the H.248 system software to assign the physical port on this slot to the H.248 protocol.

6 At this time in the configuration, the H.248 Activation field should say Disable. If it says Enable, follow the instructions for this field in the Buttons table above.

7 Click Apply TID.

In this example, after the TID command is applied, the Pseudo Termina-tion ID field will display: Client_Trunk001/1/<lp>/<ch>. Note that the <pp> string has been replaced by “2.” This means that the media gate-way controller (MGC) now recognizes the slot physical port 2.

8 Click Apply Activation.

Clicking this button activates the H.248 protocol for the selected port.

The following new information is added on the window: [Port: 02] field has been added to the display after TID configuration. This is a local con-figuration on the PSAX. The MGC can not “see” this configuration, as the logical port and associated channels are yet to be generated.

9 Click Close.

End

The next task is to select an available channel and configure the channel.

Note: The trunk name shown in Figure 4-12 is for example purposes only.

Figure 4-10. Terminal ID Configuration Window (Port)


4-14 255-700-368


Buttons The buttons on this window perform the following functions:

Button Function


Apply Activation Applies the Enabled or Disabled field value in the H.248 Activation field.

Note: If the value after this command says Disable, do nothing. Otherwise, Enable all the ready terminations associ-ated with this port and then reset the H.248 Activation field, using the Reset button. The field wll then display Disable.

Reset Resets the fields to the last set of saved values.

Close Closes the H248 Termination ID Configu-ration window.

Table 4-3. Field Descriptions for the H.248 Termination ID Port Configuration Window


Slot (display only)

Default: 1

Range: Depends on chassis type

Format: Numeric

The slot of the module where a Termination ID exists.

Port (display only)

Default: 1

Range: Depends on module type

Format: Numeric

The port of the module that is assigned the pseudo termination ID.

Pseudo Termina-tion ID

Default: 1Range: Depends on module type

Format: Numeric

A unique user-assigned value that enables the H.248 software to simultaneously assign logical termination IDs to all channels on the selected port on a module. This value is also unique within the scope of the sender.

H.248 Activation Default: Disabled H.248 protocol is disabled.

Enabled H.248 protocol is enabled.

255-700-368 4-15



Begin

Configuring a Channel for the H.248 Media Gateway Control Protocol

Begin

1 From the Port and Channel configuration window, click the Channel Configuration tab.

The Channel Configuration page appears.

2 Select an available channel.

Note: Leave the Signaling field at the default Disabled setting.

3 Select CircuitEmulation in the Interface field.

4 Click Apply to Selected.

5 Right-click the mouse and a menu appears (see Figure 4-11). Select Configure H248 TID.

The H.248 Termination ID Configuration window is redisplayed, with additional information (see Figure 4-12).

On this window, note that the Logical Termination ID field now shows the logical port 1 and channel 1 in addition to the physical port 2 shown on the Pseudo Termination ID window. This indicates that the MGC acknowledges the logical termination, whereas prior to TID activation, the MGC did not the recognize the pseudo termination ID.

Also note that this configuration only applies to one channel, 1 in the Logical Termination ID field. The configured channel also shows in the Channel display-only field under the window title. The PSAX device

Figure 4-11. Channel Configuration Menu (Displaying H.248 Option)

Figure 4-12. Terminal ID Configuration Window (Channel)


4-16 255-700-368


cannot simultaneously configure all channels on a port for H.248 at this time. If you desire configure other channels for H.248 at this point, you must return to the Port and Channel Configuration window of the mod-ule you are using and individually select an additional channel to be con-figured for circuit emulation and apply the configuration. This will auto-matically apply H.248 protocol to the selected channel, which you can verify by clicking H248 TID.

On a DS1 module, you can run a script to configure up to 144 channels. On a DS3 module, you can script-configure up to 672 channels. Slots, ports and channels configured for H.248 can only be changed by deleting the configuration before applying another configuration.

End

Table 4-4. Field Descriptions for the DS1 CE H.248 Termination ID Configuration Window


[Slot] (display only)

Default: 1

Range: Chassis dependent

Format: Numeric

The module slot where a termination exists.

[Port] (display only)

Default: 1


Format: Numeric

The module port assigned to the pseudo termina-tion ID.

[Channel] (display only)

Default: 1


Format: Numeric

The DS1 CE module channel assigned to the pseudo termination ID.

Logical Termination ID

Default:


Format:

A unique identifier used by the MGC to refer to a specific termination. A logical termination ID can be assigned either manually or automatically through a pseudo termination ID specified at a higher level (slot, physical port or logical port).

H.248 Activation Default: Disable

Range:

Format:

Specifies the last setting of the pseudo termina-tion ID before H.248 was activated.

Disable The last setting of the pseudo termination ID before H.248 was activated was Disable.

Enable The termination is currently enabled.

255-700-368 4-17


Chapter 4 H.248 Protocol and AQueView® EMS ConfigurationSaving Configuration Values

Saving Configuration Values

! CAUTION:Select Device > Save PSAX Configuration to permanently save the con-figuration.

Applied, but unsaved, configuration data will not be lost unless the PSAX system is restarted, or if power to the PSAX system is lost. Terminating the AQueView EMS will not cause the applied values to be lost because the con-figuration data is stored on the PSAX system, not in the AQueView EMS.

Chapter 4 H.248 Protocol and AQueView® EMS ConfigurationSaving Configuration Values

4-18 255-700-368


The information in this document is for informational use only, is subject to change without notice, and should not beconstrued as a commitment by Lucent Technologies, Inc. This document is without warranty of any kind, either ex-pressed or implied. Lucent Technologies, Inc. assumes no responsibility for any errors, inaccuracies, or omissions. Nei-ther is any liability assumed for damages resulting from the use of the information or instructions contained herein.Lucent Technologies, Inc. is not responsible for any damage or loss to your data or equipment resulting either directlyor indirectly from use of this document.

Lucent Technologies has made a commitment to reduce the environmental impact of its products by reusing and recy-cling material. In keeping with this commitment, this document is printed on paper containing 100% recycled paper.We encourage you to support the principle of reduction, reuse, and recycling of materials by recycling this productwhen it is no longer needed.

Copyright © 2002 Lucent TechnologiesAll rights reserved. Printed in the USA.Part Number: 202M0A8001A1

packetstar psax h.248, user guide - nokia

Documents