|
In my experience 56k for voip is not enough close to enough. If you toss in voice mail on top of the system you are adding even more overhead. It can be done, but it takes work and you need to examine your network infrastructure closely, ie: intelligent switches at each location, ample bandwidth, and I would not personally use anything but cisco routers for this. Although I do not like their voip phone systems, their routers handle the traffic extremely well. It all depends on what you are trying to accomplish. Voip can provide you with additional resources and enhanced services but if your only goal is to save money you will be somewhat disappointed. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan C Sent: Sunday, April 03, 2005 1:21 PM To: Midrange Systems Technical Discussion Subject: Re: iSeries Voice Over IP I've been working where we put in VOIP some years ago. For the technology programming, i.e. the parts that make it work, I think it's hard to beat a dedicated IP-enabled "voice server" (I guess you could call the replacement for PBX systems), that supports the voicemail and the phone lines and all that, connecting to a router that communicates with routers and similar phone systems on the other end. At the central office, we had a dedicated router for voice, another for data, and they broke up the IP packets for each branch. There was 56K dedicated for each branch, and the traffic split between dedicated 28K for voice, 28K for data. Putting the AS400 in the middle would've put it "in the way". On the other end, the router split the traffic back out. (This handled by outside support for configuring those routers in this case). The voice had about 26K dedicated for each branch (one maybe two max calls at a time). The AT&T tech who set up the phones said they now call the phones on your desk "voice terminals". I think it would be useful to have better interfacing, or technical software packages or IP-enabled API's, for feeding usage data to the iSeries system for supervisory and accouting use. After all, they're talking about putting IP into everything, airborne dust specks included. -- Alan >>We are looking to purchase a new phone system. What are the solid >>Voice Over >>IP solutions that are available to run on the iSeries and what is your >>opinion of them? >> >> > >JMHO, of course ... but using the iSeries for VOIP seems like using the >wrong tool for the job. > >Of course I haven't done any research into it ... so I could be wrong. > >david > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.