Nortel Networks NN10033-111 User Manual
Overview
13
Copyright © 2003, Nortel Networks
MCP Interworking Basics
Nortel Networks Confidential
other SIP endpoints (such as the SIP Multimedia Web Client or an
i2004 controlled by the IP Client Manager (IPCM) for voice over IP calls.
i2004 controlled by the IP Client Manager (IPCM) for voice over IP calls.
An MCP alias must be set up for each user so that the alias is the same
as the Calling Line ID sent from the TDM switch to the MCP over PRI.
When a non-CDS MCP user calls a CDS user, the call is sent out the
gateway to the CDS user’s TDM phone and the non-CDS user’s
public/private charge ID is used to identify them to the TDM switch as
the calling party. This charge ID is sent to the Converged PC Client, on
the SimRing leg of the call, and is used by the Converged PC Client to
contact the calling party’s MCP client. Therefore, the non-CDS user’s
charge ID must be included as an alias in the non-CDS user’s
provisioning. A non-CDS user’s charge ID cannot be shared amongst
users within a domain because the charge ID must be included as an
alias and a user's aliases must be unique within a domain.
as the Calling Line ID sent from the TDM switch to the MCP over PRI.
When a non-CDS MCP user calls a CDS user, the call is sent out the
gateway to the CDS user’s TDM phone and the non-CDS user’s
public/private charge ID is used to identify them to the TDM switch as
the calling party. This charge ID is sent to the Converged PC Client, on
the SimRing leg of the call, and is used by the Converged PC Client to
contact the calling party’s MCP client. Therefore, the non-CDS user’s
charge ID must be included as an alias in the non-CDS user’s
provisioning. A non-CDS user’s charge ID cannot be shared amongst
users within a domain because the charge ID must be included as an
alias and a user's aliases must be unique within a domain.
Calls to a CDS user must terminate to the existing switching system of
the CDS user before the call is routed to the MCP. For example, the
originator’s existing switching system must route calls using the
existing systems, as opposed to sending the call to the MCP. This is
required since all calls from the SIP PRI gateway are implied to have
been triggered by the SimRing feature on the existing switching
system.
the CDS user before the call is routed to the MCP. For example, the
originator’s existing switching system must route calls using the
existing systems, as opposed to sending the call to the MCP. This is
required since all calls from the SIP PRI gateway are implied to have
been triggered by the SimRing feature on the existing switching
system.
Interworking with third-party voicemail servers
There are three major types of third-party voicemail servers. The
following sections describe how the MCP can interwork with the
following types of third-party voicemail servers:
following sections describe how the MCP can interwork with the
following types of third-party voicemail servers:
•
SIP-based voicemail servers
•
Trunk-based voicemail servers
•
Line-based voicemail servers
SIP-based voicemail servers
SIP-based voicemail servers are SIP-enabled and can interwork
directly with the MCP network. SIP is used to set up connections
between the client and the voicemail server. The RTP Media Portal is
used to carry the media packets between the client and the voicemail
server.
directly with the MCP network. SIP is used to set up connections
between the client and the voicemail server. The RTP Media Portal is
used to carry the media packets between the client and the voicemail
server.
Figure 3 shows how the MCP interconnects with a SIP-aware
third-party voicemail server.
third-party voicemail server.