On 06/16/2011 04:22 AM, Geoff Van Brunt wrote: > I think at the very least, it might be a good idea for the SipX devs to > get someone to take a look at what is needed and come up with a plan for > implementing it. That way the architecture can be adapted slowly over > time as needed. In addition new features can be developed with it in > mind so there is less work in the long run. > > Just my 2 cents. > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
Basic requirements. 1. Add support for multiple listeners/muti-homing in sipX. Currently sipx only supports a single NIC with a single IP address 2. Make sure that the SIP/SDP Parser supports IPV6. 3. Make sure DNS Resolver support IPV6 Application requirements. 1. Modify sipXconfig to map IPV4 and IPV6 address to the server components. 2. Make sure all media components (suck as sipXrelay) is able to bind and mediate IPv4 and IPv6 packets including gatewaying IP4 to IPV6 3. Modify the SIP Stack so that UAS/UAC Proxy transaction tuples support madiation of IPv4->IPv6 relays. Test Requirements 1. Retest all phones/ITSPs which claim IPV6 support in their feature list and document both the howto, quirks and gotchas for each in the WIKI. Planning is easy and we do not have any shortage of time dedicated in that area. We have our eyes on IPV6 and be assured that we will get to it when the time is ripe. What is missing at the moment is the commercial reason why we (eZuce) should put ipv6 support above all others when the fact remains that there is no immediate merit for it right now. Merit versus hardship is just too off a ratio. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
