Oops. I missed saying that concurrent connections for the PSTN will probably be from 5 to 10 to begin, eventually hitting 15 to 18.
> -----Original Message----- > From: Marc Carrafiello [mailto:[EMAIL PROTECTED] > Sent: Friday, May 04, 2007 12:02 PM > To: asterisk@uc.org > Subject: [on-asterisk] Separate Network for Asterisk? > > > Hello, > > I just got confronted by my LAN wiring guy about whether or > not I wanted > double the LAN drops in a new wing that's getting an infusion > of staff and > my first Asterisk install. He said that he's still doing a lot of > double-wiring for companies, where they run the IP-PBX on a > separate network > and thus require twice the amount of LAN drops. He's even > been back to > companies to add more drops to enable this after the fact. > > I actually didn't do a lot of research on this, am I setting > myself up for > trouble by attempting to stick my IP-PBX onto my existing > network? When I'm > done, I'll be running: > > Asterisk 1.4.x with a Sangoma A101D T1 card on a fully loaded > Bell PRI. > Concurrent PSTN connections will probably > 35 (or so) Linksys SPA942's and 3 (or so) ATAs for Conference Phones. > In most circumstances, a user's desktop will be plugged into > the switch of > the Linksys SPA942 phone. > (2) Catalyst 3524's with PoE to enable the phones to not use > AC Adapters. > No QoS implemented. > > When done, our main office will have around 40 workstations > and 30 phones on > 1 LAN. With a fully switched network that isn't heavy on > printing or file > server usage, I was hoping I'm not insane. Am I insane? > Should I segregate > the networks? Implement QoS? Run away very quickly? > > > -Marc > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
