The Real-time Transport Protocol (RTP) Media Portal is an optional
component of the network that performs many media-layer functions.
The RTP Medi a Port al addresses me dia specific issues with advanced
service delivery, Internet addressing efficiencies, and system security.
It functions as a media Network Address and Port Translation (NAPT)
point that shields priv ate netwo rk co mp on ents from external exposure
through leaks in the media streams. The RTP Media Portal also
enables elements in the private network to safely communicate with
elements in the public network. The RTP Media Portal provides IP
address/port pair mapping between internal and external network
components, as well as media anchoring and media pivot abilities for
terminals.
3
Figure 1, “Network Component Interoperability,” on page 4 is a
graphical representation of the RTP Media Portal interworking among
other components in the Multimedia Communications Portfolio.
The clouds in the d iagram represe nt two distin ct networks. The Private
Network cloud interacts with the Public Network cloud through the
different edge components. The RTP Media Portal provides
media-layer functionality for Real-time Transport Protocol (RTP),
Real-time Transport Control P r otocol (RTCP), and User Datagram
Protocol (UDP) transmissions.
Hardware
Description
The RTP Medi a Portal resides on a Motorola CPX8216T pl atform which
is a CompactPCI (cPCI) chassis design.
The chassis provides th e basic operatin g environment (su ch as power ,
backplane, cooling , and mounti ng slot s) requi red to house cPCI-based
single-board computers. The CPX8216T partitions the chassis into two
separate logical oper ational domains (dividing the chassis sh elf into
two half-shelves consisting of 8-slots each).
An RTP Media Portal occupies a single chassis domain (side) on a
CPX8216T. Therefore, a single CPX8216T can host two RTP Media
Portal components (one in chassis Domain A, the other in chassis
Domain B).
Note: Chassis domai ns ar e not internet domains. This is just
another terminology intended to identify Side A and Side B of the
chassis. Other terms often u sed inte rchange ably are: Doma in A a nd
Domain B, as well as Left Domain and Right Domain.
Figure 2 Card slots for the two different domains
Overview 5
Note 1: The Hot Swap Controller in the Left Domain (Domain A)
controls the Right Dom ain (Domain B). The Hot Swap Controller in
the Right Domain (D o mai n B) contr o ls th e Le ft D om ain ( D omai n A) .
Note 2: If the chassis is viewed from the front, the slots are
numbered from left to right (1-16), and if viewed from the rear, the
slots are numbered from right to left (1-16).
The CPX8216T dual 8-slot architecture further refines the domain
definition so that each chassis domain is dedicated to a Host CPU
board (with an associat ed transition module in the r ear), an other slot is
dedicated to the Motorola Hot Swap Controller (HSC), and the
remaining six slots can be populated with peripheral resource cards
(Input/Output cards with an associated transition module in the rear)).
Each chassis half shelf consists of the following hardware components:
•Intel processor board with 1 GB memory and a SCSI Input/Output
(I/O) daughter board (CPV5370 host card)
Information on updating software loads for the RTP Media Portal are
covered in “Upgrades” on page 13.
OAM&P strategy
The OAM&P strategy for the system is to manage operations from a
central location. Th e central location for OA M&P manag ement is in the
System Management Console. From the System Management
Console, you can view and perform operations on the various
components in the system.
Interfaces
Protocols
While in service, the RTP Media Portal interfaces with the network
through the following protocols:
•MGCP+ is the Enhanced Media Gateway Co ntr o l Pr oto c ol that i s
used for messaging between the RTP Media Portal and the SIP
Application Module, and controls the making, modification and
breaking of media session c onnections.
•RTP is the Real-time Tr an spo rt Pr oto col for tran spo rt of real - ti me
media streams (for example, audio and video) across a packet
network.
Overview 7
•RTCP is the Real-time Transport Control Protocol that provides a
means of sharing session data (for example, performance data)
between endpoints.
•UDP is the User Dat agram Protocol that provides data-ba sed media
streams (for example, file transfer).
The Host CPU card provides the signaling and OAM data interface
to/from the Private Network. Each I/O card (commonly referred to as a
blade) provides a media stream interface to the Private Network and a
media stream interface to the Public Network.
Figure 5 Signaling and OAM interface - CPV5370 Host CPU
Overview 9
The rear transition module for the CP5370 Host Central Processing
Unit (CPU) card contains the following:
•COM2 port for connection to a terminal server and local monitor.
•Two Ethernet ports which provide connectivity to the Private
Network. The connection carries signaling and OAM data.
— The Ethernet 1 port is always used to provide an active
connection.
— The Ethernet 2 po rt provides a st andby connection. The sta ndby
ethernet function is enabled by default through the “Activate IP
Failover” prope rty when config uring the R TP Media Port al. (See
Table 2, “RTP Media Portal tab configurable properties,” on
page 33.)
These Ethernet connections carry the following:
•MGCP+ signaling to comm unicate with the SIP Ap plicatio n Mo dule.
•operations, admin i strati on and maintenance (OAM) data to the
Management Modu le.
Network interfaces on each of the Input/Output cards (MCPN7 65) in the
RTP Media Po rtal pro vide a p ath for media str eams to/from th e Private
Network and Public Network.
The RTP Media Portal uses the following input/output (I/O) cards:
•MCPN765 front card
•TM-PIMC-0101 rear transition module
The transition module contains two, 10/100 BaseT Ethernet
connections for RTP/RTCP/UDP media streams. Each pair of
MCPN765 and TM-PIMC-0101 cards perform the following functions:
•Provides connectivity for R TP/RTCP/UDP media streams to pa ss
between the Private Network and the Public Network, as well as the
public to public network.
•Relays media packets between end points.
•Performs Network A ddre ss a nd Po rt Translation (NAPT) functions.
NET ports
•NET1 port = IP address of Public Network
•NET2 port = IP address of Private Network
The RTP Media Portal Host CPU is o nly connected to the private
network. The RTP Media Portal is an edge component that is
dual-homed on the public network and the Private Network. It is the
Peripheral I/O cards that span these two distinct networks.
Overview 11
User interfaces
The System Management Console is used for fault and configuration
management of the RTP Media Portal. RTP Media Portal management
data is stored on both the Management Module and the Database
Module. The Mana gement Module s tores alarm, log, a nd OM data. The
Database Mod ule stor es conf iguration data.
•“OAM&P strategy” on page 13
— “RTP Media Portal software upgr ade” on page 13
•“Task flows” on page 14
— “Shutdown the RTP Media Portal component” on page 14
— “Update a software load” on page 15
OAM&P strategy
RTP Media Portal software upgrade
This section describes the update strategy for the RTP Media Portal.
The RTP Media Portal run-time sub-component can be upgraded by
deploying the new software to the target node from the System
Management Console.
13
Note: The SIP Application Module m ay try to contact th e RTP Media
Portal whi le the upgrade is in p rogress, thus genera ting error logs. To
minimize impact to service, the RTP Media Portal should first be
SHUTDOWN so that it does not a ccept n ew servi ce re quest s . While
shutting down, the RTP Media Portal is still processing established
media sessions. These pre-existing media sessions will slowly
become inactive as the calls end. The RTP Media Portal will
automatically transition into the LOCKED state when there are no
active media sessions present. When this occurs, it is safe to
proceed with the upgrade without affecting service.
Updating the software of the new ru n- tim e su b- com p onent(s) from the
System Management Console can commence.
A reset is then issued to the RTP Media Portal from the System
Management Console. This reboots the host CPU, which in turn
reboots the Peripheral CPUs. When the RTP Media Portal recovers
from the reset, it is running (UNLOCKED) with the upgraded software.
Note: It is possible to update one RTP Media Portal and reboot it
while the other half shelf is running the load that has not been
updated. Once one half shelf is updated, the other half shelf can be
locked, updated, and rebooted. Upgrading all RTP Media Portals
concurrently will cause a service outage.
The length of outage due to the reboot is approximately 3-5
minutes.
Note 1: Software loads are encrypted for security reasons.
Note 2: If a component upgrade fails, it does not roll back
automatically. A roll back prompt appears. If the upgrade is not
successful, note as much of the event as possible and contact your
next level of support.
To avoid any problems with the SIP Applicat ion Module, the following
procedure describes the steps that must be followed when updating a
software load for the RTP Media Portal component.
From the System Management Console:
1Shutdown the R TP Media Portal compon ent. See “Shutdown the
RTP Media Portal component” on page 14.
2Update the software load for the RTP Media Portal component.
See “Update a software load” on page 15.
Shutdown the RTP Media Portal component
The following procedure describes how to shutdown the RTP Media
Portal component:
From the System Management Console
1Select the RTP Media Portal Server, select Com ponents and
then select the appropriate RTP Media Portal component .
2To Shutdown the component, either right-click and select
Shutdown or select Shutdown from the Operations menu.
3The RTP Media Por t a l com po ne nt w ill shutdown gracefull y and
go into a LOCKED state, as seen in the General Information
Area of the System Management Console.