SS7 to IP Signaling Gateway Transport Architecture
draft-glaude-ss7-gw-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Normand Glaude , Tom Blain , Reg Cable | ||
| Last updated | 1998-12-14 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo defines an architectural framework for transporting SS7 signaling information over Internet Protocol networks. It describes a Signaling Gateway which acts as a bridge between the SS7 and IP networks. The Signaling Gateway can be configured as an SS7 end-node or as a Signal Transfer Point (STP) deployed singly or in a mated pair configuration. An application program interface (API) allows multiple remote devices, such as Media Gateways and Media Gateway Controllers, to register with the Signaling Gateway using TCP or UDP. The API consists of MTP and SCCP primitives which remote devices can use to send and receive ISUP and TCAP messages to effect PSTN call control and access Intelligent Network databases. The MTP and SCCP primitives ensure that application states (available, unavailable or congested) are propagated into the SS7 network. This memo also identifies some functional and performance requirements for SS7 signaling transport to IP-based application processes residing on one or more client hosts.
Authors
Normand Glaude
Tom Blain
Reg Cable
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)