SIP Subscriber Siemens

SIP Subscriber

Contents
1 SIP Subscriber Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Feature Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Call Features on the SIP Subscriber. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 SIP subscriber communication matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Direct Media Connect (DMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5 Overview Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.6 Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.6.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.7 AMO Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.2 STMI2 Board Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7.3 Configuring an SIP Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.7.4 Removing an SIP Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.7.5 Changing an SIP Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.7.6 Enabling/Disabling DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.8 Relevant AMOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.9 Settings at the SIP Terminal optiPoint 410/420 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.9.1 Required settings for the terminal without DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.9.2 Settings via the WBM of the terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.9.3 Settings via the Deployment Service (DLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.10 Settings at the SIP terminals optiPoint 150 S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.10.1 Required settings for the terminal without DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.10.2 Settings via the WBM of the terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.11 Display of the registered SIP Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

1
EN2409EN00EN_0001
© 2005 Siemens AG
 Siemens SIP Subscriber

2 optiClient 130 V5.0 SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.2 Installation and settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.3 Generating of the optiClient 130 V5.0 in the HiPath 4000 V2.0. . . . . . . . . . . . . . . . . . . 63

2
EN2409EN00EN_0001
© 2005 Siemens AG
SIP Subscriber Support Siemens

1 SIP Subscriber Support

1.1 Feature Description

The feature "SIP Subscriber Support for HiPath 4000 V3.0" encompasses the operation of SIP
endpoints (optiPoint family, optiClient, AP1120, MS Messenger), which can be run on a HiPath
4000 V3.0 system using a HG3540 board. The HG3540 is an STMI2 module configured with
functional ID 2/5 and which is used as a SIP Gateway.
The operation of SIP endpoints on IPDA shelves is also supported.
In terms of subscriber support, the operation of HFA stations that run on an HG3530 board is
possible.
In both call directions, this feature encompasses
● G.7xx audio calls
– from SIP to SIP
– from SIP to HFA
– from SIP to TDM
● G.711 transparent FAX/MODEM calls
– from SIP to SIP
– from SIP to HFA
– from SIP to TDM

1.2 Call Features on the SIP Subscriber

The supported features for SIP subscribers are:
● CLIP/CLIR
● COLP/COLR
● HOLD/RETRIEVE
● ATTENDED TRANSFER.
All other features that are offered by the SIP subscribers but require board support do not work.
All feature events (with the exception of those referred to above) from the system’s call process-
ing are rejected.

3
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

Menu items in an SIP subscriber menu that are not supported:

● Call deflect
● Call forwarding
● Park
● Call pickup
● Call transfer(= blind transfer)
● Local conference
● Message waiting

1.3 SIP subscriber communication matrix

SIP HFA HP3k/5k HiPath 3k/ PSTN

subscriber subscriber H.323 4k TDM subscriber
standard subscriber
subscriber
SIP subscriber (BC) (BC)
HFA subscriber N/I N/I N/I N/I
HP3/5k H.323 (BC) N/I N/I N/I N/I
standard subscriber
HiPath 3/4k TDM N/I N/I N/I N/I
subscriber
PSTN subscriber (BC) N/I N/I N/I N/I
Table 1-1 SIP subscriber communication matrix

4
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

1.4 Direct Media Connect (DMC)

One major function on the LAN side is "direct payload" (DMC Direct Media Connect) be-
tween the call parties. This function can be activated/deactivated for all SIP endpoints.
Direct payload transmission between SIP subscribers and other IP devices and gateways is
always desirable (due to better voice quality) . To facilitate this the HG3540 has been extended
to include a “DMC Proxy”,this is required as SIP subscribers do not support the H.323-based
DMC procedure. As far as DMC signaling is concerned, the gateway functions on behalf of the
SIP subscriber and converts the DMC signaling into SIP signaling.
For HFA subscribers the DMC connection is shown in the following diagram

Anate/TDM phone

HG3530 HG3550 V2.0 HG3550 V2.0

H323 IP Trunk

HFA Subscriber Slave Signalling Master Signalling

Slave Payload Master Payload

This figure shows the situation for an HFA subscriber calling a TDM subscriber in another node
via an H323 IP Trunk. The master connection for both signalling and payload is maintained via
the HG3530 and both HG3550 gateways. The Slave connections are the DMC conections and
these are between IP endpoints, on the one side the HFA subscriber and on the other side the
HG3550 board

5
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

The situation is different with the SIP Subscriber The transport addresses (IP addresses/ports)
for payload transmission are transmitted as part of the DMC signaling. The DMC proxy does
not transmit the actual transport address in this case, but instead transmits the address of the
addressed SIP subscriber in order to facilitate a direct RTP stream for the SIP subscriber.
Given the fact that H.323 and SIP both use RTP for voice transmission,connection between
H323, SIP and HFA subscribers, HG357x, HG3550, HG3540, HG1500 gateways is possible.
To set up a standards-compliant payload channel for the SIP subscriber, the SIP re-invite and,
preferably (provided the subscribers support it), the SIP update procedures are used (the latter
also requires SIP-PRACK support). These procedures make it possible to switch a payload
connection over to another destination. Unlike previous DMC endpoints, the "master" payload
connection to HiPath is not maintained in this case – i.e. the DMC payload connection replaces
the master connection. However, the "master" signaling for the HiPath remains established.
This is illustrated in the figure below:

Anate/TDM phone
Node 200 Node 300

HG3540-Sub HG3540-Trk HG3540 -Trk

SIP IP Trunk

SIP Subscriber Slave Signaling Master Signaling

Slave Payload Master Payload

The HG 3540-Subscriber board functions as a DMC proxy in this scenario. DMC payload is
sent between the SIP phone in node 200 and an HG 3540-Trunking in Node 300.DMC signal-
ing is between the HG 3540-Subscriber board and the HG 3540-Trunking board.

6
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

A distinction is made between the DMC proxy and the DMC endpoint. The latter is the endpoint
for DMC signaling and the DMC payload channel (RTP) and is used in HiPath 4000 V2.0. Both
gateways (HG 3550, HG 357x) and subscribers function as DMC endpoints. HG3540 in node
300 and the SIP phone are therefore DMC endpoints in the diagram.
Note that the HG 3540 in node 200 in this example is not part of a payload connection. How-
ever, a DSP is reserved for the connection in case activation of a feature terminates the DMC
and causes a fallback to the master connection. When the DMC is terminated, a master pay-
load connection must be renegotiated by SIP re-invite, as the connection does not exist for the
SIP subscriber.
Given the fact that the SIP subscribers are themselves not DMC-capable, we no longer talk
about DMC connections in HiPath 4000 V3.0, but instead more generally about an end-to-end
payload connection, or e2epc for short.
Setup of the master connection, which leads to a master payload connection between the call-
ing SIP endpoint and HG 3540 (requested in order to transmit announcements and tones from
the HiPath to the SIP endpoint) is not displayed. As is the case in HiPath 4000 V2.0, the DMC
is initiated by the called party, dependent on classmarks.
The procedure described above is even used for a call between two SIP subscribers, i.e. an
H.323-based DMC is set up from HG 3540 to HG 3540 (or internally if both subscribers are reg-
istered on the same gateway). A direct connection between HiPath 4000 SIP subscribers with-
out DMC is not possible at present.
The following diagram illustrates the possible scenarios in which an SIP subscriber is involved
in an e2epc, for example DMCs to HFA and SIP stations in the same (or in a different) node,
and DMCs to IPDA and IP trunking cards - the latter functioning as DMC endpoints.

7
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

The following connectivity is possible:

1. SIP station on HiPath 4000: DMC signaling between the HG 3540s (or internally, if both
are on the same gateway), e2epc between the stations, which replaces the master payload
connection to the gateway

HiPath 4000 V3.0

HG3540

The B channel of the DSP stays re- SIP Sub

served in case a SIP phone activa- master signalling
connection
tes a feature.
The SIP phone must do a re-invite master signalling-
connection
message, as that the master con-
nection does not exist.
SIP-Phone

SIP-Phone
e2epc end to end
payload connection

master signalling slave signalling

master payload slave payload

8
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

2. HFA station on HiPath 4000: DMC signaling between HG 3540 and HFA subscriber, e2epc
between the stations. A master payload connection to the HG 3530 is retained

The B channel of the DSP stays re-

HiPath 4000 V3.0 served in case a SIP phone activa-
tes a feature.
The SIP phone must do a re-invite
HG3530 HG3540 message, as that the master con-
nection does not exist.
HFA Sub SIP Sub

master signalling
connection
master signalling slave signalling
payload connection

SIP-Phone

HFA-Phone e2epc end to end

payload connection

master signalling slave signalling

master payload slave payload

9
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

3. TDM network/subscriber behind a remote shelf of a HiPath 4000: DMC signaling between
HG 3540 and HG 3575, e2epc between SIP subscriber and HG 3575

The B channel of the DSP stays re-

HiPath 4000 V3.0 served in case a SIP phone activa-
tes a feature.
The SIP phone must do a re-invite
HG3540 message, as that the master con-
HG3570 nection does not exist.
SIP Sub

master- signalling
connection
maste signalling
payload
slave signalling
connection SIP-Phone

e2epc end to end

payload connection

HG3575

TDM
HiPath 4000 V3.0 - AP-IP

master signalling slave signalling

master payload slave payload

10
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

4. TDM network/subscriber on another HiPath 4000: DMC signaling between HG 3540 and
HG 3550, e2epc between SIP subscriber and HG 3550

HiPath 4000 V3.0 HiPath 4000 V3.0

master
signalling & payload
HG3540 HG3550 HG3550

SIP-Sub Trunk Trunk

master signalling- TDM

connection slave signalling
connection

e2epc end to end

payload connection

SIP-Phone

master signalling slave signalling

master payload slave payload

11
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

5. HFA station of a HiPath 3000: as per b), whereby DMC is initiated by HiPath 4000 and the
master signaling runs via HG 1500

HiPath 4000 V3.0 HiPath 3000 V6.0

HG3540 HG3540 HG1500

master signalling

SIP-Sub SIP-Trunk SIP

master payload
master signalling
connection slave signalling-
connection

e2epc end to end

payload connection HFA-Phone

SIP-Phone

master signalling slave signalling

master payload slave payload

12
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

6. SIP station on HiPath 3000: DMC signaling between HG 3540 and HG 1500 (initiated by
HiPath 4000), e2epc between SIP subscribers.

HiPath 4000 V3.0 HiPath 3000 V6.0

HG3540 HG3540 HG1500

master signalling

SIP-Sub SIP-Trunk SIP

slave signalling
master signalling connection
connection

e2epc end to end

payload connection HFA-Phone

SIP-Phone

master signalling slave signalling

master payload slave payload

13
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

7. H323 subscriber on HiPath 3000: DMC signaling between HG 3540 and HG 1500 (initiated
by HiPath 4000), e2epc between SIP subscriber and HG 1500, then via the HiPath 3000
memory time switch to HG 1500, and then to the H323 subscriber by RTP. Replaces the
master connection between the H323 subscriber and HG 3550.

HiPath 4000 V3.0 HiPath 3000 V6.0

HG3540 HG3540 HG1500

master signalling

SIP-Sub SIP-Trunk SIP

slave signalling-
connection
master signalling- master payload
connection

e2epc end to end H323

payload connection

SIP-Phone

master signalling slave signalling

master payload slave payload

SIP station on HiPath 4000 to

14
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

1. SIP station on HiPath 4000: DMC signaling between the HG 3540s (or internally, if
both are on the same gateway), e2epc between the stations, which replaces the mas-
ter payload connection to the gateway
2. HFA station on HiPath 4000: DMC signaling between HG 3540 and HFA subscriber,
e2epc between the stations. A master payload connection to the HG 3530 is retained
3. TDM network/subscriber behind a remote shelf of a HiPath 4000: DMC signaling be-
tween HG 3540 and HG 3575, e2epc between SIP subscriber and HG 3575
4. TDM network/subscriber on another HiPath 4000: DMC signaling between HG 3540
and HG 3550, e2epc between SIP subscriber and HG 3550
5. HFA station of a HiPath 3000: as per b), whereby DMC is initiated by HiPath 4000 and
the master signaling runs via HG 1500
6. SIP station on HiPath 3000: DMC signaling between HG 3540 and HG 1500 (initiated
by HiPath 4000), e2epc between SIP subscribers
7. H323 subscriber on HiPath 3000: DMC signaling between HG 3540 and HG 1500 (in-
itiated by HiPath 4000), e2epc between SIP subscriber and HG 1500, then via the Hi-
Path 3000 memory time switch to HG 1500, and then to the H323 subscriber by RTP.
Replaces the master connection between the H323 subscriber and HG 3550.

