Mitel Deutschland GmbH 68635RFP36U-01 ユーザーズマニュアル
Configuration and Administration
279
SIP backup servers can be configured in the
System -> SIP menu of the OM Management Portal
(OMP), see also section 6.5.4.
You can configure IP addresses, names or full qualified domain names as server addresses. It is also
possible to configure a mixture of IP addresses, names or full qualified domain names for the different
servers.
possible to configure a mixture of IP addresses, names or full qualified domain names for the different
servers.
If fully qualified domain names are configured and the respective port setting is configured to zero (“0”),
DNS SRV queries are performed to locate a list of servers in the domain. It is assumed that all server
addresses are specified by name or IP address. With fully qualified domain names, the behavior
described in section 7.20.2 is performed in addition to contact the SIP servers in the given domain.
DNS SRV queries are performed to locate a list of servers in the domain. It is assumed that all server
addresses are specified by name or IP address. With fully qualified domain names, the behavior
described in section 7.20.2 is performed in addition to contact the SIP servers in the given domain.
This redundancy mechanism is based on a failover concept where the OMM first tries to contact the
primary server. If the primary server fails, the OMM tries to contact the secondary server and if the
secondary server fails also, the OMM tries to contact the tertiary server.
primary server. If the primary server fails, the OMM tries to contact the secondary server and if the
secondary server fails also, the OMM tries to contact the tertiary server.
The OMM failover behavior in detail depends on the backup server settings.
7.20.3.1 No Secondary/Tertiary Proxy, Outbound Proxy and Registrar Configured
In this case is no failover to a secondary/tertiary (outbound) proxy / registrar is possible.
In this case is no failover to a secondary/tertiary (outbound) proxy / registrar is possible.
7.20.3.2 Secondary/Tertiary Proxy and Registrar Configured
All REGISTER and re-REGISTER requests attempt to use the primary registrar first.
All REGISTER and re-REGISTER requests attempt to use the primary registrar first.
If the primary registrar fails (e.g. no answer in “transaction timer” time frame), the user is tried to register
with the secondary/tertiary registrar using as AOR the secondary/tertiary proxy address.
with the secondary/tertiary registrar using as AOR the secondary/tertiary proxy address.
When the registration with the secondary/tertiary registrar succeeds:
•
the MWI subscription is moved to the secondary/tertiary proxy,
•
all subsequent INVITE requests attempt to use the secondary/tertiary proxy,