Appendix C Example of an HSI Configuration File

CC_EC_MsgTypeNotImpOrWrongState =

CC_HC_MessageTypeNotCompatibleWithStateOrNonExistantOrNotImplemented

CC_EC_ElemTypeNotImp = CC_HC_InformationElementParameterNonExistantOrNotImplemented

CC_EC_InvalidElemContents

= CC_HC_InvalidInformationElementContents

CC_EC_MsgInWrongState

= CC_HC_MessageNotCompatibleWithCallState

CC_EC_RecoveryOnTimerExpiry

= CC_HC_RecoveryOnTimerExpiry

CC_EC_ParamUnrecPassed

= CC_HC_ParameterNonExistantOrNotImplementedPassedOn

#When the H323 cause on the left is received from H323,

#the Eisup cause on the right is sent to Eisup.

#Note: the reverse is not true, this is a one way mapping.

#The Eisup to H323 cause map is defined above.

 

CC_HC_UnallocatedNumber

= CC_EC_UnallocatedNumber

 

CC_HC_NoRouteToSpecifiedTransitNetwork

= CC_EC_NoRouteToTns

 

CC_HC_NoRouteToDestination

= CC_EC_NoRouteToDest

 

CC_HC_SendSpecialInformationTone

= CC_EC_SpecialInformationTone

 

CC_HC_MisdialedTrunkPrefix

= CC_EC_MisdialledTkPrefix

 

CC_HC_ChannelUnacceptable

= CC_EC_ChUnacceptable

 

CC_HC_CallAwardedEstablishedChannel

= CC_EC_CallAwardedDeliveredEstCh

 

CC_HC_Preemption

= CC_EC_Preemption

 

CC_HC_PreemptionCircuitReservedForReuse

= CC_EC_PreemptionCctRes

 

CC_HC_NormalCallClearing

= CC_EC_NormalClearing

 

CC_HC_UserBusy

= CC_EC_UserBusy

 

CC_HC_NoUserresponding

= CC_EC_NoUserResponding

 

CC_HC_NoAnswerFromAlertedUser

= CC_EC_NoAnswerAlertedUser

 

CC_HC_SubscriberAbsent

= CC_EC_SubAbscent

 

CC_HC_CallRejected

= CC_EC_CallRejected

 

CC_HC_NumberChanged

= CC_EC_NumberChanged

 

CC_HC_RedirectionToNewDestination

= CC_EC_RedirectionToNewDest

 

CC_HC_ExchangeRouteError

= CC_EC_RoutingError

 

CC_HC_NonSelectedUserClearing

= CC_EC_NonSelectedUserClearing

 

CC_HC_DestinationOutOfOrder

= CC_EC_DestOutOfOrder

 

CC_HC_InvalidNumberFormat

= CC_EC_InvalidNumberFormat

 

CC_HC_FacilityRejected

= CC_EC_FacilityRejected

 

CC_HC_ResponceToStatusEnquiry

= CC_EC_ResponseToStatusEnquiry

 

CC_HC_NormalUnspecified

= CC_EC_NormalUnspecified

 

 

Cisco H.323 Signaling Interface User Guide

 

 

 

 

 

 

 

OL-4806-01 Rev. A14

 

 

C-9

 

 

 

 

 

Page 169
Image 169
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.