13.6 |
HG 1500 Board |
Overview |
|
|
| Voice over IP (VoIP) - the transfer of voice data over IP networks - is enabled in HiPath 3000 by means of the HG 1500 boards. |
| The H.323 communication between networked HiPath 3000 systems (nodes) must be considered as gatekeeper to gatekeeper communication. Registration between HG 1500 modules of networked systems is not performed. The CorNet NQ protocol, tunneled in H.323 via Annex M1, is used. |
| The breakdown of HG 1500 resources into signaling and payload resources is a basic feature. |
Signaling Resources |
| These include all of the node-specific signaling data required for Voice over IP for IP-supported (LAN, Intranet, Internet) and circuit-switched networks (ISDN, PSTN). These resources are centrally provided by a single HG 1500 board, the signaling gateway (= Gatekeeper HG 1500), regardless of how many HG 1500 boards are available at the node. A HG 1500 board is defined as a gatekeeper HG 1500 using HiPath 3000 Manager E. |
Payload Resources |
| The node resources required for transferring VoIP voice data (payload) between IP-supported and circuit-switched networks are provided by the media gateway. One or more HG 1500 boards may be used. |
| No payload resources are required for direct transfer between IP-supported networks. |
| In the case of systems with only one HG 1500 board, this board operates both as a signaling gateway and as a media gateway when configured appropriately by HiPath 3000 Manager E. |
| In the case of systems with more than one HG 1500 board, payload resources are monitored by the node-central resource manager. This is a self-configuring service. Signaling resources are centrally provided by the first HG 1500 board. This signaling gateway also accesses other media gateway resources (codecs, B channels) and signaling data (for example, RTP, RTCP). This gives IP workpoint clients and other gateways access to central payload resources of all HG 1500 boards in a node. |
| Resources for functions not based on H.323 (for example, routing channels) are still provided by each HG 1500 board. In systems with several HG 1500 boards, resources are provided exclusively by media gateways for performance reasons. |
Features of HG 1500 V3.0 or later |
| • | Transparent B channel for ISDN B channel protocols |
| • | Flexible port number administration |
| • | Dynamic jitter buffer |
| • | SNTP functionality in the LAN |
| • | Read rights to dynamic parameters of HiPath 3000 Manager in WBM |
| • | Improved firewall function (stateful inspection, DoS, application level gateways) |
| • | T.38 fax protocol standard support |
| • | HFA workpoint support |
| • | Logging of QoS data (Quality of Service) |
| • | Licensing system as for HiPath 3000/5000 |
| • | Improved software management |
| • | Cooperation with HiPath 4000 V2.0 and later systems, for example, DMC (Direct Media Connection) |
| • | Full VPN support (Virtual Private Network) |
| • | HG 1500 as a module of a PCS (PC-based communication server) |
| • | STMI2 board with 32 B channels onboard, expandable to 64 channels |
DMC |
| This flag enables or disables the feature "DMC Interworking with HiPath 4000 Systems" (in short "DMC"). In a network with HiPath 4000, DMC enhances the voice quality between IP components (endpoints, gateways). |
| DMC is supported via networking protocols SIP-Q V2 and CorNet-NQ. In HiPath 3000 V8 and HiPath 4000 V5 and later systems, only SIP-Q V2 protocol is used for IP networking between these systems and only CorNet-NQ is used for TDM networking. CorNet-IP protocol is no longer supported. |
| DMC should be disabled in a homogeneous HiPath 3000/5000 network. If a network with HiPath 4000 systems (version 2.0 or later) exists in which DMC is configured, the DMC feature should be enabled in the HiPath 3000/5000 systems. |
| The HFA endpoints registered at the HiPath 3000/5000 system and the HiPath 3000 system itself are then in a position to accept DMC connections set up by the HiPath 4000 and its HFA endpoints. Even if the DMC feature is enabled, DMC is not performed between HiPath 3000/5000 systems. |
| Note that enabling DMC results in a reduction of DSP channel resources. This means that only about 80% of the channels will be available for connections per DSP in a HiPath 3000 system (for example, 6 channels instead of 8, 12 channels instead of 16, 48 channels instead of 60). |
Hardware Notes |
| HG 1500 is: |
| • | the STMI2 board in HiPath 3800 |
| • | the HXGS3 board in HiPath 3550 and HiPath 3350 |
| • | the HXGR3 board in HiPath 3500 and HiPath 3300 |
| The power supply comes from the system. |
System requirements for HiPath 3000/5000 |
| • | At least one Euro ISDN basic connection (connection to the network or another HiPath system) |
| • | At least one free slot in the basic system |
System Environment |
| • | Shared/switched LAN 10/1000 Base T |
| • | Client/server and peer-to-peer networks with TCP/IP protocol |
| HiPath 3000/5000 V9, Service Documentation, Issue 7 | up  |
|
 |
||
| Disclaimer & Copyright | ID: P31003H3590S100017620 | 2012-06-25 |