6 sip registration, 6 sip registration -35 – Siemens HIPATH 20 User Manual
Page 77
administration.fm
A31003-O1010-M100-9-76A9, 05/05/2008
HiPath 8000 - OpenStage Family, Administration Manual
3-35
Administration
System Settings
Administration via Local Phone
3.5.6
SIP Registration
Registration is the process by which centralized SIP Server/Registrars become aware of the
existence and readiness of an endpoint to make and receive calls. The phone supports a num-
ber of configuration parameters to allow this to happen. Registration can be authenticated or
un-authenticated depending on how the server and phone is configured.
Unauthenticated Registration
For unauthenticated registration, the following parameters must be set on the phone: Terminal
number or Terminal name (see Section 3.5.1.1, “Terminal Identity”), SIP server and SIP regis-
trar address (see Section 3.5.5.1, “SIP Addresses”). Moreover, the correct Server type must
be set. Additionally, the expiry time of a registration can be specified by Registration timer.
In unauthenticated mode, the server must pre-authenticate the user. This procedure is server
specific and is not described here.
Authenticated Registration
The phone supports the digest authentication scheme and requires some parameters to be
configured in addition to those for unauthenticated registration. By providing a User ID and a
Password which match with a corresponding account on the SIP registrar, the phone authen-
ticates itself. Optionally, a Realm can be added. This parameter specifies the protection domain
wherein the SIP authentication is meaningful. The protection domain is globally unique, so that
each protection domain has its own arbitrary usernames and passwords.
|
--- Administration
|
--- Network
|
--- Port Configuration
|--- SIP server
|--- SIP registrar
|--- SIP gateway
|
--- SIP local
>
A challenge from the server for authentication information is not only restricted to the
REGISTER message, but can also occur in response to other SIP messages, e. g.
INVITE.
>
If registration has not succeeded at startup or registration fails after having been pre-
viously successfully registered the phone will try to re-register every 30 seconds.
This is not configurable.