Huawei U-SYS MRS6100 Technical Manual page 48

Technical Manual
U-SYS MRS6100 Media Resource Server
MRS6100
RSIP_RSP
Figure 5-7 MRS6100 registration flow
1) Event 1: MRS sends an RSIP command to MGC, reporting the completion of a
load or restart and requesting to register to MGC.
An example of RSIP encoding:
RSIP 836 *@mrs6100 MGCP 1.0
RM:restart
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
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.
II. MRS6100 announcement playing flow
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:
MGC
RSIP
Huawei Technologies Proprietary
5-23
Chapter 5 MGCP and SIP