Cisco Systems H.323 manual Configuring G.726 on the Cisco HSI

Page 67

Chapter 3 Provisioning the Cisco HSI

HSI Feature Configuration

Configuring G.726 on the Cisco HSI

The G.726 codec enables transcoding a PCM channel to or from an ADPCM data stream. The standard supports four data rates:16, 24, 32 and 40 kbit/sec.

G.726 capability is advertised by the Cisco HSI and other H.323 gateways/endpoints in H.225 fast-start elements, in H.245 (tunneled or a separate TCP/IP connection) terminal capability (TCS) messages, and open logical channel (OLC) messages.

Currently, H.323 devices use several different methods to advertise G.726. ITU G.726 Annex B defines one method, referred to in this document as g726-generic. Cisco H.323 gateways (for example, the Cisco AS5400) support an alternate method referred to as g726-cisco. There is another method used by the OpenH323 project; however, the Cisco HSI does not support that method.

MGCP gateways advertise G.726 capability using the method described in RFC 3551 (RTP Profile for Audio and Video Conferences with Minimal Control). The four data rates use dynamic payloads; however, the 32kbit/sec data rate, alternatively, can have a static payload value of 2 (this alternative value is being phased out).

You can configure the Cisco HSI for 32kbit/sec MGCP support using dynamic or static payload values. In addition, you can configure the Cisco HSI to support g726-generic and/or g726-cisco for the H.323 signaling. If possible, it is best to select g726-cisco for your network because it offers additional flexibility.

The g726-generic method cannot indicate the data rate in H.245 TCS messages. The ITU standard specifies that the data rate is only advertised in the OLC messages.

Note The H.245 ASN.1 syntax supports advertising the bitrate in TCS messages; however, G.726 Annex B prohibits advertising the bitrate in TCS messages. The Cisco HSI advertises the bitrate in the TCS messages as a “hint”; however, H.323 gateways/endpoints might not extract the field and take advantage of the presence of the bitrate in the TCS message.

The fact that the g726-generic method cannot indicate the data rate in an H.245 TCS message is not a problem if the MGCP gateway and your network are designed to support all data rates for this codec. However, if all data rates are not supported, it is possible for the remote endpoint/gateway to select a non-preferred or non-supported data rate in the OLC message.

Note For example, a data-rate preference list may establish the following order: G.726-16kbit/sec (highest preference), G.711-Alaw (second preference), G.726-24kbit/sec (lowest preference). In this case, a remote endpoint could select G.726-24kbit/sec in the OLC message; whereas, the Cisco HSI would prefer G.726-16kbit/sec. In this example, the next preferred codec ought to be G.711 A-law and not G.726-24kbit/sec. However, the g726-generic limitation enables the remote endpoint to select the least preferred codec.

If a data-rate preference list specifies only a single rate (for example, G.726-16kbit/sec), it is not possible to advertise this fact in the TCS message. Subsequently, the remote endpoint may attempt to open the media stream using an unsupported data rate (perhaps, G.726-24kbit/sec).

Whenever OLC messages are exchanged and a non-supported G.726 data rate is detected, to prevent unnecessary call clearing, the Cisco HSI always attempts to send the data rate selection to the MGCP gateway. If the MGCP gateway does not support the selected data rate, it sends a message to the Cisco PGW to clear the call.

 

 

Cisco H.323 Signaling Interface User Guide

 

 

 

 

 

 

OL-4806-01 Rev. A14

 

 

3-27

 

 

 

 

 

