These protocols gain more and more importance as they suitably position customers to participate in the migration to IP networks. The DSI message handling software transports signaling information between protocol layers or between a protocol layer and an application layer in a totally transparent way, regardless of the physical source and destination of the messages. The protocol stacks, boards, and servers have been deployed throughout the world, providing signaling in various networks, as well as connections to many switch types. Figure 1. These links may be inter-chassis links, part of a dualresilient pair, or network-facing links to any other equipment supporting M2PA. The protocol is designed to be modular and symmetric, to allow it to work in diverse architectures, such as a Signaling Gateway to IP Signaling Endpoint architecture as well as a peer-to-peer IP Signaling Endpoint architecture.
|Published (Last):||14 August 2005|
|PDF File Size:||14.99 Mb|
|ePub File Size:||8.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
There are multiple adaptation layers, each has its own purpose. M3ua is the most used layer. It works at the network layer level as per the OSI model. It also covers the general adaptation layer concepts. The protocol specification is given in RFC The simplest example is the point code. An application server can be represented via a point code and with other parameters.
The set of parameters identifying an AS is called a routing key. Although this may be a Point code only or Point code and si etc. An AS is identified by a unique integer value, called routing context.
An asp can be connected directly to other nodes over the IP network. It is the IPSP model. An asp can serve multiple application servers. Its a logical entity. It implements the Sigtran stack and SS7 stack. A signaling gateway is represented by a signaling point code. This maintains the connection with the peer node and ss7 connection with other SSPs.
An SGP can serve multiple Signaling gateways located to the same node. Messages in m3ua Like other protocols, m3ua also has protocol messages. Some are protocol management messages and other user messages. Management messages are for updating elements status. The data message, which carries the actual user data over m3ua. M3ua Protocol messages: A message has a conman header and parameter section.
The parameter section has multiple parameters in TLV or tag length value format. The number of parameters and type of parameters depends on the message type. Currently, only version 1 is used. Message Class is the grouping of messages at a broad level. The following are the message classes. Other values are reserved. ASP state maintenance messages.
Means ASP can handle management messages but not any user or data messages. Routing context is an optional parameter, if not included then all AS configured in an ASP will be marked active. There are m3ua management messages used to convey the status of point code and SSN to nodes connected to SG. User data Message, this is the user application message, which carries the actual ss7 messages for m3ua users. SCTP needs to configure along with the adaptation layer configuration. It requires the parameters needed for setting up an association with the peer or remote SCTP.
Each endpoint has a port and a list of IP addresses. M3ua Startup Sequence.
Dialogic DSI SS7 Stack
The protocol standard is defined in IETF spec. Having dedicated resources for a voice call. It has links, which act as a stream of messages. This makes multiple streams to work in parallel. Enables low latency in the ss7 network and multiple paths to the peer node. A user of the ss7 link gets immediate link status congestion, link down, etc.
Dialogic DSI SIGTRAN Stack