4.2 |
VoIP over H.323 |
| HG 1500 boards are used for VoIP in HiPath 3000. |
| Gatekeeper functionalities have been integrated into the HiPath 3000 communications system from version 5.0. This means that every HiPath 3000 system with at least one HG 1500 board represents an individual gatekeeper zone to which their registered IP workpoint clients also belong. |
| Communication between networked HiPath 3000 systems (nodes) should be considered as gatekeeper to gatekeeper communication. HG 1500 boards in networked systems are not registered. The CorNet-NQ protocol is used, tunneled in H.323 via Annex M1. |
| The breakdown of HG 1500 resources into signaling and payload resources is a basic feature of version 5.0. |
| • | Signaling resources This includes all node signaling data necessary for Voice over IP for IP-supported (LAN, intranet, internal) and line switched networks (ISDN, PSTN). These resources are provided centrally by a single HG 1500 board, the signaling gateway (= HG 1500 gatekeeper), regardless of how many HG 1500 boards the node has. HG 1500 boards are defined as HG 1500 gatekeepers by HiPath 3000/5000 Manager E. |
| • | Payload resources The node resources required for gateway transfer (between IP-supported and line-switched networks) of VoIP voice data (payload) are provided by the media PC gateway (= HG 1500 gateway). This can involve one or more HG 1500 boards. No payload resources are necessary for direct transfer between IP-supported networks. |
| In systems with only one HG 1500 board, the board functions as both a signaling gateway and a media gateway. The "Release gateway resources" flag must be activated in HiPath 3000/5000 Manager E for this. You cannot assign resources if this flag is not set. |
| In systems with several HG 1500 boards, the payload resources are controlled by the node-central Resource Manager. This is a self-configuring service. Signaling resources are provided centrally by the board defined as Gatekeeper. This signaling gateway accesses additional resources (CODECs, B channels, etc.) and signaling data (for example, RTP, RTCP) of the media PC gateway. This provides IP workpoint clients and other gateways with central access to the payload resources of all the node-specific HG 1500 boards. |
| 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 only provided by the media gateway based on performance. |
| HiPath 3000/5000 V9, Feature Description, Issue 7 | up |
|
|
||
| Disclaimer & Copyright | ID: P31003H3590F100017618 | 2012-06-25 |