15
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

16
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

1.5 Overview Screen

The following overview screen illustrates the entire implementation scenario for the described
feature.

1.6 Service Information

1.6.1 General information

Up to 120 SIP endpoints can be configured on a HG3540 board,these can be spread across
all available ports or configured on one port..
For example of a Q2316-x (60 channels):
or
no 100% availability 100% availability
Port 1 can be used for SIP- Port 0:
Trunking 30 SIP phones are configu-
red;

Port 0: Port 1:
120 SIP phones are config- 30 SIP phones are configu-
ured; red;

17
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

Restrictions:
● When HG3540 operates with mixed IP Trunking and SIP Subscriber on the same board
then the trunk must always be configured on Port 0
● For codec G.729 there is one restriction.
The WBM interface allows you to configure all codecs from the G.729 family (G.729,
G.729A, G.729B and G.729AB). Only the highest priority codec is used for SIP signaling.
● The "T.38" menu item must be deactivated.
● RFCs 2833 (DTMF via RTP) and 2198 (support of redundant audio data) are supported.
● SIP subscribers cannot register if H323 is set as the IP trunking protocol (AMO STMIB, pa-
rameter TRKPROT=H323). SIP subscribers can only run on an HG 3540 card, for which
the parameter TRKPROT equals NONE or SIP.
If the board is operated in mixed mode with SIP Trunks and Subscribers,then TRKPROT
must be set to SIP.
● The following table shows the combinations of the parameters SECZONE,USERID and
PASSWD in AMO SBCSU to make secure registration possible.

