10.2  
Networking possibilities 
 

10.2.1  
Application and Networking Scenarios 
 

Overview  
This chapter contains information on key implementation and networking scenarios. The sample configurations describe how networking scenarios are configured.

Contents  
This chapter covers the following topics:
 •   Section 10.2.1.1 "HiPath 3000 standalone (TDM)"
 •   Section 10.2.1.2 "HiPath 3000 standalone (TDM and IP)"
 •   Section 10.2.1.3 "HiPath 3000 networked with HiPath 5000 via IP"
 •   Section 10.2.1.4 "HiPath 3000 networked over IP with HiPath 5000 (with VPN)"
 •   Section 10.2.1.5 "HiPath 3000 networks with OpenScape Office LX/MX/HX"
 •   Section 10.2.1.6 "HiPath 3000 networked with HiPath 2000, HiPath 4000 and HiPath 5000"
 •   Section 10.2.1.7 "HiPath 3000 as a branch on HiPath 4000 (small remote site)"
 •   Section 10.2.1.8 "Virtual Private Networks (Site-to-Site VPN)"
 •   Section 10.2.1.9 "IP Networking of Two HiPath 3000 Systems that Support Signaling and Payload Encryption (SPE)"
 •   Section 10.2.1.10 "Networking HiPath 3000 with OpenScape Voice via SIP-Q V2"

10.2.1.1  
HiPath 3000 standalone (TDM) 
 Figure 10-1   HiPath 3000 as a Standalone System
 
In this scenario, HiPath 3000 is implemented as a standalone system in the traditional telephone infrastructure environment.

10.2.1.2  
HiPath 3000 standalone (TDM and IP) 
 Figure 10-2   HiPath 3000 as a Standalone System (TDM and IP)
 
In this scenario, HiPath 3000 is implemented as a standalone system in the traditional and IP-based telephone infrastructure environment. The customer's existing IP network (corporate network) is used to exclude IP workpoints. Existing fax devices are connected to the IP network via HiPath AP 1120.
This scenario is suitable for customers who want to protect their existing investments in the traditional telephone infrastructure, but would like to migrate gradually to an IP-based environment.

10.2.1.3  
HiPath 3000 networked with HiPath 5000 via IP 
 Figure 10-3   HiPath 3000 networked with HiPath 5000 via IP
 
In this scenario, HiPath 3000 is used as a gateway to the network operator's traditional telephone infrastructure (PSTN). On the station side however, the IP-based telephone infrastructure is used.

10.2.1.4  
HiPath 3000 networked over IP with HiPath 5000 (with VPN) 
 Figure 10-4   HiPath 3000 networked over IP with HiPath 5000 (with VPN)
 
HiPath 5000 PCS is not available in HiPath 3000. Only the use of HiPath 5000 RSM has been released.

10.2.1.5  
HiPath 3000 networks with OpenScape Office LX/MX/HX 
HiPath 3000 V9 or later can be networked with OpenScape Office communication systems.
Call pickup groups and MULAPs can only be configured for stations that are connected to the same node.
Prerequisites:
 •   The HiPath 3000 call numbers must be adapted if required. The open numbering scheme is not supported for networking with HiPath 3000.
 •   The relevant HG 1500s are configured.
 •   An OpenScape Office HX is already installed and configured on HiPath 3000.
Further information and configuration examples for networking with OpenScape Office can be found in the documentation for OpenScape Office V3.  

10.2.1.6  
HiPath 3000 networked with HiPath 2000, HiPath 4000 and HiPath 5000 

Scenario  
 Figure 10-5   Networking HiPath 3000 with HiPath 2000, 4000, 5000
 
The features transmitted between communication systems are dependent on the protocol used.

Using the protocols  
Protocols are used as follows (regardless of version):
 •   HiPath 3000 V8 or later <-> HiPath 4000 V5 or later <-> HiPath 5000: SIP-Q V2 and CorNet-NQ
 •   HiPath 3000 V8 <-> HiPath 3000 V7 <-> HiPath 2000 (HiPath OpenOffice EE) <-> HiPath 4000 V4 <-> HiPath 5000: SIP-Q V2, CorNet-IP and CorNet-NQ
