ISUP parameters expected in SIP messages
draft-roach-sip-isup-parameters-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Adam Roach | ||
| Last updated | 1999-06-10 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-roach-sip-isup-parameters-00.txt
https://www.ietf.org/archive/id/draft-roach-sip-isup-parameters-00.txt
Abstract
To assure inter-operability between gateways which may choose to transit ISUP messages inside a SIP network, this document seeks to outline the types of ISUP messages which an implementation can sensibly expect to arrive in each given SIP message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)