Parameter SECZONE USERID PASSWD Possible

Set Set Set Yes
Not Set Set Set Yes
Set Not Set Set Yes
Not Set Not Set Set Yes
Set Not Set Not Set No
Not Set Set Not Set No
Set Set Not Set No
Not Set Not Set Not Set Yes
Table 1-2

● For optiPoint 410 and 420

● SIP terminals are not known to the Deployment Tool. This means that the configura-
tion and loading of software,amongst others is now only possible via the WBM or the
DLS.

18
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

● To reach the "Configuration Menu" of the terminal follow the following steps.
From the Menu prompt press the right arrow key until menu point 5=setup? ->enter -
> in the display 02=configuration? is seen. Press 6 from the dial pad (this is not seen
from the menu) -> “enter admin password” is displayed,the standard admin password
is 123456.
● To reset a terminal, a “Delivery status” can be executed via the “Configuration
Menu”. From menu point 05=Setup -> 03=Local Functions -> 04=Memory -> 02=De-
livery Status ->Clear ->enter .The telephone can also be reset by removing the Lan ca-
ble,lifting the handset and pressing the combination 2,8,and 9 simultaneously,The re-
set password is required, the Reset password is “124816”.
● If the device is in Delivery status reset mode then no input in the administration menu
is possible for around 1 minute.
● The Language settings for the terminal are found from the Administration menu
05=Setup ->2 Configuration ->01 Country Options(setting the time)->02=Language.
● To restart a terminal, press the key combination 1, 4 and 7 simultaneously and enter
the Administration password (standard 123456).

