SIP Firewall Solution
draft-thernelius-sip-firewall-solution-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Frederik Thernelius | ||
| Last updated | 2000-07-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 document describes a solution that is able to handle SIP signaling together with NAT enabled firewalls. The intent is to show that existing firewalls do not have to be replaced by 'SIP enabled' ones, instead they will only have to be reconfigured slightly. The main feature of this solution is using MGCP from a session control proxy to open/close holes in an RTP proxy which then enables RTP traffic to flow between interconnected networks. Worth noting is that this solution will not only work for SIP, it will also work for other protocols, such as H.323 or Real Audio. It does not even have to be RTP that is passed through the RTP proxy, though this draft assumes that the RTP stream is accompanied by RTCP. The solution will work for any protocol that wishes to open/close ports dynamically in the RTP proxy (maybe it should be called Forwarding Engine in the general case).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)