10.2.2 |
Networking Scenarios in the LAN Network |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The scenarios are described in the subsequent sections. |
10.2.2.1 |
Scenario 1 |
IP Trunking HiPath 3000/3000, 2 Nodes in the Network |
|
|
| • | Functional scope between both HiPath 3000 systems corresponds to CorNet-IP |
| • | Closed numbering (private numbering plan): Dialing from node to node: internal number Dialing from PSTN: subscriber line + internal number |
| • | Open numbering: Dialing from node to node: dialing of the node code + internal number (private numbering plan) |
| • | Implementation of the HiPath 5000 RSM Feature Server for closed and open numbering is possible |
| • | Max. 1000 nodes in the network when using the HiPath 5000 RSM Feature Server (incl. TDM) |
| • | Max. 32 nodes in the network when using the HiPath 5000 RSM Feature Server |
| • | Max. 64 nodes in the network without the HiPath 5000 RSM Feature Server |
| • | An optional HPCO V1.3 can be implemented (for max. 16 nodes in the network) |
| - | Alternatively, OpenScape Contact Center on a single node |
| • | An optional Xpressions Compact can be implemented centrally |
| - | Alternatively, central OpenScape Xpressions |
10.2.2.2 |
Scenario 2 |
IP Trunking HiPath 3000/5000, 2 Nodes in the Network with Closed Numbering |
|
| • | Feature scope corresponds to CorNet-IP |
| • | Closed numbering: Dialing from node to node: internal number Dialing from PSTN: subscriber line + internal number |
| • | Open numbering is not supported by this configuration. (Availability of the PSTN not guaranteed as the node number is not included in the customer's station number block, CCBS not guaranteed, etc.) Exception: where the node number + internal number are contained in the customer's station number block. |
| • | Max. 1000 nodes in the network when using the HiPath 5000 RSM Feature Server (incl. TDM) |
| • | Max. 32 nodes in the network when using the HiPath 5000 RSM Feature Server |
| • | Max. 64 nodes in the network without the HiPath 5000 RSM Feature Server |
| • | An optional HPCO V1.3 can be implemented (for max. 16 nodes in the network) |
| - | Alternatively, OpenScape Contact Center on a single node |
| • | An optional Xpressions Compact can be implemented centrally |
| - | Alternatively, central OpenScape Xpressions |
10.2.2.3 |
Scenario 3 |
IP Trunking HiPath 3000/5000, 4 Nodes at 2 Locations |
|
10.2.2.4 |
Scenario 4 |
IP Trunking HiPath 3000/4000 |
|
| • | Functional scope between HiPath 4000/3000 corresponds to CorNet-IP |
| • | Closed numbering (private numbering plan): Dialing from node to node: internal number Dialing from PSTN: subscriber line + internal number |
| • | Open numbering: Dialing from node to node: |
| - | Variant 1: Dialing of the node code + internal number (private numbering plan) |
| or |
| - | Variant 2: Dialing of the CO number (ISDN numbering plan) |
| • | Implementation of the HiPath 5000 RSM Feature Server is only possible for closed numbering |
| • | Max. 1000 nodes in the network when using the HiPath 5000 RSM Feature Server (incl. TDM) |
| • | Max. 32 nodes in the network when using the HiPath 5000 RSM Feature Server |
| • | Max. n times 64 nodes in the network without the HiPath 5000 RSM Feature Server |
| • | An optional HPCO V1.3 can be implemented (for max. 16 nodes in the network) for closed numbering and open numbering as per variant 1 only |
| - | Alternatively, OpenScape Contact Center on a single node |
| • | Central Xpressions Compact For closed numbering and open numbering as per variant 1 only |
10.2.2.5 |
Scenario 5 |
Payload Switching with IP Trunking |
| If there are more than 64 nodes or one domain, Codec G.711 must be implemented to ensure sufficient voice quality. |
|
10.2.2.6 |
Scenario 6 |
Connection to Internet telephony service providers (Internet telephony) |
| HiPath 3000 supports connection to Internet telephony service providers (ITSPs) as an Internet telephony user connection with registration of individual phone numbers. For larger system configurations, it supports connection as a Internet telephony system connection, for which the ITSP provides a phone number range. |
| • | The system supports up to four simultaneously active SIP providers via LCR. |
| • | Four different ITSPs may be registered simultaneously. |
| • | S0 connections and Internet telephony connections can be used in parallel in all networking solutions to connect to ITSP analog lines. |
| • | Internet access: HG 1500 is operated in the LAN behind an external router with firewall or NAT function. |
|
10.2.2.7 |
Scenario 7 |
Networking multiple HiPath 3000 systems, each equipped with one local Linux server with OpenScape Office HX |
| This scenario is possible from HiPath 3000 V8 MR5 (V8 R5.2.0) onwards. The individual HiPath 3000s are interconnected in the LAN using the CorNet-NQ protocol with H.323 tunneling. Up to 64 HiPath 3000 nodes with a total of 2000 stations can be present in this network. All involved HiPath 3000 systems must carry the same software version. Only closed numbering is supported. SIP and PSTN providers can only be connected locally, i.e. to any HiPath 3000. |
| To make OpenScape Office HX features available on HiPath 3000 nodes, a separate OpenScape Office HX Linux server with the OpenScape Office applications must be connected to each HiPath 3000 system. A central server is not possible. |
Graphical overview |
|
Restrictions |
| The following restrictions apply to networking with OpenScape Office HX: |
| • | The open numbering scheme is not supported; only closed numbering is supported. |
| • | Networking of OpenScape Office applications between the local OpenScape Office HX systems is not possible. The presence status of the users of the remote OpenScape Office HX node may not be visible, for instance. |
| • | Concatenated cross-node call forwarding and forwarding to OpenScape Office HX in the external HiPath 3000 node are not followed. |
| • | OpenScape Office HX is connected to the HiPath 3000 as an external H.323 gateway. Therefore, no additional networking with HiPath 4000 via H.323-Q is possible in this scenario. |
| • | Only Route 8 of the HiPath 3000 must be used for connecting OpenScape Office HX. |
| • | Due to the licensing model used, the HiPath 3000 internetwork with integrated OpenScape Office HX cannot be administered via HiPath 5000 RSM. |
Locally supported features |
| The following features may only be made available locally, not centrally in the HiPath 3000 network: |
| • | OpenScape Office: |
| - | Presence: Internal directory, Favorites |
| - | Busy status: Internal directory, Favorites |
| - | External directory |
| • | myAttendant: |
| - | Instant messaging |
| - | Adding contacts in an external directory |
| - | Querying voice mails for another station |
| - | Automatic recall, intercept, divert display |
| • | myAgent |
| • | TAPI 120, CallBridge IP (TAPI 170 network-wide) |
| • | External CSTA applications |
| • | Mobility entry with DISA access, myPortal Web |
Non-supported features |
| The following features are not supported in this scenario: |
| • | Networking via SIP/SIP-Q |
| • | Support of OpenScape Voice (HiPath 8000), HiPath OpenOffice EE, HiPath 4000 and HiPath 5000 RSM |
| • | OpenScape Office networking. HiPath 3000 V8 MR 5.2 or later allows for the connection of two HiPath 3000 V8's, each of which must be equipped with a local OpenScape Office HX V2 PC. The CorNet-NQ protocol with H.323 tunneling is used for this purpose. |
| • | HiPath 3000 systems with differing software versions |
| • | Central voice mail |
| • | Open numbering plan |
| HiPath 3000/5000 V9, Feature Description, Issue 10 | up  |
|
 |
||
| Disclaimer & Copyright | ID: P31003H3590F100017618 | 2014-02-27 |