● For optiPoint 150 S

● Selecting the "Configuration menu" of the terminal: Use menu key !, push arrow
key ! until menu 5.Settings appears -> Enter key . For the submenus Network, SIP,
NTP and Reset (=Factory Reset) use the standard password 123456.
● To reach the delivery state (Factory Reset) of the terminal, use the menu key ! and
menu 5.Settinges -> 5.Reset -> Password “123456”.
● To Restart a terminal use the menu key ! and the menu 7.Restart.
● To set the language and the country setting use the menu key ! and the menu 5.Set-
tings -> 1.User -> 3.Language and 4.Country.

19
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

1.7 AMO Usage

1.7.1 Configuration

Pen: 1-1-49 Security zone:

IP: 1.40.41.105 HIPATH4000.COM optiPoint IP
Subnet mask: 255.255.255.0
Default Gateway: 1.40.41.254
Station: 4420

Fix IP: 1.40.41.12

User-ID: USER 1
HG3540
Password: SECRET
LAN

optiPoint IP
HiPath 4000 V3.0

Station: 4421

Fix IP: 1.40.41.13

optiPoint IP optiPoint IP User-ID: USER 2
Password: known

Station: 4422 Station: 4423

Fix IP: ------------- Fix IP: -------------

User-ID: USER 3 User-ID: -----------
Password: unknown Password: --------

DHCP-Server

20
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

1.7.2 STMI2 Board Configuration

The Board can be added with FCTID = 2 or. 5 .