Image 67
Contents Corporate Headquarters Cisco H.323 Signaling Interface User GuideCisco H.323 Signaling Interface User Guide N T E N T S Introduction to MML Command Operation for HSI Hairpin 38 Fax RADVision Logging Eisuppathfailure Endpointcallcontrolinterfacefailure MML Help OL-4806-01 Rev. A14 Skeleton Configuration File Xii Document Objectives System AdministratorAudience This document is organized as follows Preface Document OrganizationSystem Operator System TechnicianBoldface Command abcDocument Conventions Meaning Comments and ExamplesHardware Documentation Global configuration modeRelated Documentation Release NotesWorld Wide Web Obtaining DocumentationSoftware Documentation Related DocumentationCisco.com Obtaining Technical AssistanceOrdering Documentation Documentation FeedbackCisco TAC Web Site Technical Assistance CenterCisco TAC Escalation Center Cisco HSI Overview IntroductionPGW Cisco HSI System DescriptionIP Network Call Control Subsystem OAM SubsystemRADVision H.323 New Features in Cisco HSI ReleaseOperational Environment Hardware RequirementsSoftware Requirements Cisco HSI RecoveryCisco HSI does not implement security features Cisco HSI System LimitationsOL-4806-01 Rev. A14 Installing the Operating System Installing and Configuring Cisco HSI Software IntroductionHardware and Software Requirements Before You Start Installing the Cisco HSIConfiguring Groups and Users Check Preinstallation Task# chmod 777 .cshrc Cisco HSI Installation InformationSource /opt/GoldWing/currentPM/local/setup.gw.csh # vi .cshrcSubdirectory Contents This command displays the following text Installing Cisco HSI# tar xvf GoldWing-4.1.tar Following text displays # cd /export/BUILDS/4.1 # ./install.shType the VSC1 name and press Enter Following text displays ## Executing checkinstall script. Modified Environment is VERSION=4.1 Cisco HSI-A # /etc/init.d/CiscoGW start Dual HSI Example Configuration ScriptStarting the Cisco HSI Example# /etc/init.d/CiscoGW stop Configuring the Cisco HSIStopping the Cisco HSI Upgrading the Cisco HSIRemoving the Cisco HSI # ./uninstall.sh# cd /opt/GoldWing # ls -l Type y and press Enter. The following text displays ## Removing installed package instance OTTgw000Provisioning the Cisco HSI Cisco HSI ConfigurationProv-sta Prov-cpy Prov-stp MML Configuration CommandsCommand Command DescriptionEtc/init.d/CiscoGW start Introduction to MML Command Operation for HSIInitiating an MML Session to Enable Dtmf on the HSI Verifying the ConfigurationReverting to the Base Configuration System Configuration DataStatic System Data Parameter Type Description Option. The default value is Parameter, set it to EnabledCan receive T.38 FAX data. The default value is Default value is 0xc8Changing Static System Data Issue the command restart-softwconfirmDynamic System Data Parameter Description DefaultOVLDLEVEL1THRESHLOWER OVLDLEVEL1PERCENTOVLDLEVEL3PERCENT OVLDLEVEL1FILTERStack Configuration Parameters Nonprovisionable DataMML Provisionable Data System ParametersNull Parameter Name Description Type Example Update TypeProv-addname=q931,maxCalls=2000 Prov-addname=ras,maxfail=3 RAS ParametersParameter Name Description Type Example ManualRAS If this parameter is presentAllowCallsWhenNonReg If this parameter is present, it String H323ESP Prov-addname=h245,masterSlave.timeout=5R0.2.4 Immediate Assigns to each version Parameter Name Type UpdateINTEGER0,1 Quick Reference for Important Parameters Codec SelectionParameter Name Parameter Value Description 14presents important static system data parameters Parameter Name Parameter Values Description VSCBPORTNUMBER1/2 VSCBIPADDR1/215presents common RAS parameters Parameter Name Parameter Value HSI Feature ConfigurationEmpty Capability Set Asymmetric Codec TreatmentHairpin 38 Fax Configuring T.38 Fax on the Cisco Pstn GatewayConfiguring T.38 Fax on a Cisco IOS H.323 Gateway Configuring T.38 Fax on a Cisco IOS Mgcp GatewayProv-edname=ccpackage,hash=C Configuring Clear Channel on the Cisco HSIProv-addname=sysconfigstatic,informationmsgdisabled = True HSI Support for Tech PrefixesClear Channel Parameters Example Value Example Configuration Configuring G.726 on the Cisco HSI Configuring the Payload Type for the Mgcp Parameter Example Value Configuration ExampleConfiguring Cisco HSI g726-cisco Configuring Cisco HSI g726-generic OL-4806-01 Rev. A14 Parameter Configuring G.729 Annex and G.729 Annex BOL-4806-01 Rev. A14 Stopping Call Processing Restarting the Cisco HSI ApplicationReporting the Cisco HSI Status Starting Call ProcessingStopping the Call Processing Application Starting the Call Processing ApplicationCounter Name Measurement Type Comments Call-Related MeasurementsFcotgcallsucctot FcinccallatttotFcinccallsucctot Fcotg CallatttotTermcapxchgatttot AvgroundtripdelayMasterslaveatttot MasterslavesucctotOverload Resetting MeasurementsRetrieving Counters Overload Level Following MML commands set overload data Setting Overload DataRetrieving Overload Data Log File Location LoggingRotating Log Files Convention for Naming the Log FileLog messages have the following format Log MessagesLogging Levels Log Message PackagesRADVision Logging Setting GappingSetting Logging Levels GappingSet-gappingbothcalltype=all,percent=60 Retrieving Call Gapping DataAlarm Severity Levels Alarms OverviewDebounce Severity Level Description Retrieving and Reporting AlarmsSnmp Trap Types Informational Event RequirementsTo display all current alarms, use the rtrv-almsMML command Retrieving Alarm MessagesNoncontinuous Mode Continuous ModeYYYY-MM-DD Acknowledging and Clearing AlarmsElement Description SystemId Name of your device and its identifierAlarm Event and Reference Severity Level Alarms ListSeverity Level and Trap Type TroubleshootingTroubleshooting DescriptionEisuppathfailure One of the two links to a single Cisco PGW 2200 has failed This alarm has not been implementedLowdiskspace Percentage of disk usage is greater than the alarm limitVscfailure Use the clr-almcommand to attempt to clear the alarmThis is an informational event Running configuration has been modifiedSeverity level is minor. The trap type is Severity level is information. The trap type isEndpointcallcontrolinterfacefailure RADVision stack reports this alarmGappedcallnormal OVERLOADLEVEL1 User has entered the stp-callproccommand through the MML ProvisioningsessiontimeoutDetailed Logging Starting an MML Command Session in the Cisco HSI MML User Interface and Command Reference IntroductionEtc/init.d/CiscoGW start Exit out of superuser MML Command Syntax MML CommandsMML Command Conventions Mml Symbol DescriptionStarting an MML Session Case SensitivityCreating a Batch File Batch FilesStarting a Batch File Rtrv MML ResponsesStatus Messages Status Message DescriptionQuitting an MML Session Error MessagesError Message Definition Description MML HelpThis section describes the following MML commands MML Command ReferenceAck-alm Ack-almevent=alarm eventClr-almevent=alarm event Clr-almcommand clears an alarm eventClr-alm Examples DiaglogRedisplay HelpStart EndRTRV-CTR Helprtrv-ctrProv-add Prov-addcommand adds a component to the Cisco HSIProv-add Prov-cpyConfirm Usage GuidelinesSession Sysconfigstatic Sysconfigdynamic H323sys Ras H245 Q931Related Commands Description Prov-dltProv-ed Prov-edcommand modifies a provisioned componentGw mml prov-edname=ras,maxfail=7 Prov-stasrcver=active, dstver=dummy1 MML batch feature to import the exported dataInstallation Prov-expProv-rtrv Gw mml prov-rtrvlist Name rasGw mml prov-rtrvname=ras Gw mml prov-rtrvsessionProv-stasrcver=version,dstver=version Prov-staProcess that started the provisioning session Prov-stpProv-stpconfirm prov-stpsession nameconfirm Session nameGw mml prov-stpuk9confirm Gw mml prov-stpconfirmGw mml prov-stpmml2confirm Radlogfile namestart stop QuitRadlog QuitGw mml restart-softw Gw mml restart-softwconfig2Restart-softw Gw mml restart-softwinitAck-alm Rtrv-almsRtrv-alms rtrv-almscont ContSyntax Description Examples Clr-meas Resets a measurement counterRtrv-calls Rtrv-ctrSet-dest-state Signalling path to the PGWService is or out of service OOS Rtrv-destRtrv-log Rtrv-gappingSyntax Description Rtrv-mml Status of the Cisco HSI Rtrv-neRtrv-ne-health Rtrv-neGw mml rtrv-overload Rtrv-overloadRtrv-overload Gw mml rtrv-ne-healthGw mml rtrv-softw Rtrv-softwOOS Set-dest-stateRtrv-dest Set-gapping Data to be activated Set-logPackage One of the packages in the Cisco HSIUpper=number Set-overloadLevel 1 level 2 level Lower=numberSta-callproc Related Commands RetrieveSta-softw Sta-trc Sta-trccommand starts the call processing tracing functionSta-callproc Starts call processing Rtrv-calls Stp-callStp-callcallref=x stp-callall CallrefStp-callproc Stp-callproctimeout=TStp-trc Stp-trcSta-trc Starts the call processing tracing function OL-4806-01 Rev. A14 RASmaxFailD1-200 Skeleton Configuration FileSysconfigstatic VSCAPORTNUMBER2 SysconfigstaticSysconfigstatic HOSTPORTNUMBER1 S Sysconfigstatic HOSTPORTNUMBER2 SCCECOperatorPriorityAccess CCECChannelOutOfServiceCCECCugAccessBarred CCECNetworkAddressExtensionError SSysconfigstatic CCECPriorityForcedRelease Sysconfigstatic CCECPrefix0DialledInErrorSysconfigstatic CCECPrefix1DialledInError Sysconfigstatic CCECPrefix1NotDialledSysconfigdynamic OvldLevel3Percent 100 AlarmDebounceTime 60000ResponseTimeOut 200 OvldLevel2ThreshUpperCPU 100Q931 H245tunneling H245 MasterSlave.timeout 65535 MasterSlave.manualOperationQ931 OverlappedSending Q931 EarlyH245H245 Modesi.audio.g711Ulaw56k H245 Modesi.audio.g711Alaw64kH245 Modesi.audio.g711Alaw56k H245 Modesi.audio.g711Ulaw64kEisup Accnociecdi AccgdesAccgdtd AccnocivcAccwaitrelretry AccnumrelretriesAccwaitrlcfail CCPackage CCECRecoveryOnTimerExpiry CCPackage CCECServiceOrOptionNotAvailCCPackage CCECServiceOrOptionNotImpUnspec CCPackage CCECInvalidElemContentsCCPackage CCHCAccessInformationDiscarded CCPackage CCHCExchangeRouteErrorCCPackage CCHCPermanentFrameModeConnectionOutOfService C CCPackage CCHCSwitchingEquipmentCongestionCCPackage CCHCBearerCapabilityNotImplemented CCPackage CCHCServiceOrOptionNotImplementedCCPackage CCHCInvalidInformationElementContents CCPackage CCHCRecoveryOnTimerExpiryCisco H.323 Signaling Interface User Guide Trace Trigger2.h323.TerminatingIPAddress Trace Trigger2.h323.CalledPartyNumberTrace Trigger2.h323.OriginatingIPAddress Trace Trigger2.h323.OriginatingIPMaskEisup Waittimebeforefailovermillisec Eisup RudptimercheckperiodmsecQ931 NonQuotedConst H323 MaxTimers TickPeriod DefaultSDPtQ931 ConnectTimeoutConst NumberNoRangeConst# Logging Package Example of an HSI Configuration FileAppendix C Example of an HSI Configuration File Appendix C Example of an HSI Configuration File Appendix C Example of an HSI Configuration File # Call Control Package Accnociecdi = Accnocicci = Accnocisi = Acctmr = # FCIAccgdes = Accgdtd =Appendix C Example of an HSI Configuration File Appendix C Example of an HSI Configuration File Appendix C Example of an HSI Configuration File Appendix C Example of an HSI Configuration File # Gapping Package # Faultmanagement Package# Trace Package Appendix C Example of an HSI Configuration File # Application Package # Eisup PackageLogprio = Trace # Dynamic System DataAlternategatekeeperip Alternategatekeeperport = AlternategatekeeperidOVLDLEVEL3FILTER = Normal = CchcdefaultOVLDLEVEL2FILTER = Normal Normal OVLDLEVEL2THRESHUPPERCPUCCECCallingDroppedWhileOnHold CCECNetworkAddressExtensionErrorCCECBlacklistBNumberMatched CCECBlacklistCliLengthInvalidCCECRemoteProcError CCECPrefix0DialledInErrorCCECPrefix1DialledInError CCECProtocolErrorUnspecAppendix C Example of an HSI Configuration File OL-4806-01 Rev. A14 Name Value Isup Name-to-Cause Value LookupAppendix D E-ISUP Name-to-Cause Value Lookup Cisco H.323 Signaling Interface User Guide OL-4806-01 Rev. A14 Value Name Isup Cause Value-to-Name LookupAppendix E E-ISUP Cause Value-to-Name Lookup Appendix E E-ISUP Cause Value-to-Name Lookup OL-4806-01 Rev. A14 Name-to-Cause Value Lookup Appendix F H.323 Name-to-Cause Value Lookup Cause Value-to-Name Lookup Appendix G H.323 Cause Value-to-Name Lookup Vscfailure ConfigchangeLowdiskspace OVERLOADLEVEL1 OVERLOADLEVEL2 OVERLOADLEVEL3 StopcallprocessingData Configurable B-1 Constant B-1 Clr-meas commandCodec parameters Commands ack-alm clr-alm clr-meas diaglog Configchange alarmHSI IsupEndpointcallcontrolinterfacefailur EndpointchannelinterfacefailureMan-machine language MML commands case sensitivity A-3conventions A-2Nonprovisionable data OverlappedSending Alarmdebouncetime CiagentscanperiodCodec Dynamic system data 245 System Logdirectory Logfilerotateinterval LogfilerotatesizePkinst file Related documentationReliable User Datagram Protocol 931 See RudpManager MIB Subagent Stp-softw commandVscfailure alarm Snmp
Related manuals
Manual 32 pages 39.25 Kb

