Since we, collectively, are steering one of the industries driving up individual utilization of the IPV4 address space as well as being one of the most sensitive to NAT which is the only way through which IPV4 has been sustained as long as it has; it seems like a worthy exercise to discuss our own, and the industries preparedness to adopt IPV6. Has anyone out there had any experience using any of the open source platforms (OpenSIPS, Asterisk, SIPPY etc) with native IPV6? It seems like these projects are the best equipped right now to handle this move since they rely heavily on the network stack of the underlying OS. Are there any endpoints or other CPE that anybody has had luck getting to work over native IPV6? So far I am unaware of any carrier grade (meaning it costs a lot of money) softswtch platforms that are ready for this, or seem like they would be without a multi-year effort. Anybody out there that can enlighten us on this one? Any experience with SBC's or border elements that are or will be ready to handle IPV6 in deployment (either native 6 to 6 or 6 to 4 through a b2bua) Finally any comments or thoughts on the whole topic, I am interested to see other opinions and approaches to the topic.
21 okt 2009 kl. 06.01 skrev anorexicpoodle:
Since we, collectively, are steering one of the industries driving up individual utilization of the IPV4 address space as well as being one of the most sensitive to NAT which is the only way through which IPV4 has been sustained as long as it has; it seems like a worthy exercise to discuss our own, and the industries preparedness to adopt IPV6.
Has anyone out there had any experience using any of the open source platforms (OpenSIPS, Asterisk, SIPPY etc) with native IPV6? It seems like these projects are the best equipped right now to handle this move since they rely heavily on the network stack of the underlying OS. Kamailio/OpenSER handles IPv6 properly, but Asterisk currently does not have any support for IPv6. There has been some work by March Blanchet from ViaGenie, but it is not up to date and not integrated into the trunk version of Asterisk.
Something that bothers me is the lack of configurations for "IPv6 default gateways" in all IPv4 based products. Even though Asterisk is only IPv4, we might still get IPv6 addresses in many cases - SRV records, Contact headers and REFER targets. In order to handle these - or the reverse case "IPv4 default gateway" - we need configuration options and logic for it. Yes, this is an important issue. So far, it seems like no one wants to put any money towards it so we can fix Asterisk. Open Source projects are in hand of the user base and their requirements. Regards, /O
Never looked into it yet. I"m still working on Gerald Ford's Great Metric Conversion :) Our current business model doesn't contain a lot of drivers that might motivate an investigation. David On Tue, Oct 20, 2009 at 9:01 PM, anorexicpoodle <anorexicpoodle at gmail.com> wrote:
Since we, collectively, are steering one of the industries driving up individual utilization of the IPV4 address space as well as being one of the most sensitive to NAT which is the only way through which IPV4 has been sustained as long as it has; it seems like a worthy exercise to discuss our own, and the industries preparedness to adopt IPV6.
Has anyone out there had any experience using any of the open source platforms (OpenSIPS, Asterisk, SIPPY etc) with native IPV6? It seems like these projects are the best equipped right now to handle this move since they rely heavily on the network stack of the underlying OS.
Are there any endpoints or other CPE that anybody has had luck getting to work over native IPV6?
So far I am unaware of any carrier grade (meaning it costs a lot of money) softswtch platforms that are ready for this, or seem like they would be without a multi-year effort. Anybody out there that can enlighten us on this one?
Any experience with SBC's or border elements that are or will be ready to handle IPV6 in deployment (either native 6 to 6 or 6 to 4 through a b2bua)
Finally any comments or thoughts on the whole topic, I am interested to see other opinions and approaches to the topic.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
David Hiers wrote:
Never looked into it yet. I"m still working on Gerald Ford's Great Metric Conversion :)
Our current business model doesn't contain a lot of drivers that might motivate an investigation.
The day IPv6 is adopted seriously, I am leaving networking/telecom and going to start a bakery. I can barely microwave Lean Cuisine, but perhaps I can secure some assistance from significant other. There is no way I am going to be managing infrastructure by way of hex nibbles. Remind me, why is it that nobody thought of using dotted decimal notation for IPv6 addresses, but just adding more octets? Are half-bite nibbles in a base humans aren't normally taught to count in more "expressive" somehow? -- Alex -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671
When you guys are looking to sell after all your customers are behind 4 NATs and nothing works right, or whatever kludge ends up happening after they/you can't get more PI IP space anymore, we're (your forward looking competitors) gonna pay a lot less to buy you out. Fair warning. -Paul Alex Balashov wrote:
David Hiers wrote:
Never looked into it yet. I"m still working on Gerald Ford's Great Metric Conversion :)
Our current business model doesn't contain a lot of drivers that might motivate an investigation.
The day IPv6 is adopted seriously, I am leaving networking/telecom and going to start a bakery. I can barely microwave Lean Cuisine, but perhaps I can secure some assistance from significant other.
There is no way I am going to be managing infrastructure by way of hex nibbles.
Remind me, why is it that nobody thought of using dotted decimal notation for IPv6 addresses, but just adding more octets? Are half-bite nibbles in a base humans aren't normally taught to count in more "expressive" somehow?
-- Alex
Hi, Here is my issue: After login to the call manager express, trying to access the phone configuration would give me the following errors and as result users lost their speed dial from their phone: Error: Unable to login as administrator to the Cisco CallManagerExpress at site 'local'. Details: CME login failed Any input? -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins Sent: Wednesday, October 21, 2009 9:18 AM To: Alex Balashov Cc: VoiceOps Subject: Re: [VoiceOps] IPV6 When you guys are looking to sell after all your customers are behind 4 NATs and nothing works right, or whatever kludge ends up happening after they/you can't get more PI IP space anymore, we're (your forward looking competitors) gonna pay a lot less to buy you out. Fair warning. -Paul Alex Balashov wrote:
David Hiers wrote:
Never looked into it yet. I"m still working on Gerald Ford's Great Metric Conversion :)
Our current business model doesn't contain a lot of drivers that might motivate an investigation.
The day IPv6 is adopted seriously, I am leaving networking/telecom and
going to start a bakery. I can barely microwave Lean Cuisine, but perhaps I can secure some assistance from significant other.
There is no way I am going to be managing infrastructure by way of hex
nibbles.
Remind me, why is it that nobody thought of using dotted decimal notation for IPv6 addresses, but just adding more octets? Are half-bite nibbles in a base humans aren't normally taught to count in more "expressive" somehow?
-- Alex
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On 20/10/09?21:01?-0700, anorexicpoodle wrote:
Any experience with SBC's or border elements that are or will be ready to handle IPV6 in deployment (either native 6 to 6 or 6 to 4 through a b2bua)
We had a discussion with Acme Packet last week about their product roadmap, which included discussion of their IPv6 plans. They currently have IPv6 running on one of their platforms (4500 I believe). One of their primary targets is IPv6/IPv4 translation - e.g. the SIP endpoint running IPv6 with the softswitch running IPv4. -- Dan White BTC Broadband
participants (7)
-
abalashov＠evaristesys.com -
anorexicpoodle＠gmail.com -
dwhite＠olp.net -
hiersd＠gmail.com -
oej＠edvina.net -
paul＠timmins.net -
Rod.Dossouvi.CTR＠dot.gov