Posted: Thu May 28, 2009 7:44 pm Post subject: [asterisk-dev] Feature request: Ability to assign which nic
It is an roadblock for those in Japan who desire to go open source and with Asterisk. One alternative, of course, is for Japanese users to have to give up on open source voip and pay exhorbinate purchase and maintenance fees for NTT proprietary voip services. However, we are talking about massive monetary amounts that only large businesses would be able to justify paying.
But, many people in the global community cherish and are passionate about open source (including Asterisk) because it does provide a free, community-driven, open alternative to big-business pricy solutions around the world.
So, yes, extending the capability of Asterisk to allow for assigning trunks to specific nic cards would solve the problem over here with overcoming the massive monopolist telecom company NTT's giving Japan people no other alternatives to the purchase of NTT's own high-priced technology and yes it would thereby solve the individuals' ability to deal with that.
I think there have been countless other situations where Asterisk and other open source products have countered monopolists with alternative products for the masses including providing alternatives to Microsoft's monopolistic efforts and as well as those of others.
Further, in the case of NTT, we are basically talking about helping an entire country of people (not just a few individuals).
Additionally, it sounds like there are other benefits to this addition as well as noted by xrg (reporter) 2009-05-25 00:52 who wrote:
This would be a major feature, better be developed against 1.6-trunk, not 1.4.
The feature would be the ability to bind to multiple interfaces for sip.c and perhaps allow to explicitly choose the interfaces per sip peer. Last time I'd seen the code, was doable but still required major restructure there. IAX has such an infrastructure. At SIP, it is a little more complicated, since SIP could be UDP and wouldn't have a "connection".
Multiple interfaces binding would also solve some routing problems, like the case of multipath (*very* useful, once we could make it work).
I vote for the feature!
Thus, it appears that there are other routing benefits. I wish that I could code this myself and contribute it but I do not have those abilities and am proposing to the community.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum