search for: nbx100

I am the network administrator at a small (20-30 employee) financial company. We are in the process of moving offices and will be obtaining a VoIP phone system when we do. Right now, it's down to the 3com nbx100 series and *. Having lurked on *-user for a few weeks and having seen the nifty features of asterisk, I'm convinced. The price difference has pretty much sold my superiors. However, they're slightly wary of the whole open-source thing. They have no way of knowing, for certain, that aste...

..., use the Wiki. On Wed, 2004-01-07 at 14:04, Jeffrey Paul wrote: > I am the network administrator at a small (20-30 employee) financial > company. We are in the process of moving offices and will be > obtaining a VoIP phone system when we do. Right now, it's down to the > 3com nbx100 series and *. Having lurked on *-user for a few weeks and > having seen the nifty features of asterisk, I'm convinced. The price > difference has pretty much sold my superiors. > > However, they're slightly wary of the whole open-source thing. They > have no way of kno...

We've been talking about moving from our NBX100 to an asterisk solution for some time now. Well, to make a long story short, the call processor on our NBX has went south. We are now forced to purchase a new call processor >$500 or move our solution to asterisk. (Which is up and running and have been tested with Grandstream Adapters.)...

Another trivial question: Is there a "place" where all the parameters are documented ? In example (my example!) I would like to know the meaning of a lot of parameter that can be used in sip.conf, A lot of these keywords are intuitive keywords (i.e. NAT=YES/NO;PORT=5060; context=xxxxx) but other are not (at least for me) i.e.: type = peer, friend insecure=very host=dynamic and so on.