1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Gateway
  5. HG 3500 V4
  6. Service manual

Siemens HG 3500 V4 Service Manual

Hipath 4000 v5 gateways
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Documentation
HiPath 4000 V5
IP Solutions - HiPath Gateways HG 3500 and HG
3575
Service Documentation
A31003-H3150-S104-2-7620
Communication for the open minded
Siemens Enterprise Communications
www.siemens.com/open

Advertisement

Table of Contents
loading

Related Manuals for Siemens HG 3500 V4

Summary of Contents for Siemens HG 3500 V4

  • Page 1 Documentation HiPath 4000 V5 IP Solutions - HiPath Gateways HG 3500 and HG 3575 Service Documentation A31003-H3150-S104-2-7620 Communication for the open minded Siemens Enterprise Communications www.siemens.com/open...
  • Page 2 Copyright © Siemens Enterprise Communications GmbH & Co. KG 2009 Hofmannstr. 51, 80200 München Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG Reference No.: A31003-H3150-S104-2-7620 The information provided in this document contains merely general descriptions or characteristics of...

  • Page 3: Table Of Contents

    4.1 HG 3500 V4 (Common Gateway) ........
  • Page 4 gatewaysTOC.fm Service Manual HiPath 4000 V5 - IP Solutions - HiPath Gateways HG 3500 and HG 3575 - Contents Nur für 4.1.4 Board Replacement............. . . 42 4.1.5 Feature Capacities .
  • Page 5 13.5 Overview of Configuration Steps ............122 14 HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB ..... . . 123 14.1 TYPE ASC - Changing the Payload QoS Setting in HHS .
  • Page 6 gatewaysTOC.fm Service Manual HiPath 4000 V5 - IP Solutions - HiPath Gateways HG 3500 and HG 3575 - Contents Nur für 17 Command Line Interface CLI in HG 3500 ..........149 17.1 General Information .

  • Page 7: Goal Of This Document

    Goal of this Document 1 Goal of this Document This document aims to provide an overview of the new HG 3500 V4 and HG 3575 V4 gateways in HiPath 4000. Only the basic board configuration is described. Detailed information on specific functions such as IP Distributed Architecture and Access Point Emergency (IPDA &...
  • Page 8 gateways_01_ziel.fm Goal of this Document A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 9: Terms

    gateways_02_terms.fm Terms Key Words 2 Terms 2.1 Key Words In order to prevent confusion, a number of key terms which are used frequently within the text are defined here in more detail. Nodes: Designates a device with a port/connection in a network. This can be a router, a HiPath 4000 CGW module or any computer.
  • Page 10 gateways_02_terms.fm Terms Key Words • Untagged Normal Ethernet frames without tagging • Priority Tagged Ethernet frames with tagging The priority bits are used The VLAN ID is 0. • VLAN Tagged Ethernet frames with tagging The priority bits are 0, The VLAN ID is >...

  • Page 11: Fax Or Modem Transmission And Detection

    gateways_02_terms.fm Terms Fax or Modem Transmission and Detection IP address 1 0 1 0 1 1 0 0 0 0 0 1 0 0 0 0 1 1 0 1 1 1 1 0 0 0 1 0 1 1 0 1 Netmask 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 Subnet...

  • Page 12: With Fmoip

    gateways_02_terms.fm Terms Fax or Modem Transmission and Detection 2.2.2 With FMoIP As of HiPath 4000 V2.0, the “FMoIP“ (FaxModem over IP) feature is used for the transmission of fax and modem signals over the IP network. FMoIP improvements The FMoIP feature provides the following new functionality: •...
  • Page 13 gateways_02_terms.fm Terms Fax or Modem Transmission and Detection Requirements • Using HG 3530 V2.0 board with AP1120 for fax/modem connection a homogeneous HiPath 4000 V2.0 2 Intro (as of SMR 8 of HiPath 4000 V2.0) network with all V2.0 boards updated to FMoIP version is required. •...

  • Page 14: Codec Standards

    gateways_02_terms.fm Terms Codec Standards 2.3 Codec Standards To transmit an analog voice signal over digital paths, it must be converted to a digital signal (and then back again). There are different methods for implementing this codec, each of which offer different levels of voice quality and requires different amounts of bandwidth.
  • Page 15 gateways_02_terms.fm Terms Voice Quality 1 ms Sender Transmission runtime Receiver ISDN: Byte-by-byte transmission, continuous data 30 ms Transmitter Packetization delay (sample size) 1 ms Transmission runtime Receiver IP: Packet-by-packet transmission, packet can only be sent when it is full Figure 2 Packet-by-packet voice transmission Sender Receiver...
  • Page 16 gateways_02_terms.fm Terms Voice Quality User satisfaction Very satisfied Satisfied Some users Many users Extremel Table 2-1 One-way delay [30 ms] (with 65 dB echo attenuation) Figure 4 Voice quality depending on delay Table 1, “Voice quality depending on delay and packet loss rate” illustrates an evaluation of voice quality depending on delay and packet loss rate.

  • Page 17: Jitter Buffer

    gateways_02_terms.fm Terms Jitter Buffer distributed directly via HFA has a IP-TDM conversion. The maximum number of IP-TDM conversions should (not including HFA terminal devices) be no higher than two. 2.5 Jitter Buffer 2.5.1 Jitter Buffer Functionality Transfer packets can arrive with different delays in TCP/IP-based networks. Because these delays cause interruptions, packets entering the data stream must be verified.

  • Page 18: Jitter Buffer Modes

    gateways_02_terms.fm Terms Jitter Buffer Buffer area for packets which arrive early Key: Buffer area for packets which arrive on time Buffer area for packets which arrive late Scenario 1: Packet arrives on time Jitter Buffer Delayed packet arrives Scenario 2: (can still be allocated) Jitter Buffer Scenario 3:...

  • Page 19: Considerations When Configuring The Delay For Static Jitter Buffer

    gateways_02_terms.fm Terms Jitter Buffer In the adaptive jitter buffer, the average delay is simply the start value for the average delay. This is automatically adjusted to the respective receive ratios during operation (green line). Maximum delay (configurable) Key: Average delay (configurable, however, only the start value for jitter buffer) packets Static jitter buffer: Average delay is constant.

  • Page 20: Clock Drift With Static Jitter Buffer

    gateways_02_terms.fm Terms Jitter Buffer Maximum delay (configurable) Key: Average delay (configurable) Received packets Lost packets Lower delay values: Natural-sounding voice transmission, however some packets are lost Measured time Higher delay values: Voice transmission with noticeable delays, however, less packet loss Measured time Figure 7 Settings for the static jitter buffer...
  • Page 21 gateways_02_terms.fm Terms Jitter Buffer If more packets are created at the transmitting end than are expected by the receiver, more packets enter the jitter buffer than intended. This leads to a constant increase in the measured average delay. If this reaches the configured maximum delay value, the jitter buffer adjusts itself.

  • Page 22: Minimum Delay For Adaptive Jitter Buffer

    gateways_02_terms.fm Terms Jitter Buffer Key: Maximum delay (configurable) Average delay (configurable) Measured average delay Measured time Figure 9 Clock drift in static jitter buffer [transmission slower than receipt] If, for example, the average delay has been set to 40 ms, this means that the measured overall delay is reduced at intervals from the start value by 40 ms.

  • Page 23: Packet Loss Control In Adaptive Jitter Buffer

    gateways_02_terms.fm Terms Jitter Buffer Maximum delay (configurable) Key: Average delay (adaptive) Minimum delay (configurable) Packets Adaptive jitter buffer: The average delay ranges between the minimum and maximum delay and tends to be as low as possible. Measured time Figure 10 Minimum delay for adaptive jitter buffer Minimum and maximum delay values are still adhered to if packets are lost.
  • Page 24 gateways_02_terms.fm Terms Jitter Buffer – Jitter Buffer Type: Select whether the jitter buffer should operate in static or adaptive mode. In adaptive mode, the jitter buffer adjusts the average delay according to the situation when the data is received. In this way, the jitter buffer tries to reduce as far as possible both the delay and the number of lost packets.

  • Page 25: Runtime And Noticeable Effects

    gateways_02_terms.fm Terms Runtime and Noticeable Effects 2.6 Runtime and Noticeable Effects 2.6.1 Delay and Echo I P N e t wo r k Says Hears Hears Says one way delay mouth to ear Three Four round trip delay Five Three Four Stop Seven...

  • Page 26: Delay And Hands-Free Talking

    gateways_02_terms.fm Terms Runtime and Noticeable Effects If an echo is generated on the B side (e.g. because of the 2-wire/4-wire hybrid of analog terminal devices, also known as hybrid coil), this is noticed by the speaker, who finds himself speaking over what he said a half a second before, for example. With high transmission runtimes, it is therefore generally necessary to have echo- free signals on the transmission path.
  • Page 27 gateways_02_terms.fm Terms Runtime and Noticeable Effects I P N e t wo r k Says Hears Hears Says We can offer you EUR 500 per unit Impatience, We can offer you EUR 500 per unit insecurity Can you deliver 10 Why does he units by Friday? not answer?

  • Page 28: Voice Encryption Devices

    gateways_02_terms.fm Terms Voice Encryption Devices 2.7 Voice Encryption Devices Voice encryption devices such as the optiset privacy module, for example, transmit encrypted voice in the same way as modems. The same rules that apply to fax and modem connections apply in this case. The changeover from unencrypted to encrypted mode does not normally take place until there is a call, which is why automatic pilot tone detection is particularly useful here.

  • Page 29: Architecture And System Requirements

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Prerequisites 3 Architecture and System Requirements 3.1 Prerequisites 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.

  • Page 30: Network Data

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Network Data In order to achieve a high Quality of Service (voice quality/real time behavior of signaling), the support of IEEE 802.1 p/q VLAN Tagging and IETF RFC 2474 DiffServ is recommended (see Section 3.4, “Network Data”).
  • Page 31 The default values assume DiffServ support on the part of the network and realize the Quality of Service strategy of Siemens AG. IMPORTANT: TOS byte can be read in a number of different ways...

  • Page 32: Bandwidth Requirements

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Bandwidth Requirements The values given in the table are the default settings of the loadware. These settings fulfil the OSCAR specifiactions. You can change the L2 priority with WBM > Explorers > Network Interfaces > LAN1 (LAN1) > Edit LAN1 Interface The values can also be changed via the appropriate AMO.

  • Page 33: Sampling Time

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Bandwidth Requirements • G.729AB with Voice Activity Detection. IMPORTANT: Note that there is virtually no delay introduced in generating G.711 encoding from TDM voice packets (Algorithmic Delay = 0 ms). For more detailed information on codecs please refer to Section 2.3, “Codec Standards”.

  • Page 34: Required Bandwidth Per Connection

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Bandwidth Requirements 3.5.4 Required Bandwidth 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. Preamble, FCS, 26 Bytes).

  • Page 35: Voice Activity Detection (Vad)

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Bandwidth Requirements Codec Sampling Payload Payload Total Bandwidth Time [ms] Frames per [Bytes] Bytes [Bit/s] second 16,67 18667 G.723 33.33 27733 16,67 17067 Table 4 Bandwidth for active DMC master connections with SPE Bandwidth for master connections no longer used (without SPE): Codec Frame Packets...

  • Page 36: Dmc Considerations

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Bandwidth Requirements Figure 13 VoIP Bandwidth Reduction Sequence 3.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.

  • Page 37: B Channels

    gateways_03_arch_sys_requ.fm Architecture and System Requirements B Channels Figure 14 DMC and Master Connection Enabling VAD will reduce the required bandwidth on the master connection to negligible levels. Note that delays for each TDM to IP conversion accumulate. In the example above the master connection goes through 3 hops which will result in approximately 200ms end to end delay assuming G.711 encoding with 30ms sampling time and a high quality network (20ms delay).

  • Page 38: B Channel Configuration

    gateways_03_arch_sys_requ.fm Architecture and System Requirements B Channels The AMO allows higher values than mentioned in the table above. But the DSP performance is only sufficient for the number of b channels listed in the table above this means the values have to be adapted manually to the values mentioned above.

  • Page 39: Amo Bcsu

    gateways_03_arch_sys_requ.fm Architecture and System Requirements B Channels 3.6.1.2 AMO BCSU The profile configured with AMO BFDAT (maximum number of b channels (BRDBCHL) and configured functions (FUNCTION)) is evaluated by AMO BCSU. Additionally the activated features in the system (i.e. DMC, SPE) will be considered.
  • Page 40 gateways_03_arch_sys_requ.fm Architecture and System Requirements B Channels Board Maximum Reduction in % Reduction in b number of channels b channels STMI2 (Q2316-X10) STMI4 (Q2324-X500) STMI4 (Q2324-X510) Table 8 Number of B channels depending on SPE and DMC This reduction is not only calculated on board level but on function level. This means that the percentage values from above will be calculated per configured function.

  • Page 41: Displaying The B Channels Currently Available/Configured (Possible Ip-Based Connections)

    gateways_03_arch_sys_requ.fm Architecture and System Requirements B Channels => Maximum number of available b-channels for HG 3530: 20-3=17 These reduced b-channel values are the upper limit for path selection. The B channel number increases appropriately when features are deactivated. Summary: In the AMO BFDAT, only the maximum number of B channels can be configured.

  • Page 42: Traffic Considerations

    gateways_03_arch_sys_requ.fm Architecture and System Requirements Traffic Considerations 3.7 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.

  • Page 43: Supported Gateways

    The common gateway HG 3500 V4 consolidates existing VoIP gateways into a single gateway. • The ommon gateway HG 3500 V4 forms a common architecture for HiPath 4000 V4 and higher based on HG 3550 V2.0 (for HiPath 4000 V3.0). •...

  • Page 44: Hardware And Loadware

    SIP trunking (native & SIP-Q) HG 3540 SIP subscriber HG 3540 Table 10 Scenarios and protocols with HG 3500 V4 4.1.4 Board Replacement To replace an STMI board please note the following: • Replace a “small“ STMI with a “small“ STMI: no problem •...

  • Page 45: Feature Capacities

    • Restart the board with RESTART-BSSU:ADDRTYPE=PEN,LTG=<ltg>,LTU=<ltu>,SLOT=<slot>; 4.1.5 Feature Capacities Information on feature capacities for both HG 3500 V4 and HG 3575 V4 see Chapter 5, “Features and Restrictions”. • The HiPath HG 3500 V4 gateway has the capacity to convert 60/120 connections into Fast Ethernet packets and provide TDM to IP conversion for 60/120 concurrent calls.
  • Page 46 Chapter 10, “Standby Board HG 3500”. • The HG 3500 V4 gateway supports secondary gateways that provide full redundancy to IP subscribers. Providing full redundancy for IP clients via secondary gateways will protect against higher level failures, like entire Access Point or host failures.
  • Page 47 • The HG 3500 V4 gateway supports QoS. VLAN-tagging according IEEE 802.1p/q on Layer 2 as well as DiffServ (defined in RFC 2474) on the IP Layer have been implemented in order to provide the best possible voice quality using an IP network.
  • Page 48 IP phone into a normal operation mode until the IP phone is logged off again by an activation of the associated optiClient 130. • “Overbooking” is possible, meaning that more IP phones per HG 3500 V4 gateway can be configured than there are available connections (maximum of 240 subscribers).

  • Page 49: Impact On Existing Functions

    Full user mobility is supported within a single system and networked systems. • The HG 3500 V4 gateway is supported in all IP distributed Access Points including AP 3500/3505 APs that were part of an upgraded v1.0 system. 4.1.6 Impact on Existing Functions •...

  • Page 50: Hg 3575 V4

    gateways_04_overview.fm Supported Gateways HG 3575 V4 – S0-adapter – V.24-Adapter • Autoset Relocate, Teleworking V2.6 and Workstation Protocol are not supported with HiPath HG 3500. • HiPath HG 3500 line gateways do not operate in a load-sharing mode - there is a fixed assignment of the IP phones to one HiPath HG 3500 gateway.

  • Page 51: Exchanging Boards

    gateways_04_overview.fm Supported Gateways HG 3575 V4 Board type Part number B channels NCUI4 Q2324-X10 120 B channels (5 DSPs) Table 11 Supported NCUI boards Board type Loadware Restricted B channels Full feature scope NCUI2+ PZKNCI40 Not possible NCUI4 PZKNCI40 Table 12 Boards, loadware, B channels and feature scope 4.2.3 Exchanging Boards HiPath 4000 - Access Point...
  • Page 52 gateways_04_overview.fm Supported Gateways HG 3575 V4 CHANGE- STMIB:MTYPE=NCUI2,LTU=18,TYPE=ASC,PRIO=PRIO3,CODEC=NONE,VAD=NO,R TP="20"; CHANGE- STMIB:MTYPE=NCUI2,LTU=18,TYPE=ASC,PRIO=PRIO4,CODEC=NONE,VAD=NO,R TP="20"; CHANGE- STMIB:MTYPE=NCUI2,LTU=18,TYPE=ASC,PRIO=PRIO5,CODEC=NONE,VAD=NO,R TP="20"; CHANGE- STMIB:MTYPE=NCUI2,LTU=18,TYPE=ASC,PRIO=PRIO6,CODEC=NONE,VAD=NO,R TP="20"; CHANGE- STMIB:MTYPE=NCUI2,LTU=18,TYPE=ASC,PRIO=PRIO7,CODEC=NONE,VAD=NO,R TP="20"; CHA- STMIB:MYTPE=NCUI2,LTU=18,TYPE=JB,AVGDLY=40,MAXDLYV=120,MINDLYV=2 0,PACKLOSS=4,AVGDLYG=60,MAXDLYD=200,JBMODE=1; CHA- STMIB:MTYPE=NCUI2,LTU=18,TYPE=SIGQOS,BANDW=0,MAXRTD=0,MINTHRPT=0 ,SIGPTHSW=STD,QOSSTAT=NO; CHA- STMIB:MTYPE=NCUI2,LTU=18,TYPE=H323,Q931T1=50,Q931T2=500,GWNAME=" HG3575-2"; CHA-STMIB:MTYPE=NCUI2,LTU=18,TYPE=DMCDATA,DMCALLWD=NO,DMCCONN=0; CHA-STMIB:MYTPE=NCUI2,LTU=18,TYPE=SNMP,CS1="public"; CHA-STMIB:MYTPE=NCUI2,LTU=18,TYPE=WBMDATA,LOGINWBM="HP4K- DEVEL",ROLE=ENGR; CHA-STMIB:MYTPE=NCUI2,LTU=18,TYPE=WBMDATA,LOGINWBM="HP4K- SU",ROLE=SU; CHA-STMIB:MYTPE=NCUI2,LTU=18,TYPE=WBMDATA,LOGINWBM="HP4K- ADMIN",ROLE=ADMIN; CHA-STMIB:MYTPE=NCUI2,LTU=18,TYPE=WBMDATA,LOGINWBM="HP4K- READER",ROLE=READONLY; CHA-STMIB:MYTPE=NCUI2,LTU=18,TYPE=GWSECTOR,GWSECTNO=0;...

  • Page 53: Features And Restrictions

    Features and Restrictions Gateway Functionality 5 Features and Restrictions The following features are supported on HG 3500 V4 and HG 3575 V4! For features concerning HG 3500 V4 only please refer to Section 4.1.5, “Feature Capacities”. 5.1 Gateway Functionality The HG 35xx V4 gateways are only supported in the HiPath 4000 V4 or higher communication platforms.

  • Page 54: Voice Compression

    gateways_05_hg35xxv4_features.fm Features and Restrictions Voice Compression 5.3 Voice Compression The HG 35xx V4 gateways support voice compression follwoing standard G.711A encoding at 64Kbps. Compression according to G.729A and G.729AB is supported as well. Also supported codecs are G.711U, G.723 (only for HG 300 V4), G.729 and G.729B.

  • Page 55: Voice Activity Detection (Vad)

    gateways_05_hg35xxv4_features.fm Features and Restrictions Voice Activity Detection (VAD) instead by a lot less. Always take the values specified in Chapter 6, “Load Calculation” in the document “IP Distributed Architecture (IPDA) and Access Point Emergency (APE)“ into account when dimensioning the bandwidth. 5.4 Voice Activity Detection (VAD) The HG 35xx V4 gateways support VAD (Voice Activity Detection).

  • Page 56: Comfort Noise Generation (Cng)

    gateways_05_hg35xxv4_features.fm Features and Restrictions Comfort Noise Generation (CNG) 5.5 Comfort Noise Generation (CNG) The HG 35xx V4 gateways support CNG (Comfort Noise Generation). While using VAD, the DSP at the destination emulates background noise from the source side, preventing the perception that a call is disconnected. 5.6 Echo Cancellation The HG 35xx V4 gateways support on board echo cancellation (performed on the on-board DSP modules) compliant with the ITU-T G.168 standard.

  • Page 57: Redundant Lan Interface

    gateways_05_hg35xxv4_features.fm Features and Restrictions Redundant LAN Interface Analog modems and fax machines use complicated phase modulation procedures for data transfer which can be affected by interference caused by echo cancellation. 5.7 Redundant LAN Interface The feature “Redundant LAN Interface” described in the document "IP Distributed Architecture (IPDA) and Access Point Emergency (APE) Chapter 10, “Information for network administrators”...

  • Page 58: Security

    This can be done via the board’s WBM. WBM > Explorers > Security > MAC Address Filtering or WBM > Explorers > Security > IP Address Filtering. For a detailed description, see "HiPath 4000 V5, HiPath Gateways HG 3500 V4 and HG 3575 V4, Administrator Documentation" (http://apps.g-dms.com:8081/ techdoc/de/P31003H3150M1010100A9/index.htm).

  • Page 59: Restrictions

    gateways_05_hg35xxv4_features.fm Features and Restrictions Restrictions 5.10 Restrictions 5.10.1 Bit Rate Problem description: If Auto Negotiation is set as the bit rate in NCUI4 and STMI4 boards in HiPath 4000 (AMO CGWB, BITRATE=AUTONEG) and 100 BRK Full Duplex is permanently set in the administrable peer, the peer does not respond to AUTONEG and "LAN message flooding"...

  • Page 60: Possible Ip Hops

    Features and Restrictions Restrictions WBM > Maintenance > Actions > Automatic Actions > Save Local Configuration for Upgrade For a detailed description, see "HiPath 4000 V5, HiPath Gateways HG 3500 V4 and HG 3575 V4, Administrator Documentation" (http://apps.g-dms.com:8081/ techdoc/de/P31003H3150M1010100A9/index.htm). 5.10.3 Possible IP hops IMPORTANT: More than 3 IP hops can lead to restrictions in a Voice over IP system, i.e.

  • Page 61: Communication Matrix

    gateways_06_com_matrix.fm Communication Matrix 6 Communication Matrix Legend for the follwoing tables: Not possible Possible A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...
  • Page 62 gateways_06_com_matrix.fm Communication Matrix HiPath 4000 V1.0 HG 3550 V1.1 H323 SIP-Q Native SIP HFA- Mobility H323 HiPath Native SIP 4000 V1.0 HG 3550 V1.1 HFA-Mobility H323 Native SIP HG 3550 V1.1 HFA-Mobility HiPath 4000 V2.0 H323 Native SIP HG 3550 V2.0 HFA-Mobility H323 Native SIP...
  • Page 63 Native SIP HFA- Mobility H323 Native SIP HG 3550 V1.1 HFA-Mobility HiPath 4000 V4 H323 Native SIP HG 3500 V4 HFA-Mobility H323 Native SIP HiPath HG 3500 V4 4000 V5 HFA-Mobility Table 13 Networking with HiPath 4000 V1.0 HiPath 4000 V2.0 HG 3550 V1.1...
  • Page 64 V2.0 HFA-Mobility H323 HG 3550 Native SIP V1.1 HiPath HFA-Mobility 4000 H323 HG 3500 V4 Native SIP HFA-Mobility Table 14 Networking with HiPath 4000 V2.0 A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...
  • Page 65 HFA- H323 SIP-Q Nativ HFA- e SIP Mobil e SIP Mobil HFA-Mobility H323 HiPath HG 3500 V4 4000 Native SIP HFA-Mobility Table 14 Networking with HiPath 4000 V2.0 HiPath 4000 V3.0 HG 3550 V1.1 HG 3550 V2.0 H323 SIP-Q Nativ...
  • Page 66 HiPath HFA-Mobility 4000 V3.0 H323 HG 3550 Native SIP V2.0 HFA-Mobility H323 HG 3550 Native SIP V1.1 HiPath HG 3500 V4 HFA-Mobility 4000 H323 Native SIP HFA-Mobility HFA-Mobility H323 HiPath HG 3500 V4 4000 Native SIP HFA-Mobility Table 15 Networking with HiPath 4000 V3.0 A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 &...
  • Page 67 Communication Matrix HiPath 4000 V4 HG 3550 V1.1 HG 3500 V4 H323 SIP-Q Nativ HFA- H323 SIP-Q Nativ HFA- e SIP Mobil e SIP Mobil H323 HiPath HG 3550 Native SIP 4000 V1.1 V1.0 HFA-Mobility H323 HG 3550 Native SIP V1.1...
  • Page 68 Communication Matrix HiPath 4000 V4 HG 3550 V1.1 HG 3500 V4 H323 SIP-Q Nativ HFA- H323 SIP-Q Nativ HFA- e SIP Mobil e SIP Mobil H323 HG 3550 Native SIP V1.1 HiPath HFA-Mobility 4000 H323 HG 3500 V4 Native SIP...
  • Page 69 Communication Matrix HiPath 4000 V5 HG 3500 V4 H323 SIP-Q Nativ HFA- e SIP Mobil H323 HiPath HG 3550 Native SIP 4000 V2.0 V3.0 HFA-Mobility H323 HiPath HG 3500 V4 Native SIP 4000 HFA-Mobility H323 HiPath HG 3500 V4...
  • Page 70 gateways_06_com_matrix.fm Communication Matrix A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 71: Load Concept For Gateway Boards

    gateways_07_load_concept.fm Load Concept for Gateway Boards Important Information 7 Load Concept for Gateway Boards 7.1 Important Information • This chapter only describes how to update the loadware for gateway boards. • To update the system as a whole, use the conventional HiPath 4000 Assistant features Software Transfer (SWT) and Software Activation (SWA).

  • Page 72: New Load Concepts

    gateways_07_load_concept.fm Load Concept for Gateway Boards New Load Concepts 7.3 New Load Concepts Load concepts have been improved to reduce the time needed to download new loadware for IP gateways (as of HiPath 4000 V4). Load concept for HG 3530/HG 3540/HG 3550/HG 3570 in HiPath 4000 V1.0/ V2.0/V3.0 When starting up an STMI board, the board is loaded via the backplane (HDLC) if newer software is available.

  • Page 73: Updating Loadware With Web-Based Management

    gateways_07_load_concept.fm Load Concept for Gateway Boards Updating Loadware with Web-Based Management 7.4 Updating Loadware with Web-Based Management IMPORTANT: Disadvantage You can only upgrade one IP gateway board at a time. • To use this option, log on to HiPath 4000 Assistant and select Expert mode >...

  • Page 74: Updating Loadware With "Lw Update Manager

    gateways_07_load_concept.fm Load Concept for Gateway Boards Updating Loadware with "LW Update Manager" • Now select the Load button to start loading. Loading can take up to five minutes. The loadware is saved in the flash memory of the board. IMPORTANT: The LAN must be connected but the IP gateway must not be rebooted during the load operation (AMO USSU, AMO BSSU).

  • Page 75: General Comments On Loading

    gateways_07_load_concept.fm Load Concept for Gateway Boards General Comments on Loading Key features of "LW Update Manager" • The "LW Update Manager" function lets you upgrade individual boards or all boards supported. • The LW Update is made up of two parts: Loadware Transfer and Loadware Activation.
  • Page 76 gateways_07_load_concept.fm Load Concept for Gateway Boards General Comments on Loading A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 77: Save Configuration Data In Local Flash

    gateways_08_local_flash.fm Save Configuration Data in Local Flash Feature Description 8 Save Configuration Data in Local Flash 8.1 Feature Description Up to HiPath 4000 V4 release 1 backup and restore of HG 35xx WBM configuration is only possible using HiPath 4000 Assistant application „HiPath Backup &...
  • Page 78 gateways_08_local_flash.fm Save Configuration Data in Local Flash Startup Scenarios A retry to reach the backup server is executed. • Backup server is not configured. The gateway starts up using its default configuration data. No retry to reach the backup server is executed. Loadware Update via HDLC Same procedures as normal restart.

  • Page 79: Configuration

    gateways_08_local_flash.fm Save Configuration Data in Local Flash Configuration Loadware Update via HiPath 4000 Assistant / WBM: backup server configured and reachable, but on the backup server an older configuration than the current one is found Same as„Loadware Update via HiPath 4000 Assistant / WBM“. 8.3 Configuration The feature will be configured with the WBM of the board.
  • Page 80 gateways_08_local_flash.fm Save Configuration Data in Local Flash Special Use Cases A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 81: Loadability Of The Fpga On The Stmi4/Ncui4 Board

    gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board 9 Loadability of the FPGA on the STMI4/NCUI4 board From HiPath 4000 V5 or later it is possible to load the FPGA code on the gateway boards STMI4 and NCUI4. Usually the FPGA code is supplied with a LW hotfix (or via fix release, minor release, hotfix).
  • Page 82 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board NOTE: The following description of the firmware update is done for SENTA loadware. For COMGA firmware the instructions are the same but choose Load COMGA- Firmware via HTTP from the menu. 1.
  • Page 83 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board 3. Upload process has finished when the following screen appears. Confirm with OK. A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...
  • Page 84 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board 4. Activate the new SENTA firmware by pressing the Activate now button. NOTE: After completion of the activation process the gateway will be rebooted automatically! 5. Confirm the activation process by clicking OK. The new SENTA firmware will be updated, activated and the gateway will be rebooted.
  • Page 85 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board 00000010| 30 36 3A 35 34 17 45 4C 46 3E 49 33 38 36 50 5A | 06:54.ELF>I386PZ 00000020| 4B 53 45 4E 30 31 2E 4F 31 2E 30 31 32 00 00 00 | KSEN01.O1.012... 00000030| 00 00 30 00 99 78 70 7A 6B 73 65 6E 30 31 00 00 | ..0..xpzksen01..
  • Page 86 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board (SWCONF tEmWeb 0x353c4c0 "08/25/2008 15:43:55.651796" cswconfigsvc02.cpp 845) Progress Response: Transferred File Size=1104209 Complete File Size=1092718 (SWCONF tEmWeb 0x353c4c0 "08/25/2008 15:43:57.721041" cswconfigsvc02.cpp 845) Progress Response: Transferred File Size=1104209 Complete File Size=1092718 The second phase of the process: (SWCONF tEmWeb 0x353c4c0 "08/25/2008 15:44:22.147227"...
  • Page 87 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board (SWCONF tEmWeb 0x353c4c0 "08/25/2008 15:46:53.140248" util.c 4769) writting SENTA FPGA code to SENTA flash is still running (SWCONF tEmWeb 0x353c4c0 "08/25/2008 15:47:03.140247" util.c 4769) writting SENTA FPGA code to SENTA flash is still running (SWCONF tEmWeb 0x353c4c0 "08/25/2008 15:47:13.140245"...
  • Page 88 gateways_09_fpga_code_update.fm Loadability of the FPGA on the STMI4/NCUI4 board Traces for failure (SWCONF tFPGAWrite 0x4e39e88 "08/28/2008 15:06:53.579613" util.c 3666) call of xsvfExecute returned error:2 A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 89: Standby Board Hg 3500

    gateways_10_standby.fm Standby Board HG 3500 Feature Description 10 Standby Board HG 3500 As of HiPath 4000 V4, this feature is supported for all common gateway boards. Regardless of the boards configuration as single feature mode or as multiple feature support (MFS). IMPORTANT: Restriction In the case of MFS, only the entire board can be transferred to the standby board! 10.1 Feature Description...
  • Page 90 gateways_10_standby.fm Standby Board HG 3500 Feature Description • Faults on the LAN connection cable. Please note that LAN faults that are located “behind“ routers, hubs or IP switches do not trigger a switchover, and nor do faults on IP terminal devices. The switchover mechanism is only triggered by a signaled Layer 1 fault, that is, a general cable defect.
  • Page 91 gateways_10_standby.fm Standby Board HG 3500 Feature Description Apart from automatically switching IP stations to a standby board when a defect occurs, this feature also offers manual switchover options that can be implemented with the AMO BSSU. This lets the IP stations maintain their group relationships, which means there is no need for station reconfiguration with the AMO SBCSU, AMO AUN, etc.
  • Page 92 gateways_10_standby.fm Standby Board HG 3500 Feature Description A History field is provided for every board in the pool. The following information can be entered here and read out with the AMO BPOOL: – Board (LTU, slot) from which the stations currently configured were switched –...

  • Page 93: User Interface

    gateways_10_standby.fm Standby Board HG 3500 User Interface 10.2 User Interface No particular consequences for telephone users. During the switchover phase, the telephone is “dead“; its display is cleared and reappears as soon as the telephone becomes operational on the new board. Before this point, additional temporary messages such as PBX NOT FOUND may appear on the display.
  • Page 94 gateways_10_standby.fm Standby Board HG 3500 Service Information transformed into a standby board (for example, STBYDEF), which means it no longer has an IP address. Although the standby board is physically connected to the LAN, meaning that Layer 1 remains in operation, the higher layers are deactivated.
  • Page 95 gateways_10_standby.fm Standby Board HG 3500 Service Information • If you are switching from a fully configured board to a partially configured board, then, following switchover, only a reduced number of active connections is possible on the new board, that is, the number supported by the partially configured board.

  • Page 96: Generation

    gateways_10_standby.fm Standby Board HG 3500 Generation 10.4 Generation Board pool No.1 Direct Link HG 3500-2 optiPoint IP 1-17-2 (Normal) Subsriber: 2160 1-3-49 Gateway: HG 3500-1 HG 3500-1 optiPoint IP HG 3500-3 Subsrciber: 2150 Gateway: HG 3500-2 HiPath4000 V4 1-3-109 (Standby) In the interest of clarity and to keep things simple, we will not discuss the general configuration of DPLN, LTU, etc.
  • Page 97 gateways_10_standby.fm Standby Board HG 3500 Generation ADD-BCSU:MTYPE=IPGW,LTG=1,LTU=17,SLOT=2,PARTNO=Q2316- X10,FCTID=1,FCTBLK=2; /*HG 3500-2 ADD-BCSU:MTYPE=IPGW,LTU=3,SLOT=109,PARTNO=Q2316- X,FCTID=1,FCTBLK=3; /*Standby board HG 3500-3 Configuration of common and global feature board data of the common gateway board. In this example 2 normal and one standby board will be configured: ADD- CGWB:LTU=3,SLOT=49,SMODE=NORMAL,IPADR=192.16.16.12,NETMASK=255.2 55.255.0;...
  • Page 98 gateways_10_standby.fm Standby Board HG 3500 Generation | DC-STATUS = READY LAN_VERB = READY SMODE = NORMAL +------------------------------------------------------------------------------+ LTU = 3 SLOT = 109 HOP-AUT-CNT = 0 HOP-MAN-CNT = 0 | DC-STATUS = READY LAN_VERB = READY SMODE = STBYRDY +------------------------------------------------------------------------------+ LTU = 17 SLOT = 2 HOP-AUT-CNT = 0...

  • Page 99: Service Steps After The Automatic Switch Over

    gateways_10_standby.fm Standby Board HG 3500 Service steps after the automatic switch over SWITCHED MANFR BRD: The IP stations were manually switched away from this board (with the AMO BSSU) (see also DATE/TIME) SWITCHED MANTO BRD: The IP stations were manually switched back to this board (with the AMO BSSU) (see also DATE/TIME) The history data can be reset with the following AMO command: CHANGE-BPOOL:MTYPE=CGW,TYPE=HISTRES,LTU=3,SLOT=109;...

  • Page 100: Relevant Amos

    gateways_10_standby.fm Standby Board HG 3500 Relevant AMOs 1. The subscribers which are switched over should get their original pens. In this case the board pool has to be defined as HOPAUT=SINGLE ! – Change the defective board resp. reconnect the LAN connection. –...
  • Page 101 gateways_10_standby.fm Standby Board HG 3500 Relevant AMOs Parameter Sprache/ Beschreibung/ Description Language TYP=IPGW IP Gateway (Common Gateway Baugruppe) MTYPE=IPGW IP gateway (common gateway board) BFDAT ANZBKAN Anzahl der funktionsbezogenen B-Kanäle. BCHLCNT Defines the number of b-channels related to the selected function. ANZSATZ Anzahl der funktionsbezogenen Saetze.
  • Page 102 gateways_10_standby.fm Standby Board HG 3500 Relevant AMOs Parameter Sprache/ Beschreibung/ Description Language FUNCTION This parameter defines the configuration profile of the CGW board. If HG3570 functionality is used, it must be configured at first position. If a prereservation of a certain line range of functions HG3530, HG3540 or HG3550 is desired, this function must be at the end of the profile just suffixed by the according HG35xxR...
  • Page 103 gateways_10_standby.fm Standby Board HG 3500 Relevant AMOs Parameter Sprache/ Beschreibung/ Description Language BSSU CGWSA CGW Schaltauftrag: CGWSWBCK: Rückschalten aller automatisch weggeschalteter IP Teilnehmer auf die Original- CGW-Baugruppe KEIN: Kein CGW bezogener Schaltauftrag STBYRDY: Verwendung als CGW Standby- Baugruppe (Reserve-Baugruppe) UMSCH: Umschalten der IP Teilnehmer der CGW-Baugruppe auf eine andere Baugruppe CGWSW CGW switching activity:...
  • Page 104 gateways_10_standby.fm Standby Board HG 3500 Relevant AMOs Parameter Sprache/ Beschreibung/ Description Language SMODE Standby Mode or Normal Mode NORMAL: A board in Normal Mode has valid board data and normally also OPTIIPs assigned to it. STDBYRDY: A board in Standby Ready Mode has no valid board data, to this board OPTIIPs can be switched over if another board of the same board reconfiguration pool (AMO...

  • Page 105: Dls Client Bootstrapping

    gateways_11_dls_client_bootstrapping.fm DLS Client Bootstrapping Bootstrapping with "No PIN" PIN Mode 11 DLS Client Bootstrapping DLS client bootstrapping is a procedure that must be performed once to allow the DLS server to exchange configuration data with the gateway. This procedure generates an individual (DLS) certificate for the gateway and transfers it to the gateway.
  • Page 106 gateways_11_dls_client_bootstrapping.fm DLS Client Bootstrapping Bootstrapping with "Default PIN" or "Individual PIN" PIN Mode Variant B: 1. Create a virtual IP device in the DLS under IP Devices > IP Device Management > IP Device Configuration > "DLS Connectivity" tab and then select the required PIN mode.

  • Page 107: Hipath Gateway Hg 3575 V4 - Changing Parameters With Amo Stmib

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE GLOBAL - Changing the Idle Bit Pattern 12 HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB IMPORTANT: Any of the settings that can be made here with AMOs are read- only in WBM.

  • Page 108: Type Ifdata - Changing The Interface-Specific Parameters Of The Access Point

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE IFDATA - Changing the Interface-Specific Parameters of the Access Point CHANGE- STMIB:MTYPE=NCUI2,LTU=99,SLOT=99,TYPE=GLOBAL,PATTERN=2 This change does not become effective until the access point is restarted. Configuration Management --> System Data --> IPDA --> IPDA System Data Click Search and select the access point.

  • Page 109: Type Servif - Changing The Login And Password For Service Access

    VLAN tagging. The same applies for the DiffServ CodePoints. If the routers do not support DiffServ, the standard TOS values must be configured without DiffServ. If DiffServ is supported, but not the Siemens CodePoints, the values specified by the network carrier must be configured.
  • Page 110 gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE SERVIF - Changing the Login and Password for Service Access • Terminal Mode In terminal mode, communication with the HiPath HG 3575 Loadware is realized directly via the Command Line Interface. IMPORTANT: HiPath 4000 V4 or higher does not support two-stage CLI.

  • Page 111: Type Asc - Changing The Payload Qos Setting Of The Access Point

    The settings can differ from access point to access point. If the routers do not support DiffServ, the standard TOS value must be configured without DiffServ. If DiffServ is supported, but not the Siemens CodePoints, the value specified by the network operator must be configured.

  • Page 112: Type Asc - Setting The Codec List For Dmc Connections, Rtp Packet Size, Voice Activity Detection And T.38 Fax

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE ASC - Setting the Codec List for DMC Connections, RTP Packet Size, Voice Activity Detection and T.38 Fax 12.5 TYPE ASC - Setting the Codec List for DMC Connections, RTP Packet Size, Voice Activity Detection and T.38 Fax See also Chapter 15, “Codec...

  • Page 113: Type Dsp - Jitter Buffer Size Of The Access Point

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE DSP - Jitter Buffer Size of the Access Point 12.6 TYPE DSP - Jitter Buffer Size of the Access Point The parameter JITBUFD only takes effect if the parameter JBMODE in the JB branch is set to 0 (LEGACY MODE).

  • Page 114: Type H323 - Changing The H323 Settings At The Access Point

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE H323 - Changing the H323 Settings at the Access Point Configuration Management --> System Data --> IPDA --> IPDA System Data Click Search and select the access point. Click Execute on the Action pull-down menu and select the mode of action Update AP, confirm with EXEC-USSU:MODE=UPDATAP,LTU=99;...

  • Page 115: Type Sigqos - Quality Monitoring For The Signaling Connection Over Ip

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE SIGQOS - Quality Monitoring for the Signaling Connection over IP Configuration Management --> System Data --> IPDA --> IPDA Access Point Click Search and select the access point. Enter the parameter on the General tab under Jitter Buffer and click Save.
  • Page 116 gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE SNMP - Changing the Community Strings for Read Access These values can be modified. CS2 can be used to assign read-only access to a second community on the SNMP agent. If, for example, CS1=“ToP_SeCrEt23“...

  • Page 117: Type Wbmdata - Changing The Login And Password For Wbm

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE WBMDATA - Changing the Login and Password for WBM CHANGE-STMIB:MTYPE=NCUI2,LTU=99,TYPE=SNMP, CS1=“ToP_SeCrEt23“; • This change does not become effective until the access point is restarted. Configuration Management --> System Data --> IPDA --> IPDA System Data Click Search and select the access point.

  • Page 118: Type Dlsdata - Configuring Dls Data

    gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB TYPE DLSDATA - Configuring DLS Data Configuration Management --> System Data --> IPDA --> IPDA Access Point Click Search and select the access point. Enter the Gateway Sector Number on the General tab and click Save. CHANGE- STMIB:MTYPE=NCUI2,LTU=99,TYPE=GWSECTOR,GWSECTNO=7;...
  • Page 119 gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB Resetting the Parameters to Default Values Configuration Management --> System Data --> IPDA --> IPDA System Data Click Search and select the access point. Click Execute on the Action pull-down menu and select the mode of action Update AP, confirm with EXEC-USSU:MODE=UPDATAP,LTU=17;...
  • Page 120 gateways_12_hg3575v4.fm HiPath Gateway HG 3575 V4 - Changing Parameters with AMO STMIB Resetting the Parameters to Default Values A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 121: General Information On How To Configure A Hg 3500 V4 Common Gateway

    General Information on How to Configure a HG 3500 V4 Common Gateway Changing the common gateway configuration General Information on How to Configure a HG 3500 V4 Common Gateway 13.1 Changing the common gateway configuration Please note that the entire board must be reconfigured if changes are made to the common gateway configuration.
  • Page 122 General Information on How to Configure a HG 3500 V4 Common Gateway Rules If the value BCHAN60&BCHAN120 is set, an STMI with 60 or 120 B channels can be used. This value is also useful if a small STMI with 60 B channels becomes defective. This can then be replaced with a large STMI with 120 B channels.
  • Page 123 General Information on How to Configure a HG 3500 V4 Common Gateway Rules Since the board configuration can only be modified by removing the board, an option has been created that allows users to reserve circuits for use at a later stage. If this feature is to be used for the functions HG3530, HG3540 or HG3550, the relevant function must be configured directly after the actual function (HG3550&HG3550R, for instance).

  • Page 124: Restrictions

    13.5 Overview of Configuration Steps An overview of the configuration steps for a HG 3500 V4 common gateway is provided below: Configure functional blocks with the AMO BFDAT (Assistant: Configuration Management > System Data > Board > CGW Functional Block) Assign the functional block to a board using the AMO BCSU (Assistant: Configuration Management >...

  • Page 125: Hipath Gateway Hg 3500 V4 - Changing Parameters With Amo Cgwb

    The settings can differ from HG 3500 to HG 3500. If the routers do not support DiffServ, the standard TOS value must be configured without DiffServ. If DiffServ is supported, but not the Siemens CodePoints, the value specified by the network operator must be configured.

  • Page 126: Type Asc - Setting The Codec List For Dmc Connections, Rtp Packet Size, And Voice Activity Detection

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE ASC - Setting the Codec List for DMC Connections, RTP Packet Size, and Voice Activity Detection Configuration Management --> System Data --> IPDA --> IPDA System Data Enter settings under Payload Connections on the System Data tab and click Save.

  • Page 127: Type Dsp - Changing The Dsp (Signal Processor) Setting At An Hg 3500

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE DSP - Changing the DSP (Signal Processor) Setting at an HG 3500 Configuration Management --> System Data --> Board --> Board Click Search and select STMI. Make the settings on the STMI Board Data tab under Number of DMC connections and Save.

  • Page 128: Type Globif - Changing The Idle Bit Pattern And Interface-Specific Parameters

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE GLOBIF - Changing the Idle Bit Pattern and Interface-Specific Parameters CHANGE- CGWB:MTYPE=CGW,LTU=5,SLOT=91,TYPE=DSP,JITBUFD=100; These changes are loaded directly to the HG 3500 and become effective immediately without interrupting operation.

  • Page 129: Type Gwsector - Changing The Hg 3500 Sector Number For The Resource Manager

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE GWSECTOR - Changing the HG 3500 Sector Number for the Resource Manager Configuration Management --> System Data --> Board --> Board Click Search and select Board Name=STMI2 or Board Name=STMI4.

  • Page 130: Type Mgntdata

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE MGNTDATA The security concept is based on two mechanisms: When the features are activated, HG 3500 sends a token in each signaling packet (consisting of a password and key, defined in AMO CGWB), to authenticate itself to a receiving HG3550V2 gateway.

  • Page 131: Type Servif - Changing The Login And Password For The Service Access

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE SERVIF - Changing the Login and Password for the Service Access The second IP address BUSIP defines the HBR that is contacted by the HG 3500 at startup during the auto restore.

  • Page 132: Type Jb - Configuring The Jitter Buffer

    HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB TYPE JB - Configuring the Jitter Buffer 14.11 TYPE JB - Configuring the Jitter Buffer As of HiPath 4000 V4, only the adaptive jitter buffer (JBMODE=2) and the static jitter buffer (JBMODE=1) are supported in the HG 3575 V4 gateway.
  • Page 133 HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB Resetting the Parameters to Default Values Note: Existing links are disconnected. DLSDATA DLSIPADR & DLSPORT : become effective after CGW restart DLSACPAS : become effective immediately without interrupting operation A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 &...
  • Page 134 HiPath Gateway HG 3500 V4 - Changing Parameters with AMO CGWB Resetting the Parameters to Default Values A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 135: Codec Settings

    gateways_15_codec.fm Codec Settings HFA and Trunking 15 Codec Settings 15.1 HFA and Trunking A priority list of the codecs is configured in the AMO CGWB for HG 3500, and accordingly in the AMO STMIB for HG 3575. During codec negotiations, the gateways use the codecs configured in this way.

  • Page 136: Ipda

    gateways_15_codec.fm Codec Settings IPDA CHANGE- STMIB:MTYPE=NCUI2,LTU=17,TYPE=ASC,PRIO=PRIO3,CODEC=G729AB,VAD =YES,RTP="40"; CHANGE- STMIB:MTYPE=NCUI2,LTU=17,TYPE=ASC,PRIO=PRIO4,CODEC=G729B,VAD= YES,RTP="20"; CHA-STMIB:MTYPE=NCUI2,LTU=17,TYPE=ASC,PRIO=PRIO5,CODEC=NONE; CHA-STMIB:MTYPE=NCUI2,LTU=17,TYPE=ASC,PRIO=PRIO6,CODEC=NONE; CHA-STMIB:MTYPE=NCUI2,LTU=17,TYPE=ASC,PRIO=PRIO7,CODEC=NONE; 15.2 IPDA For IPDA, the codecs for the master connection are switched by DNIL and configured in AMO SDAT / AMO TDCSU, etc., i.e. in the user/trunk data of the affected devices (see IP Distributed Architecture (IPDA) and Access Point Emergency (APE), Section 4.9, “Configuring Subscriber, CO/Tie Trunk Circuits in...

  • Page 137: Multiple Feature Support Configuration At The Common Gateway (Example)

    gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Important Information Multiple Feature Support Configuration at the Common Gateway (Example) 16.1 Important Information • If the function IPDA (HG3570) is configured on an STMI board, the IP address of the common gateway must be assigned with the AMO BCSU.
  • Page 138 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring Functional Blocks with the AMO BFDAT >>>>> IPDA with 120 B channels CHANGE-BFDAT:CONFIG=CONT,FCTBLK=1,FUNCTION=HG3570,BCHLCNT=120; >>>>> End configuration of this block CHANGE-BFDAT:CONFIG=OK,FCTBLK=1,ANSW=YES; Functional block 2 /* Functional block 2: Adding the functions IPDA (HG3570), IP trunking (HG3550) and HFA sub- scriber (HG3530) ADD-BFDAT:FCTBLK=2,FUNCTION=HG3570&HG3550&HG3530,BRDBCHL=BCHAN;...
  • Page 139 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring Functional Blocks with the AMO BFDAT >>>>> End configuration of this block CHANGE-BFDAT:CONFIG=OK,FCTBLK=3,ANSW=YES; Functional block 4 /* Functional block 4: Adding the functions IPDA (HG3570), IP trunking (HG3550), WAML and HFA subscriber (HG3530) ADD-BFDAT:FCTBLK=4,FUNCTION=HG3570&HG3550&WAML&HG3530,BRDBCHL=BCHAN120;...
  • Page 140 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring Functional Blocks with the AMO BFDAT >>>>> End configuration of block CHANGE-BFDAT:CONFIG=OK,FCTBLK=5,ANSW=YES; Functional block 6 /* Functional block 6: Adding the functions IP trunking (HG3550) and HFA subscriber (HG3530) ADD-BFDAT:FCTBLK=6,FUNCTION=HG3550&HG3530,BRDBCHL=BCHAN120;...
  • Page 141 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring Functional Blocks with the AMO BFDAT -------------------------------------------------------------------------------- | FCTBLK = BRDBCHL: BCHAN120 STATUS= -------------------------------------------------------------------------------- 1st FUNCT : HG3570 1 LINES UNITS ?? BCHLCNT 120 TOTAL BCHAN 120 -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- | FCTBLK = BRDBCHL : BCHL120 STATUS=...

  • Page 142: Configuring The Common Gateway Board With The Amo Bcsu

    gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring the Common Gateway Board with the AMO BCSU 3rd FUNCT : WAML 1 LINES UNITS BCHLCNT TOTAL BCHAN 4th FUNCT : HG3530 140 LINES UNITS 70 BCHLCNT TOTAL BCHAN -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- | FCTBLK =...
  • Page 143 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring the Common Gateway Board with the AMO BCSU 19 | Q2258-X ACGEN 0|*| AVAILABLE | NPR 25 | Q2205-X WAML 0|*| | NPR 31 | AVAILABLE 0| | AVAILABLE 37 | Q2316-X10 STMI2 0|*|...
  • Page 144 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring the Common Gateway Board with the AMO BCSU Assignment for functional block 4 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=43,PARTNO=Q2316-X10,FCTID=1,FCT- BLK=4,IPADDR=198.16.16.43; Assignment for functional block 5 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=49,PARTNO=Q2316-X10,FCTID=1,FCT- BLK=5,IPADDR=198.16.16.49; Assignment for functional block 6 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=55,PARTNO=Q2316-X10,FCTID=1,FCT- BLK=6,IPADDR=198.16.16.55; Assignment for functional block 7 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=61,PARTNO=Q2316-X10,FCTID=1,FCT- BLK=7,IPADDR=198.16.16.59;...
  • Page 145 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring the Common Gateway Board with the AMO BCSU 3rd FUNCT : STMI-HFA2 60 LINES B-CHANNELS : BCHLCNT : +--------------------------------+-+------------+------------+------------ 37 | Q2316-X10 STMI2 0|*| | NPR +--------------------------------+-+------------+------------+------------ | IP ADDRESS : 198. 16. 16. 37 B-CHANNELS : 120 BCHLCNT : 120 | BLOCK NO...

  • Page 146: Configuring Sip Trunking

    gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Configuring SIP Trunking 1st FUNCT : STMI2-IPGW 1 LINES B-CHANNELS : BCHLCNT : 2nd FUNCT : STMI-HFA2 90 LINES B-CHANNELS : BCHLCNT : +--------------------------------+-+------------+------------+------------ 61 | Q2316-X10 STMI2 0|*| | NPR +--------------------------------+-+------------+------------+------------ | IP ADDRESS : 198.

  • Page 147: Completed And Uncompleted Functional Block

    gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Completed and Uncompleted Functional Block 16.4 Completed and Uncompleted Functional Block 16.4.1 Uncompleted functional block /* Functional block 4: Adding the functions IPDA (HG3570), IP trunking (HG3550), WAML and HFA subscriber (HG3530) ADD-BFDAT:FCTBLK=4,FUNCTION=HG3570&HG3550&WAML&HG3530,BRDBCHL=BCHAN120;...

  • Page 148: Completed Configuration Block

    gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Completed and Uncompleted Functional Block Assignment for functional block 4 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=43,PARTNO=Q2316-X10,FCTID=1,FCT- BLK=4,IPADDR=198.16.16.43; H500: AMO BCSU STARTED F89: THE GIVEN FUNCTIONAL BLOCK IS NOT COMPLETELY CONFIGURED. PLEASE FINISH CONFIGURATION BY MEANS OF AMO_BFDAT FIRST. AMO-BCSU -54 BOARD CONFIGURATION, SWITCHING UNIT ADD NOT COMPLETED;...
  • Page 149 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Completed and Uncompleted Functional Block Assignment for functional block 4 ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=43,PARTNO=Q2316-X10,FCTID=1,FCT- BLK=4,IPADDR=198.16.16.43; H500: AMO BCSU STARTED H01: BD 1.1 . 43 ASSIGNED AMO-BCSU -54 BOARD CONFIGURATION, SWITCHING UNIT ADD COMPLETED; A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 &...
  • Page 150 gateways_16_multiple_feature_sup.fm Multiple Feature Support Configuration at the Common Gateway (Example) Completed and Uncompleted Functional Block A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 151: Command Line Interface Cli In Hg 3500

    gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 General Information 17 Command Line Interface CLI in HG 3500 17.1 General Information The common gateway supports a Command Line Interface (CLI) for installation and basic configuration, e.g. IP infra structure. In V.24 CLI it is possible to change security relevant data (e.g.

  • Page 152: Access Control

    gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 Access control 17.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.

  • Page 153: Image/File Handling

    gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 Image/File Handling ip subnet mask The parameter <ip subnet mask> is a string in the form of x.x.x.x and x is an integer between 0 and 255 (e.g. 255.255.255.224). 17.5 Image/File Handling In common gateway software configuration and distribution as well as upload and download of configuration data via CLI is not required because it is done via WBM.
  • Page 154 gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 Maintenance • Display of the IP address and subnetmask for the ethernet port: show ip address show ip subnet • Showing the time will display the time and the date: show time •...

  • Page 155: Ssl For Wbm

    gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 SSL for WBM • Normal reboot of the gateway, using the current configuration data: reset • Reset any configuration data to factory defaults and reboot: reset factory • Special reboot of the gateway using an existing self-extracting image in order to complete a software download: activate software 17.7 SSL for WBM...
  • Page 156 gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 Three security settings are available under PIN Mode for creating a virtual device in the DLS: – No PIN, – Default PIN, – Individual PIN. See also Chapter 11, “DLS Client Bootstrapping”. If you set dls pin_required to TRUE in the gateway, the gateway declines a connection if No PIN is set in the DLS.

  • Page 157: Changing The Login And Password For Wbm/Cli

    gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 Changing the Login and Password for WBM/CLI Otherwise, you can use contact dls to test if communication is possible between the gateway and DLS server. An appropriate message appears. A PIN is not needed. "No PIN" is set as the PIN mode in the DLS. A PIN is needed.
  • Page 158 gateways_17_cli_hg3500v4.fm Command Line Interface CLI in HG 3500 Changing the Login and Password for WBM/CLI vxTarget> <LW-version> <LW-version> holds the currently loaded loadware version number (e.g. L0- TOS.10.030-004) A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 159: Command Line Interface Cli At Hg 3575 V4

    gateways_18_cli_hg3575v4.fm Command Line Interface CLI at HG 3575 V4 18 Command Line Interface CLI at HG 3575 V4 Please refer to IP Distributed Architecture (IPDA) and Access Point Emergency (APE), Chapter 1, “Local Access Point Administration at CLI via Terminal”. A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 &...
  • Page 160 gateways_18_cli_hg3575v4.fm Command Line Interface CLI at HG 3575 V4 A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 161: Snmp Support Hg 3500 / Hg 3575

    The HiPath HG 3500 module supports the request of data via SNMP. Figure 19 shows the MIB tree. internet directory experimental private snmpV2 mgmt enterprises mib-2 4329 siemens system iandcProducts interfaces iandcAdmin cg2500 11 nbcs icmp 11 snmp 31 ifMIB Figure 19...
  • Page 162 gateways_19_snmp.fm SNMP Support HG 3500 / HG 3575 – (5) ICMP Group (RFC2011) – (6) TCP Group (RFC2012) – (7) UDP Group (RFC2013) – (11) SNMP Group (RFC1213) – (31) ifMIB Group (RFC2233) MIB-ASC: Implemented MIB objects: • ASC Statistics Group (ascStats) Implemented objects: { asc 1 } ascStatsOverall OBJECT-TYPE ::= { ascStats 1 }...
  • Page 163 gateways_19_snmp.fm SNMP Support HG 3500 / HG 3575 A unique value for each interface. Its value ranges between 1 and the value of ascMaxCalls ascPeerCanonicalName OCTET STRING, NPCI value for the call ascDestIP OCTET STRING, The destination IP address (of corresponding HG 3500/3575) ascBeginTime OCTET STRING, When the last call started...
  • Page 164 gateways_19_snmp.fm SNMP Support HG 3500 / HG 3575 • ASC Config Group (ascConfig) not relevant for IPDA components Implemented objects: { asc 2 } ascUdpPortLow OBJECT-TYPE ::= { ascConfig 1 } Low boundary of RTP/RTCP ports ascUdpPortHigh OBJECT-TYPE ::= { ascConfig 2 } High boundary of RTP/RTCP ports ascTcpPortLow OBJECT-TYPE ::= { ascConfig 3 }...
  • Page 165 To make the ASC-MIB known to an MIB browser, the following files are required: • smi_nbcs.my • mibasc.my These files are available in KMOSS (Knowledge Management for Operational Support and Service) under https://kmoss.icn.siemens.de. A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...
  • Page 166 SNMP Support HG 3500 / HG 3575 Select KMOSS public and search for INF-05-000733 in the Enterprise section. Or click the following link: https://kmoss.icn.siemens.de/livelink/llisapi.dll/view/INF-05-000733 A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 167: Ip Ports

    gateways_20_ports.fm IP Ports General Information 20 IP Ports 20.1 General Information The port assignments are available in the Interface Management Database (IFMDB): https://apps.g-dms.com/ifm/ IP trunking + DMC (IP trunking and IPDA) master connections The UDP port range is configured with the AMO CGWB for IP trunking master connections and DMC slave connections where HG 3500 is a DMC endpoint (i.e.

  • Page 168: Examples

    gateways_20_ports.fm IP Ports Examples The UDPPORT parameter in the AMO SIPCO applies similarly for DMC slave connections where NCUI2+/NCUI4 is the DMC endpoint. The following ports are automatically used. Maximum port number for a board with 120 B channels: With DMC: up to 100 ports for the master connections + up to 100 ports for the associated DMC connections =>...

  • Page 169: Signaling

    gateways_20_ports.fm IP Ports Examples Peripheral 3575 Boards 3500 AP 17 4352 .. 4599 uses ports 3500 Control CC-A/CC-B Peripheral 3575 Boards HiPath 4000 AP 35 in addition port 4007 must be available 4352 .. 4599 uses ports port 4007 can be used Figure 20 Example: Port usage for payload 20.2.2 Signaling...

  • Page 170: Snmp

    gateways_20_ports.fm IP Ports Examples Peripheral 3575 Boards AP 17 3500 3500 Peripheral 3575 Boards Control CC-A/CC-B AP 35 1124 or 1125 <-> 4000 signaling **) ISDN HiPath 4000 Modem Router 1128 or 1129 <-> 4002 modem test *) *) Only if signaling survivability is configured **) Only if signaling supervisory is active Figure 21 Example: Port usage for signaling...

  • Page 171: Diagnostics

    gateways_20_ports.fm IP Ports Examples 20.2.4 Diagnostics Additional services that are normally inaccessible (ports blocked) can be activated on the gateways HG 3500 and HG 3575 for fault diagnosis. These are Port 22 HTTPS/WBM: Port 443 Web server for accessing diagnostic data Access can only be modified with the parameter FACCMODE (Facility Access Mode) in the DEBUG branch of the AMO STMIB (for HG 3575 only).
  • Page 172 gateways_20_ports.fm IP Ports Examples A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 173: Hg 3500 / Hg 3575 Diagnostic Options

    gateways_21_diagnosis.fm HG 3500 / HG 3575 Diagnostic Options 21 HG 3500 / HG 3575 Diagnostic Options All diagnostic options for the gateways HG 3500 and HG 3575 are part of the WBM. The trace components can be configured in WBM. More information is provided in the WBM online help.
  • Page 174 gateways_21_diagnosis.fm HG 3500 / HG 3575 Diagnostic Options A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

  • Page 175: Frequently Asked Questions

    gateways_22_faq.fm Frequently asked Questions 22 Frequently asked Questions 4. Question: Are HG 3500 gateways supported on the Hicom 300 H? Answer: No. Customers have to upgrade to HiPath 4000 V4 or higher in order to take advantage of integrated IP gateways. 5.
  • Page 176 gateways_22_faq.fm Frequently asked Questions 10. Question: The maximum value that can be set for the jitter buffer is 210 ms. I assume that the system works properly with this setting. Can I specify this value in my WAN tender specification as a carrier requirement? Answer: The system has no problems with a 210 ms jitter buffer.
  • Page 177 gateways_22_faq.fm Frequently asked Questions Answer: The standard solution for this problem which is principally an address resolution issue is also implemented on the HG 3500 and HG 3575 gateways. After activating the hardware interface, the gateway sends an ARP request “gratuitous ARP“ to the actual IP address. This way, all IP devices on the LAN segment learn the new IP <->...
  • Page 178 gateways_22_faq.fm Frequently asked Questions ! COUNT4 ! Byte4 +----------+--------+----------+----------+----------+----------+----------+ Details on the AMO PSTAT can be found in the AMO description in the HiPath 4000 Service Manual. Modifying the statistics prevents the boards from being reset when quality problems that affect the overall function of the system occur in the IP network. Your objective must be get these problems under control.

  • Page 179: Index

    Traffic Considerations 40 Gateways-Communication Matrix 59 VAD 33, 53 Goal of this document 5 Voice Activity Detection (VAD) 33 Voice encryption devices 26 HG 3500 V4 Voice Quality 12 DLS client bootstrapping 103 exchanging modules 42 HG3500 load concept 69...
  • Page 180 gatewaysSIX.fm Index Nur für den internen Gebrauch A31003-H3150-S104-2-7620, 03/2009 HiPath 4000 V5, IP Solutions - HG 3500 & HG 3575, Service Documentation...

This manual is also suitable for:

Hg 3575 v4

Table of Contents