The CorNet-IP protocol is no longer supported from HiPath 3000 V8 and HiPath 4000 V5 to network both of these systems.  

10.2.1.7  
HiPath 3000 as a branch on HiPath 4000 (small remote site) 
 Figure 10-6   Small Remote Site: Normal state
 
This scenario is a special variant of the networking with HiPath 4000 systems. This configuration enhances the failure tolerance of the IP stations.
In the normal state, the IP stations in the branch locations (small remote site) are logged on and registered at the HiPath 4000 system.
Station 4711 at location 2 can be contacted using the number 089/722 4711 via the HiPath 4000 system at location 1.
Station 4711 at location 2 can be contacted using the number 040/123 10 via the HiPath 3000 system at location 2 (principle: the call is forwarded to station 4711 in HiPath 4000 when you dial IP station 10 in HiPath 3000).
Fax station 20 can be contacted using the number 040/123 20 via the HiPath 3000 system at location 2.
External outgoing calls from station 4711 are sent, depending on HiPath 4000 administration, either via HiPath 4000 or via the assigned HiPath 3000 gateway.
Boundary conditions for the small remote site:
With the exception of fax stations there must not be any TDM stations in the HiPath 3000 system on the station side.
The number of IP stations at the individual locations is defined by the limitations of the HiPath 4000 system and the IP infrastructure, in particular by the available bandwidths.
Bandwidth management performed by HiPath 4000 Resource Manager for IP trunking and IP stations must be taken into account here.
This networking scenario is not approved for use at the moment in networks with only HiPath 3000/5000 systems.
HiPath AllServe is not approved for use.
HiPath 5000 PCS is not approved for use.
 Figure 10-7   Small Remote Site: Failure of the IP Network
 
In emergency mode (for example, failure of the IP network), the IP stations lose the connection to the HiPath 4000 gateway. The "Small Remote Site Redundancy" function causes the call number and the gateway to be switched automatically.
Station 4711 at location 2 registers automatically on the HiPath 3000 system at location 2 and is assigned the extension number 10.
An external call to extension 10 in HiPath 3000 reaches extension 10 directly in this case.
An external call to extension 4711 over HiPath 4000 can be routed via trunks within HiPath 4000 to HiPath 3000.

10.2.1.8  
Virtual Private Networks (Site-to-Site VPN) 
HiPath3000 is a secure solution for establishing site-to-site VPNs. The solution uses the cost-effective public network infrastructure to network locations (headquarters, regional offices or branch offices). HiPath 3000 systems can be networked with each other and mixed HiPath 2000 / HiPath OpenOffice EE / HiPath 3000 networks are also possible with HiPath 3000 V5.0 or later. Connection to the Internet can be established using Internet dedicated lines or xDSL connections with a permanent IP address. Even Internet connections with a dynamic IP address can be used via DynDNS. Data and voice (TDM and VoIP) are tunneled over the Internet. HiPath 3000 checks authentication of the VPN partners, encrypts and decrypts the data packets sent and received by the relevant workpoints and applications, and ensures data confidentiality and integrity.
Advantages of VPN site-to-site networking:
 •   Secure business processes
 •   Secure integration of external partners in the company network
 •   Access to company information for field service

10.2.1.9  
IP Networking of Two HiPath 3000 Systems that Support Signaling and Payload Encryption (SPE) 
This section describes the Signaling & Payload Encryption feature. This feature is provided in HiPath 3000/5000 V7 R4 or later systems.
 Figure 10-8   IP Networking of Two HiPath 3000 Systems with SPE
 
This scenario contains two SPE-capable HiPath 3000 systems, whose respective HG 1500 gateways are connected to one another over a Secure Trunk. The signaling data between the HG 1500 and the HFA/SIP telephones is always encrypted using TLS. Several calls are displayed:
R <--> T  
Gateway call  
Payload is encrypted by HG 1500, even if a TDM terminal configured for HiPath 3000 as a "Traditional client" is involved. This is because the remote station supports payload encryption from the perspective of HiPath 3000.  
N <--> X  
Gateway call  
Traditional client: without signaling and payload encryption.  
M <--> T  
Gateway call  
Payload is not encrypted by HG 1500, because the remote station does not support payload encryption from the perspective of HiPath 3000.  
S <--> Y  
Network call  
The payload data is encrypted, since both telephones are "secure clients". Signaling data (such as IP addresses) is transmitted via the HG 1500 gateways.  
M <--> Z  
Network call  
Payload is not encrypted, because a terminal is configured as "Standard client". Signaling data (such as IP addresses) is transmitted via the HG 1500 gateway.  
Standard client: without encrypting user data.  
If SPE is activated on HiPath 3000, signaling & payload encryption is activated by default on all IP trunking connections on this HiPath 3000 system.
Due to the payload switching concept (PLS), the HG 1500 gateway is not involved in transmitting payload from a network call between two IP terminals. HG 1500's payload encryption capability is only relevant in gateway calls.

