Technical data

ManualsBrandsSiemens ManualsComputer equipmentOC130S

EN2409EN00EN_0001

Siemens

Common Gateway

1 Common Gateway (CG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 Hardware and Loadware NCUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.4 Hardware and Loadware HG3500 V4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.5 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.6 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.7 Impact On Existing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.8 Number of B Channels Dependent On Enabled Features . . . . . . . . . . . . . . . . . . . . . . . . 9

1.8.1 STMI2 (Q2316-X10) / NCUI2+ (Q2305-X40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.8.2 STMI4 (Q2324-X510) / NCUI4 (Q2324-X10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Architecture and System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3 Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 Basic Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5 Bandwidth Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5.1 Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5.2 Sampling Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5.3 IP Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.5.4 Required Bandwidth per Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.5.5 Voice Activity Detection (VAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.5.6 DMC Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.6 Traffic Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3 Capacities and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Summary of content (54 pages)

PAGE 1
Siemens Common Gateway 1 Common Gateway (CG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2 Hardware and Loadware NCUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.3 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 2
Siemens 4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Gateway Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Direct Media Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 3
Siemens 7.2 7.3 7.4 7.5 7.6 7.7 7.8 General Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Access control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Gateway Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Image/File Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
Overview 1 Siemens Common Gateway (CG) The Common Gateway combines the different IP Gateway functions (HG3530, HG3550, HG3540 and HG3570 in one SW core. Each sub-function (e.g. HFA or SIP) can be configured on one single HG3500 board, The CGW SW can run on existing STMIV2 cards or on the „new“ STMIV4 card. 1.
PAGE 6
Overview Siemens > 1.2 The NCUI2 can be used for the migration! Hardware and Loadware NCUI New loadware (PZKNCI40) is available for the boards NCUI2+ and NCUI4 in HiPath 4000 V4 and later versions. Board type Part number B channels NCUI2+ Q2305-X35 60 B channels (2 DSPs) NCUI2+ Q2305-X40 120 B channels (4 DSPs) NCUI4 Q2324-X 60 B channels (2 DSPs) NCUI4 Q2324-X10 120 B channels (5 DSPs) Table 1-1 Supported NCUI boards Board type Loadware NCUI2+ PZKNCI40 NCUI4 PZKNCI40 Table 1-2 1.
PAGE 7
Overview 1.4 Siemens Hardware and Loadware HG3500 V4 Until HiPath 4000 V3.0 was released, each feature had separate loadware. This loadware determined the function of the gateway (HG 3530, HG 3540/3550, HG 3570). In HiPath 4000 V4 and later, the various types of loadware are consolidated into a common loadware for STMI2 and STMI4. With this loadware all features are available on the board.
PAGE 8
Overview Siemens 1.6 Restrictions CQR Viewer The CQR Viewer application is only supported for HFA (FUNCTION=HG3530) and IPDA (FUNCTION=HG3570), not for trunking (FUNCTION=HG3550). 1.7 8 Impact On Existing Functions ● Impact on DLS: None. ● Impact on terminals/clients: None. All HiPath 4000 V3.0 IP telephones are supported. OpenStage telephones are also supported. ● Impact on ACL: None. ● Impact on CDR: None.
PAGE 9
Overview Siemens 1.8 Number of B Channels Dependent On Enabled Features The following two tables provide an overview of the number of available B channels that are dependent on enabled features. 1.8.
PAGE 11
Architecture and System Requirements 2 Architecture and System Requirements 2.1 Prerequisites Siemens Prior to installing IP line gateways at a customer site a network assessment is required that will determine whether the customer’s IP network is capable of supporting IP phones. This network assessment will analyze the IP network and determine parameters like jitter, packet loss, available bandwidth, supported QOS mechanisms and assess overall VoIP readiness. 2.
PAGE 12
Architecture and System Requirements Siemens Frequently, only explicitly familiar TCP/IP or UDP/IP port numbers are supported in the customer LAN for security reasons. All others are then blocked in such cases. Precisely which port numbers must be supported for the HiPath HG 3500 component in the network is described in Section 16.1, “Gateway Port Allocation”. 2.
PAGE 13
Architecture and System Requirements > Siemens Note The TOS byte can be read in a number of different ways: ● Two 3-bit values for precedence and priority ● One 6-bit value as a combination of both 3-bit values (DiffServ CP) ● The entire TOS byte including two fill bits For IPDA, the entire TOS byte is specified. The two least significant bits are always set to zero. See Section 8.1, “Key Words”. On the HG 3500 these parameters are set by using standard switch administration. 2.
PAGE 14
Architecture and System Requirements Siemens For telephony applications, voice is sampled every 125 μs at 8bits. It would not make sense to package each individual 8 bit sample into an IP packet. Instead, for G.711 encoding at least 240 8 bit samples are combined into an IP packet. It takes 30 ms to acquire 240 voice samples. The Sampling Time is defined as the time it takes to sample a specified number of voice samples that are sent out in one IP packet.
PAGE 15
Architecture and System Requirements Encoding G.729A G.723 (6.4) Table 2-1 Siemens Sampling Time IP Overhead BW per Connection 60ms 15% 73.3 Kbps 20ms 350% 36.0 Kbps 40ms 175% 22.0 Kbps 60ms 117% 17.3 Kbps 30ms 291% 25.1 Kbps 60ms 146% 15.7 Kbps 90ms 97.2% 12.6 Kbps IP Overhead and BW per Connection Note that the bandwidth calculation is based on 70 bytes of overhead: RTP (12 bytes), UDP (8 bytes), IP (20 bytes), 802.1Q VLAN Tagging (4 Bytes), MAC (incl.
PAGE 16
Architecture and System Requirements Siemens 2.5.6 DMC Considerations Whenever a DMC connection is established, a “Master Connection” is setup as well. The master connection is following the same path as the signaling through all the gateways between to IP clients. The master connection ensures that the necessary resources are always available whenever a feature is invoked that results in a multi party call (e.g. conference).
PAGE 17
Architecture and System Requirements 2.6 Siemens Traffic Considerations From a trafficking point of view, HG 3500 IP line gateways can be treated like a trunk with either 60 or 120 connections. The number of connections required depends on the number of IP phones configured per HG 3500 and the traffic (C.C.S.) values of these phones. Using a standard ErlangB calculation allows determining the number of trunks/connections that are required on each gateway for a specific configuration.
PAGE 19
Capacities and Limitations 3 Siemens Capacities and Limitations ● The HiPath HG 3500 line gateway has the capacity to convert 60/120 connections into Fast Ethernet packets and provide TDM to IP conversion for 60/120 concurrent calls. ● The HG 3500 line gateway is only supported in the HiPath 4000 V4 communication platforms. ● The HG 3500 line gateway is supported in all IP distributed Access Points including AP 3500/3505 APs that were part of an upgraded v1.0 system.
PAGE 21
Features 4 Siemens Features The HiPath HG 3500 line gateway provides a unique set of features described in the following sections. 4.1 Gateway Functionality Each HG 3500 gateway provides TDM to IP conversion and vice versa for up to 60/120 connections simultaneously. Two versions of the card are available (60 or 120 connections version) depending on the traffic needs of the specific application. Up to 240 users per gateway are supported.
PAGE 22
Features Siemens > 4.4 Note that invoking any feature that results in a multi party call (more than 2 parties) will route the payload through all gateways in the payload path (same as in HiPath 4000 V1.0). This may result in undesirable delays in certain scenarios (see Section 2.5.6, “DMC Considerations” for more details). Mobility HG 3500 gateways support mobility.
PAGE 23
Features Siemens ● Starting the optiClient 130 on a PC from any location automatically logs off the office IP phone (associated by the same phone number) and provides the same feature set and class or service to the end-user as the office IP phone. ● After the remote user returns to the office, the IP phone will still be in the logged off state and the user is prompted to start the phone.
PAGE 24
Features Siemens noise and “silence“ are transmitted. Voice activity detection makes use of this knowledge, interrupts the data transmission and drastically reduces the data rate as soon as silence is detected. As soon as voice activity is detected again, transmission for that direction is immediately re-established (with full bandwidth). The resulting bandwidth reduction is in the range of 50% to 75% which is very significant.
PAGE 25
Features Siemens ● Lost packets on VoIP payload connections between IP clients. ● Jitter for VoIP payload connections between IP clients. 4.12.2 Signaling Connection Monitoring The HiPath 4000 permanently monitors the IP connection between HiPath 4000 and each IP phone with a “Supervisory Connection“. In the case of problems the line will be deactivated. 4.12.
PAGE 26
Features Siemens HG 3500 Front View The HG 3500 provides three interfaces that are accessible to the user: 1. One RS-232/V.24 interface (serial port) classified as Data Terminal Equipment (DTE) on 9 pin Submin-D male connector used for test purposes only. 2. One 10/100 Base-T Ethernet interface for future use that provides a standard RJ45 type connector. 3. One 10/100 Base-T Fast Ethernet interface. This is the interface that provides the payload connection to the remote nodes.
PAGE 27
Features 4.14.2 Siemens Access to SNMP The acces to SNMP is restricted via read and write Community strings. These Community strings can be configured with the WBM > Maintenance > SNMP > Communities. 4.14.3 Security in CorNetTC Registration The log-on between the IP phones and HiPath HG 3500 is secured via SHA1. The payload and signaling connections are not encrypted. 4.14.4 H.235 Security When this feature gets activated all messages between the HG 3500 and the IP phones are authenticated.
PAGE 28
Features Siemens 1. Adding one or multiple standby gateways to the system protects against individual gateway failures 2. Providing full redundancy for IP clients via secondary gateways will protect against higher level failures, like entire Access Point or host failures. 4.15.2.2 Standby Gateways One or multiple standby HG 3500 IP line gateways can be defined in the system that will take over in case any of the installed line gateways fails.
PAGE 29
Features Siemens For more details please refor to Chapter 14, “Standby Board HG 3500”. 4.15.2.3 Secondary Gateways In order to protect against higher level failures (e.g. Access Point, host failures) secondary gateways can be added to the system. A secondary gateway is an additional, fully configured gateway for an IP client located anywhere within a HiPath 4000 system. Note that each IP user that is backed up via a secondary gateway will have 2 extensions, e.g.
PAGE 30
Siemens > 30 Features Important Secondary gateways and IP clients have to reside within the same system! Secondary gateways can automatically backup any IP user as long as the secondary gateway is operational and IP connectivity between the IP client and the gateway is available.
PAGE 31
Configuration Common Gateway Siemens 5 General Information on How to Configure a HG 3500 V4 Common Gateway 5.1 General Information Multiple Feature Support (MFS) - Single Feature Configuration The HG 3500 V4 common gateway can be configured as a multiple feature support (MFS) or single feature configuration. An example of a multiple feature support configuration can be found in Chapter 8, “Multiple Feature Support Configuration at the Common Gateway (Example)”.
PAGE 32
Configuration Common Gateway Siemens ● Functions are consolidated on a single board using the AMO BCSU. ● The DB line range of a board must be consecutive. ● The lines configured for a board cannot be subsequently modified. The entire board must be reconfigured if additional lines are required on a board. ● The parameter FCTID in the AMO BCSU must always be set to 1 in HiPath 4000 V4 as this parameter is used in HiPath 4000 V2.0 and V3.0. In HiPath 4000 V3.
PAGE 33
Configuration Common Gateway ● For HFA and SIP, the number of circuits (LINECNT) and the number of B channels (BCHLCNT) must be specified. > ● If reserved HFA or SIP circuits are to be configured, the B channels designated for this purpose must also be specified here. This is not necessary for reserved trunk circuits as the assignment is performed based on the number of units (UNITS). For WAML, only the number of units (UNITS) must be specified. > ● Siemens Only one circuit is possible for WAML.
PAGE 34
Configuration Common Gateway Siemens You can check the status with DISPLAY-BFDAT:FCTBLK=; If the configuration of the functional block is complete STATUS=OK is displayed. If a configuration error is detected when the block configuration is complete, the functional block must be deleted (DELETE-BFDAT:FCTBLK=,ANSW=YES;) and reconfigured. If the configuration of a functional block is not complete STATUS=CONT is displayed. The functional block may not be assigned to a board.
PAGE 35
Multiple-Feature Configuration 6 Multiple Feature Support Configuration at the Common Gateway (Example) 6.
PAGE 36
Multiple-Feature Configuration Siemens Functional block 3 Functional block 3: IP trunking, HFA subscriber function (HG3530) and reserve HFA subscriber (HG3530R) > The reserved HFA B channels must be specified during configuration of the HG3530 function as subscriber B channels are not accepted during reservation.
PAGE 37
Multiple-Feature Configuration Siemens AMO CGWB not necessary because the IP address is already configured with the AMO BCSU. The additional configuration of the IPDA (UCSU, APRT etc) must be done as before in HiPath 4000 V30. 6.4 Configuration of a HFA phone Configuring HFA subscriber on the STMI2 board in 1-1-31 (BFDAT profile 2): ADD-CGWB:LTU=1,SLOT=31,SMODE=NORMAL,IPADDR=198.16.16.54,NETMASK=255.255.255.
PAGE 38
Multiple-Feature Configuration Siemens CHANGE-BFDAT:CONFIG=CONT,FCTBLK=4,FUNCTION=HG3550,LINECNT=1,UNITS=1; >>>>> WAML with one unit (=10 B channels) CHANGE-BFDAT:CONFIG=CONT,FCTBLK=4,FUNCTION=WAML; >>>>> HFA with 70 circuits and 70 B channels CHANGE-BFDAT:CONFIG=CONT,FCTBLK=4,FUNCTION=HG3530,LINECNT=70,BCHLCNT=70; >>>>> Do not end configuration of block CHANGE-BFDAT:CONFIG=OK,FCTBLK=4,ANSW=NO; Assignment for functional block 4 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=43,PARTNO=Q2316-X10,FCTID=1,FCTBLK=4,IPADD
PAGE 39
Command Line Interface CLI at HG 3500 7 Command Line Interface CLI at HG 3500 7.1 General Information Siemens The common gateway supports a Command Line Interface (CLI) for installation and basic configuration, e.g. IP infrastructure. In V.24 CLI it is possible to change security relevant data (e.g. SSL Configuration), because the V.24 is considered to be secure. Additionally the CLI allows the monitoring of important counters and statistics. The CLI can be accessed via V.24.
PAGE 40
Command Line Interface CLI at HG 3500 Siemens 7.3 ● Access control The configuration write access has to be acquired before a store, upload or download command can be done. Because of the implemented “soft lock“ handling, at first a check if somebody else has set the write access is required. who has write access get write access release write access 7.4 Gateway Setup To permit system initialisation and basic management configuration activities following commands are needed.
PAGE 41
Command Line Interface CLI at HG 3500 Siemens /evtlog/evtlog.txt /evtlog/evtlog.bak 7.6 Maintenance The maintenance commands permit the current operational status of the gateway to be inspected, and provides access to diagnostic tools and interface and gateway controls.
PAGE 42
Command Line Interface CLI at HG 3500 Siemens show if counters ● To list all existing interfaces: show interfaces ● To get admin and operating states: show if states Ping and tracert ● Diagnosis Commands: ping Target shell ● vxWorks shell logon/logout: shell exit Gateway Reboot From the administrator point of view two different ways of a reboot command are of interest. At first there is the need to reboot the gateway with the current configuration.
PAGE 43
Command Line Interface CLI at HG 3500 Siemens show fingerprint Before accepting a certificate warning in the browser, it is strongly recommended that the administrator should compare the fingerprint of the certificate displayed in the browser against the fingerprint shown in CLI. The certificate must be accepted only, if both fingerprints are identical! ip address The parameter is a string in the form of x.x.x.x and x is an integer (e.g. 1.2.3.4).
PAGE 44
Siemens Command Line Interface CLI at HG 3500 holds the currently loaded loadware version number (e.g. L0-TOS.10.
PAGE 45
Technical Data HG 3570/3575 8 ● ● ● ● ● Siemens Technical Data for HG 3500/3575 LAN Interface ● 10/100-Base-T Fast Ethernet interface to IEEE 802.3u ● Autonegotiation, 10/100 Mbps, adjustable half/full duplex mode ● IEEE 802.3 / DIX Ethernet II Standard Framing ● Priority tagging (VLAN-TAG) to IEEE 802.
PAGE 46
Technical Data HG 3570/3575 Siemens ● Jitter Buffer - fixed size, adjustable between 0 and 210 ms ● Network Management Support ● ● SNMP Agent, SNMP Version 2, MIB2, Private MIB for Audio Stream Control Voice delay (mouth to ear) The delay is made up of the following components: ● Time for filling the voice packet (SampleSize, Encoding Time): Sample size - possible values: 20, 30, 40, 60 ms ● Implementation-specific delay on the transmission end ● Delay caused by the transmission between the HG
PAGE 47
Technical Data HG 3570/3575 Codec Type Siemens Implementation Specific Delay [ms] Voice Fax/Modem/Data G.711 40 35 G.
PAGE 49
Siemens 9 Questions and Exercises to the Common Gateway Questions 9.1 Which boards can be used in a HiPath 4000 V4 as a HG3500? 9.2 What must be considered for a setup of function blocks with the AMO BFDAT? 9.3 Which restriction exists if the HG3500 is working with the function HG3550? 9.4 Which function ID must be used with the AMO BCSU for a setup of a Common Gateway board? 9.5 Which task the AMO STMIB has? 9.
PAGE 50
Exercises Siemens Exercises 9.7 Check the predefined profiles (SFM and MFM) for the Common Gateway. 9.8 Create a Common Gateway with the HG3530 feature, 60 B channels and 120 subsribers. Remark: Use a predefined Function Block. Add two HFA phones. Add the required parameter in the HFA phones with the help of the Config Menu of the phone, WBM or DLS. 9.9 Create a Common Gateway in mixed modus.
PAGE 51
Solutions 10 Siemens Solutions Questions 10.1 Which boards can be used in a HiPath 4000 V4 as an HG3500? STMI2 Q2316-X STMI2 Q2316-X10 STMI4 Q2324-X500 STMI4 Q2324-X510 10.2 What must be considered for a setup of function blocks with the AMO BFDAT? If HG3570 functionality is part of the profile, it must be configured on the first position. 10.3 Which restriction exists if the HG3500 is working with the function HG3550? Only one trunking protocol can be used (H.323 or SIP). 10.
PAGE 52
Solutions Siemens Exercises 10.7 Check the predefined profiles (SFM and MFM) for the Common Gateway. DISPLAY-BFDAT; 10.8 Create a Common Gateway with the HG3530 feature, 60 B channels and 120 subsribers. Remark: Use a predefined Function Block. Add two HFA phones. Add the required parameter in the HFA phones with the help of the Config Menu of the phone, WBM or DLS. ADD-BCSU:MTYPE=IPGW,LTG=1,LTU=1,SLOT=14,PARTNO=Q2316X,FCID=1,FCTBLK=7,BCHL3530=60; ADDCGWB:LTU=1,SLOT=14,SMODE=NORMAL,IPADR=1.40.11.
PAGE 53
Solutions 10.9 Siemens Create a Common Gateway in mixed modus. Remarks A board with 60 B channels should be used for HG3550 with 10 B channels, HG3570 with 20 B channels and HG3530 with 30 B channels and 120 subscribers. Do not use a predefined Function Block, make your own.