Technical data

Features
EN4442EN00EN_0001
© 2007 Siemens AG
Siemens
22
4.4 Mobility
HG 3500 gateways support mobility.
HFA Mobility provides all functions and features that are available to a user at his “home” IP
phone at any IP phone within a HiPath system or network. This includes identical user
interfaces and user privileges.
A simple optiGuide supported logon procedure allows login into any IP phone within a HiPath
network. The selected phone becomes the user’s temporary home phone including all personal
settings. The actual home phone is being logged off as soon as the subscriber logs on to
another IP phone. Calls to the home phone are forwarded as defined for CFNR (Call
Forwarding No Reply).
4.5 Secondary Clients
HG 3500 gateways support optiClient 130 “Secondary Clients”.
● Secondary clients are optPoint 130 soft-clients configured with the same phone number as
a regular IP phone.
● Secondary Clients do not require a ComScendo license.
● Secondary Clients require an optiClient 130 SW license.
The standard H225 Signalling Port is 1720 and this port is used at the OC130 to establish calls
from the board to the OC130. For the OC130 Client it might be necessary to use a different
port. In the case that an other H323 application is running in parallel to the OC130 it is possible
to configure a different H225 Signalling Port on the OC130. The OC130 informs the HG 3500
at registration time and the HG 3500 will use this port for call establishment.
The OC130 can be used as a non standard VPN client. In this configuration the HG 3500
checks the delivered IP address and the real address on the connected CorNetTC socket and
informs the OC130 about its real IP address when these 2 addresses are different..
Benefits of Secondary Clients:
● Secondary clients provide remote access to all HiPath 4000 features using an optiClient
130 soft client.
>
Note that invoking any feature that results in a multi party call (more than 2 parties)
will route the payload through all gateways in the payload path (same as in HiPath
4000 V1.0). This may result in undesirable delays in certain scenarios (see Section
2.5.6, “DMC Considerations” for more details).