Appendix C Example of an HSI Configuration File

 

 

 

 

 

CC_EC_NormalUnspecified

= CC_HC_NormalUnspecified

 

 

 

 

 

 

 

 

CC_EC_NoCircuitAvailable

= CC_HC_NoCircuitChannelAvailable

 

 

 

 

CC_EC_NetworkOutOfOrder

 

= CC_HC_NetworkOutOfOrder

 

 

 

 

CC_EC_PermanentFrameModeOos

 

= CC_HC_PermanentFrameModeConnectionOutOfService

 

 

 

 

CC_EC_PermanentFrameModeOperational = CC_HC_PermanentFrameModeConnectionOperational

 

 

 

 

CC_EC_TemporaryFailure

 

= CC_HC_TemporaryFailure

 

 

 

 

CC_EC_SwitchingEquipCongestion

 

= CC_HC_SwitchingEquipmentCongestion

 

 

 

 

CC_EC_AccessInfoDiscarded

 

= CC_HC_AccessInformationDiscarded

 

 

 

 

CC_EC_ReqCircuitUnavail

 

= CC_HC_RequestedCircuitChannelNotAvailable

 

 

 

 

CC_EC_PrecedenceBlocked

 

= CC_HC_PrecedenceCallBlocked

 

 

 

 

CC_EC_ResourcesUnavailUnspec

 

= CC_HC_ResourceUnavailable

 

 

 

 

CC_EC_QualityUnavail

 

= CC_HC_QualityOfServiceNotAvailable

 

 

 

 

CC_EC_ReqFacilityNotSubscr

 

= CC_HC_RequestedFacilityNotSubscribed

 

 

 

 

CC_EC_OutgoingCallsBarredInCug

 

= CC_HC_OutgoingCallsBaredWithinCUG

 

 

 

 

CC_EC_IncomingCallsBarredInCug

 

= CC_HC_IncomingCallsBaredWithinCUG

 

 

 

 

CC_EC_BearcapNotAuthorized

 

= CC_HC_BearerCapabilityNotAuthorized

 

 

 

 

CC_EC_BaercapNotAvail

 

= CC_HC_BearerCapabilityNotPresentlyAvailable

 

 

 

 

CC_EC_InconOutgoingAccAndSubClass

= CC_HC_InconsistencyAcessInfoSubscriberClass

 

 

 

 

CC_EC_ServiceOrOptionNotAvail

 

= CC_HC_ServiceOrOptionUnavailable

 

 

 

 

CC_EC_BearcapNotImp

 

= CC_HC_BearerCapabilityNotImplemented

 

 

 

 

CC_EC_ChTypeNotImp

 

= CC_HC_ChannelTypeNotImplemented

 

 

 

 

CC_EC_ReqFacilityNotImp

 

= CC_HC_RequestedFacilityNotImplemented

 

 

 

 

CC_EC_OnlyRestrictDigInfoBearer

 

= CC_HC_OnlyRestrictedDigitalBearerInfoCapability

 

 

 

 

CC_EC_ServiceOrOptionNotImpUnspec

= CC_HC_ServiceOrOptionNotImplemented

 

 

 

 

CC_EC_InvalidCallReferenceValue

 

= CC_HC_InvalidCallreferenceValue

 

 

 

 

CC_EC_ChIdNotExist

 

= CC_HC_IdentifiedChannelDoesnotExist

 

 

 

 

CC_EC_SuspendExistButNotThisId

 

= CC_HC_ASuspendedCallExistsThisCallIdDoesNot

 

 

 

 

CC_EC_CallIdInUse

 

= CC_HC_CallIdentityInUse

 

 

 

 

CC_EC_NoCallSuspended

 

= CC_HC_NoCallSuspended

 

 

 

 

CC_EC_CallIdHasBeenCleared

 

= CC_HC_CallHavingTheRequestedCallIdHasBeenCleared

 

 

 

 

CC_EC_UserNotMemberOfCug

 

= CC_HC_UserNotMemberOfCUG

 

 

 

 

CC_EC_IncompatibleDest

 

= CC_HC_IncompatibleDestination

 

 

 

 

CC_EC_NonExistentCug

 

= CC_HC_NonExistantCUG

 

 

 

 

CC_EC_InvalidTns

 

= CC_HC_InvalidTransitNetworkSelection

 

 

 

 

CC_EC_InvalidMsgUnspec

 

= CC_HC_InvalidMessage

 

 

 

 

CC_EC_MandatoryElementMissing

 

= CC_HC_MandatoryInformationElementIsMissing

 

 

 

 

CC_EC_MsgTypeNotImp

 

= CC_HC_MessageTypeNonExistantOrNotImplemented

 

 

 

 

Cisco H.323 Signaling Interface User Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

C-8

 

 

 

OL-4806-01 Rev. A14

 

 

 

 

 

 

Page 168
Image 168
Cisco Systems H.323 manual Appendix C Example of an HSI Configuration File

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.