Mitel Deutschland GmbH 68635RFP36U-01 ユーザーズマニュアル
Configuration and Administration
281
7.20.3.5 Secondary/Tertiary Outbound Proxy Configured Only
The OMM behavior is as described in section 7.20.3.2 but
The OMM behavior is as described in section 7.20.3.2 but
•
all requests for the secondary/tertiary proxy/registrar are send through the outbound proxy;
•
if the registration with the primary registrar fails, the registration is re-tried using the primary proxy
address as AOR sent through the outbound proxy.
•
7.20.3.6 Secondary/Tertiary Registrar Configured Only
All REGISTER, INVITE and SUBSCRIBE requests attempt to use the primary proxy or registrar first.
All REGISTER, INVITE and SUBSCRIBE requests attempt to use the primary proxy or registrar first.
If a REGISTER request fails, the request attempts to use the secondary/tertiary registrar.
7.20.4 KEEP ALIVE MECHANISM
A keep-alive mechanism implemented in the OMM allows the automatic failover to secondary/tertiary
servers or automatic coming back to primary servers. The keep-alive mechanism is based on the
registration process and utilizes the special behavior that all REGISTER and re-REGISTER requests are
sent to the primary registrar first.
servers or automatic coming back to primary servers. The keep-alive mechanism is based on the
registration process and utilizes the special behavior that all REGISTER and re-REGISTER requests are
sent to the primary registrar first.
The following configuration parameters are introduced:
Failover keep alive and Failover keep alive
time. These parameters are set in the OM Management Portal (OMP) on the Backup settings tab of
the
the
System: SIP menu (see page 143).
For each registration target, a user could be registered successful with, a keep alive procedure is
started. For this purpose the first user registered successful on a registration target will be selected to re-
register all “Failover keep alive time” before the registration period expires.
started. For this purpose the first user registered successful on a registration target will be selected to re-
register all “Failover keep alive time” before the registration period expires.
If the re-registration of this selected user detects that the current primary server fails, the registration of
all users registered on the same server will be refreshed automatically. For this purpose the re-register
requests are queued and proceed according to the registration traffic settings (see section 5.4.3.5 for
OMM Web or section 6.5.4.3 for OMP).
all users registered on the same server will be refreshed automatically. For this purpose the re-register
requests are queued and proceed according to the registration traffic settings (see section 5.4.3.5 for
OMM Web or section 6.5.4.3 for OMP).
If the re-registration of a selected user detects that the primary server is available again, the registration
of all users registered on a secondary/tertiary registrar will be refreshed.
of all users registered on a secondary/tertiary registrar will be refreshed.
7.20.5 PRIORITIZED REGISTRATION
Depending on the settings for “Registration traffic shaping”, the registration of a high number of users
could need minutes. In effect single users could not be reachable for minutes during startup.
could need minutes. In effect single users could not be reachable for minutes during startup.
To guarantee a minimum blackout for very important people (e.g. emergency user) the registration of
such people can be prioritized. Therefore a special user attribute VIP (very important person) is
introduced. The corresponding option is set in the
such people can be prioritized. Therefore a special user attribute VIP (very important person) is
introduced. The corresponding option is set in the
SIP tab of the DECT phone Detail Panel (see page
188).
7.20.6 MONITORING THE SIP REGISTRATION STATUS
The SIP registration status of a DECT phone user can be monitored by using the OpenMobility
Management Portal (OMP). In OMP monitor mode you can view on which registrar a specific DECT
Management Portal (OMP). In OMP monitor mode you can view on which registrar a specific DECT