OpenScape Voice Standard Solution configuration examples

OpenScape Voice Solution
Configuration Guide
for
Trunking HiPath3000 - OpenScape Voice

Version: 2.02
Date: 08/19/2010
Author: Thomas Otto, SEN VA AP D SI 1

Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 1

OpenScape Voice Standard Solution configuration examples
Table of content
1 Configuration Guide for Trunking HiPath3000 - OpenScape Voice .......................................... 4
1.1 General.............................................................................................................................. 4
1.1.1 Prerequisites ............................................................................................................... 4
1.1.2 Features and Restrictions in Networking ..................................................................... 4
1.2 Configuration HiPath 3000................................................................................................. 7
1.2.1 Settings in Manager E on HiPath 3000........................................................................ 7
1.2.1.1 Lines/networking > IP Trunks................................................................................ 8
1.2.1.2 Lines/networking -> Routes (Route to Carrier) ...................................................... 9
1.2.1.3 Lines/networking -> Routes (Route to OpenScape Voice) .................................. 10
1.2.1.4 Lines/networking -> Routing parameters............................................................. 11
1.2.1.5 Network... -> Ext. SIP ......................................................................................... 12
1.2.1.6 Network... -> Gatekeeper.................................................................................... 14
1.2.1.7 Least cost routing ............................................................................................... 15
1.2.1.8 System parameters -> Flags............................................................................... 34
1.2.1.9 Flag: Transit allowed via Hook-on....................................................................... 36
1.2.1.10 Phone Payload Security.................................................................................... 37
1.2.2 Settings in the HG 1500 WBM................................................................................... 38
1.2.2.1 Codec Parameters.............................................................................................. 38
1.2.2.2 SIP Parameters .................................................................................................. 40
1.2.2.3 Adding and Configuring PBX Nodes ................................................................... 41
1.2.2.4 Certificates import for TLS .................................................................................. 44
2.1 Configuration OpenScape Voice...................................................................................... 47
2.1.1 Settings in Common Management Portal .................................................................. 47
2.1.1.1 Administration of an new Gateway Private Numbering Plan ............................... 48
2.1.1.2 Administration of an Endpoint Profile for a HiPath 3000 Endpoint....................... 48
2.1.1.3 Creating and configuring an endpoint for HiPath 3000........................................ 51
2.1.1.4 Creating "Digest Authentication" access for HiPath 3000.................................... 54
2.1.1.5 Configuring a Gateway Numbering Plan for Incoming Calls................................ 56
2.1.1.6 Configuring Outgoing Calls ................................................................................. 58
2.1.1.7 Display Number Modification for OpenScape Voice V5.0.................................... 66
2.1.2 Settings in StartCli..................................................................................................... 73
2.2 Configuration OpenBranch .............................................................................................. 74
2.2.1 Network Services ...................................................................................................... 74
2.2.2 VOIP ......................................................................................................................... 80
Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 2

OpenScape Voice Standard Solution configuration examples
History
Issue

Date

1.0

02/05/2008 Initial creation of version 1.0

1.1

08/08/2008 Updated Version

1.2

11/21/2008 incorporate of inputs from official documentation

2.0

04/30/2009 Input of FRN 3054 Trunking HiPath 3000 V8.0 OpenScape
Voice V4.0

2.01

10/19/2009 Updated Version for OSV V4R1 and HiPath 3000 V8R3

2.02

08/19/2010 Updated Version for OSV V5R0 and HiPath 3000 V8R5

Siemens Internal Use Only

Reason for Changes

Date: 08/19/2010

Version 2.02

Status: Released

page 3

OpenScape Voice Standard Solution configuration examples

1 Configuration Guide for Trunking HiPath3000 - OpenScape Voice
1.1 General
This section describes the configuration of SIP-Q networking between HiPath 3000 and
Open-Scape Voice. To do this, you will have to configure settings on HiPath 3000 in
Manager E and in the HG 1500 WBM. On OpenScape Voice, settings are made in the
Common Management Portal and in StartCli. The Common Management Portal is also
used for OpenScape Branch.
Contents
This section covers the following topics:
Section 1.1.2, "Features and Restrictions in Networking"
Section 1.2, "Configuration HiPath 3000 "
Section 1.3, "Configuring OpenScape Voice"
Section 1.4, "Configuring OpenScape Branch"
1.1.1 Prerequisites
Step1 (FRN 2080): 
HiPath 3000 Version 7.0 R4 
OpenScape Voice Version 3.1 R2
Step2 (FRN 3054): 
HiPath 3000 Version 8.0 R0 or newer 
OpenScape Voice Version 4.0 R0 or newer

1.1.2 Features and Restrictions in Networking
Step1 (FRN 2080):
HiPath 3000 Version 7.0 R4 or newer
OpenScape Voice Version 3.1 R2 or newer 

HiPath 3000 is only released as SIPQ Gateway. Endpoints shall not be connected
to the HiPath 3000

Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 4

