Technical Manual
U-SYS MRS6100 Media Resource Server
Chapter 5 MGCP and SIP
Huawei Technologies Proprietary
5-3
The two parts are separated by @, for example, ms/cnf/1@ mrs6100.huawei.com.
The syntax of the local name depends on the type of the endpoint. The local name
can be leveled to forma naming path from the gateway name to other endpoints.
An endpoint identifier must comply with the following conversions:
z
Each identification item in the naming path must be separated by a slash (/).
z
Each identification item must be letters, numbers or other printable characters.
The item cannot include delimiters like /, @, or space.
z
Wildcards like * or $ can be used in local names. * represents all the endpoints
above this level; $ represents one endpoint above this level.
In the MGCP, the gateway is identified by the domain name, for example,
mrs6100.huawei.com. The local name can consist of a physical interface name, for
example ms/cnf, and a terminal identifier, for example, the port number or identifier
that corresponds to the telephone number accessing the media gateway). The
terminal identifier is separated from the physical interface name by /.
For example, suppose that the AMG endpoint is ms/cnf/[email protected].
It represents the first endpoint of the ms/cnf interface of the MRS media gateway. The
domian name of the gateway is mrs6100.huawei.com.
For example, suppose that the endpoint name of the TMG is
X35V3+A4/[email protected].
It represents the thirteenth time division multiplexing (TDM) circuit on the X35V3+A4
interface of the 23# gateway in the example network.
V. Calls and connections
Connections may be either point to point (P2P) connections or multipoint connections.
A P2P connection is an association between two endpoints that send data to each
other. Once the association is set up on both sides, the data is transferred between
them. A multipoint connection is an association among multiple endpoints.
Connections can be set up over different bearer networks.
Connections are managed at endpoints and can be converged into calls.
Connections are grouped by call. One call can include one or more connections. The
setup of connections and calls are initiated by of one or more MGCs.
Figure 5-3 shows the relations among endpoints, connections, calls, and gateways.