ADD-BCSU:TYPe=PER,LTG=1,LTU=1,SLOT=49,PARTNO="Q2316-X ",
FCTID=2,LWVAR="0",HWYBDL=A,ALARMNR=0;
ADD-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,CUSIP=1.40.41.105,
SNETMASK=255.255.255.0;
CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=IFDATA,
DGWIP=1.40.41.254,VLAN=NO,VLANID=0;

The Trunking-Protocol must be set to NONE or SIP.

● NONE = only SIP Subscriber operate on the Board;
● SIP = For Mixed operation of SIP Subscriber and SIP Trunking;
CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=GLOBAL,
PATTERN=213,TRKPROT=NONE;

The Parameter GWAUTREQ and SIPREG must be set to NO,in situations where the
board is used for SIP Subscriber.
CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=SIPTRERH,
GWAUTREQ=NO;
CHNGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=SIPTRSSA,
SIPREG=NO;

21
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

1.7.3 Configuring an SIP Endpoint

If the parameters SECZONE, USERID and PASSWD are used for a secure regis-
tration in the AMO SBCSU, the parameter AUTHREQ is set to YES and the security
data must be set also in the SIP terminal !

The used COS class must have the classmark MSN !

For the settings in the AMOs see the configuration.

ADD-SBCSU:STNO=4420,OPT=FPP,CONN=SIP,PEN=1-1-49-0,
DVCFIG=S2PP,COS1=1,COS2=1,LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1,
PROT="SBDSS1",OPTIDX=10,IPADDR=1.40.41.12,PASSWD="SECRET",
USERID="USER 1",SECZONE="HIPATH4000.COM",FIXEDIP=YES,
AUTHREQ=YES,SMGSUB=NO;
ADD-SBCSU:STNO=4421,OPT=MSN,MAINO=4420,COS1=1,COS2=1,LCOSV1=1,
LCOSV2=1,LCOSD1=1,LCOSD2=1,IPADDR=1.40.41.13,PASSWD="known",
USERID="User 2",SECZONE="HIPATH4000.COM",FIXEDIP=YES,
AUTHREQ=YES,SMGSUB=NO;
ADD-SBCSU:STNO=4422,OPT=MSN,MAINO=4420,COS1=1,COS2=1,LCOSV1=1,
LCOSV2=1,LCOSD1=1,LCOSD2=1,PASSWD="unknown",USERID="User 3",
FIXEDIP=NO,AUTHREQ=YES,SMGSUB=NO;
ADD-SBCSU:STNO=4423,OPT=MSN,MAINO=4420,COS1=1,COS2=1,LCOSV1=1,
LCOSV2=1,LCOSD1=1,LCOSD2=1,FIXEDIP=NO,AUTHREQ=NO,SMGSUB=NO;

1.7.4 Removing an SIP Endpoint

DELETE-SBCSU:STNO=4421&&4423,SVC=MSN;
DELETE-SBCSU:STNO=4420,SVC=ALL;

22
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

1.7.5 Changing an SIP Endpoint

The SIP endpoint data is changed under branch "OPT=FPP"

CHANGE-SBCSU:STNO=4420,OPT=FPP,IPADDR=1.40.41.15,FIXEDIP=YES;
CHANGE-SBCSU:STNO=4421,OPT=FPP,IPADDR=1.40.41.16,FIXEDIP=YES;
CHANGE-SBCSU:STNO=4422,OPT=FPP,IPADDR=1.40.41.5,FIXEDIP=YES;
CHANGE-SBCSU:STNO=4423,OPT=FPP,PASSWD=SECRET3,AUTHREQ=YES;

1.7.6 Enabling/Disabling DMC

DMC is enabled for station 4420 and 4421,it is disabled for station 4422 and 4423.
CHANGE-SDAT:STNO=4420&4421,TYPE=ATTRIBUT,AATTR=DMCALLWD;
CHANGE-SDAT:STNO=4422&4423,TYPE=ATTRIBUT,DATTR=DMCALLWD;

23
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

1.8 Relevant AMOs

The following parameters are relevant for the "SIP Subscriber Support for HiPath 4000 V3.0"
feature:

AMO Parameter Sprache/ Beschreibung/ Description

