Nortel NN10265-111 User manual

NN10265-111
Multimedia Communication Portfolio
Multimedia Communication
Server
RTP Media Portal Basics
MCS 5100 3.5 Standard 4.0 January 2006

MCS 5100 RTP Media Portal Basics
Copyright © Nortel Networks Limited 2006
Finding the latest updates on the Nortel web site
The content of this documentation was current at the time the product was released. To
check for updates to the latest documentation and software for MCS 5100, click one of
the following links:
Link to Takes you directly to the
Latest Software Nortel page for MCS 5100 software located at
www130.nortelnetworks.com/cgi-bin/eserv/cs/
main.jsp?cscat=SOFTWARE&resetFilter=1&tranProduct=124
82.
Latest Documentation Nortel page for MCS 5100 documentation located at
www130.nortelnetworks.com/cgi-bin/eserv/cs/
main.jsp?cscat=DOCUMENTATION&resetFilter=1&tranProdu
ct=12482

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
Copyright © Nortel Networks Limited 2006

MCS 5100 RTP Media Portal Basics
Copyright © Nortel Networks Limited 2006
How to get help
This section explains how to get help for Nortel products and services.
Getting help from the Nortel web site
The best way to get technical support for Nortel products is from the Nortel Technical Support
web site:
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and tools to address
issues with Nortel products. From this site, you can:
• download software, documentation, and product bulletins
• search the Technical Support Web site and the Nortel Knowledge Base for answers
to technical issues
• sign up for automatic notification of new software and documentation for Nortel
equipment
• open and manage technical support cases
Getting help over the phone from a Nortel Solutions Center
If you do not find the information you require on the Nortel Technical Support web site, and
you have a Nortel support contract, you can also get help over the phone from a Nortel
Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the following Web site to obtain the phone number for your
region:
www.nortel.com/callus

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
6
Copyright © Nortel Networks Limited 2006
Getting help from a specialist by using an Express Routing Code
To access some Nortel Technical Solutions Centers, you can use an Express Routing Code
(ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the
ERC for your product or service, go to:
www.nortel.com/erc
Getting help through a Nortel distributor or reseller
If you purchased a service contract for your Nortel product from a distributor or authorized
reseller, contact the technical support staff for that distributor or reseller.

MCS 5100 RTP Media Portal Basics
Copyright © Nortel Networks Limited 2006
Overview
How this chapter is organized
This chapter is organized as follows:
•Functional description on page 7
•Hardware on page 8
•Software on page 12
•Operations, administration, and management on page 12
•Interfaces on page 13
—Protocols on page 13
—Network interfaces on page 14
Functional description
The Real-time Transport Protocol (RTP) Media Portal is an optional
component that addresses media plane specific issues with advanced
service delivery, Internet addressing efficiencies, and system security.
The primary function of the RTP Media Portal is to extend the reach of
multimedia services so that they are accessible to obscured endpoints,
devices residing behind a firewall, or a Network Address Translation
(NAT) and/or Network Address Port Translation (NAPT) device.
Functioning as a media NAPT point that shields Multimedia
Communications Platform (MCP) Service Network components from
external exposure, the RTP Media Portal also provides IP address/port
pair mapping between internal and external network components as
well as media anchoring and media pivot abilities for terminals.
The RTP Media Portal may be deployed in a single- or dual-network
configuration. For dual-networks, the RTP Media Portal enables
elements in the Protected MCS Network to safely communicate with
elements in the Managed IP access network.

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
8
Copyright © Nortel Networks Limited 2006
Figure 1, Network component topology, on page 8 is a graphical
depiction of the RTP Media Portal’s position in a single-network MCS
solution.
Figure 1 Network component topology
Hardware
The RTP Media Portal resides on a Motorola* CPX8216T platform, a
16-slot CompactPCI (cPCI) chassis design.
The chassis offers a High Availability platform that provides the basic
operating environment (such as power, backplane, cooling, and
mounting slots) required to sustain the resident subcomponent
single-board computers. The CPX8216T hardware architecture
partitions the chassis into separate logical operational Domains,

MCS 5100 RTP Media Portal Basics
9
Copyright © Nortel Networks Limited 2006
dividing the chassis shelf into two half-shelves consisting of 8-slots
each.
Note: The chassis logical Domains are not internet Domains.
Rather, the term is used to identify Side A and Side B of the chassis.
Other terms used interchangeably include: Domain A and Domain B,
Left Domain and Right Domain, and half-shelf.
An RTP Media Portal occupies a single logical operational Domain in
the CPX8216T. A single CPX8216T chassis can host two RTP Media
Portal components (one in chassis Domain A, the other in chassis
Domain B) as shown in Figure 2, Card slot associations for the two
logical Domains in a single chassis, on page 9.
Figure 2 Card slot associations for the two logical Domains in a
single chassis
If the chassis is viewed from the front, the slots are numbered from left
to right (1-16). If viewed from the rear, the slots are numbered from right
Domain A Domain B

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
10
Copyright © Nortel Networks Limited 2006
to left (1-16). A front view of the CPX8216T is shown in Figure 3,
Motorola chassis CPX8216T - front view, on page 10.
Figure 3 Motorola chassis CPX8216T - front view
A rear view of the CPX8216T is shown in Figure 4, Motorola chassis
CPX8216T - back view, on page 11.

MCS 5100 RTP Media Portal Basics
11
Copyright © Nortel Networks Limited 2006
Figure 4 Motorola chassis CPX8216T - back view
Within the CPX8216T dual 8-slot architecture, each logical Domain in
the chassis contains a dedicated host card (with an associated
transition module in the rear), a slot dedicated to the Motorola Hot Swap
Controller (HSC), and the remaining six slots which may be populated
with Media Blades (media input/output cards with an associated
transition module in the rear).
The Hot Swap Controller in the Left Domain controls the Right Domain.
The Hot Swap Controller in the Right Domain controls the Left Domain.

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
12
Copyright © Nortel Networks Limited 2006
Each logical Domain, and therefore each RTP Media Portal, consists of
the following hardware components:
• a single CPV5370 Intel processor board (the host card) with 1 GB
memory, a SCSI input/output (I/O) daughter board, and rear
Transition Module.
• Hot Swap Controller and Bridge (HSC) module
• SCSI CD-ROM drive
• SCSI hard drive
• Floppy drive
• One (or more) Motorola MCPN765 Power PC processor board (the
Media Blade), with 64 MB RAM and associated Rear Transition
Module.
• Available AC or DC power options
Customer provided requirements include:
•Mouse
• Keyboard
•Monitor
Software
The RTP Media Portal is primarily a software entity that is comprised of
subcomponents distributed across the hardware platform.
The RTP Media Portal, servers and components must be configured
and provisioned under the same site as the management server, even
if deployed from a remote location. Failure to deploy the RTP Media
Portal under the same site as the management server will prevent OMs,
logs, and alarms form being managed from the System Management
Console. For more information regarding network configuration, refer to
MCS 5100 Network Engineering and Deployment Guide
(NN10313-191).
For information regarding maintenance updates, refer to Maintenance
updates on page 19. For information regarding the upgrading of RTP
Media Portal software releases, refer to Full release upgrades on
page 27.
Operations, administration, and management
Operations, administration, and management (OAM) of the RTP Media
Portal is available through the System Management Console. This
console provides an overall view into the status of the various

MCS 5100 RTP Media Portal Basics
13
Copyright © Nortel Networks Limited 2006
components in the system and administrative access to OAM functions
(including fault and configuration management).
RTP Media Portal OAM data is stored on both the Management Module
and the database. The Management Module stores alarm and log data.
Configuration data is stored locally on the RTP Media Portal as well as
persistently in the database. For a graphical view of these relationships,
please refer to Figure 5, OAM interoperability, on page 13.
Figure 5 OAM interoperability
For additional information, please refer to MCS 5100System
Management Console User Guide. (NN10273-111)
Interfaces
Protocols
While in service, the RTP Media Portal interfaces with the network
through the following protocols:
•MPCP, Media Portal Control Protocol, used to control messages
between the SIP Application Module and the RTP Media Portal.
MPCP messages control the making, modification, and breaking of
media session connections.
•RTP, Real-time Transport Protocol, transports real-time media
streams (for example, audio and video) across a packet network.
•RTCP, Real-time Transport Control Protocol, provides a means of
sharing session data (for example, performance data) between
endpoints.
•UDP, User Datagram Protocol, provides data-based media streams
(for example, file transfer).

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
14
Copyright © Nortel Networks Limited 2006
•TCP, Transmission Control Protocol, communicates configuration,
performance data, logs, and alarms (OAM data) between the RTP
Media Portal and the Management Module.
Network interfaces
The RTP Media Portal is comprised of two physical hardware
subcomponents: a single Host CPU, and up to six (6) Media Blades.
The following figure shows an example of RTP Media Portal
dual-network connectivity between a Protected MCS Network and a
Public Network.
Figure 6 RTP Media Portal operational interface - dual-network deployment
The Host CPU interacts with the management infrastructure to provide
OAM capabilities. The Host CPU also provides the control capabilities
(MPCP) through which a call controller can access, manipulate, and
apply advanced functions to media streams.
The Media Blades provide the Media Packet Engine for processing
media streams. A Media Blade can be configured for a dual- (see
Figure 6) or single-network deployment (see Figure 7). For
single-network deployment, the Media Blade and Host CPU must be on
the same local network. This enables the distributed Host and Media
Blades to communicate using a non-routable network addressing
scheme.
Pub
li
c
N
et
w
o
rk
M
ed
i
a
Bl
ades
me
edia streams
ms
media stream
RTP
Media
Po
r
tal
H
ost
CP
U
co
ontrol/OAM
P
r
otected
MC
S
N
et
w
o
r
k

MCS 5100 RTP Media Portal Basics
15
Copyright © Nortel Networks Limited 2006
Figure 7 RTP Media Portal operational interface - single-network
deployment
Host CPU
As shown in Figure 8, Control and OAM interface - CPV5370 Host card
and RTP Media Portal, on page 16, the Rear Transition Module for the
host card (CPV5370) provides the following:
• COM2 port for connection to a terminal server and local monitor.
• Two Ethernet ports which provide connectivity to the Protected MCS
Network. The connection carries control and OAM data.
— The Ethernet 1 port is used to provide an active connection.
— The Ethernet 2 port provides a standby connection. The standby
ethernet function is enabled by default through the “Activate IP
Failover” property when configuring the RTP Media Portal. (For
additional information, refer to Ta bl e 2 , RTP Media Portal tab
configurable properties, on page 51.)
Network
Control/OAM
Media
Host
CPU
Media
Blades
RTP Media
Portal

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
16
Copyright © Nortel Networks Limited 2006
Figure 8 Control and OAM interface - CPV5370 Host card and RTP Media Portal
These Ethernet connections carry the following:
• MPCP control messages to communicate with the SIP Application
Module.
• Operations, administration, and maintenance (OAM) data to the
Management Module over TCP.
• Internal communications between Host and Media Blades.
Media blades
Network interfaces on each of the Media Blades (MCPN765) in the RTP
Media Portal provide a path for media streams. Figure 9, Media stream
interface – MCPN765 Media Blade to RTP Media Portal, on page 17
terminal
server
Front Main
Board
Rear Transition
Module
100BaseT Ethernet
Control and OAM
100BaseT Ethernet MCP Service
Network
Protected MCS
Network
(Standby)
(Active)

MCS 5100 RTP Media Portal Basics
17
Copyright © Nortel Networks Limited 2006
illustrates media stream interfaces in a dual-network deployment
between a Protected MCS Network and Public Network.
Figure 9 Media stream interface – MCPN765 Media Blade to RTP Media Portal
A Media Blade in the RTP Media Portal consists of the following
input/output cards:
• MCPN765 Front Main Board
• TM-PIMC-0101 Rear Transition Module
There is a 1:1 relationship between the Front Card and Rear Transition
Module.
Protected
MCS Network

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
18
Copyright © Nortel Networks Limited 2006
The Rear Transition Module contains two, 10/100 BaseT Ethernet
connections for RTP/RTCP/UDP media streams. Each Media Blade
(pair of MCPN765 and TM-PIMC-0101 cards) performs the following
functions:
• Connectivity for RTP/RTCP/UDP media streams.
• Address and Port Discovery (APD) for obscured media endpoints.
• Relay of media packets between end points.
• An array of NAT and/or NAPT functions.
The NET ports are used as following:
• In a single-network deployment, only the NET2 port is used.
• In dual-network deployment, NET2 is used for connectivity to the
Protected MCS Network and NET1 for the other network.
References
The following are referenced in this document and provide additional
information:
•MCS 5100 Network Engineering and Deployment, NN10313-191
•MCS 5100 System Management Console User Guide,
NN10273-111
•Provisioning Client User Guide, NN42020-105
•MCS 5100 Fault Management: Alarm and Log Reference,
NN10385-900
•MCS 5100 Accounting Module Basics, NN10279-111

MCS 5100 RTP Media Portal Basics
Copyright © Nortel Networks Limited 2006
Maintenance updates
How this chapter is organized
This chapter is organized as follows:
•Functional description on page 19
•Operations, administration, and management on page 19
•Maintenance update tasks on page 20
—Shut down the RTP Media Portal component on page 21
—Update the RTP Media Portal component on page 23
Functional description
This chapter documents upgrade tasks to be performed when
upgrading a maintenance release.
Tools and utilities
Upgrades to the RTP Media Portal are performed through the System
Management Console. Please refer to MCS 5100 System Management
Console User Guide (NN10273-111) for more information.
Operations, administration, and management
The SIP Application Module may try to contact the RTP Media Portal
while the update is in progress, potentially generating error logs. To
minimize impact to service, the RTP Media Portal should first be
SHUTDOWN so that it does not accept new service requests. While
shutting down, the RTP Media Portal will continue to process
established media sessions. These pre-existing media sessions are
cleared as the associated calls end. The RTP Media Portal
automatically transitions into the LOCKED state when there are no

NN10265-111 MCS 5100 3.5 Standard 4.0 January 2006
20
Copyright © Nortel Networks Limited 2006
active media sessions present. When this occurs, it is safe to proceed
with the upgrade without affecting service.
If an upgrade fails during the initial stages, a rollback to the previous
load is performed. A notification of the failure appears within the System
Management Console.
If a component upgrade fails after the initial stages of the upgrade, it
does not rollback automatically. A dialog box appears in the
Management Console stating that the upgrade failed and prompts the
administrator to determine whether a rollback should be performed.
Upgrade commands may require several minutes to complete
execution and will initiate a reboot of the RTP Media Portal. The length
of the reboot is approximately 2-3 minutes. Due to reduced capacity,
perform updates during low traffic periods.
Maintenance update tasks
For maintenance updates, administrators may decide to either upgrade
the RTP Media Portal component to the latest maintenance release, or
downgrade the RTP Media Portal component to a previous
maintenance release.
To upgrade or downgrade the RTP Media Portal, the update operation
is issued to the RTP Media Portal from the System Management
Console. This operation will reboot the host card, which in turn reboots
all Media Blades. When the RTP Media Portal recovers from this
operation, it is in service (UNLOCKED) with the updated software.
To avoid any conflicts with service requests from the SIP Application
Module(s), the following procedure describes the steps that must be
CAUTION
It is possible to update and reboot one RTP Media
Portal in a chassis, while the RTP Media Portal in the
other half of the chassis continues to run the previous
software. Once one RTP Media Portal is updated, the
other RTP Media Portal in the chassis can be
shutdown, locked, updated, and rebooted. This
rolling upgrade will only impact available capacity and
will not cause a service outage.
Updating all RTP Media Portals concurrently will
cause a service outage.