1 / 4

Addressing SIP Traversal Through Firewalls and NATs: Key Controls and Solutions

This draft outlines crucial controls required for successfully passing SIP and media streams through firewalls and NATs. It examines application layer and IP layer controls needed for effective SIP Application Layer Gateway (ALG) interaction. Additionally, the draft highlights challenges such as re-INVITE issues and handling forwarding protocols. It suggests exploring the use of the TRIP protocol for gateway registration as a preferred solution. A session will be held to discuss the matter further and evaluate its potential as a working group item.

alexia
Télécharger la présentation

Addressing SIP Traversal Through Firewalls and NATs: Key Controls and Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIP wg: New Drafts Jonathan Rosenberg dynamicsoft

  2. Increasingly important to get SIP through firewalls and NATs Draft describes Controls needed to be exercised on a firewall to get media streams through SIP ALG for NAT, both application layer and IP layer Controls needed to be exercised on a NAT to get SIP and media through Standard remote-control protocol for NAT and firewall control would be VERY NICE Gotchas! 183, re-INVITEs, forwarding, etc. Where to go from here? Foglamps BoF Wed 1pm for more info Should this be a wg item? Should this be a new wg? Not really a proposed standard, perhaps informational? SIP through Firewalls and NATs

  3. Problem: How does a proxy learn which of its local gateways to use for routing calls? One solution: SIP REGISTER Been proposed on list at least twice Bad idea Better Solution: TRIP Big complaint: too complex However, turns out a very minimal subset is needed Discussed during iptel session Monday Check it out… draft-rs-trip-gw-00.txt Usage of TRIP for GW registration

More Related