Carrying ISUP in SIP Messages (SIP-ISUP-ANNEX)
draft-miller-sip-isup-annex-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Frank w. Miller | ||
| Last updated | 2003-03-20 | ||
| 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
SIP-ISUP-ANNEX is a mechanism by which an XML representation of certain ISUP messages can be transported in the body of SIP INFO messages. This mechanism can be used to allow PSTN elements to control trunk interfaces that are terminated by SIP-controlled access equipment without having to implement the binary ISUP protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)