NN Multimedia Communication Portfolio Multimedia Communication Server 5100 H.323 Gateway Basics. MCS Standard (02.

Transcription

1 NN Multimedia Communication Portfolio Multimedia Communication Server 5100 H.323 Gateway Basics MCS Standard (02.02) February 2004

2

3 Product overview How this chapter is organized This chapter is organized as follows: Functional description on page 3 Hardware on page 13 Software on page 13 Interfaces on page 13 Functional description The H.323 Gatekeeper component of the Multimedia Communication Server 5100 (MCS 5100) solution is an optional component and is deployed on its own Sun Fire* v100 server. The H.323 Gatekeeper allows the MCS 5100 system to interface with gateways that use the H.323 protocol and to integrate them with the Session Initiated Protocol (SIP) applications, SIP PRI Gateways, and other H.323 endpoints registered with the SIP Application Module. Network overview The H.323 Gatekeeper combines the functions of an H.323 Gatekeeper and an H.323/SIP gateway into a single network element. By registering devices that use the H.323 family of protocols with the SIP Application Module, connectivity can be provided between those devices and a variety of other devices supported by the SIP Application Module, including registered SIP applications and the PRI gateway. Figure 1, H.323 Gatekeeper network overview contains a network view of the elements. Note: Note that H.323 endpoints directly provisioned on the system are referred to as local endpoints. Gatekeepers that the H.323 Gatekeeper interacts with are referred to as external gatekeepers. MCS 5100 H.323 Gatekeeper Basics

4 4 Endpoints managed by these gatekeepers are referred to as external endpoints. Reference to an endpoint means a local endpoint unless otherwise stated. Figure 1 H.323 Gatekeeper network overview NN MCS Standard (02.02) February 2004

5 5 Figure 2, H.323 Gatekeeper signaling relationships shows the network elements with which the H.323 Gatekeeper communicates directly. Figure 2 H.323 Gatekeeper signaling relationships Protocols H.323 s five signaling protocols are H.225 RAS (Registration, Admission, and Status) protocol is optional and is only used with gatekeepers transported over UDP. It uses a transactional, well-known port, 1719, and may use other ports dynamically specified. The dynamic port is provided from GRQ, GCF, RRQ, ARQ, LRQ, LCF, IRQ, IRR. H.225 Call Control, based on Q.931 with User-User Information Element carrying H.323-specific information (ASN.1 PER format) is transported over TCP connection channel and can be dynamically established on call setup well-known port: 1720, or specified within RAS messages (RRQ,RCF, ACF, ARJ, LCF, IRR).There is no keep-alive mechanism as Q931 relied on Q921 for link maintenance. MCS 5100 H.323 Gatekeeper Basics

6 6 H.245 used for media channel negotiation and control dynamic allocation of ports on call setup and renegotiation transported over TCP Real Time Protocol and Real Time Control Protocol, both are used for bearer traffic. Both use dynamically allocated UDP ports (generally randomly selected from a well known port range). H.323 Gatekeeper services The H.323 Gatekeeper provides H RAS Signaling (for Gatekeeper functionality) (See Functionality on page 8.) Supports mandatory and optional registration Supports static (through H.323-id and IP address) and dynamic (based only on H.323-id or E.164 number) endpoint registration Gatekeeper-routed call signaling (See Gatekeeper-routed call signaling on page 12.) Fast Connect/Fast Start support (See Fast Connect/Fast Start Support on page 12.) H.323 call setup without fast connect (See H.323 Call setup without fast connect on page 12.) H.245 media manipulation (See H.245 media manipulation on page 12.) gatekeeper-to-gatekeeper interworking tunneling of non-standard data, including QSIG, MCDN, and UIPE-formatted messages DTMF in H.245 UserInputIndication (Out-of-band DTMF) in-band DTMF through normal RTP (not RFC 2833 compliant) symmetrical codec operation and recovery procedures (in other words, codec negotiation) wide range of audio codec support (G.711 A-law, G.711 mu-law, G.729A, G.729B). Supported G.711 packet times are 10, 20, and 30 ms. Generic Silence Suppression RTP/RTCP Gatekeeper discovery Converged Desktop support over Simring NN MCS Standard (02.02) February 2004

7 7 Support for TCP (H.225) trunking H.323 access over a single TCP connection. H.323 Gatekeeper functionality (gatekeeper routed) to accommodate H.323 endpoints an H.323/SIP protocol gateway between H.323 endpoints and the SIP Application Module number qualification for H.323 endpoints support for private dialing plans, such as UDP and CDP, to interwork with Enterprise configurations In addition to the H.323 Gatekeeper services already available through H.323 endpoints, the MCS 5100 solution provides H.323 endpoints with the following telephony services: TON/NPI support for each call for H.323 Basic UDP/CDP Dialing to interwork with Enterprise products. Routing using SIP Application Module translation services, based on E.164, Private Number, or alias-id PRI and analog interworking through SIP gateways Calling Line ID between both H.323 and SIP endpoints Calling Name ID between both H.323 and SIP endpoints (not supported by M1/Succession 1000) Call Transfer Three-way call (audio conferencing) Call Forward Call Reject Call Pass Ring-back Simultaneous Ringing Sequential Ringing SIP user-based Call Screening Routing based on E.164, Private Number, alias ID (M1 does not support alias ID) Call accounting using IPDR generation Bandwidth Management and multi-zone support MCS 5100 H.323 Gatekeeper Basics

8 8 Fault Tolerance Scalability (by deploying on other V100 servers, similar to the addition of SIP PRI gateways to increase PRI connectivity) Functionality The H.323 Gatekeeper is designed to interact with H.323 endpoints (specifically H.323 gateways and gatekeepers) and with the SIP Application Module. While an H.323 network consisting solely of endpoints is capable of performing intra-network communication, the addition of the H.323 Gatekeeper, and its interaction with the SIP Application Module, provides a high-level control element that not only facilitates communication between networks and other administrative entities, but also provides functions that individual network elements themselves cannot. These functions are Address translation: Telephony addresses such as digit patterns are translated into network call signaling addresses in the form of IP address and port. The H.323 Gatekeeper does this by forwarding all calls to the SIP Application Module, which then performs the translation. Admission control: Generally, endpoints that are known to the H.323 Gatekeeper through pre-provisioned information are allowed to access the network, whereas devices that are unknown to the gatekeeper are denied access. Bandwidth management: The H.323 Gatekeeper may monitor the aggregate bandwidth available on the network under its control and allow or deny calls based on whether bandwidth is available. Call control signaling: The H.323 Gatekeeper may act on behalf of endpoints or gateways under its control by forwarding call signaling messages to the SIP Application Module, which will then route the call to an appropriate destination. This is referred to as the Gatekeeper-routed model, and it provides the H.323 Gatekeeper with the ability to use additional functions provided by the SIP Application Module. H.323 endpoints interact with the H.323 Gatekeeper directly through the following RAS messages: Gatekeeper Request (GRQ) messages to locate a gatekeeper with which to register Registration Request (RRQ) messages to register with the gatekeeper, which forwards the request to the SIP Application Module Admission Request (ARQ) messages to request admission to the network before placing or accepting a call NN MCS Standard (02.02) February 2004

9 9 Unregistration Request (URQ) messages to unregister from the gatekeeper, which forwards the request to the SIP Application Module Bandwidth Request (BRQ) to modify bandwidth allocation during a call For each type of request message there is a pair of corresponding response messages: a confirm message, which provides an indication of successful completion, and a reject message, which indicates that the requested operation could not be performed. Thus, for the Registration Request (RRQ) message there is a Registration Confirm (RCF) and a Registration Reject (RRJ); for the Admission Request (ARQ) message there is an Admission Confirm (ACF) and an Admission Reject (ARJ). All request messages contain a mandatory requestseqnum field that the receiver of the message echoes back in the response it sends. Additional features The H.323 Gatekeeper supports the following additional features: Unicast/multicast channels The H.323 Gatekeeper is capable of receiving request messages on two different types of UDP communication channels: unicast and multicast. When using unicast communication, H.323 entities know in advance the IP address of the gatekeeper with which they are communicating, and they send request messages to well-known UDP port 1719 at that IP address. In some cases, H.323 entities either do not know the IP address of their gatekeeper, or they wish to send the same message to a group of gatekeepers. In these cases, multicast communication is performed by sending certain types of request messages to the gatekeeper discovery multicast address: , port Gatekeepers that receive request messages on the unicast port always either return a confirmation or a reject message to the requesting entity. The multicast address is typically used for Gatekeeper Request (GRQ). The multicast address is not used for Registration Request (RRQ), Admission Request (ARQ) or Unregistration Request (URQ) messages. Note that the actual registration is not only with the H.323 Gatekeeper but in conjunction with the SIP Application Module. All registration requests received by the H.323 Gatekeeper are MCS 5100 H.323 Gatekeeper Basics

10 10 forwarded to the SIP Application Module where registration status is tracked. For more information about call flows, see Appendix A Call flows. Gatekeeper-to-Gatekeeper interworking In addition to interacting with H.323 endpoints, the H.323 Gatekeeper, as a result of this feature activity, communicates with other H.323 gatekeepers. This is done through RAS Location Request (LRQ) messages. This interaction is frequently referred to as gatekeeper-to-gatekeeper communication. Gatekeeper-to-gatekeeper communication supports the routing of calls between H.323 endpoints. When an H.323 gatekeeper receives an Admission Request from one of its subtending endpoints containing destination information like dialed digits for which the gatekeeper is unable to determine the destination call signaling address, it uses gatekeeper-to-gatekeeper communication to see if there is another H.323 gatekeeper that does know how to route the call and can provide the destination call signaling address. A gatekeeper wishing to initiate gatekeeper-to-gatekeeper communication with the H.323 Gatekeeper can send an LRQ message on either unicast or multicast UDP communication channel. When using unicast communication, an H.323 gatekeeper knows in advance the IP address of the H.323 Gatekeeper with which it will communicate and sends the LRQ to the UDP port 1719 at that IP address. In some cases, an H.323 gatekeeper either does not know the IP address of the H.323 Gatekeeper, or wishes to send the same message to a group of gatekeepers. In these cases, the H.323 gatekeeper sends the LRQ to the gatekeeper discovery multicast address ( , port 1718). When it receives an LRQ on the gatekeeper discovery multicast address, the H.323 Gatekeeper will only respond (through an LCF message) if the call is determined to be route-able; the H.323 Gatekeeper will never respond in any way to an LRQ received on the gatekeeper discovery multicast address if it determines that the call is not route-able. The H.323 Gatekeeper may itself initiate gatekeeper-to-gatekeeper communication when it is unable to determine the destination call signaling address for a call by sending an LRQ to another H.323 gatekeeper and waiting for the needed information to arrive in an LCF response message. H.323 gateway to H.323 gateway interoperability is fully supported between Succession 1000 and the MCS 5100 solution. In order for the Branch Office and Virtual Office features to work, the NN MCS Standard (02.02) February 2004

11 11 Succession 1000 Network Connect Server must be configured with the H.323 endpoints. The Succession 1000 Gatekeeper is currently the only available Succession 1000 Network Connect Server and, therefore, it is best to have the CSE 1000 virtual trunking and Network Connect Server both use the CSE 1000 Gatekeeper. Alternatively, the virtual trunking can use the H.323 Gatekeeper and in addition a separate signaling server is required to run a primary Gatekeeper for the Succession 1000 Network Connect Server. In this case the H.323 endpoints are non-ras endpoints. The private numbering plan would have to be configured on both the H.323 Gatekeeper and the Succession 1000 Gatekeeper. If the Branch Office and Virtual Office features are not required within the Succession 1000 portion of the network, then the Succession 1000 H.323 gateway can be used in a network with the MCS 5100 and without the CSE 1000 Gatekeeper. Gatekeeper discovery In some cases, H.323 endpoints are provisioned with the IP address of their gatekeeper. In other cases, endpoints make use of gatekeeper auto-discovery to locate their primary gatekeeper when initially establishing communication, or to locate an alternate gatekeeper in cases where an endpoint experiences a failure of communication with the primary gatekeeper. Even when an endpoint is pre-provisioned with the IP address of its gatekeeper, it may use auto-discovery to confirm that the gatekeeper is available. An endpoint performs gatekeeper auto-discovery by sending a Gatekeeper Request (GRQ) message to either the unicast gatekeeper address (if it knows the IP address of its gatekeeper) or the multicast gatekeeper address (if it does not know the IP address of its gatekeeper). The H.323 Gatekeeper processes a GRQ message as follows: If the GRQ was received on the gatekeeper s unicast address, the H.323 Gatekeeper will unconditionally send a Gatekeeper Confirm (GCF) message containing its unicast communication address for RAS messages in the rasaddress field. If the GRQ message was received on the gatekeeper s multicast address, the H.323 Gatekeeper will verify that the requesting entity is a provisioned endpoint by examining the rasaddress field of the GRQ message. If the rasaddress field contains the IP address of a provisioned endpoint, the H.323 Gatekeeper will respond with a Gatekeeper Confirm (GCF) message containing its unicast communication address in the rasaddress field. Fault tolerance MCS 5100 H.323 Gatekeeper Basics

12 12 The H.323 Gatekeeper provides fault tolerance through the deployment of a secondary Gatekeeper instance. However, it also uses a reliability mechanism that hides this fact from the endpoints; that is, both the primary and secondary Gatekeeper appear to share the same IP address. The endpoint, on detection of failure (and no defined alternate), sends a multicast Gatekeeper Request (GRQ), and the newly activated secondary responds to this and takes over service. Dynamic registration of an endpoint IP address using RRQ A registered endpoint must send RRQ messages to its gatekeeper periodically in order to keep its TTL timer from expiring. As long as the endpoint continues re-registering within the TTL window, the H.323 Gatekeeper will respond with an RCF. If the TTL timer expires for a registered endpoint, the H.323 Gatekeeper will send an Unregistration Request (URQ) message to the endpoint. If the endpoint believes that it is still alive, this URQ has the effect of forcing the endpoint to re-register. In conjunction with the URQ, the H.323 Gatekeeper will unregister the endpoint with the SIP Application Module by sending a SIP REGISTER message to it. H RAS signaling Gatekeeper-routed call signaling Fast Connect/Fast Start Support H.323 Call setup without fast connect H.245 media manipulation Tunneling of non-standard data, including QSIG, MCDN, and UIPE-formatted messages DTMF in H.245 UserInputIndication (out-of-band DTMF) Converged support using Simring In-band DTMF using normal RTP (not RFC 2833 compliant) Symmetrical codec operation and recovery procedures (in other words, codec negotiation) Wide range of audio codec support (G.711 A-law, G.711 u-law, G.729AnnexA, G.729wAnnexB, G.729AnnexAwAnnexB) Generic silence suppression RTP/RTCP Support for TCP (H.225) trunking H.323 access over single TCP connection NN MCS Standard (02.02) February 2004

13 13 Hardware The Sun Fire v100 is the required hardware for the H.323 Gatekeeper platform. See Table 1, Hardware configuration for the required hardware configuration. Table 1 Hardware configuration Required hardware Description Quantity Sun Fire v100, rack mountable, small footprint Minimum of 4 for non-redundant setup; 8 for redundancy. 500MHz UltraSparc IIi processor KB external cache 1 GB RAM IDE, 40GB hard 7200RPM 2 24X CD-ROM 1 10/100 Base-T internet ports 2 USB ports 2 Software Interfaces The H.323 Gatekeeper software can be deployed on a specific node and can be deployed on any server as long as the engineering guidelines are followed. The H.323 Gatekeeper requires the following be deployed in the same network: Sip Application Module Provisioning Module Management Module The H.323 Gatekeeper interoperates with the following H.323-capable devices: CSE 1000 Release 3.0 Gatekeeper/Gateway M-1 Project 26, IP-Peer MCS 5100 H.323 Gatekeeper Basics

14 14 CS 2000 (SN06 and backward compatible to SN05) over SIP-T interface on SIP Application Module BCM 3.5 Interworkings The H.323 Gatekeeper functions as an H.323/SIP gateway between the SIP Application Module and H.323 endpoints. This allows a registered H.323 Endpoint to place a call that, based on dialed digits, can be routed by the H.323 Gatekeeper through the SIP Application Module (routeability determined by the SIP Application Module) to any call entity controlled by the SIP Application Module for the purpose of establishing two-way audio. That destination may be a SIP application, a PRI Gateway, or another H.323 Endpoint controlled by an H.323 Gatekeeper. any call entity controlled by the SIP Application Module to place a call that, based on dialed digits, is routed by the SIP Application Module through the H.323 Gatekeeper to an H.323 Endpoint for the purpose of establishing two-way audio an H.323 Endpoint to hold/retrieve a two-way audio call with an application controlled by the SIP Application Module. a SIP application controlled by the SIP Application Module to hold/retrieve a two-way audio call with an H.323 Endpoint an H.323 Endpoint to hold/redirect a two-way audio call with an application controlled by the SIP Application Module an H.323 Endpoint to hold/redirect a two-way audio call with an application controlled by the SIP Application Module an out-of-band DTMF to be played between H.323 Endpoints and applications controlled by the SIP Application Module by mapping the H.245 UserInputIndication (UII) message to/from a SIP INFO message Configure the H.323 Gatekeeper as a trusted node on the SIP Application Module. Do this by adding the IP address of the H.323 Gatekeeper to the list of authorized SIP nodes in the Authentication tab of the SIP Application Module. References The H.323 Gatekeeper uses RAS messages for endpoint registration, call admission, and gatekeeper-to-gatekeeper communications. The RAS message specifications and the meaning of the information contained in them are located in sections of ITU-T Recommendation H.225.0, Call signaling protocols and media stream packetization for packet-based multimedia communication systems. NN MCS Standard (02.02) February 2004

15 15 The H.323 Gatekeeper uses H messages to establish calls to/from H.323 endpoints. The H message specifications and the meaning of the information contained in them are located in sections of ITU-T Recommendation H.225.0, Call signaling protocols and media stream packetization for packet-based multimedia communication systems. Media information can be exchanged between the H.323 Gatekeeper and H.323 endpoints, media streams opened between H.323 endpoints, and media streams removed between H.323 endpoints by using H.245 procedures. The H.245 message specifications and the meaning of the information contained in them are located in ITU-T Recommendation H.245, Control protocol for multimedia communication. RAS, H225.0 and H245 messages are all defined using Abstract Syntax Notation One (ASN.1). The ASN.1 definitions of both RAS and H messages are located in Annex H of ITU-T Recommendation H.225.0, Call signaling protocols and media stream packetization for packet-based multimedia communication systems. Those for H245 can be found in Annex A of ITU-T Recommendation H.245, Control protocol for multimedia communication. The ASN.1 language is defined in ITU-T Recommendation X.680, Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation. The H.323 Gatekeeper and SIP Application Module communicate using SIP. SIP has been implemented by these components in accordance with the IETF RFC 3261, SIP: Session Initiation Protocol. SIP represents media streams using Session Description Protocol (SDP). SDP is described in IETF RFC 2924, SDP: Session Description Protocol. DTMF is represented within SIP by using the INFO method. The INFO method is described in IETF RFC 2976, The SIP INFO Method. The encapsulation of DTMF using that method is described in the IETF Internet Draft, draft-choudhuri-sip-info-digit-00, RFC SIP INFO method for DTMF digit transport and collection. The H.323 Gatekeeper operates on networks that use the TCP/IP protocol suite. All RAS messages are exchanged between communicating H.323 entities using UDP as the transport protocol. All H225.0 and H245.0 messages are exchanged using TCP as the transport protocol. SIP messages exchanged between the H.323 Gatekeeper and the SIP Application Module use UDP as the transport MCS 5100 H.323 Gatekeeper Basics

16 16 protocol. The UDP protocol is defined in IETF RFC 0768, User Datagram Protocol. The TCP protocol is defined in IETF RFC 0793, Transmission Control Protocol. NN MCS Standard (02.02) February 2004

17 Upgrades This is the first release of this product. If you require a maintenance upgrade or downgrade, use the following procedure. Procedure 1 Upgrading the load or reverting to an earlier load at the System Management Console 1 Navigate to the component that you wish to update. 2 Right-click on the component. 3 From the shortcut menu, select Update. 4 From the dialog box that appears, select the version to which you want to update or downgrade. 5 Select Apply or cancel. MCS 5100 H.323 Gatekeeper Basics

18 18 NN MCS Standard (02.02) February 2004

19 Fault management Fault management strategy The H.323 Gatekeeper does not create any additional alarms other than those currently present in the system. The H.323 Gatekeeper provides fault tolerance through a redundant configuration. Fault management procedures Alarm surveillance, correlation and reporting The H.323 Gatekeeper does not generate alarms. Log collection configuration Access logs through the Log Browser on the System Management Console. The H.323 Gatekeeper generates logs for the following: OAM&P Failure H.323 Endpoint transitioned to a new state No Available Bandwidth Call Rejected Caller Not Registered Call Rejected Endpoint Not Provisioned Endpoint ID/Terminal Alias Missing Unsupported Information Element Received Bandwidth De-allocated Message Unrecognized Unexpected Message Invalid Parm Length Parameter Missing Parameter Unsupported Parameter Field Missing Message Send Failure Unexpected Message MCS 5100 H.323 Gatekeeper Basics

20 20 Call Not Admitted (no RAS Admission Found) Call Identifier in H Not That From Admission (RAS) Call Exception Occurred Call Task Resources Timer Resource Exhaustion Call Model Resources Exhausted Translations Errors Unexpected Event Called Party Number Format Incorrect SETUP on un-admitted endpoint. NN MCS Standard (02.02) February 2004

21 H.323 Gatekeeper configuration How this chapter is organized This chapter is organized as follows: Overview on page 21 Software delivery packaging on page 22 Initial configuration on page 22 Beginning the process on page 22 Configuring the services on page 24 Endpoint maintenance on page 75 Adding endpoints on page 57 Adding the gateway (H.323 endpoint) as a valid SIP user on page 57 Administrative dialing plan configuration and planning on page 58 Overview Your support team performs the initial installation and commissioning for you. Once the installation and commissioning are completed, you can begin to configure your system to make it fully operational. The phrase operational configuration is used to encompass all of these functions and activities. Configuration refers to specifying the hardware and software within network elements such as the number, type, and position of circuit packs in a shelf. Provisioning refers to the services associated with provisionable circuit packs such as the trunk carriers provisioned on a specific circuit pack. Translations refers to the process of defining how different call types are screened and routed through the system. All of these activities involve specifying and storing data in a database. MCS 5100 H.323 Gatekeeper Basics

22 22 The procedures in this document are organized into the following areas: initial set up of the network procedures for implementing new features and functions or customizing and updating the existing datafill This document also contains a section that describes the tools and utilities that are used for configuration activities. Software delivery packaging The H.323 Gatekeeper at a minimum requires the SIP Application Module, Provisioning Manager, and Management Module to be deployed within the same network. It is deployed on its own server. Initial configuration Initial configuration of the H.323 Gatekeeper component is detailed below. This procedure assumes a standard configuration is already present and that a load containing the H.323 Gatekeeper is present. Note: The figures shown are for example purposes only. Procedure 2 Beginning the process at the System Management Console 1 Navigate to Components as shown in Figure 3, Navigating to the Components selection. Figure 3 Navigating to the Components selection 2 Right-click on Components and select Add->Component as shown in Figure 4, Adding the component. NN MCS Standard (02.02) February 2004

23 Figure 4 Adding the component 23 3 When the loadlist appears, select the h323gatekeeper option as shown in Figure 5, Selecting the load. Figure 5 Selecting the load 4 Click on the Apply button. 5 The configuration window appears, showing all of the configurable tabs. Once the configuration window appears, enter a label with a maximum of six characters in the Service Component Name field at the bottom. This name must be unique among the components. Figure 6, Example window with MCS 5100 H.323 Gatekeeper Basics

24 24 Service Component Name added, shows an example with the name H323 entered in the Service Component Name field. Figure 6 Example window with Service Component Name added ATTENTION DO NOT click on Apply until you have FINISHED filling in the fields that you need. Note that there are a number of different tabs representing the configurable services that the H.323 Gatekeeper requires. The following sections in this chapter describe each tab in detail and provide guidance on how to configure the tabs. Many of the fields already contain default values, and administrators can leave most of these default values alone. Note: The parameters with asterisks (*) are mandatory. The grayed-out fields are for information only and cannot be changed. After you click the Apply button, the System Manager begins the deployment of the H.323 Gatekeeper software. The Adding Services Progress dialog box appears. Procedure 3 Configuring the services ATTENTION To start new services, ensure that the configurable services are LOCKed before making any changes. NN MCS Standard (02.02) February 2004

25 25 at the System Management Console 1 Select the H323 Gatekeeper tab. This service specifies the transport for H.323 and the multicast IP address. Changes to this service require a restart. For more information on multicasting, see Unicast/multicast channels on page 9. MCS 5100 H.323 Gatekeeper Basics

26 Figure 7 H323 Gatekeeper tab 26 Table 2 H323 Gatekeeper tab field descriptions Field Value Description Transport Config Gatekeeper ID H323 Gatekeeper Discovery Port Show GUI Type=string Range=N/A Default= see description Type=string Range=3 to 30 characters Default=N/A Type=integer Range=N/A Default= 1719 Type=checkbox Range=N/A Default= N/A This field specifies the transport, IP addresses, and ports. Transports can appear more than once. The multicast address by default is :1718. In a typical deployment, the Transport Config IP address should be that of the server where the H.323 Gatekeeper will be deployed. If you are configuring a redundant system, leave this field blank since these transports are specified in the Transport Manager tab. This field contains the name identifying a gatekeeper. All H.323 endpoints wishing to connect to the H.323 Gatekeeper must have this ID configured. This field contains the port from which the H.323 Gatekeeper listens for registration requests. This read-only box prevents the GUI from appearing. NN MCS Standard (02.02) February 2004

27 27 2 Select the H.323 Zone Configuration tab. This is the tab where you create and define H.323 Zones. Administrators can configure endpoints for zone-based management. At least one zone must be present to properly configure the H.323 endpoints. In the following example, one zone is configured. If administrators need to delete a particular configured zone, they can select the row in the table and select the delete button. Administrators can add or delete zones while the H.323 Gatekeeper is in service. If the administrator tries to delete a zone in use (in other words, configured by an H.323 endpoint), a pop-up error box will appear, and the deletion will fail. MCS 5100 H.323 Gatekeeper Basics

28 Figure 8 H.323 Zone Configuration tab 28 Table 3 H.323 Zone Configuration tab field descriptions Field Value Description H323 Zone Name H323 Zone BandWidth Type=string Range=1 to 64 characters Default= N/A Type=integer Range= to bytes Default= N/A This field contains the name given to a H.323 zone. When an H.323 endpoint is configured, the administrator must assign it a zone. This field specifies the amount of bandwidth available to a particular zone. 3 Select the H323 Domain Names tab. This service creates domains that may be used for both defining H.323 endpoints and also for number qualification purposes. Administrators can add NN MCS Standard (02.02) February 2004

29 29 multiple domains but cannot remove domains in use. The domains entered must match the domain of the H.323 endpoint that was configured on the Provisioning Client. For more information, see the SIP Provisioning Client User Guide. Administrators can add or delete domains while the H.323 Gatekeeper is in service. If an attempt is made to delete a domain in use (in other words, configured by an H.323 endpoint or number qualifier), a pop-up error box will appear and the deletion will fail. Endpoints and Number Qualifier tabs depend on the entries in this tab. MCS 5100 H.323 Gatekeeper Basics

30 Figure 9 H323 Domain Names tab 30 Table 4 H323 Domain Names tab field descriptions Field Value Description Fully Qualified Domain Name Type=string Range=N/A Default=N/A This field contains the domain name. NN MCS Standard (02.02) February 2004

31 31 4 Select the H.323 Endpoint Configuration tab. This service creates and defines H.323 Endpoints. Administrators can add endpoints while the H.323 Gatekeeper is in service. This service requires a restart following modification. The following example shows one H.323 Endpoint configured. To add endpoints, fill in the fields shown and select the Add button. To delete endpoints, select the row in the table corresponding to the endpoint entry and select the Delete button. Note: If an endpoint already exists and the administrator wants to delete it, the endpoint must be offline before it can be deleted. MCS 5100 H.323 Gatekeeper Basics

32 32 Figure 10 H323 Endpoint Configuration tab Table 5 H.323 Endpoint Configuration tab field descriptions (Sheet 1 of 3) Field Value Description H232 Endpoint ID Domain Name Type=string Range=1 to 64 characters Default= N/A Type=string Range=1 to 64 characters Default= N/A This field contains the endpoint name. If the endpoint represents an external H.323 gatekeeper, this field is used to enter the gatekeeper identifier of the external gatekeeper when a gatekeeper type of endpoint is being configured. This field is only for informational purposes and is not examined or used in gatekeeper-to-gatekeeper communication. This field contains the domain the H.323 endpoint is configured on. Domains are created through the Domain Names service. NN MCS Standard (02.02) February 2004

33 33 Table 5 H.323 Endpoint Configuration tab field descriptions (Sheet 2 of 3) Field Value Description Call Signaling Address Endpoint Type E.164 Number Type=integers Range=IP address Default= N/A Type= drop-down menu Range= gateway, gatekeeper, client Default= gateway Type= checkbox Range=N/A Default= unchecked This field contains the IP address of the endpoint. A checkbox will be available for this entry as well labeled dynamic. If this checkbox is selected, the IP address entered (if any) is ignored and the Gatekeeper extracts the endpoint s IP address from the RRQ message during endpoint registration. If the endpoint represents an external H.323 gatekeeper, and the gatekeeper type of endpoint is being configured, enter the IP address at which the external gatekeeper sends and receives RAS messages in this field. When the H.323 endpoint is a gatekeeper, use an IP address. Dynamic is not valid for Gatekeepers. In order to support the CSE 1000 gatekeeper redundancy scheme, you will need to add the IP addresses of the other gatekeepers in the redundant group to this field. You can configure up to three IP addresses (three redundant gatekeepers) in this field, delimited by a + sign. This field specifies the endpoint type, such as Gateway, Client, or Gatekeeper. If the endpoint represents an external H.323 gatekeeper, this field will be augmented to add gatekeeper to the list of selectable endpoint types. Select the gatekeeper item from the list when configuring a gatekeeper type of endpoint. If this checkbox is checked, the H.323 Gatekeeper assumes that the H.323 ID entered is an E.164 number and will treat it as such; therefore, any H.323 ID present in the RRQ will be ignored. MCS 5100 H.323 Gatekeeper Basics

34 34 Table 5 H.323 Endpoint Configuration tab field descriptions (Sheet 3 of 3) Field Value Description TCP Trunking H323 Zone Name Time To Live Maximum Simultaneous Calls Type= checkbox Range=N/A Default= unchecked Type=string Range=N/A Default=N/A Type=string Range=0-300 Default= N/A Type=string Range= Default=N/A Make a selection according to the behavior of the external endpoints managed by this external gatekeeper. The selection is applied to all endpoints. If the checkbox is checked. It indicates that each endpoint will establish a single TCP connection to the H.323 Gatekeeper for all call establishment and call termination messaging originating from the endpoint. If the checkbox is unchecked, that means that a TCP connection is established for each call. This field indicates the Zone that the H.323 endpoint will be associated with. If the endpoint represents an external H.323 gatekeeper, the meaning of this field will not change. A zone should be selected from the list, but the zone is ignored when a gatekeeper type of endpoint is being configured. This field contains the amount of time an endpoint will be considered in the Registered state by the Gatekeeper. If the endpoint represents an external H.323 gatekeeper, enter a value. However, the value is ignored when a gatekeeper type of endpoint is being configured. This field contains the value that indicates the maximum number of calls which any endpoint (for example, gateway) is allowed to place simultaneously to the H.323 Gatekeeper. This value will be enforced on each external endpoint each time it attempts to establish a call. If this limit is reached, no further calls will be allowed from the endpoint until existing calls are released. If the endpoint represents an external H.323 gatekeeper, enter a value that indicates the maximum number of calls any external endpoint (for example, gateway) this external gatekeeper manages is allowed to place simultaneously to the H.323 Gatekeeper. This value will be enforced on each external endpoint each time it attempts to establish a call. If this limit is reached, no further calls will be allowed from the endpoint until existing calls are released. NN MCS Standard (02.02) February 2004

35 35 5 Select the SIP TCF Base tab. The H.323 Gatekeeper is one of several components that use the SIP TCF Base. Changes to this service require a restart. The SIP TCF Base provides support for the SIP protocol. The SIP TCF Base contains many parameters pertaining to transport configuration. It includes information regarding the transport IP addresses/ports, timers, number of redirects, and retransmission, among other items. Modifications to the SIP TCF Base tab require that the SIP TCF Base be locked. MCS 5100 H.323 Gatekeeper Basics

36 Figure 11 SIP TCF Base tab 36 Table 6 SIP TCF Base tab field descriptions (Sheet 1 of 2) Field Value Description Transport Config Invite Timer Type=string Default=UDP= : 5070:optional;TCP= :5070:optional Type=integer Range=time in milliseconds Default= milliseconds Specifies the transport, IP addresses, and ports. Includes both the public and private interfaces. If your system consists of only public IPs, do NOT duplicate the string. This field indicates the public IPs for the UDP and TCP portions only. Transports can appear more than once. Use this field only for a standalone system. Enter the machine logical IP address of the H.323 Gatekeeper. For redundant configurations, leave this field blank. This field controls the maximum time in milliseconds to wait for an INVITE to receive a Final Response after receiving a provisional Response. NN MCS Standard (02.02) February 2004

37 37 Table 6 SIP TCF Base tab field descriptions (Sheet 2 of 2) Field Value Description Maximum Number of Redirections Initial Maximum Hop Value Type=integer Range=3-10 numbers Default=5 Type=integer Range=5-50 numbers Default=20 Maximum number of redirections allowed before a request is dropped. Maximum number of hops allowed before a request is dropped. 6 Select the H323 Gatekeeper Base tab. This service is responsible for configuring the SIP Application Module s proxy information that the H.323 Gatekeeper will connect to the user agent header and name information that will be present in all requests originated from the H.323 Gatekeeper Changes to this service require a restart. MCS 5100 H.323 Gatekeeper Basics

38 Figure 12 H323 Gatekeeper Base tab 38 Table 7 H323 Gatekeeper Base tab field descriptions Field Value Description Gateway ID Gateway User-Agent Header SIP Application Module Type=string Range=1 to 20 characters Default=N/A Type=string Range=1 to 20 characters Default=RAS SIP Gateway Type=integers Range=1 to 250 digits Default= :5060 This field specifies the id that is appended to the User Agent header delivered in all Requests originated from the gateway. This field specifies the user agent name used in User Agent header delivered in all requests originated from the gateway. The RASSipGwy Service manages process for H.323 Endpoint Registration, Admission, and Status. No configuration is required for this service. This field specifies the SIP Application servers that the H.323 Gatekeeper communicates with. This field can contain up to ten server IPs:ports separated by a + sign. 7 Select the Number Qualifiers tab. The Number Qualifiers service specifies how Numbering Plan Indicator (NPI)/Type of Number (TON) values should be mapped to phone-context parameters that will be present in the SIP URI and vice-versa. The Type of Numbers and Numbering Plans available on the H.323 NN MCS Standard (02.02) February 2004

39 39 Gatekeeper are listed in the drop-down menus. A combination for a given domain name maps to a string identifier. This identifier must also be configured through the Provisioning Client for end-to-end communication across the system. Number qualifiers may be added or deleted while the H.323 Gatekeeper is in service. For more information on Number Qualifiers, see Administrative dialing plan configuration and planning on page 58. MCS 5100 H.323 Gatekeeper Basics

40 Figure 13 Numbers Qualifier tab 40 NN MCS Standard (02.02) February 2004

41 41 Figure 14 Type of Number field drop-down menu Table 8 Numbers Qualifier tab field descriptions Field Value Description Number Qualifier Identifier Number Qualifier Domain Numbering Plan Type of Number Type=string Range=1-100 characters Default=N/A Type=drop-down menu Range=N/A Default=N/A Type=drop-down menu Range=Unknown, ISDN, Private, Data, Telex, National Default=Unknown Type=drop-down menu Range=See Figure 14, Type of Number field drop-down menu. This field contains the name for the number qualifier that you are defining. This field contains the Domain that this number qualifier pertains to (Domains are created using the Domain Names service). The entries of none are there as defaults and have no actual impact on the system operations. This field contains the numbering plan. This field specifies private, public, or unknown numbers. 8 Select the H225 Signaling Address tab. This service specifies the transport IP address and port for H.225 signaling. Only a port value of 1720 is valid. If you are configuring a redundant system, MCS 5100 H.323 Gatekeeper Basics

42 42 Figure 15 H225 Signaling Address tab leave this field blank since these transports are specified in the Transport Manager tab. Table 9 H225 Signaling Address tab field descriptions Field Value Description H225 Signaling Address Type=string Range= Default=TCP= :1720:selectbased This field contains the address and port for H.225 signaling. The port should always be Select the H.245 Signaling Address tab. This service specifies the transport IP address and port for H.245 signaling. Only a port value of 0 is valid. This value forces ephemeral server behavior. If you are configuring a redundant system, leave this field blank since these transports are specified in the Transport Manager tab. NN MCS Standard (02.02) February 2004

43 Figure 16 H245 Signaling Address tab 43 Table 10 H245 Signaling Address tab field descriptions Field Value Description H245 Signaling Address Type=string Range=N/A Default=TCP= :0 :selectbased This field contains the address and port for H.245 signaling. Transports can appear more than once. The TCP port should always be 0 to force ephemeral server behavior. When configuring H.245 Signaling address tab, make sure that the trailing 0 (signifying that the gatekeeper is to spin up an ephermal H.245 address) is not accidently deleted. 10 If you are configuring a redundant system, select the Server Properties tab. This tab specifies the labels used for the public and private SIP services. Leave the values blank, since, in a redundant system, the addresses come from the Transport Manager. This tab requires a restart. MCS 5100 H.323 Gatekeeper Basics

44 Figure 17 Server Properties tab 44 NN MCS Standard (02.02) February 2004

45 45 Table 11 Server Properties tab field descriptions Field Value Description Label: Value Label: Value: Label: Value: Type=string Range=1-80 characters Default=Public_Service_Address Type=string in the form of a valid IP address (x.x.x.x) Type=string Range=N/A Default=Private_Service_Address Type=string in the form of an IP address (x.x.x.x) Type=string Range=1-80 characters Default=blank Type=string Range=1-80 characters Default=blank This is a label that identifies the public address. This field contains the public machine logical IP address assigned to the label just above this field. Only add an entry for a standalone system. Ignore this field. Ignore this field. This field contains a unique label to reference the value to the field directly below assigned below. Enter server.gateways. Only add an entry for redundant configurations. This field contains the nodes that the software needs to check upon boot up. This value is assigned to the label just above this field. 11 Select the Transport Management tab. This service is used for configuring the H.323 Gatekeeper in a highly available manner. You can modify the Transport Manager tab without locking or restarting the service. The Transport Manager Configuration tab is organized into three sections: The first section contains server group information. The second section, Server Parameters, contains server specific group configuration information. The third section, Network Service Descriptor, contains service instance data. The service name is arbitrary. The ServerID must be unique across the set of peer application servers and should start with 1. The Stand Alone checkbox must be unchecked in order to enable the H.323 Gatekeeper Reliability capability. MCS 5100 H.323 Gatekeeper Basics

46 46 Figure 18 Transport Management tab The public and private static addresses are shown entered for this server (note that the full display is not in view below). Table 12 Transport Management tab field descriptions (Sheet 1 of 2) Field Value Description Service Name Server ID Type=string Range=1-20 characters Default=H323GK Type=integer Range=1-4 numbers Default=1 This field indicates the name of the service this Reliability Manager is supporting. This field indicates the ID number for this server. NN MCS Standard (02.02) February 2004

47 47 Table 12 Transport Management tab field descriptions (Sheet 2 of 2) Field Value Description StandAlone Server Type=checkbox Default=N/A Is the server standalone or part of a reliable group? Check the box if the server is standalone. If the box is checked, ignore the remainder of the fields in this tab. Uncheck the box for a redundant system. Note: The server heartbeat data should be provisioned with the public and private IP addresses of the other servers in the service group. There are two heartbeat entries for each peer server in the group. Each entry that is enabled must have the HB Address Enabled checkbox selected. The remote server address should be the remote IP address of the peer server s corresponding static address on the same network. The Local Server Address should be the public or private label assigned in the Server Parameter section. Label Value Label Value Type=string Range=1-15 characters Default=Public_Static_Address Type=string in form of an IP address Type=string Range=1-15 characters Default=Private_Static_Address Type=string in form of an IP address This field contains a unique label that references the value. This field contains the value to assign this label (IP address). This is a machine-logical IP address. This is a unique label that references the value. This field contains the value to assign this label (IP address). Ignore this field. MCS 5100 H.323 Gatekeeper Basics

48 Figure 19 Server Heartbeat data 48 A NN MCS Standard (02.02) February 2004

49 49 Table 13 Transport Management tab field descriptions, Server Heartbeat Data HeartBeat Port Sending Interval HeartBeat Timeout Discovery Period Active Pending Period A HB Address: HB Address Enabled HB Address: Remote Server Address HB Address: Local Server Address Type=integer Range=40001 Default=40001 Type=integer Range= numbers Default=250 Type=integer Range=1-10 numbers Default=3 Type=integer Range=2-60 seconds Default=3 Type=integer Range=2-10 seconds Default=4 Type=checkbox Default=unchecked Type=checkbox Default=N/A Type=string in the form of a valid IP address Type=string Range=1-50 characters Default=Public_ Static_Address This read-only field contains the port for all servers to use to send or receive reliability messages. This is the interval in milliseconds between reliability messages. Accept the default. This is the number of seconds before a server is declared failed. Accept the default. This is the number of seconds a server stays in Discovery Mode. Accept the default. This is the number of seconds a server stays in Active Pending Mode. Accept the default. Use these checkboxes when you want to delete the section below the checkbox. Check this checkbox to indicate that the address is enabled. Check the box for a redundant system. This is the public, machine- logical IP address for the server that this gatekeeper must maintain a heartbeat with. A heartbeat is sent to this address from the one mapped to the label below. This field contains a unique label that references the value assigned in the Server Parameter field. The H.323 Gatekeeper does not use the fields assigned to the Private_Static_Address. MCS 5100 H.323 Gatekeeper Basics

50 50 If there are a total of four servers in the group (the max number supported) then you will have three pairs of heartbeat peer data (a total of six entries enabled). Configuration of the Network Service Descriptor (NSD) is what defines the network services of the H.323 Gatekeeper that require reliability. If you have two physical servers in a 1+1 active/standby configuration then you will provision one active NSD. Each active NSD describes the SIP services to activate on an active server. The servers in the group negotiate which NSDs each will activate. The server that finds all NSDs already activated automatically becomes a standby server. For this example configuration, a 1+1 configuration, we will have one NSD enabled. Each enabled NSD must define a unique public and private service address and may define other instance specific properties. Note that the public and private service address tag values (their provisioned IP addresses) should be different from the provisioned static addresses. NN MCS Standard (02.02) February 2004

51 51 Figure 20 Transport Manager tab, Network Service Descriptor Next, for the same NSD, the SIP transports must be defined for each network the server will use for SIP communications. Here we show provisioning that enables both TCP and UDP transports on both the public and private networks (for a total of four activated transports). Below is the configuration for UDP and TCP on the public and private network. MCS 5100 H.323 Gatekeeper Basics

52 52 Figure 21 Transport Manager tab, Network Service Descriptor, SIP transport B NN MCS Standard (02.02) February 2004

53 53 Table 14 Transport Management tab subfield descriptions, cont d Field Value Description B NSD Number NSD Enabled Service Parameter: Label Service Parameter: Value Type=checkbox Default=unchecked Type=integer Range=1-3 numbers Default=N/A Type=checkbox Default=N/A Type=string Range=1-15 characters Default= Public_Service_Address Type=string in the form of a valid IP address Range=1-15 numbers Use these checkboxes when you want to delete a the section below the checkbox. This is the unique number for this Network Service Descriptor (NSD). Check the box if this NSD is enabled. This is a unique label that references the value. The MCS 5100 does not use the label Private_Service_Address. This field contains the value to assign this label (IP address). In the same way, set up the various H.323 transports: H323-RAS, H323-H225, and H323-H245. See the following figures for examples. MCS 5100 H.323 Gatekeeper Basics

54 54 Figure 22 Transport Manager tab, Network Descriptor, H323-RAS NN MCS Standard (02.02) February 2004

55 55 Figure 23 Transport Manager tab, Network Descriptor, H323-H225 MCS 5100 H.323 Gatekeeper Basics

56 56 Figure 24 Transport Manager tab, Network Descriptor, H323-H The Interworking Base tab does not require configuration but is included here for information only. NN MCS Standard (02.02) February 2004

57 Figure 25 Interworking Base tab After all of the configuration tabs are filled, click on the Apply button. You can cancel the configuration at any time by clicking on the Cancel button. Procedure 4 Adding endpoints at the System Management Console 1 To add an endpoint from the file tree, navigate to and select the Endpoints tab. 2 Lock the service by right clicking on it and selecting Lock from the shortcut menu. 3 Right click again and select Modify from the shortcut menu. 4 Fill in the fields as necessary for each endpoint you need to add. 5 Click on the Apply button or cancel. For the following procedures, use the Provisioning Client GUI. Procedure 5 Adding the gateway (H.323 endpoint) as a valid SIP user at the Provisioning Client 1 Ensure that the H.323 Endpoint is fully configured. See the SIP Provisioning Client User Guide for more complete information on using the SIP Provisioning Client for setting up and routing to gateways. The number of H.323 Gatekeepers deployed requires an equal number of routes to be set up. 2 Add the gateway (H.323 Endpoint) as a valid SIP user under Domains->Domain name->users->add user. This is required for MCS 5100 H.323 Gatekeeper Basics

58 58 RAS to work properly. Do not configure any aliases for the H.323 endpoints. 3 Add a telephony route. 4 Add a routelist. 5 Configure the gateway in the following order: domain of the H.323 endpoint address of the MCS 5100 H.323 Gatekeeper H.323 id, to the gateway host. The h323_endpoint specifies the H323-id that was configured on the MCS 5100 H.323 Gatekeeper. This value is added to the SIP URI and is required for the MCS 5100 H.323 Gatekeeper to route calls to the appropriate H.323 endpoint. In this example, the gateway is Example Gateway host: enterprise.com;maddr= :5070;h 323_endpoint=Harry-GW1 Gateway type: Harry-GW1-on-gatekeeper3 6 Calls can now route to and from the SIP applications and H.323 Gatekeeper and endpoints. 7 At this point administrators should configure their dialing plan support. See Administrative dialing plan configuration and planning on page 58. Administrative dialing plan configuration and planning The H.323 Gatekeeper supports multiple dialing plan configurations to fit into a network, namely CDP and UDP dialing plans and networks with a combination of both. Coordinated Dialing Plans (CDP) Coordinated Dialing Plans (CDP) enable a service provider with a number of local PBXs to coordinate the dialing plan for stations at these switches. When implemented, CDP allows a station at one switch to call a station at another switch without using a unique number and without access codes. The H.323 Gatekeeper supports the following: The H.323 Gatekeeper allows stations at a PBX to call SIP clients using the numbering plan that a user is already accustomed to. NN MCS Standard (02.02) February 2004

59 59 Likewise, SIP clients will be able to dial PBX stations in the same fashion. The H.323 Gatekeeper will allow CDP dialing in a multi-site configuration where both MCS 5100 and supported Enterprise platforms coexist. Universal Dialing Plans Universal Dialing Plans enable a customer with a network of PBXs to communicate with a private dialing plan in which each PBX has its own site code. The H.323 Gatekeeper supports the following: one MCS 5100 serving not only its current location but also other sites connected over a WAN one location hosted by the MCS 5100 and another hosted by a supported Enterprise platform connected over a WAN locations where both MCS 5100 and supported Enterprise platforms are present Provisioning to support the dialing plans In order to support CDP and UDP dialing plans, the administrator must provision the following three screens in the Provisioning Client: Number Qualifier page Pre-Translations page Gateway Route Parameters provisioning page Provision the Number Qualifier page before provisioning the Pre-Translations and Gateway Routes parameter pages. The Pre-Translations and Gateway Routes parameter pages have a drop-down field called Number Qualifier, which gets filled automatically from the Number Qualifier page. The SIP Application Module must be able to qualify numbers destined for supported components so it can route the call appropriately. TON/NPI is mapped to the RFC-2806 phone-context parameter in the SIP URI. In order for the SIP Application Module to translate a phone call and set the phone-context parameters correctly, some provisioning must take place. The administrator needs to enter Number Qualifiers for each domain through the Provisioning Client. Use the following screen in the Provisioning Client to enter new Number Qualifiers and also display those already available for this domain. Whenever administrators MCS 5100 H.323 Gatekeeper Basics

60 60 create a new domain, it is automatically populated with some common Number Qualifiers, such as: udp cdpdomain local national private publicunknown privateunknown unknown Administrators can edit or delete any of the above Number Qualifiers if necessary. Figure 26 Add, Edit, and Delete Number Qualifiers provisioning page NN MCS Standard (02.02) February 2004

61 61 The Number Qualifier on the SIP Application Module corresponds generally to a NPI/TON pair on the gateway. Use the Number Qualifier to set the value of the parameter phone-context in the SIP URI for outgoing calls and to choose the right digit to prefix to the called number, if the call is coming from a PBX with phone-context parameter set in it. Number Qualifiers are considered according to the domain/sub-domain structure defined by the administrator. If a matching Number Qualifier is not found in the domain identified in the request URI, the Number Qualifiers (if any) of that domain s parent domain (if any) will be considered next. This process continues until a match is found or the software hits a top-level domain that has no parent domain. Each subdomain/domain has its own pre-translations table. Fill in the pre-translations table for the subdomains/domains into which the call is coming from the gateways. In addition, if any subscriber is behind any PBX or other switch, that subdomain should have this table provisioned for proper functioning of outgoing calls. MCS 5100 H.323 Gatekeeper Basics

62 62 Figure 27 Add, Edit, and Delete Pre-Translations table provisioning page The administrator needs to provision the following: The Number Qualifier defines the value that the gateway should send in as phone-context parameter of the SIP URI. This maps to TON/NPI pair on the gateways. The Length column identifies the length of the digits in the SIP URI. The Prefix column s value is used to prefix before the called number. It tells what the user might have prefixed for this type of call (Number Qualifier and Length identifies the type of call). A null value is permissible in this field and is allowed in order to prevent a recursive lookup on a parent domain. This gives the administrator the ability to limit the type of dialing plans available to users in a given sub-domain. NN MCS Standard (02.02) February 2004

63 63 The administrator also needs to provision the GWRoute parameters and qualify each gateway route with a value from the Number Qualifier. This drop-down list gets populated from the Number Qualifier screen. MCS 5100 H.323 Gatekeeper Basics

64 64 NN MCS Standard (02.02) February 2004

65 Accounting management The H323 Gatekeeper uses the existing accounting functionality on the SIP Application Module and Accounting Module components. As the system routes H.323-originated or terminated calls through the SIP Application Module, the software collects accounting data the same way it does in SIP-originated calls. The system sends data to the Accounting Module for formatting, storage, and delivery. For more information on this functionality, please refer to the MCS 5100 Accounting Module Basics document. Note: Due to the nature of the H.323 Gatekeeper, the following restrictions must apply to the production of accounting records: The system will only create an SDP record for call hold or call retrieve when the H.323 endpoint sends notification to the H.323 Gatekeeper that it has placed a call on hold or retrieved a call. The system will not create a REFER record for call transfers when the request originates from supported H.323 endpoints through the H.323 Gatekeeper. This is because the H.323 endpoint does not send notification to the H.323 Gatekeeper that it has transferred a call. Restrictions and limitations Media captured in billing records for for H.323 slowstart to H.323 slowstart calls will not be valid due to fundamental differences between H.323 slow start and SIP. Specifically, the billing record fields origsdpport, origconnaddr, termsdpport, termconnaddr, and codec will be defaulted to 333, , 333, , and 0 PCMU/8000 respectively. Similarly, for fast start to fast start transit calls, only initial media will be captured in billing record (in other words, subsequent media modifications will not be captured). Billing records will only be generated for transfer and hold scenarios if the H.323 endpoint informs the H.323 Gatekeeper. For example, if a call is established between a PC Client and a device connected to a CSE 1000, and the CSE 1000 device initiates a transfer MCS 5100 H.323 Gatekeeper Basics

66 66 to another device resident on the CSE 1000, the call is transferred locally and from the H.323 Gatekeeper perspective, a transfer never took place and thus no billing records would be generated. Similarly, if the call is then placed on hold and the H.323 Gatekeeper did not receive Terminal Capability Set hold information, the PC client would never know that it was placed on hold and no billing record would be generated. NN MCS Standard (02.02) February 2004

67 Performance management Operational Measurements (OM) OMs are viewable at the OM browser interface on the System Management Console. Two OM groups provide a means to measure specific messages, as follows: ITUH323IN measures H Q.931 messages received ITUH323OUT measures H Q.931 messages sent Table 15 OM Group details Table 15, OM Group details gives details about these OM groups. OM group OM name OM definition H225_SIGNALING_TCF inbound OMs H323 INBOUND ALERT H323 INBOUND CALL PROCEEDING H323 INBOUND CONNECT H323 INBOUND PROGRESS H323 INBOUND SETUP H323 INBOUND SETUP ACKNOWLEDGE H323 INBOUND RELEASE COMPLETE Alerting message received Call proceeding message received Connect message received Progress message received Setup message received Setup acknowledged message received Release complete message received MCS 5100 H.323 Gatekeeper Basics

68 Table 15 OM Group details 68 OM group OM name OM definition H225_SIGNALING_TCF H323 INBOUND INFO H323 INBOUND USER INFORMATION H323 INBOUND NOTIFY H323 INBOUND STATUS H323 INBOUND STATUS ENQUIRY H323 INBOUND FACILITY H323 INBOUND UNRECOGNIZED H323 OUTBOUND ALERT H323 OUTBOUND CALL PROCEEDING H323 OUTBOUND CONNECT H323 OUTBOUND PROGRESS H323 OUTBOUND SETUP Information message received User information message received Notify message received Status message received Status enquiry message received Facility message received Unrecognized message received Alerting message sent Call proceeding message sent Connect message sent Progress message sent Setup message sent NN MCS Standard (02.02) February 2004

69 Table 15 OM Group details 69 OM group OM name OM definition H323 OUTBOUND SETUP ACKNOWLEDGE H323 OUTBOUND RELEASE COMPLETE H323 OUTBOUND INFO H323 OUTBOUND USER INFORMATION H323 OUTBOUND NOTIFY H323 OUTBOUND STATUS H323 OUTBOUND STATUS ENQUIRY H323 OUTBOUND FACILITY H323 OUTBOUND UNRECOGNIZED Setup acknowledged message sent Release complete message sent Information message sent User information message sent Notify message sent Status message sent Status enquiry message sent Facility message sent Unrecognized message sent Additionally, the H.323 Gatekeeper maintains the following existing OM s that are available on other components as part of the general framework. SIP_TCF_FACTORY (ACTIVE, PROCESSED transactions) OSSMGMTAGENT MCS 5100 H.323 Gatekeeper Basics

70 70 OSSLSCFACADE MECOMCHN REFERSERVICE TRANSPORT MANAGER Finally, as part of the management framework, these OM s appear but do not really provide any value: RAS-SIP GATEWAY H225SIPGWY NN MCS Standard (02.02) February 2004

71 Security and administration How this chapter is organized This chapter contains the following information: Security on page 71 Administration on page 71 Component Maintenance Operations on page 71 Endpoint maintenance on page 75 Security There are currently no security functions implemented on the H.323 Gatekeeper. Administration Component Maintenance Operations The following maintenance operations will be available to the component: Modify Change component parameters Gatekeeper ID and Discovery Port Update Update deployed component with new load Query View component parameters Delete Remove component Restart Stop and start component Stop Stop component Lock Offline component Unlock Return Component to service H.323 Endpoint Maintenance at the System Management Console 1 To access these maintenance operations, navigate to your H.323 Gatekeeper, as shown in the following example. MCS 5100 H.323 Gatekeeper Basics

72 72 Figure 28 Navigating to the H.323 Gatekeeper 2 Right-click on the H323Gatekeeper1 button, in this case. The name of the server is determined when the server is initially added. The shortcut menu shown in appears. Figure 29 Shortcut menu NN MCS Standard (02.02) February 2004

73 73 3 Right-click on whichever operation you need. Procedure 6 Using the Modify service at the System Management Console 1 Select the Lock option and lock the operations. 2 Select the Modify option. A Modify screen appears. Figure 30 Example of the Modify screen 3 Make whatever modifications you need in any of the configurable tabs. 4 Select the Apply button. 5 A Modifying Services Progress screen appears. When the modifications are complete, a Modifications Successful screen appears. Procedure 7 Using the Log Browser at the System Management Console 1 Refer to the System Management Console Basics. Procedure 8 Using the H.323 Endpoint Maintenance service at the System Management Console 1 Selecting H.323 EndPoint Maintenance option will bring up the H.323 Endpoint Maintenance screen (see Figure 31, H.323 Endpoint Maintenance screen), which allows the administrator MCS 5100 H.323 Gatekeeper Basics

74 74 to view the configured H.323 endpoints. From this screen the administrator can OFFLINE or RTS individual H.323 endpoints. These two terms refer to whether the H.323 Gatekeeper will process incoming RAS messages and subsequently calls from endpoints. If the H.323 endpoint is in the OFFLINE state, the H.323 Gatekeeper will not allow the endpoint to register. If the H.323 endpoint has been placed in the RTS state, the endpoint will either be registered or unregistered. Please note that these states do not affect the H.323 endpoint itself, and any maintenance the endpoint receives is done using the endpoint s OAM&P interfaces. Figure 31 H.323 Endpoint Maintenance screen The Maintenance screen contains the following tabs, which can be rearranged or deleted: H.323 ID E.164 Number H.323 Zone Domain Endpoint State NN MCS Standard (02.02) February 2004

75 75 Provisioned Call Signaling Address Call Signaling Address TTL Endpoint Type TCP Trunking Max Simultaneous Calls Figure 32 Maintenance screen: Move H.323 Endpoint Endpoint maintenance Procedure 9 Bringing the endpoints into service at the System Management Console 1 After the administrator has configured the endpoints, they need to be brought into service. To do so, bring up the H.323 Endpoint Maintenance screen by navigating to the H.323 server. MCS 5100 H.323 Gatekeeper Basics

76 76 Figure 33 Navigating to the H.323 Gatekeeper 2 Right click on the H.323 selection and select H.323 Endpoint Maintenance from the shortcut menu. NN MCS Standard (02.02) February 2004

77 77 Figure 34 Selecting H.323 endpoint maintenance 3 The following screen appears with all the configured endpoints displayed. Select the endpoints that you wish to bring into service. MCS 5100 H.323 Gatekeeper Basics

78 78 Figure 35 H.323 Endpoint Maintenance screen 4 Click on the Post arrow (pointing right) and all the selected Endpoints will appear on the right-hand side of the screen. NN MCS Standard (02.02) February 2004

79 79 Figure 36 H.323 Endpoint Maintenance screen, modifying an endpoint 5 From this panel, right-click on any endpoint and select Return H.323 Endpoint to Service or, to offline the endpoint, select Offline H.323 Endpoint. MCS 5100 H.323 Gatekeeper Basics

80 80 Figure 37 H.323 Endpoint Maintenance screen Procedure 10 Deleting endpoints at the System Management Console 1 To delete an endpoint, make sure that endpoint is offlined as shown in Section 9, Bringing the endpoints into service. 2 Lock the service by right clicking on it and selecting Lock from the shortcut menu. 3 Select the endpoint you wish to delete as shown in Figure 38, Deleting an endpoint. 4 Click on the Delete button or cancel. NN MCS Standard (02.02) February 2004

81 Figure 38 Deleting an endpoint 81 MCS 5100 H.323 Gatekeeper Basics