My 2 cents...I think it would be wise to wait until endpoints fully support ip 6 (not sure if phones/gateways/etc. currently do). Investing programming time into something that is not "the norm" seems like 'putting the cart before the horse'.
This doesn't afford any real functionality or stability - but it will create lots of unneeded bugs :) Nathaniel Watkins IT Director Garrett County Government 203 South 4th Street, Room 210 Oakland, MD 21550 Telephone: 301-334-5001 Fax: 301-334-5021 E-mail: [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Staffan Kerker Sent: Friday, June 10, 2011 1:09 PM To: Discussion list for users of sipXecs software Cc: Kyle Haefner Subject: Re: [sipx-users] sipXecs and IPV6 On 10 jun 2011, at 03.36, Joegen Baclor wrote: > If you need IPV6 and you need it now, you may opt to deploy a SER router > as ingress and egress for sipX. IPV6 will be a tough beast to beat, > IMHO. It requires that transaction be stateful so that a UAS-UAC pair > can have V4 on the inbound leg and V6 on the outbound leg. Not to > mention, v6 requires that sipx first support multiple interfaces which > it does not currently. Does this mean that a major change to the SipXecs code will be needed to provide native IPv6 support? I'm really interested in this so if in any way I can help to get SipXecs on the IPv6 train I'm more than happy to help testing. What's the view of the community to get IPv6 support in? I know there are quite some complications, escpecially in partial dual-stack environments, but I really think it would be great to get this going and testing started. //Staffan -- Staffan Kerker mail/sip/xmpp: [email protected] "There is absolutely no money above the 5th fret..." /Donald "Duck" Dunn This message and any files transmitted with it are intended only for the individual(s) or entity named. If you are not the intended individual(s) or entity named you are hereby notified that any disclosure, copying, distribution or reliance upon its contents is strictly prohibited. If you have received this in error, please notify the sender, delete the original, and destroy all copies. Email transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Garrett County Government therefore does not accept any liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Garrett County Government, 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 www.garrettcounty.org _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