Language
SBCSU ART=FPP d Hauptrufnummer des S0-/S2-Punkt zu Punkt An-
schlusses
OPT=FPP e Functional point-to-point connection
ANSCHL=SIP d Anschlussart=SIP
CONN=SIP e Kind of connection=SIP
GERKON=S2PP d S2-Punkt zu Punkt Anschluss
DVCFIG=S2PP e S2-point-to-point
PROT=SBDSS1 d Protokollvariante DSS1
PROT=SBDSS1 e Protocol variant DSS1
OPT=10 d Optiontabellenindex 10
OPTIDX=10 e Option table index 10
IPADR d IP-Adresse
IPADDR e IP address
PASSWD d Passwort
PASSWD e Password
KENNUNG d Benutzerkennung
USERID e User ID
SECBER d Security-Bereich (Art Domäne)
SECZONE e Security zone (kind of a Domain)
FESTEIP d Feste IP-Adresse
FIXEDIP e Fixed IP address
AUTHERF d Authentifizierung erforderlich
AUTHREQ e Authentification required
SMGTLN d SMG Teilnehmer;
Für Survivability-Lösung mit der H8k;
SMGSUB e SMG subscriber
For survivability solution with H8k;

24
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Support Siemens

AMO Parameter Sprache/ Beschreibung/ Description

Language
SDAT EMERK d Teinehmermerkmal einfügen
AATTR e Add attribute
AMERK d Teinehmermerkmal ausfügen
DATTR e Delete attribute

25
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber Support

26
EN0000DE00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

1.9 Settings at the SIP Terminal optiPoint 410/420

The terminal settings can be done via the configuration menu at the terminal or via WBM (WEB
Based Management) or via the DLS (Deployment Servive).
In this document only the basic steps via the WBM and via the DLS of the new optiPoint SIP
software of the terminal are described. For detailed information please use the Administration/
User manual.

1.9.1 Required settings for the terminal without DHCP

If the customer has no DHCP server, DHCP must be switched off at the terminal and
the appropriate IP data have to be enterd.
Change to 05=Setup -> Press key 6 at the number block -> Enter the Administration Pass-
word “123456” (standard)

Administration: Enter
01 = Network?

Network: On Enter
01 = DHCP IP assign?

Switch DHCP to OFF and confirm with the Enter key.

Change to 02 = Terminal IP addr.:

Network: 0.0.0.0
02 = Terminal IP addr.? > Enter

Change to 03 = Terminal mask:

Network: 0.0.0.0 Enter

03 = Terminal mask? >

27
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

Change to 04 = Default route:

Network: 0.0.0.0 Enter

04 = Default route? >

Change to 06 = QoS:

Network: Enter
06 = QoS ? >

The further settings are described in this documentation via the WBM of the terminal and via
the DLS. They are also valid using DHCP.

28
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

1.9.2 Settings via the WBM of the terminal

Procedure:
Administration -> System -> SIP Environment

Subscriber
number from AMO
SBCSU

SIP Routing must

be set to Server

IP address (CUSIP) of the HG3540 (STMI2) from

AMO STMIB with Port number 5060

29
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

SIP Port must be

set to 5060 and
RTP Base Port to
5004.

SIP transport must

be set to UDP and
SIP server type to
Other.

The following description shows the association to the H4k generating, if secu-
rity data for the registration on the HG3540 Gateway should be used:

SIP realm -> Entry in parameter SECZONE in AMO SBCSU

SIP user ID -> Entry in parameter USERID in AMO SBCSU
New SIP password and Confirm SIP password -> Entry in parameter PASSWD
in AMO SBCSU

30
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

Procedure:
Administration -> Speech

If a Deployment Service Server (DLS) is used and this server IP address is not set via the
DHCP server, the IP address must be set via the WBM for the terminal.
Procedure:
Administration -> Configuration Management... -> Settings

31
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

Depending on the custumer situation, the Quality of Service settings must be performed (is
possibly already be set in the terminal via the configuration menu without DHCP).
Standard settings are: L2 and L3 are set to ON.
Procedure:
Administration -> Quality of Service

32
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

1.9.3 Settings via the Deployment Service (DLS)

1. Scanning workpoints

1.

2.

3.

4.

33
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

5.

34
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

2. Setting workpoint configuration

35
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

The following description shows the association to the H4k generating, if secu-
rity data for the registration on the HG3540 Gateway should be used:

SIP realm -> Entry in parameter SECZONE in AMO SBCSU

SIP user ID -> Entry in parameter USERID in AMO SBCSU
New SIP password and Confirm SIP password -> Entry in parameter PASSWD
in AMO SBCSU

36
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

Codec settings

37
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

QoS settings

38
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

