[asterisk-dev] STUN support in chan_sip revisited

[Robert Hoffmann]

I assume asterisk can act as a relay for media?
Then, if ICE is on your roadmap, you will need a full STUN client AND server
implemenation for that.
This is because in ICE, a list of address candidates is gathered and all
these candidates are tested with STUN messages. A STUN answer determines a
successful connection.
Also you will need to implement RFC 5626 because ICE needs an already
working signaling session via SIP.

2010/8/9 Russell Bryant <russell at digium.com>

> On Mon, 2010-08-09 at 16:25 -0500, David Vossel wrote:
> > 1. Remove current STUN support in chan_sip.  More than likely we will
> decide to just depreciate it's use in sip.conf.sample but leave the code.
>  This means anyone using this broken implementation to do something they
> perceive as being useful will not lose the ability to do so, but the
> sip.conf options will be removed from the documentation.
>
> If it's not useful, then just remove it completely for 1.8 and trunk and
> make a note in UPGRADE.txt about it.
>
> --
> Russell Bryant
> Digium, Inc.  |  Engineering Manager, Open Source Software
> 445 Jan Davis Drive NW   -    Huntsville, AL 35806  -  USA
> jabber: rbryant at digium.com    -=-    skype: russell-bryant
> www.digium.com -=- www.asterisk.org -=- blogs.asterisk.org
>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100810/28834a40/attachment.htm