asterisk users - Apr 2009 - IPv6 support?

Hey,

Just wondering if anyone can let me know what the status of IPv6 support
for Asterisk is currently.  I see that the branch where development was
happening has gone away.  I was trying:

  http://svn.digium.com/svn/asterisk/team/blanchet/v6

Has this branched moved to somewhere else?

Cheers!

-- 
Andrew Ruthven, Wellington, New Zealand
At work: andrew.ruthven at catalyst.net.nz
At home: andrew at etc.gen.nz
GPG fpr: 34CA 12A3 C6F8 B156 72C2  D0D7 D286 CE0C 0C62 B791
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20090428/a374207a/attachment.pgp

On Tue, 2009-04-28 at 09:08 +1200, Andrew Ruthven wrote:
> Hey,
> 
> Just wondering if anyone can let me know what the status of IPv6 support
> for Asterisk is currently.  I see that the branch where development was
> happening has gone away.  I was trying:
> 
>   http://svn.digium.com/svn/asterisk/team/blanchet/v6
> 
> Has this branched moved to somewhere else?
> 
> Cheers!
> 
Sometime ago i got this status from _the_ guru...
Russell replied, referencing 1.6.2...
(but other code might get in-the-way)



From: Russell Bryant <russell at digium.com>
> Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion
> <asterisk-users at lists.digium.com>
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> <asterisk-users at lists.digium.com>
> Subject: Re: [asterisk-users] Asterisk and IPv6
> Date: Mon, 28 Jan 2008 18:45:42 -0600
> 
> Hans Witvliet wrote:
> > Any progress on IPv6 ?
> > Still completely seperate code, or is it already being merged into the
> > tree...
> > 
> > Perhaps i overlooked it, but i couldn't find any reference in:
> > http://svn.digium.com/view/asterisk/tags/1.6.0-beta1/CHANGES?view=co
> 
> There has been progress.  It is not yet merged into the main tree, though. 
I
> would expect it to go in within the first few releases of 1.6 ...
>