Professional Documents
Culture Documents
V100R002
BOM 31026861
Website: http://www.huawei.com
Email: Support@huawei.com
All other trademarks and trade names mentioned in this document are the
property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort
has been made in the preparation of this document to ensure accuracy of the
contents, but all statements, information, and recommendations in this document
do not constitute the warranty of any kind, express or implied.
Release Notes
This manual applies to the MRS6100 Media Resource Server V100R002 (the
MRS6100 for short).
Organization
Conventions
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Convention Description
Format Description
Press the key with the key name in Boldface. For example,
Key
Enter, Tab, Backspace, or A.
Press the keys concurrently. For example, Ctrl+Alt+A
Key1+Key2
means the three keys should be pressed at the same time.
Press the keys in turn. For example, Alt, A means the two
Key1, Key2
keys should be pressed in turn.
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Environmental Protection
This product has been designed to comply with the requirements on environmental
protection. For the proper storage, use and disposal of this product, national laws and
regulations must be observed.
Table of Contents
i
Technical Manual
U-SYS MRS6100 Media Resource Server Table of Contents
ii
Technical Manual
U-SYS MRS6100 Media Resource Server Table of Contents
iii
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
1-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
The service management layer provides value-added services and operation support
based on the established calls. It includes the following entities:
z MRS6100
It provides the media processing functions in the basic and enhanced services,
including service announcement, conference, interactive voice response (IVR),
notification, and advanced tone services.
z iOSS
The integrated operation support system (iOSS) includes the network
management system (NMS) and the integrated billing system.
z AS
The application server (AS) is a stand-alone device at the service management
layer. It provides the following functions:
1) Create and manage the logic related to the value-added services and
intelligent network services
2) Provide various open application programming interfaces (API).
3) Provide the development platform for the thirty-party services.
4) Separate service control from call control. This helps introduces new
services.
z Policy Server
It manages the policies for the following aspects:
1-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
The network control layer implements call control. It uses softswitch as core
technology to implement basic real-time call control and connection control.
As shown in Figure 1-1, the SoftX3000 SoftSwitch is the core device in the NGN. It
implements the following functions:
1) Call control
2) Media gateway access control
3) Resource allocation
4) Protocol processing
5) Routing
6) Authentication
7) Charging
8) Provides basic voice services, mobile services, multimedia services, and APIs.
The core switching layer adopts the packet technology. It is composed of the devices
like routers and layer-3 switches in the backbone network and the metropolitan area
network (MAN). It provides subscribers with a unified and integrated transmission
platform with high reliability, quality of service (QoS) assurance and a large capacity.
1-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
The edge access layer connects the subscribers and terminals with the network by
various access means. It converts the original information formats into those that can
be transferred over the network. The following devices can connect with the network:
z Integrated access device
The integrated access device (IAD) is a user access layer device in the NGN. It is
used to introduce the data, audio, and video services to the packet based
network.
z Access media gateway
The access media gateway (AMG) provides multi-service access, including
analog user access, integrated services digital network (ISDN), V5, and x digital
subscriber line (xDSL).
z SIP phone
The SIP phone is a kind of multimedia terminal device that supports the Session
initiation protocol (SIP).
z H.323 phone
The H.323 phone is a multimedia terminal device that supports the H.323
protocol.
z SG
The Signaling gateway (SG) connects the No.7 signaling network with the IP
network. It converts the N0.7 signaling of the public switched telephone network
(PSTN) and the signaling of the IP network.
z TMG
The Trunk media gateway (TMG) is located between the circuit switched network
and the IP packet switched network. It converts the formats between pulse code
modulation (PCM) signal streams and the IP media streams.
z UMG
The Universal media gateway (UMG) converts the media stream formats and the
signaling. It can act as a TMG, a built-in SG or an AMG. It can connect the
devices such as PSTN exchange, private branch exchange (PBX), access
network, network access server (NAS), and base station controller.
The MRS6100 supports open protocols like the SIP and the media gateway control
protocol (MGCP). It provides various interfaces to connect with the entities, such as
softswitch devices, AS, media gateways, IP intelligent terminals, and NM center. With
these interfaces, the MRS6100 can meet your special networking requirements.
1-4
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
z Open protocols
The MRS supports the following open protocols:
1) MGCP
2) SIP
3) Real-time transport protocol/RTP control protocol (RTP/RTCP)
4) Session description protocol (SDP)
5) Voice extensible markup language (VoiceXML or VXML) protocol, HTTP,
FTP, NFS and TCP/IP.
z The standard NMS interface is the man-machine language (MML) interface.
1-5
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
4) Administrator information
5) Logs.
z Ensure operation security
The MRS6100 ensure the system security on the following aspects:
1) Operator management
2) Login and logout control
3) Security control and protection
4) Operation logs.
5) Authority management
The MRS6100 authenticates the user before login and records the detailed operation
logs to ensure the system security and traceability.
The MRS6100 provides the following handy and practical operation and maintenance
(O&M) functions:
z Flexible and diversified management modes
The MRS6100 provides you with multiple maintenance modes such as the
graphic user interface (GUI) client and MML You can set up your NMS network
flexibly based on the network structure, management requirements and
investment scale. The MRS6100 support multi-access to the system from local
or remote clients.
z GUI
The OMS uses the O&M interface with the navigation tree. The MML Client
works with the GUI to ease your O&M tasks.
z Powerful traffic statistics capability
The MRS6100 uses lists a graphics to analyze and display the performance data.
It monitors the real-time performance data and collects the background
performance data. The MRS6100 also can meet your customized traffic statistics
requirements.
z Real-time fault management
The MRS6100 receives and reports the faults about the network devices in real
time. It provides real-time audible and visible alarms through the topology, alarm
panel, or the alarm box. Also, the MRS6100 provides the fault management
system to report and filter leveled faults. This helps the carriers quickly locate
and remove the faults.
z Comprehensive help system
The online help is integrated in the MRS6100. You can retrieve the help system
whenever you want.
z Other functions
The MRS6100 also supports the following functions:
1) Install software patches online.
2) Debug the system online.
1-6
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 1 System Overview
V. Smooth expansion
z Easy to update
The MRS6100 setup interface features Windows style. It provides the similar
setup wizard. The default settings are most applicable. This helps you install,
upgrade or recover the system easily. The program design is separated from the
data design. This ensures that the updated system can inherit the legacy data.
z Safe to update
During the update, the MRS6100 setup program backs up the system database
in multiple modes several times to ensure system security. Also, the MRS6100
setup program backs up the loading files of the old version to ensure that the
system files can be restored to the old version if the new version fails to be
loaded.
z Online update
The MRS6100 provides uninterrupted online update for network services
z Separate update tool
The MRS6100 provides you with a separate tool to ensure update efficiency and
security.
1-7
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 2 Hardware Structure
2-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 2 Hardware Structure
This subsystem loads the software or data, manages and maintains the devices, and
implements the inter-board communication.
It includes the System Management Unit (SMUI), the System Interface Unit (SIUI) of
the SMUI, and the Hot-Swap and Control Unit (HSCI).
z SMUI
The SMUI is the main control board of the frame. It loads the devices, configures the
data, and controls their working status.
z HSCI
The HSCI implements the bridging between the left and right shared resource buses,
board hot swap control, and intra-frame Ethernet bus switching.
The HSCI does not include a CPU. It is configured and maintained through the shared
resource bus by the SMUI.
This subsystem provides the call processing function for the SIP and the MGCP.
The Media Call Control Unit (MCCU) resolves the SIP and the MGCP. The VPS
interprets the VXML script. The MCCU and the VPS communicates with the Media
Service Unit (MSU) through the internal Ethernet bus to control the MSU for media
processing.
This subsystem manages and maintains the entire system. It consists of the following
devices:
z Back Administration Module (BAM)
z Work Station (WS)
z Emergency WS
Figure 2-2 and Figure 2-3 shows the configuration of the MRS6100. The SMUI, SIUI,
HSCI, ALUI, MCCU, and the UPWR must be installed and fastened in the fixed slots.
2-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 2 Hardware Structure
Each MSU can support up to 400 uncoded announcement voice channels or 240
codec IVR voice channels. You can configure the MSU as required.
2-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 3 Software Architecture
This subsystem is the software platform of the MRS6100. It uses HUAWEI distributed
object-oriented programmable real-time architecture (DOPRA) platform middleware
to provide the application layer with the uniform APIs.
Also, the support subsystem provides the upper layer with the implementation
mechanisms on the following functions:
z O&M
z Alarm management
z Traffic statistics
z Signaling and user tracing
z Data backup
z Board switchover
z Online loading
3-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 3 Software Architecture
This subsystem interprets the MGCP, SIP, and the VXML scripts.
The Ethernet IP interface is the lower layer interface protocol of the call processing
subsystem. The MCCU board processes the media access control (MAC) protocol
and the IP packets.
3-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 3 Software Architecture
The call processing subsystem processes the transport layer protocols like the UDP
and the TCP. These protocols bear the call control protocols like HTTP at the upper
layer over the IP network.
3-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 3 Software Architecture
The MRS6100 allocates and manages its resource through the media resource
management module. This module provides the following functions:
z Allocate the channel and conference resources to each SIP/MGCP call
z Reserve the resources.
z Recover the resources when the connection is released.
The MRS6100 serves as a media resource pool. It provides media services to the AS
or SoftSwitches. The MRS6100 also controls the service flows to simplify the
operation and control on the AS and SoftSwitches.
3-4
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 4 Media Resource Function
4-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 4 Media Resource Function
4.6 Recording
The MRS6100 supports recording for a channel or for the conference. It supports
several audio file formats, such as G.711A/u and G.729A. The recorded audio files are
stored in the specified directory on the FTP server.
4-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Figure 5-1 Using the MGCP and SIP with the MRS6100
As shown in Figure 5-1, the MRS6100 can be controlled by the SoftSwitch or the AS.
The control protocols include the MGCP, SIP, and the H.248.
z Under the control of the SoftSwitch, the protocols are used in the services
provided by the SoftSwitch, such as basic call services and supplementary
services.
z Under the control of the AS, the protocols are used in the services provided by
the AS, such as conferences, voice e-mail, and uniform communications.
5.2 MGCP
5.2.1 Brief Introduction
RFC2705 defines the API and the related MGCP. The MGCP is used to control the
voice over IP (VoIP) gateways from external call control units.
The MGCP defines a call control structure. In this structure, call control is separated
from the service bearer. As shown in Figure 5-2, the call control function is separated
from the media gateways (MG). The function is implemented by the external call
control unit, such as the media gateway controller (MGC) or the call agent (CA). The
MG executes the commands sent from the MGC. Therefore, the MGCP is essentially
a master/slave protocol.
5-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
I. Gateway
The call agent (CA) provides signaling and call processing functions. It is an external
call control element used to control the telephony gateways.
III. Endpoint
The endpoint is the data source or data sink. It can be a physical link or a virtual link
running on the physical link.
For example, the interface through which the trunk gateway terminal connects with
the PSTN exchange and the E-phone interface that the access gateway connects are
physical endpoints. The audio source in the MRS is a virtual endpoint.
To create a physical endpoint, you need to install the related hardware. To create a
virtual endpoint, you do not need to do so. You can use the related software to create
a virtual endpoint.
Endpoints are identified by endpoint identifiers. Endpoint identifiers are not case
insensitive.
An endpoint identifier consists of two parts:
z The local name of the endpoint in the gateway, and
z The domain name of the gateway.
5-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
5-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
When the two gateways are managed by the same CA, the connection can be set up
through the following steps:
1) The CA asks the first gateway to create a connection on the first endpoint. The
gateway allocates resources to that connection and responds to the command
through a session description. The session description contains the information
necessary for a third party to send the packets to the connection, such as IP
address, UDP port, and packing parameters.
2) The CA then asks the second gateway to create a connection on the second
endpoint. The command carries the session description provided by the first
gateway. The gateway allocates resources to this connection and responds to
the command through a session description.
3) The CA provides the second session description to the first endpoint by using the
command for modifying connections. Once this process is complete, the two
endpoints can communicate with each other.
The gateway creates the connection. It assigns a unique identifier for the connection
on the local end. The connection identifier is a hexadecimal character string.
Calls are identified by unique identifiers. The identifiers are created by the MGC. Call
identifiers can be considered as unstructured character strings. When an MGC builds
several connections for the same call, the connections must be associated with the
same call.
In the MGCP, the CAs are identified by domain names. To enhance the system
reliability, the MGCP can have a redundant CA. These CAs share the same domain
5-4
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
name but have different network addresses, such as IP addresses. Typically, the
gateway identifies a CA through its domain name. For lower-layer operations, the
gateway obtains the CA network addresses list from the domain name server (DNS),
and then uses an appropriate network address to communicate with the CA. The
redundancy mechanism is very helpful to enhance the reliability of the MRS6100.
Other entities, such as gateways and information servers, are also identified by their
domain names. Also, these entities can use the redundancy design to enhance the
reliability of the system. The CAs and gateways identify these entities through their
domain names.
With the domain names, you do not need to identify these entities using their network
addresses. The domain names are relatively stable while the network addresses can
be easily changed. For example, if an entity is moved to a different local access
network (LAN), the IP address of the entity will be changed. But you can keep using
the same domain name. The domain name lifetime ensures that other entities can
obtain the new IP addresses by updating the domain name information.
In the MGCP, CAs and other entities are represented by e-mail addresses.
For example:
Call-agent@ca.example.net represents the CA in the example network
Busy-signal@ann12.example.net represents the busy signal in the 12# information
server in the example network
Events and signals are essential to the MGCP. The CA may ask to be notified about
certain events that occur at an endpoint, such as offhook, onhook, flash-hook, or
dialing. The CA may request certain signals to be applied to an endpoint, such as dial
tone, ring back tone, or busy tone.
Events and signals are integrated into packages. Each package is supported by a
specific endpoint.
An event is named in the following format:
Package name/event name
In the name, the package name is optional because each type of endpoint has a
related default package. If the package name is not included in the name, the default
package name is used.
The symbol @ with the event connection can be added after the event name. you can
also use the event range and a wildcard to indicate an event name. the wildcard *
represents “all” while the wildcard $ represents “current or any”.
Each signal has an associated signal type, such as on/off (OO), timeout (TO), and
brief (BR).
Table 5-1 lists some basic packages.
5-5
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Package Package ID
General media package G
DTMF package D
MF package M
Trunk package T
Line package L
Handset emulation package H
RTP package R
Network access server package N
Announcement server package A
5-6
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
X. Digit map
The CA may request the gateway to collect the dialed digits. For example, the MRS
collects the dialed number or the credit card number. In this case, the CA loads a digit
map to the gateway. Like a numbering plan, the digit map collects all the numbers,
and then sends the digits in a message. This helps to save the network resources.
This digit map is expressed using a strict syntax. It is composed of a list of digits and
letters. If collected dial sequence matches one of the defined strings, it indicates
necessary digits have been collected. What are supported in the definition of digit
strings include the digits from 0 to 9, the letters from A to D, the pound sign (#), the
asterisk sign (*), the letters T and x, and the dot sign (.). The digit strings separated by
| are alternative number schemes. The brackets ([]) indicates any of them. The
asterisk sign (*) indicates the digits are reported one by one if * is dialed. The letter T
indicates the timer is detected timeout. The letter x indicates any digit. The dot sign (.)
indicates any number of letters, including zero number of letters, can appear before it.
The pound sign (#) indicates to report the digits immediately.
For example, we can dial the following numbers using a phone.
5-7
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The dial plan described above results in the following digit map:
(0T| 00T|[1-7]xxx|8xxxxxxx|xxxxxxx#|*xx|91xxxxxxxxxx|9011x.T)
MGCP
UDP
IP
MAC
MGCP messages are transmitted over UDP/IP. The transport layer protocol is UDP
and the network layer protocol is IP.
I. Command
Table 5-4 gives the names and corresponding meanings of MGCP commands, which
include connection processing and endpoint processing commands. There are nine
commands defined in this protocol.
Serial Command
Code Description
No. name
From MGC to MRS, used to show the
EndpointConfig
1 EPCF encoding feature of an endpoint circuit in the
uration
gateway.
5-8
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Serial Command
Code Description
No. name
From MGC to MRS, used by the call agent to
associate an endpoint with a specified IP
address and UDP port. Apart from that, a
CreateConnecti
2 CRCX CreateConnection command is also sent to
on
the remote endpoint, which is required to
create the connection between the two
endpoints.
ModifyConnecti From MGC to MRS, used to modify
3 MDCX
on parameters of established connections.
DeleteConnecti From MGC to MRS and MRS to MGC, used
4 DLCX
on to delete an existing connection.
Used to instruct the gateway to monitor
NotificationReq
5 RQNT specific events on a specified endpoint. If it
uest
happens, the call agent will be notified.
From MRS to MGC, used by the gateway to
6 Notify NTFY notify the call agent that a specific event
requested to monitor takes place.
From MGC to MRS, used by the call agent to
7 AuditEndpoints AUEP audit the status of an endpoint or a group of
endpoints.
From MGC to MRS, used by the call agent to
AuditConnectio
8 AUCX audit the status of a connection on an
n
endpoint.
II. Response
All MGCP commands require responses. The response carries a return code which is
an integer, which can be within one of the following ranges:
100–199: indicates a provisional response.
200–299: indicates a successful completion of the command.
400–499: indicates that a transient error occurs.
500–599: indicates that a permanent error occurs.
Whether to return response parameters depends on specific commands.
Table 5-5 gives response codes that have been defined.
5-9
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Response
Meaning
code
The transaction is currently being processed. An actual completion
100
message will follow on later.
200 The requested transaction is already processed normally.
5-10
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Response
Meaning
code
522 No such event or signal.
523 Unknown action or invalid combination of actions.
524 Internal inconsistency in LocalConnectionOptions.
I. Commands
1) Command format
Figure 5-5 shows the format of an MGCP command, which consists of a command
line and a group of parameter lines. A line feed character distinguishes the command
line and each parameter line.
2) Command parameters
z ResponseAck (K)
The response acknowledgement attribute indicates the identifiers of transactions that
have received the response command. It contains a comma-separated list of
confirmed transaction ID ranges, for example, K: 6234–6255, 6257, 19030–19044.
z BearerInformation (B)
5-11
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
It refers to the bearer attribute. At present, only one attribute, namely “encoding” (the
code is “e”), is defined. Its values can be set to “A” which represents A-law and “µ”
which represents µ-law. For example, a BearerInformation code is B: e:mu.
z Call-ID (C)
Call-ID is a globally unique parameter that identifies the call (or session) to which this
connection belongs. Connections that belong to the same call share the same Call-ID.
The Call-ID can be used to identify calls for reporting and accounting purposes.
Call-ID identifies calls, which is a hexadecimal string of 32 characters at the
maximum.
z ConnectionId (I)
The ConnectionId parameter is a hexadecimal string of 32 characters at the
maximum.
z NotifiedEntity (N)
NotifiedEntity specifies where the notifications will be sent. If this parameter is absent,
the notifications will be sent to the originator of the NotificationRequest.
z RequestIdentifier (X)
RequestIdentifier is used to correlate this request with the notifications that it triggers.
RequestIdentifier is a hexadecimal string of 32 characters at the maximum.
z LocalConnectionOptions (L)
The local connection options describe the optional parameters that the call agent
recommends to the gateway. The parameters include: the packing period in
milliseconds (encoded as the keyword “p”), the preferred type of compression
algorithm (encoded as the keyword “a”), the bandwidth in kilobits per second
(encoded as the keyword “b”), the echo cancellation parameter (encoded as the
keyword “e”), the gain control parameter (encoded as the keyword “gc”), the silence
suppression parameter (encoded as the keyword “s”), the type of service parameter
(encoded as the keyword “t”), the resource reservation parameter (encoded as the
keyword “r”), the encryption key (encoded as the keyword “k”), and the type of
network (encoded as the keyword “nt”). All these parameters are optional. In the case
of multiple parameter values, commas are used for separation, for example:
L: p:10, a:PCMU
L: p:10, a:G726-32
L: p:10-20, b:64
L: b:32-64, e:off
z Connection Mode (M)
Table 5-6 gives connection modes and corresponding meanings.
5-12
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
z RequestedEvents (R)
The RequestedEvents parameter provides a list of events that have been requested.
Each event can be restricted by a requested action, or by a list of actions. The actions,
when specified, are encoded as a list of keywords, enclosed in parenthesis and
separated by commas. Table 5-7 lists the codes for various actions.
Code Action
N Notify immediately
A Accumulate
D Treat according to digit map
S Swap
I Ignore
K Keep signal(s) active
E Embedded notification request
When no action is specified, the default action is to notify the event. In this case, ft
equals to Ft (N). Events that are not listed are ignored.
5-13
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The digit-map action can only be specified for the digits, letters and inter-digit timers in
the MF and DTMF packets, or in other packages that need to define the encoding of
digits and timers.
The requested list is encoded on a single line, with event/action groups separated by
commas. The following is an example of RequestedEvents encoding.
R: hu(N), hf(S,N)
R: hu(N), [0-9#T](D)
z SignalRequests (S)
The SignalRequests parameter provides the name of the signals that have been
requested.
Several signals, such as announcement or ADSI display, can be qualified by
additional parameters:
the name and parameters of the announcement
the string that must be displayed
These parameters are encoded as a set of UTF8 character strings, separated by
commas and enclosed within parenthesis, as in:
S: adsi("123456 Francois Gerard")
S: ann(no-such-number, 1234567)
When several signals are requested, their codes are separated by commas, for
example:
S: asdi(123456 Your friend), rg
z ObservedEvents (O)
The ObservedEvents parameter provides a list of events that have been observed.
The following are examples of observed actions.
O: L/hu
O: 8295555T
O: 8,2,9,5,5,L/hf,5,5,T
O: L/hf, L/hf, L/hu
z ConnectionParameters (P)
Connection parameters are encoded as a string of type and value pairs, where the
type is either a letter identifier of the parameter or an extension type, and the value is
decimal integer. Types are separated from value by an equal sign (=). Parameters are
encoded from each other by a comma.
Table 5-8 shows the connection parameter types.
5-14
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Example
P: PS=1245, OS=62345, PR=0, OR=0, PL=0, JI=0, LA=48
z ReasonCode (E)
Reason codes are used by the gateway when it deletes a connection to inform the call
agent about the reason for deleting the connection. They may also be used in a
RestartInProgress command to inform the gateway of the reason of the restart. The
reason code is an integer. Table 5-9 lists the defined values.
Reason codes are three-digit numeric values. The reason code is optionally followed
by a white space and commentary, for example:
900 Endpoint malfuctioning
z SpecificEndpointId (Z)
5-15
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
5-16
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The RestartMethod parameter specifies the type of restart, encoded as one of the
following keywords:
graceful: A “graceful” restart method indicates that the specified endpoints will be
taken out of service after the specified delay. The established connections are not yet
affected, but the call agent should refrain to establish new connections, and should try
to gracefully tear down the existing connections.
forced: A “forced” restart method indicates that the specified endpoints are taken
abruptly out of service. The established connections, if any, are lost.
restart: A “restart” method indicates that service will be restored on the endpoints after
the specified restart delay. There are no connections that are currently established on
the endpoints.
disconnected: A “disconnected” method indicates that the endpoint has become
disconnected and is now trying to establish connectivity. The restart delay specifies
the number of seconds the endpoint has been disconnected. Established connections
are not affected.
cancel-graceful: A “cancel-graceful” method indicates that a gateway is canceling a
previously issued “graceful” restart command.
Example
RM:restart
z RestartDelay (RD)
The restart delay parameter is expressed as a number of seconds. If the number is
absent, the delay value is considered null.
In the case of the “graceful” method, a null delay indicates that the call agent should
simply wait for the natural termination of the existing connections, without establishing
new connections. The restart delay is always considered null in the case of the
“forced” method. A restart delay of null for the “restart” method indicates that service
has already been restored. This will typically occur after gateway startup/reboot.
z EventStates (ES)
The EventStates parameter is encoded as a comma separated list of events.
Example
E: hu
z Capabilities (A)
The Capabilities parameters inform the call agent about capabilities of endpoints
when they are audited. The encoding of capabilities is based on the
LocalConnectionOptions encoding for the parameters that are common to both. The
parameters used are Event Packages (v), Modes (m), a list of supported codec (*),
type of network (nt), and so on.
5-17
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
In addition, capabilities can also contain a list of supported packages and a list of
supported modes.
z RemoteConnectionDescriptor (RC)
The RemoteConnectionDescriptor includes the same fields as in the
LocalConnectionDescriptor, such as IP address, UDP port and packetization
parameters. For the CreateConnection command, this parameter may have a null
value when the information for the remote end is not known yet. This occurs because
the entity that builds a connection starts by sending a CreateConnection to one of
the two gateways involved in it. For the first CreateConnection issued, there is no
information available about the other side of the connection. This information may be
provided in SDP packets later through a ModifyConnection call.
z LocalConnectionDescriptor (LC)
The LocalConnectionDescriptor is a session description that contains information
about IP address and port number suitable for the local connection, as defined in SDP.
3) Command expressions
What are within the parenthesis preceded by the command name are input
parameters. Those enclosed by brackets are optional.
z EndpointConfiguration
EPCF (EndpointId, BearerInformation)
z NotificationRequest
RQNT
(EndpointId,[NotifiedEntity,][RequestedEvents,]RequestIdentifier,[DigitMap,][SignalR
equests,][QuarantineHandling,][DetectEvents,][encapsulated
EndpointConfiguration])
z Notify
NTFY (EndpointId,[NotifiedEntity,]RequestIdentifier,ObservedEvents)
z CreateConnection
CRCX
(Call-ID,EndpointId,[NotifiedEntity,]LocalConnectionOptions,]Mode,[RemoteConnecti
onDescriptor,][Encapsulated NotificationRequest,][Encapsulated
EndpointConfiguration])
z ModifyConnection
MDCX
(Call-ID,EndpointId,ConnectionId,[NotifiedEntity,][LocalConnectionOptions,][Mode,][
RemoteConnectionDescriptor,][Encapsulated NotificationRequest,][Encapsulated
EndpointConfiguration])
z DeleteConnection
DeleteConnection from the call agent:
5-18
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
DLCX (Call-ID,EndpointId,ConnectionId,[Encapsulated
NotificationRequest,][Encapsulated EndpointConfiguration])
DeleteConnection from the VoIP gateway:
DLCX (Call-ID,EndpointId,ConnectionId,Reason-code,Connection-parameters)
DeleteConnection from the call agent to delete multiple connections:
DLCX (Call-ID,EndpointId)
z AuditEndpoint
AUEP (EndpointId,RequestedInfo)
z AuditConnection
AUCX (EndpointId,ConnectionId,RequestedInfo)
z RestartInProgress
RSIP (EndpointId,RestartMethod,[RestartDelay,][Reason-code])
4) Command example
The following is an MGCP command encoding example.
CRCX 693585490 ms/cnf/1@mrs6100 MGCP 1.0
C:a265
L:a:PCMA,P:20
M:sendrecv
v=0
c=IN IP4 182.20.40.4
m=audio 30002 RTP/AVP 8
The 1st line: The CreateConnection command. The transaction identifier is
693585490 and it is used to correlate this command with the responses that it triggers.
It indicates to create a connection between MGC and the first port of the MRS6100
whose domain name is mrs6100 and the interface name is ms/cnf. The protocol
version of MGCP is 1.0.
The 2nd line: The call identifier is a265.
The 3rd line: The local connection options. The call agent recommends to the MRS
that the compression algorithm is PCMA and the encapsulation delay is 20
milliseconds.
The 4th line: The connection mode is sendrecv, that is, both sending and receiving
packets are allowed.
The 5th line: Null, indicating what is preceded is an SDP session description.
The 6th line: The SDP protocol version is 0. It is the local connection descriptor at this
time.
5-19
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The 7th line: c in the response identifies the connection information. IN refers to
network type in the form of a text string. The currently defined IN is Internet. IP4
indicates the type of connection address is IP4. 182.20.40.4 represents the network
address of the remote gateway of MRS that has a connection with the MGC.
The 8th line: Media description. audio indicates the type of media is audio. (audio is
used for audio connections, and nas is used for data access.) 30002 is the number of
transport layer port to which media streams are transmitted. RTP/AVP is the transport
layer protocol. Its value is associated with the type of address in the c line. For IP4, a
great number of media service streams are transferred over RTP/UDP. There are two
classes of protocols defined: RTP/AVP, audio/video application document,
transported over UDP; Udp, the DUP protocol. At this time, the mapping relation from
RTP payload type to encoding is that 8 corresponds to the media encoding format
PCMA.
II. Responses
1) Response format
Similar to the format of MGCP commands, the response format is composed of a
response line followed by a group of optional parameter lines. The response line
consists of the response code, transaction identifier and an optional commentary that
is separated by a space, as shown in Figure 5-6. The response code is a three-digit
numeric value, indicating the execution status of the command.
2) Response parameters
The response parameter lines are optional and depend on the specific commands.
For more information, refer to the section “Command parameters”, earlier in this
chapter.
3) Response expressions
What are within the parenthesis preceded by the command name are response
parameter values. Those enclosed by brackets are optional.
z EndpointConfiguration
EPCF (ReturnCode)
z NotificationRequest
5-20
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
RQNT (ReturnCode)
z Notify
NTFY (ReturnCode)
z CreateConnection
CRCX (ReturnCode,ConnectionId,[SpecificEndpointId,][LocalConnectionDescriptor])
z ModifyConnection
MDCX (ReturnCode,[LocalConnectionDescriptor])
z DeleteConnection
DeleteConnection from the call agent:
DLCX (ReturnCode,Connection-parameters)
DeleteConnection from the VoIP gateway:
DLCX (ReturnCode)
DeleteConnection from the call agent to delete multiple connections:
DLCX (ReturnCode)
z AuditEndpoint
AUEP
(ReturnCode,EndpointIdList|{[RequestedEvents,][DigitMap,][SignalRequests,][Requ
estIdentifier,][NotifiedEntity,][ConnectionIdentifiers,][DetectEvents,][ObservedEvents,
][EventStates,][BearerInformation,][RestartReason,][RestartDelay,][ReasonCode,][C
apabilities]})
z AuditConnection
AUCX
(ReturnCode,[Call-ID,][NotifiedEntity,][LocalConnectionOptions,][Mode,][RemoteCon
nectionDescriptor,][LocalConnectionDescriptor,][ConnectionParameters])
z RestartInProgress
RSIP (ReturnCode,[NotifiedEntity])
4) Response example
The following is an example of connection response.
200 693585490 CRCX OK
I:1607901
v=0
c=IN IP4 182.20.50.101
m=audio 10000 RTP/AVP 8 0 18 4
a=ptime:20
5-21
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The 1st line: 200 indicates the successful receipt of the command. 693585490 is a
transaction identifier which is the same as the transaction identifier contained in the
CreateConnection command that triggers this response. CRCX OK is a
commentary.
The 2nd line: The connection identifier is 1607901.
The 3rd line: Null, indicating what is preceded is an SDP session description.
The 4th line: The SDP protocol version is 0. It is the local connection descriptor at this
time.
The 5th line: c in the response identifies the connection information. IN refers to
network type in the form of a text string. The currently defined IN is Internet. IP4
indicates the type of connection address is IP4. 182.20.50.101 represents the local
network address of MRS6100.
The 6th line: Media description. audio indicates that the type of media is audio. (audio
is used for audio connections, and nas used for data access.) 10000 is the number of
transport layer port to which media streams are transmitted. RTP/AVP is the transport
layer protocol. Its value is associated with the type of address in the c line. For IP4, a
great number of media service streams are transferred over RTP/UDP. There are two
classes of protocols defined: RTP/AVP, audio/video application document,
transported over UDP; Udp, the DUP protocol. For audio and video signals, 8 0
represents the type of media payload defined in the RTP audio/video application
document. It means that all the formats carried in the session might be used, but the
first one is the default format for the session. At this time, the mapping relation from
RTP payload type to encoding is that 34 corresponds to the media encoding format
H263 .8 corresponds to the media encoding format PCMA. 0 corresponds to the
media encoding format PCMU. 18 corresponds to the media encoding format G.729.
4 corresponds to the media encoding format G.723.
The 7th line: Attribute. Attribute is the basic method for SDP extension. It can be
defined as session-level attribute or media-level attribute. There are two forms of
attributes:
a=<flag>, as feature attribute. It is a binary attribute, indicating the session has this
nature. For example, a=recvonly indicates the feature is “receive only”.
a=<attribute>:<value>, as numeric value attribute. For example, a=ptime:20 indicates
the domain name of the media attribute is ptime and the value of the media attribute is
20.
If the control protocol is MGCP, MRS6100 must register to MGC before it can proceed
to subsequent procedures. The registration flow of MRS6100 is shown in Figure 5-7.
5-22
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
MRS6100 MGC
RSIP
RSIP_RSP
The 1st line: the RestartInProgress command. The transaction identifier is 836, used
to correlate this command with responses that it triggers. The field *@mrs6100
indicates the restart of all endpoints with the domain name mrs6100. The MGCP
version is V1.0.
The 2nd line: The restart mode is restart. It indicates that the service will be restored
on endpoints of the media gateway (MG) after the specified restart delay. There are
no connections that are currently established on endpoints of MG.
2) Event 2: MGC sends a response to the registration request sent by MRS. The
following are RestartInProgress response examples.
Example 1:
200 836 OK
z The field 200 indicates the successful receipt of the command. The field 836 is a
transaction identifier, the same as the transaction identifier contained in the
command that triggers this response. OK is a comment. It indicates that MG
receives the response and the registration succeeds.
Example 2:
500 836 The endpoint is unknown
The field 500 indicates that the transaction cannot be carried out, because the
endpoint is unknown. The field 836 is a transaction identifier, the same as the
transaction identifier contained in the command that triggers this response. The
endpoint is unknown is a comment. It indicates that MG receives the response and
the registration fails.
Figure 5-8 shows the flow of MRS6100 announcement playing and calling under the
control of one MGC.
In the following example, it is assumed that:
5-23
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
MGC MRS6100
CRCX (1)
CRCX ACK
RQNT(pa,pc) (2)
RQNT ACK
NTFY
(3)
(oc,of,digit)
NTFY ACK
DLCX (4)
DLCX ACK
v=0
c=IN IP4 182.20.40.4
m=audio 30002 RTP/AVP 8
The 1st line: the CreateConnection command. The transaction identifier is 693585490,
used to correlate this command with responses that it triggers.MGC establishes a
connection with the Endpoint1 of MRS6100. MRS6100's domain name is
mrs6100.com and interface name is ms/cnf. The MGCP version is V1.0.
5-24
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
v=0
c=IN IP4 182.20.50.101
m=audio 10000 RTP/AVP 8 0 18 4
a=ptime:20
The field 200 indicates the successful receipt of the command. 693585490 is a
transaction identifier, the same as the transaction identifier contained in the command
that triggers this response. OK is a comment. It indicates that MG has received and is
processing the request. The field I is the connection identifier. MRS returns the
connection identifier to MGC after establishing a connection. In addition, MRS returns
the SDP session description, MRS port number and IP address.
2) Event 2: After establishing a connection, MGC sends the RQNT announcement
playing command to MRS.
z RQNT encoding
RQNT 170983909 ms/cnf/1@mr6100.com MGCP 1.0
X:1e000424
R:A/of(N),A/oc
S:BAU/pa@0(an=HWF001000B?lang=chi iv=10 it=20)
5-25
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The 1st line: the OperationRequest command. The endpoint is ms/cnf/1, and the
domain name is mrs6100.com.
The 2nd line: The request identifier is 1e000424, used to correlate this request with
notifications that it triggers.
The 3rd line: Request events include the oc (operation complete) event and the of
(operation fail) event in packet A.
The 4th line: The signal tone is the pa (play announcement) event in packet BAU. The
voice is HWF001000B. The playing language is Chinese. The parameter it indicates
the announcement playing is carried out for 20 times. The parameter iv indicates that
the announcement playing interval is one second.
z RQNT_ACK encoding
200 170983909 OK
The field 200 indicates the successful receipt of the command. 170983909 is a
transaction identifier that is the same as the transaction identifier contained in the
command that triggers this response. OK is a comment. It indicates that MG has
received and is executing the request.
3) Event 3: After playing announcements, MRS sends the NTFY command to MGC
to notify it of the completion.
z NTFY encoding
NTFY 170983911 ms/cnf/1@mr6100.com MGCP 1.0
X:1e000424
O:oc
The 1st line: the Notify command. The endpoint is ms/cnf/1, and the domain name is
mrs6100.com.
The 2nd line: The request identifier is 1e000424. The value is the same as the value
of the parameter contained in the RQNT command that triggers this notification. It is
used to correlate the RQNT command with the NTFY command.
The 3rd line: The oc event is detected.
z NTFY ACK encoding
200 170983911 OK
The field 200 indicates the successful receipt of the command. 170983911 is a
transaction identifier, the same as the transaction identifier contained in the command
that triggers this response. OK is a comment. It indicates that MG has received and is
executing the request.
4) Event 4: MGC sends a DLCX command to MRS, requesting to delete the
existing connection.
z DLCX encoding
DLCX 171000292 ms/cnf/1@mr6100.com MGCP 1.0
5-26
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
I:1607901
O:oc
Line 1: the DeleteConnection command. The endpoint is ms/cnf/1, and the domain
name is mrs6100.com.
The 2nd line: The connection identifier is 1607901.
z DLCX ACK encoding
250 171000292 OK
P:PS=300,OS=3000,PR=1000,OR=10000,PL=0,JI=0,LA=0
250 indicates the connection is deleted.171000292 is a transaction identifier. OK is a
comment. The 2nd line is the returned statistics information.
Figure 5-9 shows the flow of MRS6100 announcement playing and calling under the
control of one MGC.
The connection establishing and deleting have the same flow with the announcement
playing. Here we only describe the digit collection flow.
MGC MRS6100
RQNT(pc)
(1)
RQNT ACK
NTFY
(digit) (2)
NTFY ACK
1) Event 1: After establishing a connection, MGC sends the RQNT digit collection
command to MRS.
z RQNT encoding
RQNT 1709839323 ms/cnf/1@mr6100.com MGCP 1.0
X:1e000425
R:D/[0-9*#T](N),of
D:( 0xxxxxxxxxx|*|x.# )
Line 1: It indicates the operation request command. The endpoint is ms/cnf/1, and the
domain name is mrs6100.com.
5-27
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Line 2: The request ID is 1e000425. The ID associates the request with the
notification.
Line 3: The request events are the digit collecting event under packet D and the
operation fail (of) event.
Line 4: It indicates the Digit Map. The MGC delivers the dial scheme to the gateway
where the Endpoint1 is located. 0xxxxxxxxxx represents an 11-digit number starting
with 0. The asterisk (*) indicates that if you dial *, the number is reported one by one.
x.# indicates if you dial any number and then #, the number is reported immediately.
z RQNT ACK response encoding
200 1709839323 OK
The 1st line: the Notify command. The endpoint is ms/cnf/1, and the domain name is
mrs6100.com.
The 2nd line: The request identifier is 1e000424. The value is the same as the value
of the parameter contained in the RQNT command that triggers this notification. The
request identifier is used to correlate the RQNT command with the NTFY command.
The 3rd line: The number detected by MRS is 12345.
z NTFY ACK encoding
200 170983911 OK
The field 200 indicates the successful receipt of the command. 170983911 is a
transaction identifier which is the same as the transaction identifier contained in the
5-28
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Figure 5-10 shows the call flow of an MRS6100 three-party conference under the
control of one MGC. The flow is the simplest one. There are some more complex
flows that are alike in principle. To focus on the description of MGCP, we do not
introduce other flows here. In the following example, it is assumed that:
z The Endpoint1 ID is ms/cnf/1@mrs6100.com.
z The IP address of MCCU of MRS6100 is 182.20.50.101.
MGC MRS6100
CRCX (1)
CRCX ACK
CRCX (2)
CRCX ACK
CRCX (3)
CRCX ACK
RQNT(pa) (4)
RQNT ACK
NTFY (5)
NTFY ACK
DLCX (6)
DLCX ACK
v=0
c=IN IP4 182.20.40.4
m=audio 30002 RTP/AVP 8
z CRCX ACK encoding
5-29
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
200 693585490 OK
I:1607901
v=0
c=IN IP4 182.20.50.101
m=audio 10000 RTP/AVP 8 0 18 4
2) Event 2: MGC specifies MRS6100 to send a CRCX command to the same
Endpoint1, requesting to establish the second-party connection. The mode is not
specified. While selecting the confrnce or the sendrecv mode, participants can
both listen and speak. While selecting the sendonly or the recvonly mode,
participants can only speak or only listen. Other parameters can also be modified
according to the successive MDCX.
z CRCX encoding
CRCX 693585491 ms/cnf/1@mrs6100.com MGCP 1.0
C:a265
L:a:PCMA,P:20
M:confrnce
v=0
c=IN IP4 182.20.40.5
m=audio 30004 RTP/AVP 8
z CRCX ACK encoding
200 693585491 OK
I:1607902
v=0
c=IN IP4 182.20.50.101
m=audio 10002 RTP/AVP 8 0 18 4
3) Event 3: MGC specifies MRS6100 to send a CRCX command to the same
Endpoint1, requesting to establish the third-party connection. The mode is not
specified. While selecting the confrnce or the sendrecv mode, participants can
both listen and speak. While selecting the sendonly or the recvonly mode,
participants can only speak or only listen. Other parameters can also be modified
according to the successive MDCX. Then the three-party conference has been
established.
z CRCX encoding
5-30
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
v=0
c=IN IP4 182.20.40.5
m=audio 30006 RTP/AVP 8
z CRCX ACK encoding
200 693585492 OK
I:1607903
v=0
c=IN IP4 182.20.50.101
m=audio 10004 RTP/AVP 8 0 18 4
4) Event 4: After establishing a connection, MGC sends the RQNT announcement
playing command to MRS, to play announcements for the entire conference. If
the command contains a connection identifier, MRS will play announcements to
a specified party.
z RQNT encoding
RQNT 170983709 ms/cnf/1@mr6100.com MGCP 1.0
X:1e000324
R:of, oc
S:BAU/pa(an=HWF001000B?lang=chi)
z RQNT ACK encoding
200 170983709 OK
5) Event 5: After the announcement playing is completed, MRS sends a NTFY
command to MGC, to notify it of the completion of the announcement playing for
the entire conference.
z NTFY encoding
NTFY 170983917 ms/cnf/1@mr6100.com MGCP 1.0
X:1e000429
O:oc
z NTFY ACK encoding
200 170983917 OK
5-31
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
6) Event 6: MGC sends a DLCX command to MRS, requesting to delete the entire
conference. If the command does not contain a connection identifier, it indicates
the entire conference is to be deleted. Or a specified party of the conference is to
be deleted.
z DLCX encoding
DLCX 171000299 ms/cnf/1@mr6100.com MGCP 1.0
z DLCX ACK encoding
250 171000292 OK
P:PS=300,OS=3000,PR=1000,OR=10000,PL=0,JI=0,LA=0
5.3 SIP
5.3.1 Basic Concepts
Put forward and studied by the IETF, Session Initiation Protocol (SIP) is an
application-layer control protocol for multimedia communication over IP network,
which can be used for creating, modifying and terminating sessions with one or more
participants. These sessions include Internet multimedia conferences, Internet
telephone calls, distance learning, telemedicine, and similar applications.
Multimedia sessions refer to two-party or multiparty interactive multimedia
communication activities on the Internet. Participants in a session can communicate
through multicast or through a mesh of unicast relations. Alternatively, they can
communicate through a combination mode of these two.
SIP learns from design concepts of other Internet standards and protocols and follows
Internet principles including the concision, openness, compatibility and expandability,
with security issues taken into account. On the other hand, SIP comprehensively
provides support to traditional PSTN services including IN and ISDN services.
SIP invitations with session descriptions are used to create sessions, which allow
participants to agree on a set of compatible media types. The protocol supports user
mobility by sending proxy and redirecting requests to the user’s current location.
Users can also register their current locations. SIP is not tied to any particular
conference control protocol. It is also designed to be independent of the lower-layer
transport protocol, so SIP can be extended with additional functions.
Being an application-layer multimedia session protocol, SIP can be used to initiate
sessions, as well as inviting members to sessions that have been advertised and
established by other means. Sessions can be advertised using multicast protocols
such as Session Announcement Protocol (SAP), electronic mail, web pages or
Lightweight Directory Access Protocol (LDAP). SIP supports name mapping and
redirection services, allowing the implementation of ISDN and IN services. These
facilities also enable personal mobility, that is, the ability of end users to request and
5-32
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
5.3.2 Terms
I. Call
A call refers to a conference where participants are all invited by a common source. It
is identified by a globally unique call-ID.
For example, all participants invited by a common source in a conference form one
call. A point-to-point Internet telephony conversation is one of the simplest sessions
and maps into a single SIP call.
A call is generally established by the caller. However, it can also be established by a
third party who does not participate in the media communication, where the caller of
the session is not the same as the inviter of the session. For multicast conferences,
when a user is invited to one multicast session by several people at the same time,
each of these invitations is a unique call. In an MCU-based call-in conference, each
participant uses a separate call to invite himself to the MCU.
5-33
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
II. Transaction
SIP is a client/server protocol. A SIP transaction occurs between a client and a server
and comprises all messages from the first request to the final response sent from the
server to the client.
A normal call consists of three transactions. Call initiation consists of two operation
requests, INVITE and ACK. The former requires a response. The latter is used for
acknowledging the reception of the final response, and need not to send back a
response. Call termination consists of one operation request, BYE.
SIP uniform resource locators (URLs) are used for addressing purposes. The SIP
URL syntax is defined according to the uniform resource ID (URI) guidelines specified
in RFC 2396. The user name field could be a telephone number to support addressing
of IP telephony gateway and achieve the interworking between IP calls and PSTN.
A SIP URL has the syntax:
SIP: User name: Password @ Host: Port: Transmission Parameters: User
parameters: Method parameters: TTL parameters: Server address parameters?
header name= header value.
SIP indicates that SIP is used for the communication to the specified end system.
User name is composed of any characters. Generally, it can be a phone number or a
user name as in E-mail address.
Host is either a domain name or an IPv4 address.
Port refers to the port number to which a request message is sent. The default port
number is 5060, the public SIP port number.
Password can be included in a SIP URL, which is not recommended for the sake of
security.
Transport parameter indicates the used transport protocol, TCP or UDP. The default
transport parameter is UDP.
A function of SIP URL is to allow the host to be an IP telephony gateway with a
telephone number as the username. Because BNF syntax cannot distinguish
telephone number from general username, User parameter is added to follow the
domain name. Two values are available for this field: IP and phone. When the field is
set to phone, the username is a telephone number and the corresponding end
system is an IP telephony gateway.
Method parameter refers to the method (operation) to be used.
Lifetime parameter indicates the life of UDP multicast data packets. This parameter
is valid only when the transport parameter is set to UDP and the server address
parameter is set to multicast address.
5-34
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Server address parameter indicates the address of the server communicating with
the user, which overwrites the address in the host field. It is usually a multicast
address.
Transport parameter, Lifetime parameter, Server address parameter, and
Method parameter are URL parameters used only in a redirect address, that is, the
Contact field which will be mentioned later.
The following are some SIP URL examples.
Sip: 55500200@182.20.1.112;
55500200 is a username. 182.20.1.112 is the IP address of an IP telephony gateway.
Sip: 55500200@127.0.0.1:5061; User=phone;
55500200 is a username. 127.0.0.1 is the IP address of a host. 5061 is a port number
of the host. The user parameter is phone, indicating the username is a telephone
number.
Sip: alice@registrar.com; method=REGISTER;
Alice is a username. registrar.com is the domain name of a host. Register is the
method parameter.
User location is based on registration. After a SIP user terminal is powered on, it starts
to register to a registrar. For that specific purpose, REGISTER request and
registration procedure are defined in SIP.
V. Location service
A location service is used by a SIP redirect or proxy server to obtain information about
a callee's possible location. Location services are offered by location servers.
Location servers may be co-located with a SIP server, but the manner in which a SIP
server requests location services is beyond the scope of this document.
Proxy server is a logical network entity that acts as both a server and a client for the
purpose of forwarding requests or responses on behalf of other clients. Proxy server
may be in one of the three states: Stateless, Stateful and Call Stateful. It attempts to
forward requests to multiple addresses with a branch or cycle method.
Proxy server implements the functions of routing, authentication, charging monitoring,
call control and service provision.
Redirect server is a server that accepts a SIP request, maps the address into zero or
several new addresses, and returns these addresses to the client. Then the client can
directly initiate requests to these new addresses again. Redirect server implements
5-35
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
the routing function rather than receive or reject calls. Cooperating with a registration
process, it can support the mobility of SIP terminals.
VIII. Registrar
UAC is a client application that initiates the SIP request. For example, SIP Phone is
an application of UAC.
UAS is a client application that receives the SIP request. For example, MRS6100 is
an application of UAS.
The distinguishing of UAC and UAS is based on one transaction.
Figure 5-11 shows the protocol stack structure of IETF multimedia data and control
architecture.
RTP
TCP UDP
IP
Figure 5-11 Protocol stack structure of IETF multimedia data and control architecture
SIP is part of the overall IETF multimedia data and control architecture, cooperating
with other protocols such as:
5-36
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
SIP messages are encoded in text form. There are two types of messages, request
messages and response messages.
I. Request messages
Request messages are SIP messages sent from a client to a server, for invoking
particular operations. Request messages include INVITE, ACK, OPTIONS, BYE,
CANCEL and REGISTER messages. Functions of these messages are listed in
Table 5-10.
Request
Message meanings
messages
The INVITE message indicates that the user is being invited to
participate in a session. The message body contains a
description of the session to which the callee is being invited.
For two-party calls, the caller indicates the type of media it is
able to receive as well as their parameters. A success response
INVITE must indicate in its message body which media the callee
hopes to receive and may indicate the media the callee is going
to send.
The callee can acknowledge the participating of the caller and
send the 200 (OK) response, according to the Call-ID or the
identifier in the session description.
The ACK request confirms that the client has received a final
ACK response to an INVITE request. ACK is used only with INVITE
messages.
UAC uses BYE to indicate to the server that it hopes to release
BYE
the call.
The CANCEL request cancels a pending request, but does not
CANCEL affect a completed request. (A request is considered completed
if the server has returned a final status response.)
5-37
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Request
Message meanings
messages
REGISTER MG registers to MGC.
The OPTIONS request is used to query servers about their
OPTIONS
capabilities.
Serial
Status-Code Message functions
No.
Informational Indicating the request message has been received
1xx
(provisional) and is being processed
100 Trying
180 Ringing
182 Queued
200 OK
5-38
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Serial
Status-Code Message functions
No.
401 Prohibited
403 Forbidden
410 Gone
420 No reply
485 Ambiguous
493 Undecipherable
5xx Server error The server failed to fulfill an apparently valid request.
5-39
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Serial
Status-Code Message functions
No.
501 Not implemented
502 Invalid gateway
503 Service unavailable
504 Server time-out
505 Version not supported
513 Message too large
6xx Global failure The request cannot be fulfilled at any server.
600 All busy
603 Decline
604 Not exist anywhere
606 Not acceptable
Note:
Both the request and the response messages contain SIP fields and SIP message
fields.
SDP message fields are added into SIP messages.
I. Request messages
5-40
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Start
Command Peer UPI Version
line
Call-ID:Value
From:Value
To:Value
Cseq:Value
Via:Value
Contact:Value
Message
Max-Forwards:Value head
Allow:Value
Content-Lengh:Value
Supported:Value
User-Agent:Value
Content-Type:Value
... ...
Space
SDP Message
body
5-41
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The host is a domain name defined globally or an IP address routable globally. The
local ID is composed of unique URI characters in the scope of host. Otherwise, the
local ID must be a globally unique value to ensure the global uniqueness of Call-ID.
Call-IDs are case-sensitive.
An example of Call-ID field :
Call-Id: call-973636852-4@182.20.20.105
182.20.20.105 is the IP address of a host. call-973636852-4 is a globally unique local
ID.
z From
All requests and responses must contain the From field that indicates the initiator of
the request. The server duplicates this field from the request message to response
messages.
This field has a generic format:
From: display-name<SIP-URL>;tag=xxxx
The display-name is the character displayed on the user interface. The system will
use the display name Anonymous if the identity of the client remains hidden. The
display-name is optional. The tag is a string of hexadecimal numbers in which the
hyphen (-) can be added. When two user instances sharing the same SIP address
use the same Call-ID to initiate a call invitation, this tag is used for distinguishing
purposes. The tag value must be globally unique. A user should maintain the same
Call-ID and tag value in the whole process of a call.
An example of From field:
From: <sip:1000@182.20.20.105>;tag=1c17691
z To
The To field specifies the logical recipient of the request. The format of the To field is
the same as that of the From field except that the first key is replaced by To. All
requests and responses must contain this field.
The tag parameter in the field distinguishes different user instances that are identified
by the same SIP URL. A proxy server can concurrently deliver several requests, and
the same request might reach different instances (home telephone, for example) of
the user. Because the instances might all respond to the request, it is required to use
the tag to distinguish the responses from different instances. The tag in the To field is
put by each instance in the response message.
Examples of To field:
To: <Sip:1000@182.20.50.1>
To: <sip:1001@182.20.50.1>;tag=62beb3ca
In SIP, the Call-ID, From, and To fields identify one call branch. When a proxy server
concurrently distributes requests, a call might have several call branches.
5-42
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
z CSeq
CSeq refers to command sequence. A CSeq field in a request contains a command
name and a single decimal sequence number. Request client defines the sequence
number, which is unique inside the Call-ID. The initial value of the sequence number
is arbitrary. The subsequent values share the same Call-ID. For a request with a
different command name and a different message body, the CSeq sequence number
must be increased by one. A retransmitted request contains the same sequence
number. The server replicates the CSeq value from the request to the response
message to correlate the request with the response it triggers.
The CSeq value (decimal sequence number) of an ACK or a CANCEL request is the
same as that of the corresponding INVITE request. The CSeq sequence number of a
BYE request must be greater than that of the corresponding INVITE request. The
server must remember the highest sequence number of an INVITE request having the
same Call-ID. Upon receipt of an INVITE request with a lower sequence number, the
server sends a response and discards the INVITE request.
Several requests concurrently delivered by the proxy server have the same CSeq
value. Strictly speaking, CSeq is required for any request that is cancelled by a BYE or
CANCEL request and also for continuous requests with the same Call-ID sent by the
client.
An example of CSeq field:
CSeq: 1 INVITE
z ViaF
The Via field indicates the path taken by the request. The field can avoid loops during
the transport of the request and ensure the same path taken by the responses, for
example, in firewall occasions.
The client originating a request must add its host name or network address in the Via
field of the request. When the client does not use the default port, it must add the used
port number in the field. During the forwarding of a request, the proxy server must add
its address in a new Via field that is put before the existing Via. If the proxy server
receives a request containing its address in a Via field, the proxy server returns a
response indicating a loop detection.
When a request is passing a network address translation (NAT) entity (firewall for
example), the requested source address and the port number may be changed and
thus the Via field cannot be the base for routing responses. To avoid that, the proxy
server must check the top Via field. If the value of the top Via is different from the
previous hop’s address that is detected by the proxy server, the server add the
receive parameter in the Via which is thus called the Via field tagged by the receiver.
For example,
Via:SIP/2.0/UDP softx3000.bell-telephone.com:5060
Via:SIP/2.0/UDP 10.0.0.1:5060;received=182.20.12.30
5-43
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
When the request from the point 10.0.0.1 passes a NAT point with the external
address 182.20.12.30, the request reaches the proxy server
softx3000.bell-telephone.com. Noticing the inconsistence between the previous hop’s
address and the Via field address, the proxy server adds the actual sending address,
as a receiver’s tag, at the end of the top Via and then adds its own address in a new
Via that is put at the topmost.
If the proxy server sends a request to multicast address, the proxy server must add
the maddr parameter in the Via to indicate that.
The proxy server or UAC complies with the following rules to process the received
Via:
z Rule 1: The first Via field should indicate the proxy server or the UAC itself. If not,
the proxy server or UAC discards the message. Otherwise, the proxy server or
UAC deletes the Via field.
z Rule 2: If there is no a second Via field, the response should reach the
destination. Otherwise, proceed as follows.
z Rule 3: If the second Via field contains the maddr parameter, the proxy server or
UAC sends the response according to the multicast address indicated in the
parameter. The used port number is specified in the sent-by parameter. If not
specified, the proxy server or UAC uses a port number 5060. The lifetime of the
response should be specified in the ttl parameter. If not specified, the proxy
server or UAC sets it to 1.
z Rule 4: If the second Via field does not contain the maddr parameter but has a
field tagged by the receiver, the proxy server or UAC sends the response to the
address specified in the received parameter.
z Rule 5: If there is neither the maddr parameter nor a tag, the proxy server or
UAC sends the response to the address specified in the sent-by parameter.
The Via field has a general format:
Via: sent-protocol sent-by; hidden; ttl; maddr; received, branch
The sent-protocol is in the form of protocol-name/protocol-version/transport, in which
the default values for protocol-name and transport are SIP and UDP. The sent-by is
usually the host and port number of the sender. The hidden parameter has a key
word—hidden. If the hidden parameter exists, it indicates that the field has been
encrypted by the previous proxy for privacy purpose. For the meanings of the maddr
and received parameters, refer to earlier descriptions. The ttl and maddr parameters
are coordinated with each other. The branch parameter is used by the proxy server
concurrently delivering requests to tag the branches. If the response reaches the
destination, the proxy uses it to judge the branch from which the response comes.
An example of Via field:
Via:SIP/2.0/UDP182.20.1.116:5060;ttl=16;maddr=182.20.10.20;branch=z9hG4bkbc
427dad6
5-44
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
z Contact
The Contact field is present in INVITE, ACK, and REGISTER requests, success
responses, call process responses, and redirection responses to provide an address
for direct communication with the user.
The Contact field in an INVITE or ACK request indicates the location where the
request is originated. With the field, the callee can directly send a request (BYE for
example) to that address, instead of asking a series of proxy servers to forward the
request by using the Via field.
A success response to INVITE can contain the Contact field, which helps to send the
subsequent SIP requests (ACK for example) directly to that address specified in the
field. That address usually indicates the host of the callee. If the host is behind a
firewall, that address indicates the proxy server.
Call process response message to an INVITE request contains a Contact field that
has the same meaning as the success response message. However, a CANCEL
request cannot be directly sent to that address. Instead, the CANCEL must be
forwarded through the same path of the original request.
The Contact field in a REGISTER request indicates the reachable location of the user.
The request also defines a wildcard Contact field * that can only be used with the
expires field with a value of 0 to remove all registrations of a user. In the Contact field,
the expires parameter (optional) can also be specified to indicate the expiration
interval of the registration. If the parameter is not specified, the expires field value is
taken as its default value. If neither case is adopted, it is considered that the expiration
interval of the SIP URI is one hour.
The Contact field in a success response to the REGISTER request returns all
locations that are currently reachable for the user.
The Contact field in a redirect response such as Moved Temporarily, Moved
Permanently, or Address Ambiguous specifies other alternative addresses for retry,
which can be used for a response to a BYE, INVITE or OPTIONS request.
The Contact field has a generic format:
Contact: address; q; action; expires; extension
The address is expressed in the same form as To and From. The q parameter has a
value range of [0, 1] indicating the relative priority of the given location. The greater
the value is, the higher the priority is. The action parameter is only used in a
REGISTER request, indicating the server is required to perform the proxy service or
redirection service on the subsequent requests to the client. If the Contact field does
not contain the parameter, the action to be performed depends on the configurations
of the server. The expires parameter indicates how long the URI is valid either in
seconds or by SIP date. The extension attribute is actually the extension name.
An example of Contact field:
5-45
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Contact: <Sip:66500002@182.20.1.110:5061>;q=0.7;expires=3600
z Max-Forwards
The Max-Forwards field serves to limit the number of hops a request can transit on the
way to its destination. It consists of an integer that is decremented by one at each hop.
If the Max-Forwards value reaches 0 before the request reaches its destination, it will
be rejected with a 483 (Too Many Hops) error response.
The purpose of inserting this field is to avoid consuming proxy server resources in an
event of loop. The default field value is 70.
The Max-Forwards field has a generic format:
Max-Forwards: decimal integer
z Allow
The Allow field gives a list of request types that can be supported by the proxy server.
An example of Allow field:
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE
z Content-Length
The Content-Length field indicates the size of the message body, in decimal format.
Applications use this field to indicate the size of the message body to the transferred,
regardless of the media type of the entity. If the used transport protocol is based on
streams, TCP for example, this field must be used.
The size of the message body does not include the carriage return line feed (CRLF)
that separates the message header from the message body. The value of
Content-Length must be equal to or greater than 0. If a message does not contain a
message body, the value of the Content-Length field must be set to 0.
SDP serves to construct the message body of a request or 2xx response.
The Content-Length field has a generic format:
Content-Length: decimal value
An example of Content-Length field:
Content-Length: 349
The example indicates the length of the message body is 349 bytes.
z Content-Type
The Content-Type field indicates the media type of the message body. If the message
body is not null, the Content-Type field must be present. If the body is empty and a
Content-Type field is present, it indicates that the body length of the specific type is
zero (an empty audio file for example).
An example of Content-Type field:
Content-Type: application/sdp
5-46
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
z Supported
Transportation of a 100 temporary response defined in SIP is not reliable. In other
words, it is not guaranteed that UAC can receive the provisional response sent by
UAS.
If the response is required to carry information about media, it must be guaranteed
that the message can be reliably transported to the peer. The 100rel extension
provides an appropriate mechanism for the reliable transportation of the 100
response. The acknowledgement request method for a provisional response in 100rel
is PRACK.
If UAC supports the extension, it adds the field of Supported: 100rel in the message
transmitted. If UAS supports the extension, it adds the field of Require: 100rel in the
100 response transmitted. Upon receipt of the response, UAC is required to send a
PRACK request to UAS, to notify it of the receipt of the provisional response. UAS
sends a 2xx response to UAC to terminate the acknowledgement process of the
provisional response.
If a UA wants to send a provisional response carrying a SDP message body, UAC and
UAS must support and use the 100rel extension to guarantee the reliable
transportation of the message.
An example of Supported field:
Supported: 100rel
z User-Agent
The User-Agent field contains information about the UAC originating the request.
Revealing the specific software version of UA may set the user in a position of being
more vulnerable to attacks against software that is known to contain security holes.
Therefore, the User-Agent field should be set to be a configurable option.
An example of Use-Agent field:
User-Agent: Softphone Beta1.5
z Expires
The Expires field gives the relative time after which the message (or content) will
expire.
An example of Expires field:
Expires: 5
z Accept-Language
The Accept-Language field is used in requests to indicate the preferred languages for
reason phrases, session descriptions, or status responses carried as message
bodies in the response. If no Accept-Language field is present, the server assumes all
languages are acceptable to the client.
An example of Accept-Language field:
5-47
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Accept-Language: en
z Authorization
The Authorization field contains authentication credentials of a UA.
The following introduces a general process for UA to request an authorization from
the server.
If the server requires authorizing the user when UA originates a request, a nonce is
generated at the local end for this authorization and all parameters necessary for the
authorization request field are returned to UA to initiate a user authorization process.
Upon receipt of the authorization request, UA generates an encrypted response using
a particular algorithm according to the information returned from the server and the
user configurations. UA sends the response through a new request message to the
server.
Upon the receipt of a new request with the authorization response, the server firstly
checks the correctness of the nonce. If the nonce is not generated locally, the server
returns a failure message. If the nonce is generated locally but the authorization
expires, the server regenerates a nonce and reinitiates a user authorization
procedure. The earlier nonce is returned with the cnonce parameter.
If the nonce passes the verification, the server generates a response with the same
algorithm as UA according to the nonce, URI, username and password (the server
can obtain the password of the user from the local user information). In addition, the
server compares the generated response with the response carried in the request
message. If they are identical, the user successfully passes the authorization.
Otherwise, the authorization fails.
The Authorization field has a generic format:
Authorization: method username, realm, nonce, response, URI, cnonce, algorithm
The authorization methods include digest, basic, chap-password, and carddigest.
Digest is an HTTP-digest method.
Username indicates the authenticated user.
Realm is used to identify the domain from which the authorization procedure is
initiated.
Nonce is an encryption factor that is generated by the entity initiating the
authorization procedure.
Response is a string of characters that UA generates, by using a particular algorithm,
according to the nonce, username, password, and URI from the server upon receipt of
the authorization request. The string contains the encrypted password of the user.
(During the authorization procedure, UA and the server exchange other information,
except password, in plain text in SIP messages.)
URI refers to the request-URI of the originated call request message. UA is required to
re-originate a request with the authorization response information to the server after
5-48
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
receiving the authorization request. Some fields such as the Request-URI may be
modified while the request is transmitted through the network server. While UA
originates a request, the URI parameter in the authorization field is used to deliver the
Request-URI of the original message for authorization, to guarantee the correctness
of the authorization.
Cnonce: If UA does not return the new request with the authorization response
information to the server until the server expires, the server will regenerates a nonce
and reinitiates a user authorization procedure. The earlier nonce will be returned to
UA with the cnonce parameter.
Algorithm is used for exchanging algorithms that generate the RESPONSE.
An example of Authorization field:
Authorization: DIGEST USERNAME="6540012", REALM="huawei.com",
NONCE="200361722310491179922",
RESPONSE="b7c848831dc489f8dc663112b21ad3b6", URI="sip:182.20.150.30"
3) An example of request message
The following is an example of request message encoding.
INVITE sip:dialog.vxml.digits.vxml@182.20.50.1 SIP/2.0
From: sip:4444@182.20.20.105;tag=1c25759
To: sip:dialog.vxml.digits.vxml@182.20.50.1
CSeq: 1 INVITE
Call-Id: call-973668242-23@182.20.20.105
Via: SIP/2.0/UDP 182.20.20.105:5061
Contact: <sip:4444@182.20.20.105>
Supported: 100rel,100rel
Max-Forwards:70
Allow:INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SU
BSCRIBE,NOTIFY,MESSAGE,REFER
Content-Length:230
Content-Type: application/sdp
v: 0
o: UNICA 1073741831 1073741831 IN IP4 182.20.20.105
s: Sip Call
c: IN IP4 182.20.70.1
t: 0 0
m: audio 30000 RTP/AVP 8 0 4 18
5-49
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
a: rtpmap:8 PCMA/8000
a: rtpmap 0 PCMU/8000
a: rtpmap 4 G723/8000
a: rtpmap 18 G729/8000
The 1st line: The start line of the request is the INVITE request message. The request
URI, the current address of the invited user, is
sip:dialog.vxml.digits.vxml@182.20.50.1. The dialog.vxml. digits.vxml indicates the
AS requests MRS to parse the local script file digits.vxml. The IP address of MRS is
182.20.50.1. The SIP protocol version is 2.0.
The 2nd line: This is a From field. It indicates that the address of the request initiator
AS is <sip:4444@182.20. 20.105>. The tag is 1c25759. For all requests sent by one
AS to MRS, their From fields can be the same.
The 3rd line: This is a To field. It indicates that the IP address of MRS is
sip:dialog.vxml.digits.vxml @182.20.50.1. Its partial information is the same as the
request URI in the start line of the request.
The 4th line: This is a CSeq field. It is used to correlate the INVITE request with the
triggered responses and corresponding ACK and CANCLE requests.
The 5th line: This is a Call-ID field. It identifies an INVITE that is globally unique. The
Call-ID is call-973668242-23@182.20.20.105, in which 182.20.20.105 is the IP
address of the caller AS and call-973668242-23 is the local ID.
The 6th line: This is a Via field. It indicates the path taken by the request.SIP/2.0/UDP
represents the protocol used for the transmission, in which SIP is the protocol name,
2.0 is the protocol version number, and UDP is the transport layer.
182.20.20.105:5060 represents the request sender AS, in which 182.20.20.105 is the
IP address and 5061 is the port number.
The 7th line: This is a Contact field. It indicates that subsequent requests (BYE for
example) can be directly sent to <sip:4444@182.20.20.105>, without using the Via
field.
The 8th line: This is a 100rel extension. It provides an appropriate mechanism for the
reliable transportation of 100 response messages.
The 9th line: This is a Max-Forwards field. It indicates the maximum number of hops a
request can transit on the way to its destination is 70.
The 10th line: This is a Allow field. It gives a list of request types that can be supported
by the AS whose IP address is 182.20.20.105.
The 11th line: This is a Content-Length field. It indicates the length of the message
body.
The 12th line: This is a Content-Type field. It indicates that the message body is a
single one and is an SDP.
5-50
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The 13th line: Null. It indicates what is preceded is an SDP session description.
The 14th line: This is the SDP protocol version number. At present, it is the version 0.
The 15th line: This line contains the session owner/creator and the session identifier,
used to give the initiator (username and host address) of the session, the session
identifier, and the session version number. UNICA is the username that is used by the
user to log into the originating host. If the host does not support user ID, this field is
tagged to be a sign (-). The first 1073741831 is the session identifier. The session
identifier in the form of a digit string helps the multiple tuples (username, session
identifier, network type, address type, and address) to construct the globally unique
identifier of the session. The second 1073741831 is the version number of the
session announcement, which is provided for the proxy server to detect the latest one
from the several announcements of the same session. The basic principle is to
increment that version number once the session data is modified. IN refers to the
network indicator in the form of a text string. The currently defined IN is Internet. IP4
refers to the address type in the form of a text string. At present, IP4 and IP6 are
defined. 182.20.20.105 is the IP address of the host that creates the session.IP4
addresses can be expressed in full domain name or dotted decimal notation.IP6
addresses can be expressed in full domain name or compressed file form.
The 16th line: This line contains the session name. Each session description must
have one and only one session name.
The 17th line: This line contains the connection related data. At present, the network
type and the address type are defined to be IN and IP4. 182.20.70.1 may be the IP
address of an MG (the terminal type is ESL telephone connected to an IAD/AG) under
the control of the SoftX. 182.20.70.1 may also be the IP address of a SIP or H.323
terminal (the terminal type is SIP or H.323 phone).
The 18th line: This line contains the time description. It provides a time segment when
the session can be activated, allowing the session to periodically occur. The 0
represents the start time. The format for the field is t:<start time><end time>. The
values of start time and end time are expressed in the decimal form of network time
protocol (NTP) time values. The unit is second.
The 19th line: This line contains the media-level description. It provides information
that is suitable only for the media stream. The audio refers to the media type. At
present, five types of media are defined: audio, video, application, data, and control.
30000 represents the transport-layer port to which the media stream is transmitted,
that is, the UDP port number of the MG (the terminal type is ESL phone connected to
an IAD/AG) or the UDP port number of a SIP or H.323 terminal (the terminal type is
SIP or H.323 phone). RTP/AVP is the transport-layer protocol. Its value is associated
with the type of address in the c line. For IP4, a great number of media service
streams are transferred over RTP/UDP. There are two classes of protocols defined:
RTP/AVP, audio/video application document, transported over UDP; Udp, the DUP
protocol. The 8 0 4 18 is, for audio and video, the media payload type that is defined in
5-51
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
the RTP audio/video application document. It means that all formats carried in the
session may be used, but the first one is the default format for the session.
The whole line indicates that A-law PCM single-channel audio signal is used by
default, its static payload type is numbered 8 in the RTP audio/video application
document, and the signal is transmitted to a UDP port 30000.
From the 20th line to 23rd line: These lines introduce rtpmap attributes, specifying
the mapping correspondence from RTP payload type to encoding. The format of such
a line is a: rtpmap:<payload type><encoding name>/<clock rate>[/<coding
parameter>]. In the format, coding parameter refers to the number of audio channels.
This parameter is unavailable to video signals.
5-52
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Start
Command Peer UPI Version
line
Call-ID:Value
From:Value
To:Value
Cseq:Value
Via:Value
Contact:Value
Message
Max-Forwards:Value head
Allow:Value
Content-Lengh:Value
Supported:Value
User-Agent:Value
Content-Type:Value
... ...
Space
SDP Message
body
5-53
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
The 1st line: The SIP protocol. The protocol version is 2.0. The status code is 180.
Ringing is a descriptive phrase, referring to sending the ringing tone to the callee.
The 2nd line and 3rd line: Refer to "An example of request message".
The 4th line: This is a CSeq field, used to correlate the INVITE request with the
triggered responses and corresponding ACK and CANCLE requests. The CSeq field
in this response has the same meaning as that in the request described earlier. Both
are 1 INVITE, indicating the response is trigger by the previous request.
The 5th to 8th lines: Refer to "An example of request message".
Generally, MRS6100 only acts as a UAS to receive call requests sent from an AS.
After a session is created, AS can modify session attributes with the reINVITE
command. AS can also record, play announcements, collect digits, and specify a
VXML script to perform a series of operations through the URL.AS can also execute
these operations with INFO messages, except for modifying session channel
attributes, as shown in Figure 5-14.
5-54
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
SIP
AS MRS6100
terminal
INVITE
INVITE
100 Trying
100 Trying
180 Ringing
180 Ringing
200 OK
200 OK
ACK ACK
RTP
......
Cancel
reINVITE annoucem
ent
200 OK
ACK
Repuest
reINVITE
annoucement
200 OK
ACK
INFO
200 OK
......
BYE BYE
200 OK 200 OK
Event 1: AS sends an INVITE request to MRS6100. The request contains SDP-1, the
session attribute of the remote caller SIP entity.
IINVITE sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
To: sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1
Contact: sip:182.20.62.2
Call-ID: 4000@182.20.62.2
CSeq: 10 INVITE
5-55
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Content-Length: 214
Content-Type: application/sdp
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
v=0
o=TestTeam 4000 4000 IN IP4 182.20.62.2
s=phone-call
c=IN IP4 182.20.70.2
t=0 0
m=audio 8000 RTP/AVP 0 4 8 96 97
a=rtpmap:96 telephone-event/8000/1
a=rtpmap:97 red/8000/1
a=ptime:20
a=x-ssrc:00a6a390
For interpretation of each line, refer to "Request message parameters" in Section
5.3.5 1, "Request messages".
Event 2: MRS6100 returns a 100 Trying response to AS, to notify it that MRS6100 has
received and is processing the request.
SIP/2.0 100 Trying
From: <sip:1@182.20.62.2>;tag=8000
To: <sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>
CSeq: 10 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Content-Length: 0
Event 3: MRS6100 sends 180 Ringing to AS, and then AS forwards it to the remote
caller SIP entity.
SIP/2.0 180 Ringing
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 10 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
5-56
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Contact:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1:5061;tr
ansport=udp>
Content-Length: 0
Event 4: MRS6100 sends the 200 OK message to AS, which contains the SDP-2.
SIP/2.0 200 OK
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 10 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Contact:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1:5061;tr
ansport=udp>
Content-Length: 288
Content-Type: application/sdp
v=0
o=HuaweiMRS6100 1073743905 1073743905 IN IP4 182.20.60.1
s=Sip Call
c=IN IP4 182.20.60.30
t=0 0
m=audio 10008 RTP/AVP 0 4 8 96 97 18
a=rtpmap:0 PCMU/8000
a=rtpmap:4 G723/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
a=rtpmap:97 red/8000
a=rtpmap:18 G729/8000
For interpretation of each line, refer to "Request message parameters" in Section
5.3.5 1, "Request messages".
Event 5: AS sends an ACK message to MRS6100, acknowledging the receipt of the
final response to the INVITE request from MRS6100.
ACK sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
5-57
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
Call-ID: 4000@182.20.62.2
CSeq: 10 ACK
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
Content-Length: 0
A call between AS and MRS6100 is established successfully. An RTP media stream
connection is established between MRS6100 and the remote caller SIP entity.
MRS6100 starts to play welcome4.chi files for the user.
Event 6: AS sends the request for canceling the announcement playing operation with
the reINVITE command.
INVITE sip:annc.cancel@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
Contact: sip:182.20.62.2
Call-ID: 4000@182.20.62.2
CSeq: 13 INVITE
Content-Length: 0
Content-Type: application/sdp
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
Event 7:MRS6100 response the opration request.
SIP/2.0 100 Trying
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 13 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Content-Length: 0
Event 8: MRS6100 sends 200 OK, indicating the cancellation of announcement
playing.
SIP/2.0 200 OK
5-58
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 13 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Contact:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1:5061;tr
ansport=udp>
Content-Length: 0
Event 9: AS sends an ACK message to MRS6100, acknowledging the receipt of the
final response to the reINVITE request from MRS6100.
ACK sip:annc.cancel@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
Call-ID: 4000@182.20.62.2
CSeq: 13 ACK
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
Content-Length: 0
Event 10: AS sends the announcement playing request with the reINVITE command,
while playing the welcome1.chi audio file.
INVITE sip:annc.BAU.pa%28an%3dfile%3a//welcome1%29@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
Contact: sip:182.20.62.2
Call-ID: 4000@182.20.62.2
CSeq: 1163751 INVITE
Content-Length: 0
Content-Type: application/sdp
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
SIP/2.0 100 Trying
From: <sip:1@182.20.62.2>;tag=8000
5-59
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 1163751 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Content-Length: 0
Event 11: MRS6100 sends 200 OK, indicating the success of announcement playing
request.
SIP/2.0 200 OK
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 1163751 INVITE
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Contact:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1:5061;tr
ansport=udp>
Content-Length: 0
Event 12: AS sends an ACK message to MRS6100, acknowledging the receipt of the
final response to the reINVITE request from MRS6100.
ACK sip:annc.BAU.pa%28an%3dfile%3a//welcome1%29@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
Call-ID: 4000@182.20.62.2
CSeq: 1163751 ACK
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
Content-Length: 0
Event 13: After playing announcements, MRS6100 reports the result to AS with the
INFO message, describing the success or failure of announcement playing.
INFO sip:182.20.62.2 SIP/2.0
From:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1
e0a19
To: <sip:1@182.20.62.2>;tag=8000
5-60
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
CSeq: 1 INFO
Call-ID: 4000@182.20.62.2
Via: SIP/2.0/UDP 182.20.60.1:5061;branch=z9hG4bK3e8156831
Max-Forwards: 70
Content-Length: 34
Content-Type: application/Huawei
Event-Type=ivr
Event-Content=OC
Event 14: AS returns the INFO message response.
SIP/2.0 200 OK
From:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1
e0a19
To: <sip:1@182.20.62.2>;tag=8000
CSeq: 1 INFO
Call-ID: 4000@182.20.60.1
Via: SIP/2.0/UDP 182.20.60.1:5061;branch=z9hG4bK3e8156831
Content-Length: 0
Event 15: AS sends a BYE message, requesting to release the connection.
BYE sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1 SIP/2.0
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
Call-ID: 4000@182.20.62.2
CSeq: 352758950 BYE
Via: SIP/2.0/UDP 182.20.62.2:5060
User-Agent: MRS6100 DP
Content-Length: 0
Event 16: MRS6100 returns the BYE response, indicating the connection has been
released.
SIP/2.0 200 OK
From: <sip:1@182.20.62.2>;tag=8000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome4%29@182.20.60.1>;tag=1a1e0a
19
CSeq: 352758950 BYE
Call-ID: 4000@182.20.62.2
5-61
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
In an unsuccessful call flow shown in Figure 5-15, UA deletes the call in the process of
creating a session. It sends a CANCEL message that results in the call failure.
SIP
SIP AS MRS6100
terminal
INVITE INVITE
180 Ringing
180 Ringing
CANCEL CANCEL
ACK
ACK
5-62
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
v=0
o=TestTeam 2000 2000 IN IP4 182.20.62.2
s=phone-call
c=IN IP4 182.20.69.4
t=0 0
m=audio 8766 RTP/AVP 0 4 8 96 97
a=rtpmap:96 telephone-event/8000/1
a=rtpmap:97 red/8000/1
a=ptime:20
a=x-ssrc:00a6a390
For interpretation to each line, refer to "Request message parameters" in Section
5.3.5 1, "Request messages".
Event 2: MRS6100 returns a 100 Trying response to AS, to notify it that MRS6100 has
received and is processing the request. .
SIP/2.0 100 Trying
From: <sip:1@182.20.62.2>;tag=5220000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@1
82.20.60.1>
CSeq: 10 INVITE
Call-ID: 2000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Content-Length: 0
Event 3: MRS6100 sends 180 Ringing to AS, and then AS sends it to the remote
caller SIP entity.
SIP/2.0 180 Ringing
From: <sip:1@182.20.62.2>;tag=5220000
To:
<sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@182.
20.60.1>;tag=68a574c9
CSeq: 10 INVITE
Call-ID: 2000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
5-63
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
Contact:
<sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@182.
20.60.1:5061;transport=udp>
Content-Length: 0
Event 4: AS sends a CANCEL message to MRS6100 to cancel the current session.
CANCEL
sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@182.2
0.60.1 SIP/2.0
Via: SIP/2.0/UDP 182.20.62.2:5060
From: <sip:1@182.20.62.2>;tag=5220000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@1
82.20.60.1>
Call-ID: 2000@182.20.62.2
CSeq: 10 CANCEL
Content-Length: 0
User-Agent: MRS6100 DP
Event 5: MRS6100 returns the CANCEL response.
SIP/2.0 200 OK
From: <sip:1@182.20.62.2>;tag=5220000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@1
82.20.60.1>
CSeq: 10 CANCEL
Call-ID: 2000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Content-Length: 0
Event 6: MRS6100 returns the final response to the INVITE request.
SIP/2.0 487 Request Terminated
From: <sip:1@182.20.62.2>;tag=5220000
To:<sip:annc.BAU.pa%28an%3dfile%3a//welcome2%20it%3d2%20iv%3d20%29@1
82.20.60.1>;tag=68a574c9
CSeq: 10 INVITE
Call-ID: 2000@182.20.62.2
Via: SIP/2.0/UDP 182.20.62.2:5060
Content-Length: 0
5-64
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 5 MGCP and SIP
5-65
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
Alarm Box
Lan Switch
To Network
Management Center
WAN
WS WS
The EAM board in the figure is the BAM server of MRS6100 system.
6-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
Note:
For working principles of the NMS software, refer to the related user manual.
The BAM communicates with the FAM, implementing system operation and
maintenance, and bill management.
The BAM and the NMS interact through the standard man-machine language
(MML)/simple network management protocol (SNMP), thereby realizing the
centralized maintenance and management of MRS6100 by the NMS. The NMS
provides an access interface to its upper NMS.
The BAM and workstations communicate with each other using TCP/IP through
Ethernet. They can also communicate using serial port through communication
gateway.
6-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
provides a complete set of practical operation and maintenance methods and tools, to
guarantee the normal running of the system, minimize the business cost, and improve
the quality of communication service.
The BAM is the core of the local operation and maintenance system. Being the
TCP/IP server, the BAM responds to connection requests from clients (or
workstations), creates connections, analyzes commands from clients, and carries out
appropriate processing. Meanwhile, the BAM responds to connection requests from
the equipment, creates connections, achieves the communication between the BAM
and the equipment, and receives and processes data loading requests and alarms
from the equipment.
The BAM provides two network interfaces to core LAN Switches, thereby being
connected to the HSCIs in the basic frames. The two network interfaces provided by
the BAM are respectively in the same network segment with the active/standby
SMUIs (two closed LANs connected to the equipment). The connection to a client
belongs to a different network segment (an open operation and maintenance LAN).
The three network segments are not seeable with each other. In this way, the network
security is ensured to a certain extent and the dependence on the system security is
reduced. The network configuration of the BAM is shown in Figure 6-3.
MR S6100
S S
M M
U U
I I
H S H S
S I S I
C U C U
I I I I
NIC3 NIC3
BAM server
Emergency ws
LAN
WS0 WS1
6-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
Note:
z The BAM server implements the back administration function of the MRS6100.
z The NIC1 and the NIC2 of the BAM communicate with other boards through the
HSCI.
z The fixed IP address of the NIC1 is 172.20.200.0. The fixed IP address of the NIC2
is 172.30.200.0.
BAM
Service Shake hand
Monitor
Monitor Security
Manager
Dataman
Maintain
MML GUI Device
MML Server Exchange
Warn
WS
LogMan Stats
6-4
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
1) High reliability
A carrier-class SQL Server is used as a large database system. The programs are
designed with multi-layer self-monitoring measures so as to achieve data backup and
recovery conveniently, and ensure data security.
2) Client/Server structure
The BAM software is integrated with communication server and database server.
Various maintenance tasks are carried out in the Client/Server mode. The software
supports local and remote maintenance tasks to set data simultaneously.
Maintenance operations can be performed conveniently and quickly.
3) Remote maintenance
The MRS6100 provides remote maintenance functions and supports flexible
networking modes. It can be connected with a remote maintenance system through
Internet.
The following details a commonly used method, iWeb remote maintenance solution.
As shown in Figure 6-5, HUAWEI iWeb remote maintenance system, based on
Internet, enhances remote monitoring and encrypted data transmission, thereby
ensuring the security of the equipment running.
6-5
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
LAN
Client Agent
Device
6-6
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
6-7
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
6-8
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
The system provides functions such as connection tracing, signaling tracing, interface
tracing and message interpretation. With these functions, a real-time and dynamic
trace can be conducted on the connection process, state transition, resource usage,
telephone number information transfer and control information streams related to
terminal users, trunk circuits, signaling links and interface protocols. The tracing
information can be preserved for future reference. In this way, the system provides
powerful fault analysis and location capabilities for users.
z Signaling analysis
The system provides embedded signaling analysis tool software developed
independently by Huawei. The software works along with the trace management
functions to analyze the signaling interaction processes in an online or offline mode.
The system provides strong maintenance approaches to quickly locate fault causes
and optimize the signaling link configuration.
The alarm console correctly reflects the alarms recorded in the BAM in real time.
Through the alarm console, an operator can query and view all alarms, and manage
the alarms as well.
Alarm information includes the alarm name, generation (and restoration) time, alarm
level, location information, and restoration suggestions.
6-9
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
Item Configuration
CPU 2 × Intel Xeon DP 2.4 GHz or higher
Hard disk 2 × 36 GB 10000RPM SCSI hard disks or more
Memory 1 GB or more
2 × 1000M integrated network adapters
Network adapter
2 × 1000M extended network adapters
RAID card Built-in RAID. RAID 0 and RAID 1 are supported.
6-10
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 6 MRS6100 Terminal System
Figure 6-6 Setting the BAM communication gateway when the BAM or the
emergency workstation is connected to the alarm box
6-11
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
Command group is a basic unit of authority setting. One command may belong to
one or more command groups. When an operator or workstation has the authority
of the command group, he has the authority to carry out all commands contained in
this group at this workstation.
The OMS contains 66 command groups, namely, G_0–G_63, and two special
command groups, G_SYS and G_GUEST. The super user and the user GUEST
respectively own the two special command groups. G_0 to G_9 are ten preset
command groups, and most commands of the system are allocated to them
according to their different functions. Each command group contains a large
number of commands, and all operators belonging to this command group have the
authority to carry out these commands. However, the commands related to
authority and login cannot be allocated to the 64 command groups from G_0 to
G_63, and only the super user of the system has the authority for these commands.
The user with the authority of the G_SYS command group is called super user.
Similarly, the workstation with the authority of the G_SYS command group is called
super-workstation. In the system, there may be multiple super-workstations, but
there must be only one super user. The default name of super user is set during
system installation, and it cannot be modified. The super user can only set his
password. A super-workstation can be set during system installation, or a super
user can set a super-workstation by authorizing a workstation with G_SYS
command group with the Add WS command. This allows super users to control the
whole system on any super-workstation, thus facilitating system management. Only
the super user can perform all operations related to authority management, such as
7-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
The MRS6100 operating system identifies an operator uniquely through user name.
A new user account can have the same name and attributes with a deleted account,
whose authority cannot be transferred to the new user with the same name. This
eliminates the possibility of using invalid or deleted account to log in to the system.
In addition, encrypted user password is stored in the database. The database
security mechanism and password encryption algorithm ensure its security, thus
effectively protecting the user password.
The MRS6100 OMS can be configured to allow an operator to log in to the system
only in the specified period. An operator can carry out the commands contained in
the authorized command group only when he logs in to the system at allotted time.
7-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
All BAM data are stored in the SQL Server of the BAM. Through the data
management program on the BAM, operator authorities can be managed in a
hierarchical mode.
The BAM data can be backed up automatically and periodically. When some
important data are modified, manual backup also can be performed.
The FAM system data are stored in the FAM with backup in Flash memory or
without backup in Flash memory.
After the data are loaded to the BIOS successfully, it automatically backs up data
into Flash memory. When the system is powered on, according to the BAM soft
switch, you can choose to reload data from the BAM or directly read system data
from the Flash memory on this board.
When the BAM carries out data setting, the backup program module of the active
board automatically backs up the modified static data to its Flash memory or the
memory database of the standby database. Moreover, the backup program of the
standby database automatically synchronizes its changed memory database to its
Flash memory.
If the system configuration data on the board have no backup in the Flash memory,
the board data must be loaded from the BAM when they are started each time.
When the BAM performs data setting, it sends the data to the active and standby
boards simultaneously. Meanwhile, the changed data in an active board are not
backed up to the standby board.
7-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
Data format conversion means that the BAM converts the format of operation and
maintenance-oriented data received from workstation to the data format that can be
processed by the Service Processing Module. An operator can convert some or all
modified data as required. After conversion, the data can be loaded to the Service
Processing Module. This operation is needed in the following three cases:
z The operator forces to regenerate data files.
z When the operator performs the operations of adding, deleting and modifying
data with the MML, the data management console automatically starts the
format conversion command to update data files.
z After receiving the format conversion command from the traffic measurement
console, the BAM performs format conversion and writes the converted data to
the data file of the corresponding module.
Data setting sends the data with the converted format in the BAM to the
corresponding modules of the FAM.
After the data in the BAM are modified, data setting must be performed. The time of
data setting is related to the connection status between the BAM and FAM, and the
formatting switch. When the BAM is connected with the FAM, data setting is
automatically conducted once the data in the BAM are modified. Otherwise, data
setting is not automatically conducted until they are connected. Data setting
operation will be conducted in two cases:
1) After the operations of adding, deleting or modifying data are carried out, the
BAM will automatically perform the data sending operation
2) The operator can carry out the data setting command to forcibly perform the
operation.
7-4
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
To ensure the consistency of data in the BAM (background) and the FAM modules
(FAM), MRS6100 OMS provides the CRC function to verify the consistency of BAM
data and FAM data.
The BAM periodically originates check requests for data in the FAM (data check is
performed in single table form). Through CRC, it can be obtained whether a data
table in the BAM is consistent with that in the FAM. When the BAM detects any
inconsistency between the BAM and FAM data, it initiates a data setting request to
the FAM. If data setting failures exceed the limit, the BAM generates an alarm
automatically. The operator can make data consistent by setting or loading data.
To ensure the security of data, the system provides the function to back up BAM,
registry files and configuration files to the specified directory. In case of system
failure, the operator can restore the system by using the backup database files and
configuration files. Data backup can be implemented in two ways:
z Automatic backup of background data
z The system data are backed up when the traffic is relatively low. When the
system is carrying out the backup command, it will not accept any service
command request.
z Manual backup of background data
There are two ways to manually back up system data. One way is to implement
backup with the MML commands and the other is to use the database management
utility to back up database directly.
There may be unfinished data format conversion and data sending tasks when the
BAM is shut down improperly (for example, power failure). When the BAM restarts,
the system checks for unfinished tasks and continues them.
7-5
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
7.4.1 Architecture
The alarm system mainly consists of the fault detection subsystem and alarm
generation subsystem.
It monitors the running status of devices through various ways such as hardware
detection and software detection, and reports fault information in time.
Hardware detection is implemented by each board, and its contents include:
z Operating status of this board (normal/abnormal; active/standby)
z Channel fault
z Online/offline
The operator can find logical errors through software detection that cannot be
detected through hardware detection, and its contents mainly include:
z Self-loop test to board
z CRC check
z Memory check
z Data consistency check
The subsystem collects fault information and handles it, and then generates
detailed alarm information in various tables accordingly to inform the maintenance
engineers.
As shown in Figure 7-1, the alarm generation subsystem includes BAM software
module, Exchange module, device modules, alarm server (alarm application
module, alarm processing module and DB), alarm GUI, MML client and alarm box.
7-6
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
All MRS6100 boards are intelligent. They can monitor the status, running conditions
and external interfaces, test and designate the operating status, and report
abnormities to superior devices.
The superior devices can automatically monitor the running status of lower-level
devices, report the detected abnormities to the higher-level ones, and implement
such operations as channel blocking, active/standby switchover, system
reorganization, device restarting and so on.
7-7
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
z Alarm reporting path of the front board of basic frame (except ALUI and
UPWR): After collecting the alarm information from the front board through
shared resource bus, the SMUI reports the alarm to the BAM through Ethernet.
z Alarm reporting path of the back board: no processor exists in the back board
of MRS6100. The corresponding front board collects its status and reports it to
the SMUI board through the shared resource bus. After receiving the
information of the back board, the SMUI board sends an alarm to the BAM
through Ethernet, and delivers the back board status to the ALUI through serial
port bus. Then the ALUI drives the indicators on its front panel to indicate the
status of the back boards. A board can be in the status of uninstalled, normal
and abnormal.
Note:
The following displays the status of the boards that are configured on BAM. If a
board is not configured, its status cannot be displayed even if it is inserted.
z Alarm reporting path of the power board of basic frame: The ALU collects the
status signals of the power modules through backplane and drives the
indicators on the corresponding panel to indicate the status of the power
module. Meanwhile, the ALU reports the power module status information to
the SMU through the serial port bus, and the SMU generates an alarm to the
BAM through Ethernet.
Note:
The ALUI does not provide indicators to indicate the working and in-position state of
the two front UPWRs, but provides indicators to indicate the state of the two back
UPWRs.
7-8
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
Alarm levels are used to identify the severity of alarms. According to the severity,
the alarms are classified into the following four different levels.
z Critical alarm: refers to the system-featured alarms on faults and events that
make the system down, such as the faults on SMUI and HSCI boards.
z Major alarm: refers to the alarms on faults and events, which affect the
board/line in certain area, such as interface board fault and communication link
fault.
z Minor alarm: refers to the alarms on ordinary faults and events that describe
the working state of boards or lines, such as board reset and PCM alarm.
z Warning alarm: refers to the warnings that do not affect system performance,
such as switchover alarm.
The alarms exported by the alarm console contain alarm types indicating the alarm
property. There are three types of alarms in the system: fault alarm, recovery alarm
and event alarm.
z Fault alarm: refers to the alarm generated due to hardware equipment fault or
abnormity in some important functions.
z Recovery alarm: refers to the alarm generated when the faulty equipment or
abnormal function recovers to normal. It is in one-to-one correspondence to
the fault alarm.
z Event alarm: refers to the prompts or fault alarms that do not have
corresponding recovery alarms.
7-9
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
z Explicit report function: The operator can select multiple measurement indices
in the same measurement function type for a measurement object, and
register them in the same measurement task.
7-10
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
z The information query function enables operators to query static data of tasks
in the FAM, including task status, measurement function set, task time
attributes, measurement body, and object types.
z If the operator does not perform measurement statistics of an existing task, but
deactivates the task, he must activate the task to export statistics results again,
so that the statistics results can be exported continuously.
z The operator can only deactivate tasks in the activated status, or activate tasks
in the deactivated status. Once a task is deactivated, the operator cannot
dynamically modify the task object, but he can delete or query the task.
z During the running of statistics task or after the task ends, the operator can
query the task result, and sort the result according to the object, time and body.
The result can be displayed in the form of table, bar, line, cake shape or dot.
z The operator can conduct printing setting, preview and print the query result.
7-11
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
7.6.2 Features
A software patch is developed based on a basic version, and can only be used for
that basic version. When the number of patches for a basic version reaches the
threshold, software upgrading is required. The patches for the old version are
integrated into the new version, and the patches for the new version will be
released when a new problem occurs.
For each error, one or more patches can be developed to solve the problem, and
each patch is assigned with a patch number. The patch number starts from 1, and
7-12
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
Caution:
Because online software patching affects the operation of software in CPU, only the
system administrator can perform this operation.
When the system is faulty, such as system power failure or abnormal restart,
patched modules in the FAM can automatically restore to the previous patched
status.
7.6.3 Structure
The software patching system includes three parts: patch creation tools, BAM patch
management module and FAM patch management module.
The patch creation tools are used to organize one or more patches and create a
patch file for a certain software version. The creation of patch file is completed
offline.
The BAM patch management module is a part of BAM software. It functions in:
z Providing operators with a command interface for managing and maintaining
patches.
z Maintaining the module patch configuration table and module patch status
table to keep them consistent with those in FAM devices according to related
7-13
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 7 Operation and Maintenance
The FAM patch management module is a part of FAM software. It functions in:
z Processing relevant patch commands from BAM to the maintenance interface,
because device patch management module is a part of the FAM software.
z Maintaining the module patch status table to keep it consistent with that in the
BAM according to the operation commands of users.
z Receiving patch files, separating patches and sending them to the patch area.
z Writing patch files into the Flash memory.
z Restoring patches after the system restarts.
z Active and standby boards.
7-14
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
The processing capability of MRS6100 is 1440 times per second, if the average
duration is 5 seconds for the system to play an announcement and return the result, or
to give a prompt, collect user information and return the result.
8-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
Parameter Index
Repair rate 0.3%
Usability 99.99983%
MTBF 53 years
MTTR 48 minutes
Pause time 0.89 minutes per year
Table 8-4lists the power consumption of functional units or devices in the MRS6100
cabinet.
8-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
Power
Functional unit consumption Configuration
(W)
(MCCU+BFII)×2+(MSUC+MRIC)×10+(SMUI+SI
Basic frame ≤610 UI)×2+HSCI×2+ALUI×1+UPWR×4+Fan frame
(SMUI+SIUI)×2+HSCI×2+(MSUC+MRIC)×12+A
Extended frame ≤680 LUI×1+UPWR×4+Fan frame
z Basic cabinet (in full configuration, including a basic frame and an extended
frame. The TTS Server and the VPS board are exclusive.)
z Extended cabinet (in full configuration, including an extended frame. The TTS
Server and the VPS board are exclusive.)
z Extended cabinet (in full configuration, including an extended frame and the VPS
parser. The TTS Server is exclusive.)
8-3
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
I. Climate
Item Scope
Altitude ≤ 5000 m
Atmosphere 70–106 kPa
Temperature: -40°C – +70°C
Temperature variation rate ≤1°C/min
Relative humidity 10%–100%
8-4
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
Note:
Suspended dust: diameter ≤ 75 Dm
Precipitable dust: 75 Dm ≤ diameter ≤150 Dm
Sand: 150 Dm ≤ diameter ≤1000 Dm
3) Table 8-7 lists the restrictions on the densities of active chemical materials
O3 mg/m³ 0.05–0.10
Note:
z Impact response spectrum: The maximum acceleration response curve
produced by the equipment under the defined impact excitation. Impact response
spectrum II means the duration for semisinusoidal impact response spectrum is 6
minutes.
z Quiescent load: The Pressure from above that the equipment with packing can
endure in the specified stack mode.
8-5
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
The applicable standard is EUROPEAN ETS 300 019-1-2 “Class 2.3 PUBLIC
transportation”.
I. Climate
Item Scope
Altitude ≤ 5000m
Note:
z Suspending dust: diameter ≤ 75 Dm
z Precipitable dust: 75 Dm ≤ diameter ≤150 Dm
z Sand: 150 Dm ≤ diameter ≤1000 Dm
8-6
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
3) Table 8-11 lists the restrictions on the densities of active chemical materials.
HF mg/m³ ≤ 0.03
O3 mg/m³ ≤ 0.10
Offset ≤7.5 mm – –
Note:
z Impact response spectrum: The maximum acceleration response curve
produced by the equipment under the defined impact excitation. Impact response
spectrum II means the duration for semisinusoidal impact response spectrum is 6
minutes.
z Quiescent load: The Pressure from above that the equipment with packing can
endure in the specified stack mode.
8-7
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
I. Climate
Note:
z The measurement points of temperature and humidity refer to the values
measured 1.5 meters above the floor and 0.4 meters away from the front of shelf
when there are no protection panels in the front and back of the shelf.
z Short term means that the consecutive working duration is not more than 48
hours and that the accumulated working duration of a year is not more than 15
days.
Item Scope
Altitude ≤ 4000m
Atmosphere 70–106kPa
Temperature change rate ≤ 5°C/h
Solar radiation ≤ 700W/s²
Heat radiation ≤ 600W/s²
8-8
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
Sand mg/m³ ≤ 30
Note:
z Suspended dust: diameter ≤ 75 Dm
z Precipitable dust: 75 Dm ≤ diameter ≤150 Dm
z Sand: 150 Dm ≤ diameter ≤1000 Dm
3) Table 8-16 lists the restrictions on the densities of active chemical materials.
8-9
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 8 Technical Specifications
Note:
z Impact response spectrum: The maximum acceleration response curve
produced by the equipment under the defined impact excitation. Impact response
spectrum II means the duration for semisinusoidal impact response spectrum is 6
minutes.
z Quiescent load: The Pressure from above that the equipment with packing can
endure in the specified stack mode.
8-10
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 9 Compliant Standards
9-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 9 Compliant Standards
z IETF RFC 2833, RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals
z IETF RFC 2327, Session Description Protocol (SDP)
9-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 10 Reliability Design
10.1 Security
10.1.1 Network Security
Except the network services in use (such as SIP, MGCP and RTP/RTCP), MRS6100
closes the network services not in use, so as to prevent illegal users from intervening
the device operation through illegal entry.
The NMS of MRS6100 provides a strict user authentication function. Only the users
who pass the authentication and are granted with legal rights can perform normal
network management on MRS6100.
The system can take the corresponding measures when an exception occurs,
including error prevention measures and voltage protection measures (too high or too
low voltage). The system adapts well to the environment (especially to the hot stress),
and it can take protection measures if it is powered off during loading.
The system provides multiple alarm processing mechanisms. It ensures the normal
system status and timely fault alarming through panel indicators and buzzers; on the
other hand, it generates an alarm to the operation and maintenance personnel using
the network management mode, so as to facilitate maintenance personnel to perform
operations and maintenance through console or the NM workstation.
The system has strong error tolerance ability, and it takes processing and recovery
measures when an exception occurs.
The system adopts the redundant inter-board communication design.
10-1
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 10 Reliability Design
The MRS6100 ensures the system operation security through the following
measures:
z It strictly restricts the access authority of operation and maintenance personnel.
The user name and password are required when one accesses the system, and
the system makes record of it every time. According to the requirements of
maintenance and operation personnel, the operation authority can be classified.
z All important operations are recorded in the operation log, which facilitates the
location and tracing of the historical operation.
z Prompt alarms are available against system abnormality due to error operations.
z An excellent check function is available for configuration activities of an operator
and illegal configurations are refused.
z The maintenance and operation system can protect user names and passwords.
If a user makes no operation for a specified period, the system automatically logs
off to prevent the access of unauthorized users.
10.2 Reliability
10.2.1 Hardware Reliability
I. Distributed processing
10-2
Technical Manual
U-SYS MRS6100 Media Resource Server Chapter 10 Reliability Design
brought into service immediately. The standby one replaces the active one to control
the running and operation of the modules against service interruption of the system.
Mutual-aid work is also known as load-sharing. With the mutual-aid work mode, two or
more boards share the related functions during the normal working. Once one of the
boards becomes faulty, other boards take over the tasks imposed on the faulty one on
the premise that certain performance parameters such as call loss are guaranteed.
I. Protection Performance
From requirement analysis, system design to software test, all stages of the
development of MRS6100 strictly follow the Capability Maturity Model (CMM)
procedures. Code walk-through, review, inspection, unit test, system test and other
useful quality assurance measures taken during MRS6100 development greatly
improve the reliability of the software.
The MRS6100 can automatically detect and diagnose both software and hardware
faults. The faulty components can be automatically switched, restarted and reloaded
to avoid service interruption.
10-3
Technical Manual
U-SYS MRS6100 Media Resource Server Appendix A Acronyms and Abbreviations
A-1