10.2.1.10  
Networking HiPath 3000 with OpenScape Voice via SIP-Q V2 

Prerequisites  
 •   HiPath 3000 V8 MR5 or later
 •   OpenScape Voice as of V5 R0

Example scenario  
 Figure 10-9   HiPath 3000 as a gateway, networked with OpenScape Voice
 

Supported scenarios  
All models of the HiPath 3000 family can be used as a gateway for connecting to OpenScape Voice systems. The following scenarios have been released:
 •   A HiPath 3000 as a single gateway with connection to digital exchanges
(ISDN, T1, CAS)
 •   Several HiPath 3000 systems as gateways with connection to digital exchanges
(ISDN, T1, CAS)
 •   For Brazil only:
The connection of analog trunks to HiPath 3000 gateways has been released in this context (due to dual-sided "Silent Reversal" support of trunks in Brazilian exchanges).

Telephones:  
The following devices can be connected to the HiPath 3000 gateway in the above scenarios:
 •   Analog and digital telephones
 •   DECT telephones
 •   IP telephones with HFA protocol
    If IP phones with the HFA protocol are to be used, the additional requirement of B-channels must be taken into account in the project planning. For each connection between HiPath 3000 and OpenScape Voice, 2 B-channels of the HG 1500 are required for these telephones; for TDM devices, by contrast, only 1 B channel is needed.

Supported features and restrictions to be observed  
The supported features are described in Section 10.3.3 "HiPath 3000 as a gateway for OpenScape Voice V4".
The following restrictions must be noted:
 •   The connection of analog trunks to HiPath 3000 gateways has not been released (Exception: Brazil, due to dual-sided "Silent Reversal" support in Brazilian exchanges).
 •   Networking of HiPath 3000 gateways to one another or with systems other than OpenScape Voice is not supported. HiPath 5000 Real-Time Services Manager RSM is not supported. Networking of HiPath 3000 gateways to OpenScape OpenScape must use a star network topology.
 •   Path replacement via SIP-Q V2 is not supported for TDM workpoints connected to a HiPath 3000 gateway.
 •   To avoid poor voice quality for transit connections, avoiding the use of the G.729 voice codec is recommended. The G.729 voice compression could degrade voice quality (especially when HiPath 3000 HFA telephones are connected to OpenScape Voice). The use of the G.711 codec is therefore recommended.
    Transit trunk connections can stem from features such as Conference, Call Forwarding, and Transfer as path replacement is not supported.
 •   No cross-system support is available for features such as call pickup groups, group calls and hunt groups between OpenScape Voice and HiPath 3000 gateways. Consequently, groups may include only OpenScape Voice or HiPath 3000 stations, but not both. The sole exception is the "One Number Service" of OpenScape Office.
 •   Encryption (SPE) is not supported between OpenScape Voice and HiPath 3000 gateways.
 •   The TDM workpoints and trunk lines connected to a HiPath 3000 gateway cannot be integrated into OpenScape Voice applications and cannot use these. Dialing from OpenScape Voice applications over HiPath 3000 gateways will be supported from HiPath 3000 V8 MR5 onward.
 •   Only networking with an E.164 numbering plan will be supported.

Setting in Manager E  
The switch "Always use DSP" must be activated in HiPath 3000/5000 Manager E (Settings: Trunks/Networking - Routes) for the OpenScape Voice networking trunk group.

HiPath 3000/5000 V9, Feature Description, Issue 10   up Top
Disclaimer & Copyright   ID: P31003H3590F100017618   2014-02-27