H.323 specifications

Cisco Systems H.323 is a set of standards designed for transmitting audio, video, and data over packet-switched networks. It is a critical technology that enables real-time communication and has become integral to the world of VoIP (Voice over Internet Protocol) and video conferencing applications. Originally developed by the ITU-T, H.323 has been widely adopted and implemented by Cisco Systems, allowing organizations to leverage reliable and scalable communication solutions.

One of the standout features of H.323 is its ability to support interoperability among varying equipment and platforms. This means that devices from different manufacturers can communicate seamlessly, which is vital in a diverse technical environment. H.323 does this by defining protocols that handle signaling, media transport, and control, ensuring that various systems can work together effectively.

Key technologies utilized within H.323 include H.225 and H.245 signaling protocols. H.225 is responsible for call setup and management, establishing communication between endpoints. In contrast, H.245 manages the negotiation of media channels, allowing devices to configure themselves based on the capabilities of each other. This adaptability is crucial for dynamic network conditions typical in VoIP applications.

Another defining characteristic of H.323 is its support for multiple types of multimedia communication, including point-to-point and multipoint calls. This flexibility supports everything from simple audio calls to complex videoconferencing setups, where many participants can share video and audio streams concurrently. Cisco enhances this capability through its hardware and software offerings, optimizing performance for conference calls.

H.323 also features robust error resilience mechanisms. This ensures that real-time data, which is typically sensitive to delays and losses, can be transmitted with minimal disruption. Moreover, it facilitates quality of service (QoS) implementation, allowing organizations to prioritize voice and video traffic over less critical data services, thereby improving the overall user experience.

In conclusion, Cisco Systems H.323 stands out as a comprehensive solution for real-time communication over packet-based networks. Its main features, including interoperability, multimedia support, and enhanced error resilience, position it as a relevant technology in both corporate and personal communication settings. As organizations continue to adopt cloud and hybrid communication models, H.323 remains a reliable backbone for ensuring connectivity and collaboration across diverse platforms.