1.10 Settings at the SIP terminals optiPoint 150 S

The settings for the terminal can be done via the configuration menu of the phone Menu 5.Set-
tings or via the WBM (WEB Based Management). The Deployment Service does not support
the optiPoint 150 S terminal.
In this document only the basic steps via the WBM of the new optiPoint SIP software of the ter-
minal are described. For detailed information please use the Administration respectively User
manual.

1.10.1 Required settings for the terminal without DHCP

If the customer has no DHCP server, DHCP must be switched off at the terminal and
the appropriate IP data have to be enterd.
Menu key ! -> change with the arrow key ! to Menu 5.Settings -> Enter key -> with
arrow key ! to Menu 2.Network -> “123456” -> 1.Mode -> with Enter key

Enter key -> change from

1.Mode ! DHCP to Static IP and chan-
DHCP ge with the arrow key! to the
next settings.

2.IP Address Enter key -> enter IP address

000.000.000.000 of the terminal

change to 3.Subnet Mask.:

3.Subnetmask Enter key -> enter netmask

000.000.000.000

change to 4.Gateway

4.Gateway Enter key -> enter IP address

000.000.000.000 of the Default Router

39
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

QoS settings can only be done via the WBM of the terminal !

The further settings are described via the WBM in this documentation. They can be also used
with DHCP (standard setting).

1.10.2 Settings via the WBM of the terminal

1. Access to the WBM of the terminal.
e.g.: http:\\1.40.11.14

123456

40
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

2. SIP settings:

IP address (CUSIP) of the HG3540

(STMI2) from AMO STMIB with Port
5060

Station no from
AMO SBCSU

The following description shows the association to the H4k generating, if secu-
rity data for the registration on the HG3540 Gateway should be used:

SIP realm -> Entry in parameter SECZONE in AMO SBCSU - can not be used for
this terminal
SIP user ID -> Entry in parameter USERID in AMO SBCSU
New SIP password and Confirm SIP password -> Entry in parameter PASSWD
in AMO SBCSU

41
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

3. Check and/or set the SIP extension settings:

4. Codec settings:

42
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

5. Language setting, date - and time setting:

6. Backup the configuration- and the phone book data:

43
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

1.11 Display of the registered SIP Subscribers

Registered and unregistered SIP subscribers (optiPoint or optiClient) can be displayed via the
HG3540/50 v2 Manager in the HiPath 4000 V3.0 Assistant.

Procedure in the Assistant:

Expert mode -> HG3540/50 v2 Manager
In the HG3540/50 Manager: Explorer -> Voice Gateway
Example for a registered subscriber:

44
EN0000EN00EN_0000
© 2005 Siemens AG
SIP Subscriber Siemens

Example for an unregistered subscriber:

45
EN0000EN00EN_0000
© 2005 Siemens AG
 Siemens SIP Subscriber

46
EN0000EN00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

2 optiClient 130 V5.0 SIP

2.1 Description
It is possible to use a client as a SIP client in the HiPath 4000 V3.0 with the optiClient 130 V5.0
S software. The software can also be used for an HFA client, depending on the selected provi-
der (SIP- or HiPath-Provider). It supports the feature Direct Media Connection (DMC) and is
connected to a STMI2 board. The new protocol, which can be used, is SIP.

2.2 Installation and settings

In this document only the basic steps are described. For detailed information please use the
Administration /User manual.
The installation will be started with the Setup.exe file. Then follow the menu of the installation
routine.

During the installation routine, it is possible to select a Standard Provider and the DLS Server
data.

The optiClient 130 V5.0 S can be installed with a 30-day-license for testing. To acti-
vate this 30-day-license, you have to start the Setup.exe in the directory
..../Licensing/CLA, on the PC and follow the menu of the installation routine.

47
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

After the optiClient 130 V5.0 S software is installed and started on the PC , the following set-
tings and entries have to carried out.

1.

3.
2.

If an user ID is added without a password, the login window will not be display-
ed for future startup of the client. To get the login window, e.g. to change set-
tings, it is necessary to press the Shift-key during the client boot.

48
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

4.

Select color scheme for the Client-sur-

face

49
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

Example for Audio settings in the PC:

● Signal channel via Sound card
● USB Handset is used

50
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

Select the desired Audio-Scheme and move it to the

upper position.

51
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

In this menu it is possible to define the options for click in the display of the
Client.

Free phone can be

closed by clicking on
the display a second
time.

52
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

