[TriLUG] VoIP for 125 users

[Chris Bullock]

I know this is late in the game but we have an Avaya system and are really pleased with it.  Not sure what your plans are but we have 4 remote offices connecting via IP to our main facility, each site is independent but uses some resources from the home site(long distance plans, centralized voicemail, hotdesking.)  We have a mix of digital and IP sets.  I was running a VPN at home and had an IP set at home and could work fine from that.  The huntgroups are very configurable and work really well.  Avaya coupled with their voicemail/autoattendant  product adds much configure ability, ie DB access, mail, and analog controls, ie unlock a door by call a particular line or extension.  Avaya has the ability to handle analog devices also, this alone has saved us thousands of dollars on B1 lines every year.
I will say that their new pricing model is much more expensive than it used to be.  Everything now is licensed based.

Chris

--- On Fri, 10/15/10, David M. <turnpike420 at gmail.com> wrote:

> From: David M. <turnpike420 at gmail.com>
> Subject: Re: [TriLUG] VoIP for 125 users
> To: "Triangle Linux Users Group General Discussion" <trilug at trilug.org>
> Date: Friday, October 15, 2010, 10:55 AM
> Matt, that's an amazing amount of
> info.  You've clearly got your head
> wrapped around this stuff.  Roll our own is a
> possibility, but I do think we
> are likely to go with a vendor ... if something goes wrong,
> it's their fault
> not mine.  :)
> 
> On Thu, Oct 14, 2010 at 9:36 PM, Matt Pusateri
> <mpusateri at wickedtrails.com>wrote:
> 
> > You can look at sipXecs, which was backed by nortel,
> and sold by nortel.
> >  Avaya has picked up the remnants,  and will
> be releasing a product on it.
> >  I was really not impressed with Avaya or there
> local people when I had to
> > deal with them at a previous job.  Most of the
> commercial systems I looked
> > at are old pbx/key systems and voip is just an bolt on
> and really do not
> > seem to be done well.  SipXecs (http://www.sipfoundry.org)  has forked
> > from the Avaya build and there is a company Euze, that
> is sponsoring it and
> > doing development work.  You can get commercial
> support from them, so it's
> > not like you're just downloading asterisk/trixbox
> etc.  Of course you can
> > get commercial support for Asterisk and Trixbox as
> well. I run Trixbox at my
> > current job, and there things I like and things I
> dislike about it.   The
> > more I use Trixbox, the less I like it
> specifically.     Trixbox is Asterisk
> > plus FreePBX 2 with Trixbox addons hacked on
> top.  FreePBX 3 has forked and
> > is under a new name
> >  .  This kinda makes Trixbox less appealing
> in the long run.   What I
> > really like about sipx/sipfoundry is that they are
> really implementing sip
> > correctly or appear to be.   This
> allows them to use proxy's and SBC's and
> > not make a B2BUA like asterisk do the wrong type of
> work.  The sipfoundry
> > architecture is just a much better design.  You
> can't even set the product
> > up without doing DNS correctly for sip uri
> dialing.  Plus they have basic
> > clustering/ldap/ and jabber support out of the
> box.  I have a test box right
> > now, and hope to eventually replace trixbox/asterisk
> at work with it.
> >
> > If you are going to roll you own or use a FOSS
> solution (Again commercial
> > support is available and may get you past the PHB's) I
> would recommend
> > Polycom phones over Cisco's or Snoms or
> Astara's.  Polycom seems to be
> > trying hard to make  a SIP compliant phone.
> >
> > If you need more help or have questions feel free to
> ping me off list.
> >
> >
> > Matt P.
> >
> >
> >
> -- 
> This message was sent to: Chris Bullock <cgbullock at yahoo.com>
> To unsubscribe, send a blank message to trilug-leave at trilug.org
> from that address.
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web    :
> http://www.trilug.org/mailman/options/trilug/cgbullock%40yahoo.com
> TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions
>