Nortel Networks NN43001-121 User Manual
Page 78
78
Planning and engineering
Systems, platforms, and applications
Interoperable
Supported
AT&T SIP trunk
Y
N
Broadsoft
Y
N
ACME SBC
Y
N
3100 Mobile Communication Gateway
Y
N
Redundancy
Remote Call Control (RCC) services are supported (with limitations) in the
following scenarios:
•
Single node redundancy
•
Campus redundancy
•
Geographic redundancy
Single node Redundancy
The same master and follower mechanism used for Virtual Trunk (VTRK)
and TPS applications is used to support redundancy within a node for RCC.
After the master of the node fails, one of the followers takes over the node
IP and continues to deliver service. VoIP mode session state is preserved
when a new master is elected.
Redundancy across multiple nodes is possible using the Least Cost Routing
feature of NRS. When considering a multinode redundant configuration, see
the restrictions on establishing TR/87 sessions from multiple nodes that
have AML links to a single Call Server. For more information, see
.
Campus redundancy
Campus Redundancy increases the distance between the two CPU cores of
CS 1000E.
The CS 1000E is the only large system that supports this feature.
Geographic redundancy
Geographic Redundancy can be supported with the limitations that currently
exist for SIP gateway SIP traffic. The main impacts are.
•
During transition periods, situations can arise where IP phones are
registered to a Call Server that is different from the call server that
provides support for the TR/87 FE. In this situation, TR/87 support is
undefined. TR/87 clients can register successfully; however, the status
of the IP Phone is impacted by any actions performed on the telephone
or the TR/87 client, as the FE and IP Phone interface different Call
Servers. NRS is required to support redundancy.
Nortel Communication Server 1000
Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007
NN43001-121
01.03
Standard
Release 5.0
30 April 2008
Copyright © 2005–2008, Nortel Networks
.