38 is not supported. analog and CMI) can be connected to HiPath 3000.  Two HiPath 3000 systems cannot be networked via a direct IP connection.711. Carrier Trunk connection  HiPath 3000 supports ISDN and CAS (Channel-Associated Signaling) interfaces for the trunk connection.  For incoming calls through HiPath 3000 the name display on the phone shows the calling party number (calling party number appears twice on the phone display)  ISDN Data transfer: outgoing data calls from OpenScape Voice to CO is currently not supported yet (ISDN modem -> Mediatrix TA –> HP3k -> CO) Step2 (FRN 3054): HiPath 3000 Version 8.  Analog trunks and SIP providers are not supported to use in HiPath 3000. A direct IP-Trunking connection between 2 HiPath 3000 is not allowed.0 R0 or newer OpenScape Voice Version 4.  IP devices cannot be connected to HiPath 3000. Fax will be sent via G.38 (Fax) is not supported. The codec will be switched in case of detection of fax tone. Only a star networking topology is supported.  A HiPath 3000 gateway is not released in a branch environment with Comdasys SIP proxies. The OpenScape Voice must be the central node in the IP-Trunking network. T.0 R0 or newer Network  Only star networks are supported.02 Status: Released page 5 .OpenScape Voice Standard Solution configuration examples     HiPath 3000 supports as CO trunk the interface ISDN and CAS. Analog trunk is not supported. Terminal Devices  TDM devices (UP0. This means that OpenScape Voice is always the central switch. Siemens Internal Use Only Date: 08/19/2010 Version 2.  A HiPath 3000 gateway is not released in an OpenScape Voice geographical node separated environment. Fax HiPath 3000 V8 R4 and earlier:  T. Path replacement is not supported and must be deactivated  All OpenScape Voice endpoints including all HiPath 3000 gateways must be registered on the same OpenScape Voice node.

OpenScape UC users can be configuring to a “HiPath 3000 subscriber”/”external party over HiPath 3000” as OND-Device. Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 6 . the "low bandwidth only" codec may not be activated.38 is supported now.711 is supported.  Rerouting is not supported and must be deactivated. OpenScape Branch environment  HiPath 3000 is released as a gateway for a branch solution with OpenScape Branch SIP proxies.  Trunk optimization  Path optimization is not supported and must be deactivated. Central voicemail  Central voicemail can be connected on HiPath 3000 or on OpenScape Voice. The codec is automatically switched on if a fax tone is detected. OpenScape UC application  HiPath 3000 V8 R4 and earlier: OpenScape UC users have not to configure a “HiPath 3000 subscriber”/”external party over HiPath 3000” as OND-Device.OpenScape Voice Standard Solution configuration examples Fax over G.  HiPath 3000 V8 R5 and newer: restriction with OND-Device not more exist.  MoH is not available when proxy is in Limited Mode.  On optiPoint telephones. HiPath 3000 V8 R5 and newer:  T. The connection to HiPath 3000 remains silent when on hold. Comdasys proxy is not supported.

2. "Lines/networking -> IP Trunks" Section 1. make the following settings: Section 1.1.1.5. "Settings in Manager E on HiPath 3000" Section 1.2.1. "System parameters -> Flags" Section 1.OpenScape Voice Standard Solution configuration examples 1. 2. "Lines/networking -> Routing parameters" Section 1.7.10. SIP" Section 1.8.9.1..1 Settings in Manager E on HiPath 3000 Procedure 1. "Flag: Transit allowed via Hook-on" Section 1. "Network -> Gatekeeper" Section 1. "Network. Contents In HiPath 3000 Manager E.6.02 Status: Released page 7 . Follow the remaining steps in sequence.1.1..2.1. “Phone Payload Security” Siemens Internal Use Only Date: 08/19/2010 Version 2.2.2.1.4.1. -> Ext.1. "Least Cost Routing" Section 1.2. "Lines/networking -> Routes (Route to Carrier)" Section 1.1.2. "Lines/networking -> Routes (Route to OpenScape Voice)" Section 1.1.2.2.2.3.2.2. "Settings in the HG 1500 WBM" 1.2. Start Manager E.2.2.2 Configuration HiPath 3000 Contents This section covers the following topics: Section 1.

● Click Add. Siemens Internal Use Only Date: 08/19/2010 Version 2. make the following settings: ● Gatekeeper HG1500: e. 2.OpenScape Voice Standard Solution configuration examples 1. Under "Selection".SIP. select Lines/networking.1. make the following settings: ● enter the number of trunks and Ext. Click Apply. 3. Your changes are saved.g. Systemview -> Settings -> Lines/networking -> select IP Trunks.2.02 Status: Released page 8 . In the system view. The window "IP Trunks" is displayed.1 Lines/networking > IP Trunks 1. Under "Number". 4. Slot5 ● Enable gateway resources: activate the checkbox in case Gatekeeper resources shall be used.

● Location number: Activate the checkbox.2. Systemview -> Settings -> Lines/networking -> select Routes. 4. Select the route "Trk Grp 1" (route to the Carrier). 2.02 Status: Released page 9 . To do this proceed as follows: 1. Siemens Internal Use Only Date: 08/19/2010 Version 2. Click Apply. 5113. Your changes are saved.1. for example:49.OpenScape Voice Standard Solution configuration examples 1. 3. 69.164 format for the country code. The settings for this route are displayed. local area code and system number. The window "Routes" is displayed.2 Lines/networking -> Routes (Route to Carrier) One route to the Carrier must be configured. make the following settings: ● Route Name/Name: CO ● PABX number-incoming: Enter the location number in the E. For Trk Grp 1.

164 format for the country code.2. ● Digit transmission: en-bloc sending ● Always use DSP: Activate the checkbox. 3. This number is generally the same as the number entered for route "CO" (see previous section). 5113. 4.1. Click Apply. Systemview -> Settings -> Lines/networking -> select Routes. Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 10 . To do this proceed as follows: 1. in this example: 49. 69. make the following settings: ● Route Name/Name: Hp8k ● 2nd trunk code: Enter 0 for the local PSTN access code ● PABX number-incoming: Enter the location number in the E.OpenScape Voice Standard Solution configuration examples 1.3 Lines/networking -> Routes (Route to OpenScape Voice) One route to OpenScape Voice must be configured. For Trk Grp 10. 2. The window "Routes" is displayed. Select the route "Trk Grp 10" (route for OpenScape Voice). Your changes are saved. The settings for this route are displayed. local area code and system number.

To do this proceed as follows: 1. Siemens Internal Use Only Date: 08/19/2010 Version 2.2.1. The window "Routing parameters" is displayed.4 Lines/networking -> Routing parameters You must set routing parameters for the "Hp8k" route created in the previous section. and type. 3.02 Status: Released page 11 . 2. Click Apply. Select the "Hp8k" route. make the following settings: ● Route type: PABX ● No. For "Hp8k".OpenScape Voice Standard Solution configuration examples 1. The settings for this route are displayed. Your changes are saved. outgoing: Country code ● Route optimize active: No 4. Systemview -> Settings -> Lines/networking -> select Routing parameters.

OpenScape Voice Standard Solution configuration examples 1. ● IP Address: enter an IP-Address of the following components . Your changes are saved.g. . SIP. Make the following settings in the "Gateway" window: ● Environment: HiPath 8000 ● Trunking mode: SIP-Q ● Call Number: Alias number of the terminal device in OpenScape Voice. 3.TLS trunking to OpenScape Voice enter the IP of sipsm3 for Node 1 or IP of sipsm4 for Node2.1.02 Status: Released page 12 . Select the check box "Operate with external SIP-Registrar". ● Port: Enter 5060 for TCP or enter 5061 for TLS. 4. ● Realm: Enter the Realm Name e.g. Systemview -> Settings -> Network -> select Ext. SIP" is displayed. ● Registration expiry: At least 300. To do this proceed as follows: 1. hipath3000br13 ● Password: Enter the password. ● TLS: Activate the checkbox for TLS or uncheck for TCP ● Alternate RG IP address: enter a fallback IP-Address .2. ● Confirm password: Re-enter the password to confirm. The window "Ext. 13310.IP of OpenBranch Proxy .. . Make the following settings in the "Security" window: ● Activate the "Authentication Required" checkbox if Digest Authentication is prescribed by OpenScape Voice. Click Apply. e.5 Network.TCP trunking to OpenScape Voice enter the IP of sipsm2 for Node 2 or IP of sipsm1 for Node1. -> Ext.TCP trunking to OpenScape Voice enter the IP of sipsm1 for Node 1 or IP of sipsm2 for Node2.TLS trunking to OpenScape Voice enter the IP of sipsm4 for Node 2 or IP of sipsm3 for Node1. ● Perform registration: Activate the checkbox.g. sol 5. ● SIP User ID: e. 2. Siemens Internal Use Only Date: 08/19/2010 Version 2.. SIP Parameters for the external SIP registrar must be set.

02 Status: Released page 13 .OpenScape Voice Standard Solution configuration examples TCP non secure TLS secure Siemens Internal Use Only Date: 08/19/2010 Version 2.

3. In the "SNTP Server" area.1. This is achieved by all components using the same NTP server. the same time must be set for all connections.. -> Gatekeeper Enter the NTP server address. make the following settings: ● IP address: Enter the NTP server IP address Attention: For TLS connections. Your changes are saved.OpenScape Voice Standard Solution configuration examples 1..6 Network.2.02 Status: Released page 14 . Systemview -> Settings -> Network -> select Gatekeeper. To do this proceed as follows: 1. Click Apply. Siemens Internal Use Only Date: 08/19/2010 Version 2. The "Gatekeeper" window is displayed. 2.

Make the following settings: ● Activate LCR: Activate the checkbox. Click Apply.2.02 Status: Released page 15 . 4. The "Flags and COS" window is displayed. Siemens Internal Use Only Date: 08/19/2010 Version 2.7 Least cost routing Basic settings Proceed as follows: 1.1. ● In the "Class of service" table. 2. assign COS 14 to all phone numbers.OpenScape Voice Standard Solution configuration examples 1. Your changes are saved. Systemview -> Settings -> Least Cost Routing -> select Flags and COS.

must be handled in 3 LCR rules. COS). COS). 0C0-Z (Dialed digits). national calls (Dialed digits 0C0-Z). During a trunk failure. -. 14 (min. Local calls (Dialed digits 0CZ). 14 (min. CO (Dial rule). 14 (min.2.OpenScape Voice Standard Solution configuration examples 1. 3 (Route table) Route table: CO (Route). -. Local calls Dialed digits: CO (name). Display + tone (Warning) International calls: Dialed digits: CO (name). E. COS). 1 (Route table) Route table: CO (Route). 0C00-Z (Dialed digits). COS). 14 (min. Display + tone (Warning) Siemens Internal Use Only Date: 08/19/2010 Version 2. This route is only used to bridge trunk failures. E.164 int.164 city (Dial rule).02 Status: Released page 16 . -. 0CZ (Dialed digits). (Dial rule).164 nat. 14 (min. -. E. -.1. COS). CO (Dial rule). 14 (min.7. and International calls (Dialed digits 0C00-Z). 2 (Route table) Route table: CO (Route). CO (Dial rule). Display + tone (Warning) National calls: Dialed digits: CO (name). As an option. -. calls are routed to OpenScape Voice (with a transition to another OpenScape Voice gateway). (Dial rule).1 Least cost routing to CO (Carrier) Overview The first route should lead to the CO. None (Warning) Hp8k (Route). COS). None (Warning) Hp8k (Route). None (Warning) Hp8k (Route). a second route can be configured for least cost routing to OpenScape Voice.

02 Status: Released page 17 .164 number format. Siemens Internal Use Only Date: 08/19/2010 Version 2.OpenScape Voice Standard Solution configuration examples Warning! All outdial rules for OpenScape Voice must be configurable in the international E.

Systemview -> Least Cost Routing -> select Dial plan. In the top table. In the Dial rule wizard. 3. Route to OpenScape Voice: 1. The window "Dial plan" is displayed. The Dial rule wizard is closed. set the route to CO. Both tables are now completed as follows. In the "Dial rule" column. and click on Dial rule wizard.164 city ● Network provider’s method of: Corporate network ● Dial rule format: D4969E2A ● min. for example: Name: CO. select it. In the Dial rule wizard. Select the route Hp8k in the lower table in the column "Route" (directly under the route to CO). In the "Route table" selection field.OpenScape Voice Standard Solution configuration examples Step by step configuration For local calls Proceed as follows: 1. The Dial rule wizard is displayed. Your changes are saved. define the dial rule for the selected route. and click on Dial rule wizard. you can make the following settings: ● Edited dial rule: CO ● Network provider’s method of: Main network supplier ● Dial rule format: A ● min. select route table 1 (defined in the previous step). COS. Click OK. COS. 4. Click Apply. Route to CO: 1. 2. select it. 6.02 Status: Released page 18 . 3. 2. Select the route CO in the lower table in the column "Route". 3. Dialed digits: 0CZ. Click OK. 5. The Dial rule wizard is closed. you can make the following settings: ● Edited dial rule: E.: 14 ● Schedule: ● Warning: display + tone ● Type of Number (TON): Country code 4. 2. for example: Siemens Internal Use Only Date: 08/19/2010 Version 2.: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Unknown 4. Route table: 1. The table then shows. define the dial rule for the selected route. The Dial rule wizard is displayed. In the "Dial rule" column.

14 (min. 0CZ (Dialed digits). . COS). rerouting over Hp8k Date: 08/19/2010 Version 2. . Display + tone Route to CO Siemens Internal Use Only in case of CO outage.(Schedule). None (Warning) Hp8k (Route).02 Status: Released page 19 . CO (Dial rule). 1 (Route table) Route table: CO (Route).164 city (Dial rule). E.OpenScape Voice Standard Solution configuration examples Dialed digits: CO (name). COS). 14 (min.(Schedule).

Select the route Hp8k in the lower table in the column "Route" (directly under the route to CO). select route table 2 (defined in the previous step). COS. Route to CO: 1. Both tables are now completed as follows. 3. Systemview -> Least Cost Routing -> select Dial plan. 4. 2. 3. define the dial rule for the selected route. define the dial rule for the selected route. for example: Siemens Internal Use Only Date: 08/19/2010 Version 2. In the "Dial rule" column. The Dial rule wizard is displayed. In the top table. Route to OpenScape Voice: 1. 5. you can make the following settings: ● Edited dial rule: E. The Dial rule wizard is displayed. The Dial rule wizard is closed. for example: Name: CO. In the "Route table" selection field. Click OK. COS. Select the route CO in the lower table in the column "Route". and click on Dial rule wizard. select it. 2.02 Status: Released page 20 . Click OK. In the Dial rule wizard. 3. The Dial rule wizard is closed. The window "Dial plan" is displayed.: 14 ● Schedule: ● Warning: display + tone ● Type of Number (TON): Country code 4. you can make the following settings: ● Edited dial rule: CO ● Network provider’s method of: Main network supplier ● Dial rule format: A ● min.164 nat. Click Apply. Your changes are saved. In the Dial rule wizard. select it.OpenScape Voice Standard Solution configuration examples For national calls Proceed as follows: 1. The table then shows.: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Unknown 4. 2. and click on Dial rule wizard. Dialed digits: 0C0-Z. 6. ● Network provider’s method of: Corporate network ● Dial rule format: D49E3A ● min. set the route to CO. Route table: 2. In the "Dial rule" column.

. CO (Dial rule). COS). 14 (min. .OpenScape Voice Standard Solution configuration examples Dialed digits: CO (name). 14 (min. 0C0-Z (Dialed digits). (Dial rule).02 Status: Released page 21 . None (Warning) Hp8k (Route). E.(Schedule). COS). 2 (Route table) Route table: CO (Route). Display + tone Route to CO Siemens Internal Use Only in case of CO outage. rerouting over Hp8k Date: 08/19/2010 Version 2.164 nat.(Schedule).

(Dial rule). and click on Dial rule wizard. . you can make the following settings: ● Edited dial rule: CO ● Network provider’s method of: Main network supplier ● Dial rule format: A ● min. COS). define the dial rule for the selected route. 3.OpenScape Voice Standard Solution configuration examples For international calls Proceed as follows: 1. In the "Dial rule" column. E. Both tables are now completed as follows. select it. In the Dial rule wizard. 2. select route table 3 (defined in the previous step). The Dial rule wizard is displayed.(Schedule). set the route to CO. you can make the following settings: ● Edited dial rule: E. CO (Dial rule). Route to CO: 1. COS. 5. 14 (min. Click OK.02 Status: Released page 22 . The window "Dial plan" is displayed. Display + tone Siemens Internal Use Only Date: 08/19/2010 Version 2. 3. Route table: 3. 3 (Route table) Route table: CO (Route). The Dial rule wizard is closed. In the "Dial rule" column. None (Warning) Hp8k (Route). Click Apply. Click OK. Systemview -> Least Cost Routing -> select Dial plan.: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Unknown 4. define the dial rule for the selected route. The table then shows. In the Dial rule wizard. .(Schedule).164 int. COS). Select the route Hp8k in the lower table in the column "Route" (directly under the route to CO). 2. 6. The Dial rule wizard is closed. 0C00-Z (Dialed digits). 4. for example: Name: CO.164 int. Select the route CO in the lower table in the column "Route". Dialed digits: 0C00-Z.: 14 ● Schedule: ● Warning: display + tone ● Type of Number (TON): Country code 4. In the top table. ● Network provider’s method of: Corporate network ● Dial rule format: E3A ● min. The Dial rule wizard is displayed. 2. for example: Dialed digits: CO (name). 3. 14 (min. and click on Dial rule wizard. Your changes are saved. COS. select it. Route to OpenScape Voice: 1. In the "Route table" selection field.

02 Status: Released page 23 .OpenScape Voice Standard Solution configuration examples Route to CO Siemens Internal Use Only in case of CO outage. rerouting over Hp8k Date: 08/19/2010 Version 2.

-10x (Dialed digits). -. 14 (min.OpenScape Voice Standard Solution configuration examples 1. Rerouting HQ30 (Dial rule).02 Status: Released page 24 . CO (Dial rule). Display + tone (3 routes are necessary to prevent loops) E. COS). COS). COS). Rerouting HQ30 (Dial rule). COS). None (Warning) Hp8k (Route). (Dial rule).164 internal (Dial rule). 10x (name). -. Display + tone Dialing a short number for all other locations in OpenScape Voice Dialed digits: HQ30 (name).2 Least cost routing to OpenScape Voice Overview Dialing a short number in the same location in OpenScape Voice Dialed digits: int. 15 (min. COS). 15 (min. None (Warning) Hp8k (Route).7. 5 (Route table) Route table: Hp8k (Route).164 internal (Dial rule). 14 (min. 14 (min.1. 0C0-30400xxxxx (Dialed digits). -. E. -. -30xxx (Dialed digits). None (Warning) CO (Route). -. None (Warning) CO (Route). 8 (Route table) Route table: CO (Route). -. E. Rerouting HQ30 (Dial rule).164 Routing to all other numbers in OpenScape Voice Dialed digits: HQ10 (name). 14 (min. None (Warning) CO (Route). COS). -. -.164 nat. E. 14 (min. COS). COS). 14 (min. CO (Dial rule). Display + tone (Warning) (3 routes are necessary to prevent loops) Siemens Internal Use Only Date: 08/19/2010 Version 2. 17 (Route table) Route table: CO (Route).2.

Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 25 .OpenScape Voice Standard Solution configuration examples Warning! All outdial rules for OpenScape Voice must be configurable in the international E.164 numbering format.

2. Systemview -> Least Cost Routing -> select Dial plan. define the route to OpenScape Voice. COS. 5. 3. As an option. Dialed digits: -10X. COS. 10x.164 number is used for HiPath 3000 Phones and OpenScape Voice Phones. During LAN failure. In the "Dial rule" column. This rule will handle calls to OpenScape Voice Phone with the same E. select it. Proceed as follows: 1. you can make the following settings: ● Edited dial rule: Rerouting HQ30 ● Network provider’s method of: Main network supplier ● Dial rule format: D030400E2A for dialing over another Gateway ● min. Route to CO (Carrier): 1. define the dial rule for the selected route. The Dial rule wizard is displayed. In the "Route table" selection field.: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Country code 4.02 Status: Released page 26 . a second route can be configured for least cost routing via the CO. select it. and click on Dial rule wizard. select route table 5 (defined in the previous step). you can make the following settings: ● Edited dial rule: E. The window "Dial plan" is displayed. The second route bridges the gap in the case of LAN failure. The table then shows. The Dial rule wizard is closed. and click on Dial rule wizard.OpenScape Voice Standard Solution configuration examples Step by step configuration Dialing a short number in the same location in OpenScape Voice In case HiPath 3000 is used as a Gateway in a Banch it can by that the same E. 3. 2.164 number. Select the route Hp8k in the lower table in the column "Route". Route table: 5. In the "Dial rule" column. define the dial rule for the selected route.164 internal ● Network provider’s method of: Corporate network ● Dial rule format: D49695113A ● min. Route to OpenScape Voice: 1. calls are routed via the local CO to another OpenScape Voice gateway. In the Dial rule wizard. The Dial rule wizard is displayed. forexample: Name: int. Click OK. The first route should lead to OpenScape Voice. In the top table. 3. In the Dial rule wizard.: 14 ● Schedule: - Siemens Internal Use Only Date: 08/19/2010 Version 2. Select the route CO in the lower table in the column "Route" (directly under the route to OpenScape Voice). 2. 4.

-10x (Dialed digits). 5 (Route table) Route table: Hp8k (Route). Rerouting HQ30 (Dial rule). 10x (name). E. Click Apply. Click OK. Both tables are now completed as follows. 14 (min. -. COS). 6. None (Warning) CO (Route). The Dial rule wizard is closed. Display + tone Route direct to OpenScape Voice Siemens Internal Use Only for LAN outage.02 Status: Released page 27 .164 internal (Dial rule). 14 (min. for example: Dialed digits: int. -. COS). Your changes are saved. rerouting over CO Date: 08/19/2010 Version 2.OpenScape Voice Standard Solution configuration examples ● Warning: display + tone ● Type of Number (TON): Unknown 4.

In the "Route table" selection field. define the dial rule for the selected route. During the LAN failure. 2. you can make the following settings: ● Edited dial rule: HQ30 ● Network provider’s method of: Corporate network ● Dial rule format: e. and click on Dial rule wizard. The Dial rule wizard is displayed. select it. In the "Dial rule" column. you can make the following settings: ● Edited dial rule: Rerouting HQ30 ● Network provider’s method of: Main network supplier ● Dial rule format: D030400E2A ● min. callers must be routed to another OpenScape Voice gateway via the local CO. In the "Dial rule" column. 3. Route to “CO”: 1. so HiPath 3000 telephones can use this route. "CO location" is used if the LAN on the route to OpenScape Voice/OpenScapeBranch fails." (minimum class-of-service) must be set to 14.g. Dialed digits: -30XXX. define the route to OpenScape Voice. The window "Dial plan" is displayed. define the dial rule for the selected route.02 Status: Released page 28 . COS. In the Dial rule wizard. This route is used when OpenScape Voice is not available and OpenScapeBranch routes the call via HiPath 3000. 4. Proceed as follows: 1. 2. 3." (minimum class-of-service) must be set to 15. so only trunks can use this route.: 15 ● Schedule: ● Warning: none ● Type of Number (TON): Unknown 4. D4930400E2A Siemens Internal Use Only Date: 08/19/2010 Version 2. Systemview -> Least Cost Routing -> select Dial plan. forexample: Name: HQ30. Click OK. Route to "OpenScape Voice": 1.OpenScape Voice Standard Solution configuration examples Dialing a short number for all other locations in OpenScape Voice ● The first route "CO" is only for OpenScape Voice callers via HiPath 3000 to CO. Select the route Hp8k in the lower table in the column "Route" (directly under the route to OpenScape Voice). In the Dial rule wizard. The value "min. The Dial rule wizard is closed. select it. COS. 5. Route table: 17. Select the route CO in the lower table in the column "Route". The table then shows. 2. COS. select route table 17 (defined in the previous step). The value "min. 3. ● The third route. ● The second route "OpenScape Voice" is used for callers from HiPath 3000 to OpenScape Voice. In the top table. and click on Dial rule wizard. The Dial rule wizard is displayed.

In the Dial rule wizard. COS). Both tables are now completed as follows. 3. The Dial rule wizard is displayed. for example: Dialed digits: HQ30 (name). 4. -. None (Warning) CO (Route). 2. Your changes are saved. COS. 14 (min. Rerouting HQ30 (Dial rule). Display + tone Siemens Internal Use Only Date: 08/19/2010 Version 2. 7. 15 (min. None (Warning) Hp8k (Route).: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Country code 4. define the dial rule for the selected route. Click OK. 17 (Route table) Route table: CO (Route). Select the route CO in the lower table in the column "Route". Click OK. you can make the following settings: ● Edited dial rule: Rerouting HQ30 ● Network provider’s method of: Main network supplier ● Dial rule format: D030400E2A ● min. Click Apply. COS). select it.: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Unknown 4.OpenScape Voice Standard Solution configuration examples ● min. The Dial rule wizard is closed. COS). 14 (min. -30xxx (Dialed digits). Route to “CO Location”: 1. Rerouting HQ30 (Dial rule). -.02 Status: Released page 29 .164 internal (Dial rule). COS. The Dial rule wizard is closed. and click on Dial rule wizard. -. In the "Dial rule" column. E.

rerouting over CO Date: 08/19/2010 Version 2.02 Status: Released page 30 .OpenScape Voice Standard Solution configuration examples Breakout OpenScape Voice to CO Siemens Internal Use Only Calls from Hp3k to OpenScape Voice for LAN outage.

select it. 5. In the "Dial rule" column." (minimum class-of-service) must be set to 14. define the dial rule for the selected route. The Dial rule wizard is displayed. The Dial rule wizard is closed. so only trunks can use this route. Route to "OpenScape Voice": 1. 2. The value "min. 2. select it. This route is used when another node is in limited mode (WAN failure) and OpenScape Voice routes the call via HiPath 3000." (minimum class-of-service) must be set to 15. 3. ● The third route. In the Dial rule wizard. Systemview -> Least Cost Routing -> select Dial plan. ● The second route "OpenScape Voice" is used for callers from HiPath 3000 to OpenScape Voice.164 Routing to all other numbers in OpenScape Voice Warning: All numbers in the OpenScape Voice network must be configured in the LCR. In the "Route table" selection field. you can make the following settings: Siemens Internal Use Only Date: 08/19/2010 Version 2. Dialed digits: 0C0-30400XXXXX. The table then shows. Route to “CO”: 1. Select the route Hp8k in the lower table in the column "Route" (directly under the route to OpenScape Voice).: 15 ● Schedule: ● Warning: none ● Type of Number (TON): Unknown 4. define the route to OpenScape Voice. callers must be routed to another OpenScape Voice gateway via the local CO. COS. define the dial rule for the selected route. forexample: Name: HQ10. Route table: 8. The value "min.OpenScape Voice Standard Solution configuration examples E. COS. 3. select route table 8 (defined in the previous step). so HiPath 3000 telephones can use this route. COS. 2. The Dial rule wizard is displayed. The window "Dial plan" is displayed. 4. In the top table. Select the route CO in the lower table in the column "Route". and click on Dial rule wizard. Proceed as follows: 1. ● The first route "CO" is only for OpenScape Voice callers via HiPath 3000 to CO. During the LAN failure. "CO location" is used if the LAN on the route to OpenScape Voice fails.02 Status: Released page 31 . In the "Dial rule" column. you can make the following settings: ● Edited dial rule: CO ● Network provider’s method of: Main network supplier ● Dial rule format: A ● min. and click on Dial rule wizard. In the Dial rule wizard. 3. Click OK. All numbers are in Openscape Voice Assistant under Global Translation and Routing -> Directory Number -> Office Codes.

15 (min. Route to “CO Location”: 1. COS. -. Click OK.: 14 ● Schedule: ● Warning: display + tone ● Type of Number (TON): Unknown 4. 14 (min. 2. CO (Dial rule). define the dial rule for the selected route. CO (Dial rule).OpenScape Voice Standard Solution configuration examples ● Edited dial rule: E. (Dial rule). -. -. 7.164 nat.: 14 ● Schedule: ● Warning: none ● Type of Number (TON): Country code 4.02 Status: Released page 32 . None (Warning) Hp8k (Route). 4. Click Apply.g. you can make the following settings: ● Edited dial rule: CO ● Network provider’s method of: Main network supplier ● Dial rule format: A ● min. None (Warning) CO (Route). Click OK. 0C0-30400xxxxx (Dialed digits). select it. Select the route CO in the lower table in the column "Route". E. COS.164 nat. Your changes are saved. 3. The Dial rule wizard is closed. 14 (min. The Dial rule wizard is closed. Display + tone (Warning) Siemens Internal Use Only Date: 08/19/2010 Version 2. ● Network provider’s method of: Corporate network ● Dial rule format: e. In the "Dial rule" column. COS). COS). In the Dial rule wizard. The Dial rule wizard is displayed. Both tables are now completed as follows. 8 (Route table) Route table: CO (Route). D49E3A ● min. for example: Dialed digits: HQ10 (name). COS). and click on Dial rule wizard.

OpenScape Voice Standard Solution configuration examples Breakout OpenScape Voice to CO Siemens Internal Use Only Calls from Hp3k to OpenScape Voice for LAN outage. rerouting over CO Date: 08/19/2010 Version 2.02 Status: Released page 33 .

In the "Transit permission" area. Your changes are saved. Click Apply. 2.2.02 Status: Released page 34 .OpenScape Voice Standard Solution configuration examples 1. 3. In the "Switch".8 System parameters -> Flags Proceed as follows: 1.1. Systemview -> System parameters -> select Station flags. this setting enables forwarding via the CO to another OpenScape Voice gateway.164 numbering scheme: Activate the checkbox. make the following settings: ● Path optimization: Deactivate the checkbox. If the LAN fails. ● E. make the following settings: ● External traffic transit: Activate the checkbox. 4. Siemens Internal Use Only Date: 08/19/2010 Version 2. ● If the network contains a HiPath 4000: – Direct Media Connection (DMC): Activate the checkbox. – HiPath 4000 networking: Early DMC: Activate the checkbox. – SPE advisory tone: Activate the checkbox. ● If TLS is available: – SPE support: Activate the checkbox. The window "Flags" is displayed.

02 Status: Released page 35 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

02 Status: Released page 36 . by hanging up.1. The "Flag status" tab applicable to a specific internal station is displayed. Siemens Internal Use Only Date: 08/19/2010 Version 2. ● If an internal station is participating in a conference as the conference leader and hangs up. Procedure To activate the flag. The "Flag status" tab applicable to the selected internal station is displayed. the following can be defined by activating the "Transit allowed via Hook-on" flag: ● An internal station can. transfer an external call to another external station. Your changes are saved. In the "Station selection" area. 3. "Transit allowed via Hook-on": Activate the checkbox. select the internal station you wish to make settings for. 4.2.OpenScape Voice Standard Solution configuration examples 1. Stationview -> select Flag status. Click Apply. This setting also applies in Proxy is in Limited Mode (in the case of WAN failure).9 Flag: Transit allowed via Hook-on Overview For certain internal stations. proceed as follows: 1. the other participants may continue the conference. 2.

1.10 Phone Payload Security Overview If TLS is used all HiPath 3000 phones shall have Payload Security set ON. 3. Procedure Proceed as follows: 1. Click Apply. Stationview -> select Activated features. 4. 2. Your changes are saved.2. In the "Station selection" area. Siemens Internal Use Only Date: 08/19/2010 Version 2. Payload Security: Select the check box “ON”.02 Status: Released page 37 .OpenScape Voice Standard Solution configuration examples 1. The "Activated features" tab applicable to the selected internal station is displayed. The "Activated features" tab applicable to a specific internal station is displayed. select the internal station you wish to make settings for.

T.4. 5. Start WBM for HG 1500 (in Manager E: Systemview -> HG 1500 / Xpress@LAN).2. Siemens Internal Use Only Date: 08/19/2010 Version 2.2.711 u-law: change the Frame Size to 20ms.2. "Codec Parameters " Section 1.2.1. T. In HiPath 3000 V8 R5 and newer T.38 is not supported and must be deactivated. "SIP Parameters" Section 1. 7.2.711 A-law: change the Frame Size to 20ms.711 has to change to 20ms on HG1500 side.02 Status: Released page 38 . 4. "Adding and Configuring PBX Nodes" Section 1.38 Fax: .2. 6.1 Codec Parameters Overview T. Right-click on Edit Codec Parameters.2. 3. Codec G.2 Settings in the HG 1500 WBM Contents This section covers the following topics: Section 1. Frame Size: HiPath Cordless IP and OpenScape Mobile Connect only support Frame-size 20msec for codec G. 8.3.2.2. The menu "Codec Parameters" is displayed. Click Apply.OpenScape Voice Standard Solution configuration examples 1. Select Explorer -> Voice Gateway -> Codec Parameters.2.Activate the checkbox for HiPath 3000 V8 R5 and newer 9.2. The "Codec Parameters" mask is displayed.38 is supported and can be deactivated.2.Deactivate the checkbox for HiPath 3000 V8 R4 and earlier .38 Fax: In HiPath 3000 V8 R4 and earlier T. Codec G. If the network contains one of this both products the Frame-size for G.38 Fax: Deactivate the checkbox. “Certificates import for TLS” 1. Proceed as follows: 1. Right-click: Select "Edit Codec Parameters".711. 2.

02 Status: Released page 39 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

follow these steps: 1.02 Status: Released page 40 .2. 3.2. 4. Start WBM for HG 1500 (in Manager E: Systemview -> HG 1500 / Xpress@LAN). Select Explorer -> Voice Gateway -> SIP Parameters. Click Apply. These are: ● SIP transport protocol • SIP via TCP: Yes • SIP via UDP: Yes • SIP via TLS: Yes ● SIP session timer • RFC 4028 Support: Yes • Session Expires (sec): 1800 • Minimal SE (sec): 90 ● Provider calls • Maximum possible Provider Calls: 0 5. Right-click: Select "Edit SIP Parameters". The "SIP Parameters" mask is displayed. Reset the SIP parameters to the default values. 2.2 SIP Parameters Keep the default SIP Parameters. Siemens Internal Use Only Date: 08/19/2010 Version 2. Verify the SIP Parameters.OpenScape Voice Standard Solution configuration examples 1.

if HiPath 3000 is registered via a proxy server.2. Siemens Internal Use Only Date: 08/19/2010 Version 2. must be configured as separate PBX nodes.02 Status: Released page 41 . To minimize all the scenarios you have to configure all Openscape Voice SIP-IP’s Networking scenarios for OpenScape Voice V4 R0 and earlier Scenario 1: OpenScape Voice system – networking to HiPath 3000 with TCP The following IP addresses must be configured as separate PBX nodes: ● IP of sipsm1 for Node 1 ● IP of sipsm1backup (sipsm1_vip2) for Node 1 ● IP of sipsm2 for Node 2 ● IP of sipsm2backup (sipsm2_vip2) for Node 2 ● IP address of the proxy server. Scenario 2: OpenScape Voice system – networking to HiPath 3000 with TLS The following IP addresses must be configured as separate PBX nodes: ● IP of sipsm3 for Node 1 ● IP of sipsm3backup (sipsm3_vip2) for Node 1 ● IP of sipsm4 for Node 4 ● IP of sipsm4backup (sipsm4_vip2) for Node 2 ● IP address of the proxy server.OpenScape Voice Standard Solution configuration examples 1. multiple networking scenarios are available because of the different variants of OpenScape Voice.2.3 Adding and Configuring PBX Nodes Networking Scenarios All IP addresses that communicate with HiPath 3000. if HiPath 3000 is registered via a proxy server. If HiPath 3000 is networked with OpenScape Voice. Networking Scenarios in OpenScape Voice V4 R1 and later The following IP addresses must be configured as separate PBX nodes: ● IP of sipsm1 for Node 1 ● IP of sipsm2 for Node 2 ● IP of sipsm3 for Node 1 ● IP of sipsm4 for Node 2 ● IP address of the proxy server. if HiPath 3000 is registered via a proxy server.

The menu "PBX Node / IP Addresses" is displayed. see section "Networking Scenarios". 2. – Alive Monitoring: Deactivate the checkbox – Security Level of Node Encryption in TCP networking: traditional in TLS networking: secure 3. Siemens Internal Use Only Date: 08/19/2010 Version 2. Start WBM for HG 1500 (in Manager E: Systemview -> HG 1500 / Xpress@LAN). 3. Configuring PBX nodes: 1. Start WBM for HG 1500 (in Manager E: Systemview -> HG 1500 / Xpress@LAN). 2. Right-click: Select "Edit IP Addresses".OpenScape Voice Standard Solution configuration examples 1. 3. 2. Select Explorer -> Voice Gateway -> PBX -> Nodes. Right-click: Select "Add PBX Node". Click Apply. 2. The menu "Add PBX Node" is displayed. Enter the node number. Station numbers do not have to be configured in WBM under Explorers -> Voice Gateway -> PBX -> Routing for OpenScape Voice. Adding PBX nodes: 1.02 Status: Released page 42 . Click Apply. Adding PBX nodes Proceed as follows: 1. SIP – HXG Gatekeeper Board 1 IP Address: Enter the IP address of the SIPIP (SIPSM) from OpenScape Voice. 2. 3. Select the menu items: Explorer -> Voice Gateway -> PBX -> Nodes -> <node number of the PBX node you wish to add>. Make the following settings: – LAN trunking protocol: SIP-Q – LAN trunking type: Ext. Configuring PBX nodes Proceed as follows: 1.

02 Status: Released page 43 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

Start WBM for HG 1500 (in Manager E: Systemview -> HG 1500 / Xpress@LAN). 4.pem.pem client. Copy the file root.2.pem: 1.pem. File with certificate (PEM or binary): Click “Browse” and select the rootcert. 2 certificates needs to import: rootcert. Press button “View Fingerprint of Certificate”.OpenScape Voice Standard Solution configuration examples 1.pem from OpenScape Voice /usr/local/ssl/certs and rename it to rootcert. Proceed as follows to import the rootcert. 3.02 Status: Released page 44 . Select Explorer -> Security -> Signaling and Payload Encryption (SPE) -> SPE CA Certificate(s).pem is located in OpenScape Voice in the folder /usr/local/ssl/private rootcert.pem and client. The fingerprint is displayed Siemens Internal Use Only Date: 08/19/2010 Version 2.2.pem must be created by using the root.4 Certificates import for TLS Overview For Signaling and Payload Encryption via TLS a certificate import to HG1500 is needed. 2.pem file 5. Right-click: Select "Import trusted CA Certificate (PEM or Binary)". Use an editor to delete RSA-private-key (text from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY).

Press button “Import Certificate from File” to import the certificate. Right-click: Select "Import SPE certificate plus private key (PEM or PKCS#12)". 3. Press button “View Fingerprint of Certificate”. Proceed as follows to import the client.pem file 5.OpenScape Voice Standard Solution configuration examples 6. 4. File with certificate and private Key (PEM or PKCS#12format): Click “Browse” and select the client.02 Status: Released page 45 . Start WBM for HG 1500 (in Manager E: Systemview -> HG 1500 / Xpress@LAN). Select Explorer -> Security -> Signaling and Payload Encryption (SPE) -> SPE Certificate. 2. Siemens Internal Use Only Date: 08/19/2010 Version 2. The fingerprint is displayed.pem: 1.

OpenScape Voice Standard Solution configuration examples 6. Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 46 . Press button “Import Certificate from File” to import the certificate. Reboot of board will happen automatically.

OpenScape Voice Standard Solution configuration examples

2.1 Configuration OpenScape Voice
Overview
HiPath 3000 as a gateway (endpoint) and the OpenScape Voice subscribers shall be
located in different Private Numbering Plans but in the same business group.
That means every location gets an own Private Numbering Plan for subscriber and an
own Private Numbering Plan for gateways/endpoints (HiPath 3000).
Contents
This section covers the following topics:
Section 1.3.1, "Settings in the Common Management Portal"
Section 1.3.2, "Settings in StartCli"
2.1.1 Settings in Common Management Portal
Procedure
1. Start the Common Management Portal.
2. Follow the remaining steps in sequence.
Contents
This section covers the following topics:
Section 1.3.1.1, “Administration of an new Gateway Private Numbering Plan”
Section 1.3.1.2, "Creating and Configuring an Endpoint Profile for a HiPath 3000
Endpoint"
Section 1.3.1.3, "Creating and configuring an endpoint for HiPath 3000"
Section 1.3.1.4, “Creating "Digest Authentication" access for HiPath 3000”
Section 1.3.1.5, "Configuring a Gateway Numbering Plan for Incoming Calls"
Section 1.3.1.6, "Configuring Outgoing Calls"
Section 1.3.1.7, “Display Number Modification for OpenScape Voice V5.0”

Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 47

OpenScape Voice Standard Solution configuration examples

2.1.1.1 Administration of an new Gateway Private Numbering Plan
Proceed as follows:
1. OpenScape Voice -> select Business Group.
2. On the left side of the window, select the following:
• Available Switches: Select the OpenScape Voice
• Available Business Groups: Select the business group for which the endpoint
profile is to be created, e.g. bg_sol.
3. On the left side of the window, select Private Numbering Plans. On the right side of
the window, a list of all Private Numbering Plans is displayed.
4. To create a new Private Numbering Plan, click the Add button. The configuration
window is displayed.
5. Name: Enter a name for the Private Numbering Plan, e.g. NP_br13_gw.
6. Click Save.

2.1.1.2 Administration of an Endpoint Profile for a HiPath 3000 Endpoint
Proceed as follows:
1. OpenScape Voice -> select Business Group.
2. On the left side of the window, select the following:
• Available Switches: Select the OpenScape Voice
• Available Business Groups: Select the business group for which the endpoint
profile is to be created, e.g. bg_sol.
3. On the left side of the window, select Profiles -> Endpoint Profiles. On the right side
of the window, a list of endpoint profiles is displayed.
4. To create a new endpoint profile, click the Add button. The configuration window for
this endpoint profile is displayed.
5. Make the following settings in the General tab
Endpoint Profiles
• Name: Enter a name for the endpoint profile, e.g. EP_hg1500.br13.
• Numbering Plan: Select the numbering plan which was create before, e.g.
NP_br13_gw.
Management Information
• Class of Service: No setting necessary.
• Routing Area: No setting necessary.
• Calling Location: No setting necessary.
Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 48

OpenScape Voice Standard Solution configuration examples
• SIP Privacy Support: Basic
• Failed Calls Intercept: Disabled
• Language: e.g. German
6. Open the Services tab. Make the following settings in this tab:
• Voice mail: Yes
• Call Transfer: No
• Call Forward Invalid Destination: Yes and enter station number.
• Toll and Call Restrictions: No
8. Click Save. Your changes are saved.

Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 49

OpenScape Voice Standard Solution configuration examples
OpenScape Voice V4R1

OpenScape Voice V5R0

Siemens Internal Use Only

Date: 08/19/2010

Version 2.02

Status: Released

page 50

e.g. e.3 Creating and configuring an endpoint for HiPath 3000 Proceed as follows: 1. EP_hg1500. SIP-Q Signaling: Activate the checkbox. click the Add button. 8. • Available Branch Offices: Select the branch office for which the endpoint is supposed to be created.br13. 9. OpenScape Voice -> select Business Group. hg1500. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created.113. Make the following settings in this tab: 1.br13. Transport protocol: – Select TCP for traditional network. To create a new endpoint.g. Open the Attributes tab. 6. Open the Aliases tab. Click the Add button and enter the HiPath 3000 registration number. for: Select HiPath 4000/3000. The endpoint is created and configured.g.g. – Select MTLS for secure network. Click the Add button and enter the HG 1500 IP address. 3. On the left side of the window. Siemens Internal Use Only Date: 08/19/2010 Version 2.22. Make the following settings in the General tab: • Name: Enter a name for the endpoint.1. • Profile: Select the endpoint profile selected in the previous step. 7. Click Save. 4.02 Status: Released page 51 . 13310. 10.g. bg_sol. The configuration window for this endpoint is displayed. On the left side of the window. e. 2. e.191. Make the following setting in this tab: • Accounting Type: PSTN Gateway 10.1. Your changes are saved. BR13. e. e. Make the following setting in this tab: • Activate the "Rerouting Forwarded Calls" checkbox.g. Open the SIP tab.OpenScape Voice Standard Solution configuration examples 2. 2. select Members -> Endpoints. Make the following settings in this tab: SIP Configuration 1. 5. 3. Open the Aliases tab. 2.

02 Status: Released page 52 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

02 Status: Released page 53 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

Make the following settings: – Trusted entity: Deactivate the checkbox. 10.g.191. e. Click Save. – Confirm Local Password: Enter the password once more. Click OK and the Sip Configuration window is closed.4 Creating "Digest Authentication" access for HiPath 3000 Proceed as follows: 1. e.1.113. – Local Password: Enter the password.g. 6. Open the Realms tab: 4. OpenScape Voice -> select Administration. – Local User Name: Enter the user name. select Signaling Management -> Digest Authentication. To create "Digest Authentication" access. e.22. 2. On the left side of the window. sol.1.g. – Local Realm: Enter the realm. hipath3000br13.OpenScape Voice Standard Solution configuration examples 2.02 Status: Released page 54 . 3.g. e. Siemens Internal Use Only Date: 08/19/2010 Version 2. e. click Add. – Remote Realm: Enter the realm. – Signaling IP: Enter the HG 1500 IP address. – All Ports: Optional field not activated. – Remote Password: Enter the password. 5. – Confirm Remote Password: Enter the password once more.g. – Port Range: Optional field not activated. sol. 7. – Remote User Name: Enter the user name. Your changes are saved and the Digest Authentication window is closed. hipath3000br13.

02 Status: Released page 55 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

1.1. 5.g. To create new destination code click Add. Make the following settings: • Destination Code: e.g. Proceed as follows: 1. 3. Your changes are saved. On the left side of the window. e. Siemens Internal Use Only Date: 08/19/2010 Version 2.5 Configuring a Gateway Numbering Plan for Incoming Calls This is only a short description how to route an incoming call.02 Status: Released page 56 . select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created. Click Save. • Available Private Numbering Plan: Select the private numbering plan in which the endpoint was created. A detailed description is available in the routing concept described in the reference architecture. select Translation -> Destination Codes. 49695113 • Nature of Address: International • Destination Type: Home • Office Code: e. bg_sol. +49 (69) 5113 6.OpenScape Voice Standard Solution configuration examples 2.g. 4. This is only a simplified example. OpenScape Voice -> select Business Group. On the left side of the window. 2.

02 Status: Released page 57 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

• Available Private Numbering Plan: Select the private numbering plan in which the subscribers are in. The configuration window for this prefix access code is displayed. This is only a simplified example. Make the following settings: • Prefix Access Codes: e. select Translation -> Prefix Access Codes. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created. Siemens Internal Use Only Date: 08/19/2010 Version 2. 3. 5. Subscriber Numbering Plan . A detailed description is available in the routing concept described in the reference architecture. 2. OpenScape Voice -> select Business Group. e.OpenScape Voice Standard Solution configuration examples 2. On the left side of the window.1. To create new Prefix Access Codes click Add. bg_sol.g. Click Save. 4. On the left side of the window.g.6 Configuring Outgoing Calls This is only a short description how to route an outgoing call.1.Prefix Access Codes Proceed as follows: 1. Your changes are saved.02 Status: Released page 58 . 0 • Minimum Length: 1 • Maximum Length: 30 • Digits Position: 1 • Digits to insert: 4969 • Prefix Type: On-net Access • Nature of Address: International • Destination Type: BG Common Destination 6.

02 Status: Released page 59 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

On the left side of the window. • Fallback to Local Numbering Plan: leave the checkbox unchecked. 3. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created.hg1500. Open the new Destination to edit. On the left side of the window.g. • Available Private Numbering Plan: Select the common numbering plan. Add an additional endpoint to have a fallback when HiPath 3000 is not in service. 9. 15.br13 • Nature of Address: Undefined 11. Click Save. Open the Routes tab. 10. 13. 12. click Add. bg_sol.g. Follow the instruction above. 5.g. 100 • Type: SIP Endpoint • SIP Endpoint: e. Siemens Internal Use Only Date: 08/19/2010 Version 2. 4. hg1500. To add an endpoint to this destination. e. select Destinations and Routes -> Destinations. Click Save.br13 6. OpenScape Voice -> select Business Group. 2. To create a new Destination click Add.g.OpenScape Voice Standard Solution configuration examples Common Numbering Plan – Destination 1. Open the Route Lists tab. 14. Make the following settings: • Prioritized: Activate the checkbox. Your changes are saved. Click Save. Make the following setting in the General tab: • Name: e. Your changes are saved. 7. Make the following settings: • ID: e. c. 8.02 Status: Released page 60 .

OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 61 .

4.Prefix Access Codes 1. bg_sol. Siemens Internal Use Only Date: 08/19/2010 Version 2. select Translation -> Prefix Access Codes. Click Save. 5. 4 • Minimum Length: 1 • Maximum Length: 30 • Digits Position: 0 • Digits to insert: leave empty • Prefix Type: On-net Access • Nature of Address: International • Destination Type: None 6. Make the following settings: • Prefix Access Codes: e. Your changes are saved. 2. To create a new Prefix Access Codes click Add. e. • Available Private Numbering Plan: Select the common numbering plan. 3.g. The configuration window for this prefix access code is displayed. On the left side of the window. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created.g. OpenScape Voice -> select Business Group.OpenScape Voice Standard Solution configuration examples Common Numbering Plan . On the left side of the window.02 Status: Released page 62 .

02 Status: Released page 63 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

OpenScape Voice -> select Business Group.hg1500. Click Save. On the left side of the window.br13 6.OpenScape Voice Standard Solution configuration examples Common Numbering Plan . To create a new Destination Code click Add. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created.g. 3. 4969 • Nature Of Address: International • Destination Type: Destination • Destination Name: select the destination which was created before e. 4.Destination Codes 1.g. 2. 5.02 Status: Released page 64 . • Available Private Numbering Plan: Select the common numbering plan.g. c. select Translation -> Destination Codes. Make the following settings: • Destination Code: e. e. bg_sol. Your changes are saved. On the left side of the window. Siemens Internal Use Only Date: 08/19/2010 Version 2.

OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 65 .

5.0 Definitions Proceed as follows: 1.g. Digits: 8 • Max.02 Status: Released page 66 .1. select Display Number Modification -> Definitions. bg_sol. To enter a new Number definition click Add.1. On the left side of the window. Click Save. Your changes are saved. 4. On the left side of the window.g. bg_sol • Numbering Plan: ANY • Numbering plan indication: Public • Country/L2 Code: 49 • Area/L1 Code: 69 • Local Office/L0 Code: 5113 • Number of digits to skip: enter the number length of the Local Office Code e.g. 3. 4 • Min. Digits: 30 6.7 Display Number Modification for OpenScape Voice V5. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created. Make the following settings: • Business Group: Select the used business group e.OpenScape Voice Standard Solution configuration examples 2. OpenScape Voice -> select Business Group. e. Siemens Internal Use Only Date: 08/19/2010 Version 2. 2.

02 Status: Released page 67 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

Siemens Internal Use Only Date: 08/19/2010 Version 2. On the left side of the window. 2. Make the following settings: Public Network Access Code Prefix International 0 00 National 0 0 Subscriber 0 6. bg_sol. Your changes are saved.g. OpenScape Voice -> select Business Group. 4. 5. select Display Number Modification -> Prefixes. On the left side of the window.02 Status: Released page 68 . To enter a global prefix definition click Add. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created. e. 3.OpenScape Voice Standard Solution configuration examples Prefixes Proceed as follows: 1. Click Save.

Make the following settings in Terminating Context Setting: • Business Group: Select the used business group e. On the left side of the window. On the left side of the window. OpenScape Voice -> select Business Group.OpenScape Voice Standard Solution configuration examples Modifications – Gateway Numbering Plan Proceed as follows: 1. 4. click Add. bg_sol • Numbering Plan: Select the numbering plan of the endpoint e. NP_br13GW • Endpoint: NONE 7. Click Save.g. Make the following settings in Origination Context Setting: • Business Group: ANY • Numbering Plan: ANY 6. 3.g. Siemens Internal Use Only Date: 08/19/2010 Version 2. Your changes are saved. select Display Number Modification -> Modifications. To enter a new Modification for the Gateway Numbering plan.g. 5. 2.02 Status: Released page 69 . Make the following settings in Modification Rule: • Input Type Of Number: ANY • Priority: 1 • Output Type Of Number: International • Number Source: Input Number • Presentation Restricted: unselected • Prefix Required: unselected • Optimize Type Of Number: None 8. bg_sol. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created. e.

02 Status: Released page 70 .OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.

5. Make the following settings in Modification Rule: • Input Type Of Number: ANY • Priority: 4 • Output Type Of Number: ANY • Number Source: Input Number • Presentation Restricted: unselected • Prefix Required: Activate the checkbox. On the left side of the window. Click Save. Your changes are saved. bg_sol. 4. NP_br13eg • Endpoint: NONE 7. select the following: • Available Switches: Select the OpenScape Voice • Available Business Groups: Select the business group for which the endpoint profile is to be created. • Optimize Type Of Number: Extension 8. Siemens Internal Use Only Date: 08/19/2010 Version 2. 3. To enter a new Modification for the Subscriber Numbering plan.OpenScape Voice Standard Solution configuration examples Modifications – Subscriber Numbering Plan Proceed as follows: 1. e.g.g. 2. click Add. OpenScape Voice -> select Business Group. Make the following settings in Terminating Context Setting: • Business Group: Select the used business group e.02 Status: Released page 71 . On the left side of the window. Make the following settings in Origination Context Setting: • Business Group: ANY • Numbering Plan: ANY 6. bg_sol • Numbering Plan: Select the numbering plan of the subscriber e. select Display Number Modification -> Modifications.g.

OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 72 .

In Openscape Voice V5 and newer: The Parameter above is not more available.1.2 Settings in StartCli In Openscape Voice V4R1 and earlier: the follow CLI parameter must be set Srx/Main/OutGoingCallingPartyNumberType to Value=0 This needs to send the Calling Party Number with Typ of Number International. Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 73 .OpenScape Voice Standard Solution configuration examples 2. Calling Party Number definitions will be made in the Display Number Modification.

which is available in SEN E-Docu. 10. e.g.255. Contents This section covers the following topics: Section 1.2. Make the following settings: • Interface 1 – IP address.2 Configuration OpenBranch Only some HiPath 3000 specific information is covert in this guidline. "VoIP" 2. e.113. 10.4.22.4.2. Subnet mask: Enter the IP address and subnet mask of the OpenScape Branch proxy server. Siemens Internal Use Only Date: 08/19/2010 Version 2.g.1. "Network Services" Section 1.0.254. 2.OpenScape Voice Standard Solution configuration examples 2.02 Status: Released page 74 .1 Network Services Proceed as follows: 1.22. OpenScape Branch -> select Network Services. • Routing – Default gateway IP address: Enter the IP address of the default gateway.255.113.10 and 255. For more detailed information about OpenScape Branch refer to official guide “Administrator Documentation”.

– Enable DNS server: Activate the checkbox. 10. In the "Type" column. enter the IP address of the customer DNS server. In the "IP Master/Forward" column. Click Add. – DNS configuration: Click this button for additional configuartion • DNS configuration Zone configuration To do this proceed as follows: 1.sol.de.g. Forward IP Siemens Internal Use Only Date: 08/19/2010 Version 2.g. enter the name of the DNS zone. – Synchronize now: Click this button. e. • DNS Server – OpenScape Branch domain name: Enter the "DNS-SRV" name of the external office (Domain Name System SERVICE).7. 2. e. 5.de. In the "Zone name" column.255.02 Status: Released page 75 . to add a row to the table.21. sol. – NTP server: Enter the NTP server IP address. select the slave type. e.g. GMT+1:00 – Synchronize with NTP server: activate this field. 4.OpenScape Voice Standard Solution configuration examples • NTP – Timezone: e. br13. enter the file name where the DNS zone data should be saved.g. 3. In the "File name" column.

Your changes are saved.22. The IP address is added to the "Forward IP Address list". Click Save. Siemens Internal Use Only Date: 08/19/2010 Version 2. 2. and click Add.100.g.02 Status: Released page 76 . 10. e.OpenScape Voice Standard Solution configuration examples In the "Forward IP Address list". The customer DNS server is required for queries outside of the transmitted zone.100. the IP address of the customer DNS server must be entered. To do this proceed as follows: 1. Enter the customer DNS server IP address in the input field.

e.22.100.100. 10.02 Status: Released page 77 . and click Add. Siemens Internal Use Only Date: 08/19/2010 Version 2. The IP address is added to the "DNS server list.g.OpenScape Voice Standard Solution configuration examples • DNS Client – Enter the customer DNS server IP address in the input field “DNS server list”.

10.254 Siemens Internal Use Only Date: 08/19/2010 Version 2. e.113. make the following settings: • Subnet: e.0 • IP address from: e.113. Enter the OpenScape Branch proxy server IP address in the input field.101 • DLS Port: 18443 • Routers: e.22.255 • Domain name: "DNS-SRV" name of the external office (Domain Name System SERVICE) e. • DHCP configuration Most important setting In the "DNS server list" of the "DHCP Server" window. 255.0 • Netmask: e.100.sol.255. Enter the customer DNS server IP address in the input field.22.g.g.22. 10. 10. To do this proceed as follows: 1.g.g.129 • Static IP address list configuration: Do not click.g.g. e.g. Additional settings In the "DHCP Server" window.Enable DNS server: Activate the checkbox.113. lease time: 604800 • Interface: Interface 1 • Update style: None • Broadcast address: e.100.22.22. and click Add.113.g.22. The IP address is added to the "DNS server list.g. • Lease time: 86400 • Max. 10.g. br13. 2. The IP address is added to the "DNS server list.255. 10.100.02 Status: Released page 78 .113.113. – DHCP configuration: Click the button to configure the DHCP Server.22. 10. 10. 10.OpenScape Voice Standard Solution configuration examples • DHCP – Enable DHCP server: Activate the checkbox. and click Add.de • DLS server: IP of the DLS Server e.10. the OpenScape Branch proxy server and customer DNS server IP addresses must be specified.22.100 to: e.

OpenScape Voice Standard Solution configuration examples Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 79 .

2 VOIP Proceed as follows: 1.02 Status: Released page 80 .2. Siemens Internal Use Only Date: 08/19/2010 Version 2.OpenScape Voice Standard Solution configuration examples 2. OpenScape Branch -> select VOIP. – For more information see the official Openscape Branch Administrator documentation chapter “How to Configure the Communication System “. 2. Make the following settings: • SIP configuration SIP connectivity to OpenScape Voice will not be described here.

Complete the table as follows: Explanations: First row: The phone number must have a plus "+" at the beginning so HiPath 3000 can recognize this as an international phone number. Third to fifth rows: These settings enable phones to dial a short internal number and not international dialing. as telephones are not registered with a plus "+". SIP Manipulation The settings in this table are required for emergency handling.OpenScape Voice Standard Solution configuration examples • SIP Manipulation: Click the button to configure SIP headers. Siemens Internal Use Only Date: 08/19/2010 Version 2. Second row: The plus "+" in the Request-URI (R-URI) must be deleted.02 Status: Released page 81 .

Siemens Internal Use Only Date: 08/19/2010 Version 2.02 Status: Released page 82 . – Use the screenshot below as an example. For more information see the official Openscape Branch Administrator documentation chapter “Configuration of Gateways“. – Gateways/Trunks configuration: Click this button for adding a gateway – HG 1500 should be added as a gateway.OpenScape Voice Standard Solution configuration examples • Gateway/Trunks – Enable Gateways/Trunks: Activate the checkbox.

Siemens Internal Use Only Date: 08/19/2010 Version 2. The DSCP priority must be entered as decimal value. – DSCP for SIP: enter 46 for L3 QoS priority Diffserv EF. – QoS configuration: Click this button to setup the Layer 3 priority.02 Status: Released page 83 .OpenScape Voice Standard Solution configuration examples • QoS – Enable QoS: Activate the checkbox. – DSCP for SIP: enter 26 for L3 QoS priority Diffserv AF31.

: Siemens Internal Use Only Date: 08/19/2010 Version 2.e.02 Status: Released page 84 . i.OpenScape Voice Standard Solution configuration examples • Codec – Set the codec priority as in HG 1500.