There the symbols in the communication circuit and the image of the easy-
Com - design can be defined.

If you want to select

image to be represented
in colors that match the
current color scheme, en-
able the option.

53
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

In the Provider-Module the SIP-Functional-Provider and the Stimulus-Provider be

selected !!!

Connnection data entry.

Your own choice;

Recommended:
Name of the user

Select the PC IP
address

Enter the subscriber

number from AMO
SBCSU

54
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

The following description shows the association to the H4k configuration, if se-
curity data for the registration on the HG3540 Gateway should be used:

Realm -> Entry in parameter SECZONE in AMO SBCSU

Login -> Entry in parameter USERID in AMO SBCSU
Password -> Entry in parameter PASSWD in AMO SBCSU

IP address of the STMI2 board from AMO STMIB.

55
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

Settings of the Network access:

56
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

Codec settings:

57
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

Settings of the used ports:

58
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

Quality of Service settings (QoS for L2 and L3 are switched off in standard):

59
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

Manager Module for the settings of the Key Manager

Under Server, enter the IP address of the PC on which the license agent (CLA) for optiClient
130 is installed. For a local installation of the license server (as in the illustrated example),
enter the local IP address or the address of the local host. If the license server is installed
on the network, enter its IP address on the network.

60
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

Configuration of the display control in Stimulus Provider:

61
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

Only the function keys F2 up to F11 of the PC can be used!

Attention: You will delete the Windows functions, if you use the function keys
for the optiClient V5.0 !

62
EN0000DE00EN_0000
© 2005 Siemens AG
optiClient 130 V5.0 SIP Siemens

2.3 Generating of the optiClient 130 V5.0 in the HiPath 4000 V2.0

1. Define the number of STMI2IGW boards:

ADD-DIMSU:TYPE=SYSTEM,STMI2IGW=xx;

2. Add the STMI2 board:

ADD-BCSU:MTYPE=PER,LTG=1,LTU=1,SLOT=49,PARTNO=Q2316-x/Q2316-x10,
FCTID=2 / 5;

ADD-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,CUSIP=1.40.41.105, SNET-
MASK=255.255.255.0;

CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=IFDATA,
DGWIP=1.40.41.254,VLAN=NO,VLANID=0;

The Trunking protocol must be set to NONE or SIP.

● NONE = only SIP Subscriber can be installed on the board;
● SIP = for mixed mode operation of SIP Subscriber and SIP Trunking;

CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=GLOBAL,
MUSTER=213, TRKPROT=NONE;

The parameters GWAUTREQ and SIPREG must be set to NO, if the board is only used for
the feature SIP Subscriber.

CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=SIPTRERH,
GWAUTREQ=NO;

CHANGE-STMIB:MTYPE=STMI2IGW,LTU=1,SLOT=49,TYPE=SIPTRSSA,
SIPREG=NO,REGIP=0.0.0.0,REGPORT=5060,REGTIME=120;

63
EN0000DE00EN_0000
© 2005 Siemens AG
 Siemens optiClient 130 V5.0 SIP

3. Add optiClient 4222:

The parameter AUTHREQ must be set to YES and the security data has to be en-
tered in the SIP software, if the parameters SECZONE, USERID and PASSWD are
used in AMO SBCSU for a secured registration !

Add the primary station number or MSN (primary station number already exists):

e.g.:

ADD-SBCSU:STNO=4422,OPT=FPP,CONN=SIP,PEN=1-1-49-0, DVCFIG=S2PP,
COS1=131,COS2=131,LCOSV1=9,LCOSV2=9,LCOSD1=1, LCOSD2=1,
PROT="SBDSS1",OPTIDX=10,IPADR=1.40.41.2,PASSWD="SECRET",
USERID="USER1",SECZONE="HIPATH4000.COM",FIXEDIP=YES,AUTHREQ=YES,
SMGSUB=NO;

or e.g.

ADD-SBCSU:STNO=4422,OPT=MSN,MAINO=4420,COS1=131, COS2=131,
LCOSV1=9,LCOSV2=9,LCOSD1=1,LCOSD2=1,FIXEDIP=NO,AUTHREQ=NO, SMG-
SUB=NO;

4. Activate the feature Direct Media Connection (DMC) for the station:

CHANGE-SDAT:STNO=4422,TYPE=ATTRIBUTE,AATTR=DMCALLWD;

64
EN0000DE00EN_0000
© 2005 Siemens AG