thanks for the hijack comment now and to figure out the code words for alix and wondering what we mean exactly by atom On Sep 13, 2011 1:51 PM, "Michael Picher" <[email protected]> wrote: > yea, i like the idea of the atom machines better than the alix ones... but > that's me being a speed freak. > > Not that you need that much speed to drive a typical internet connection. > > i think we successfully hijacked this one. > > On Tue, Sep 13, 2011 at 1:46 PM, Tony Graziano < [email protected] >> wrote: > >> im a fan of both. though since pfsense is not a cpu hog I NEVER throw a PC >> at it anymore unless I'm in a jam. >> >> alix devices are cheap, diskless and have low power. the smaller the office >> the dumber i want the box to be. its better than a consumer device. >> >> i also like the small low power servers like the atom based devices. I have >> one i just installed with 6 NIC's and a 2.5" sata drive with 4gb of >> nanoflash. yes its more expensive than what i have laying around as parts, >> but its more reliable because its new and since it uses very little power, >> it pays for itself in time versus the PC approach. I can do ANYTHING pfsense >> can do with it, including squid. the room runs much cooler now, thank you! >> >> but if you have the pc there now and need it done, do it. you can always >> backup and restore the config to another device. >> >> On Tue, Sep 13, 2011 at 1:32 PM, Todd Hodgen <[email protected]> wrote: >> >>> I’ve grown fond of the small appliance. As Tony said, no moving parts, >>> lower power consumption, very compact, and Compact Flash can be upgraded >>> offsite as needed with software updates. $19 for a 4gb compact flash these >>> days, and it’s much more than they will ever need.**** >>> >>> ** ** >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Michael Picher >>> *Sent:* Tuesday, September 13, 2011 10:24 AM >>> *To:* Discussion list for users of sipXecs software >>> >>> *Subject:* Re: [sipx-users] Shared trunks between servers**** >>> >>> ** ** >>> >>> I'm just kinda funny about having a PC... i guess it's just me. i can >>> replace it in a snap, i know where to get power supplies, etc.**** >>> >>> On Tue, Sep 13, 2011 at 1:22 PM, Todd Hodgen <[email protected]> >>> wrote:**** >>> >>> $214 buys a PFSense appliance loaded with three ports from Netgate. Works >>> great!**** >>> >>> **** >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Michael Picher >>> *Sent:* Tuesday, September 13, 2011 9:44 AM**** >>> >>> >>> *To:* [email protected]; Discussion list for users of sipXecs software >>> *Subject:* Re: [sipx-users] Shared trunks between servers**** >>> >>> **** >>> >>> No.**** >>> >>> **** >>> >>> Buy a used Dell Optiplex GX280 or something similar off eBay, slap in a >>> fresh drive, a second NIC and use that... $200 and you're done without >>> messing around.**** >>> >>> **** >>> >>> If it were me, and it's not (ha Tony)... Don't try to make stuff do what >>> it isn't supposed to do... you might save a couple $$ up front but you burn >>> tons of time and end up with something that is inherently a pain in the >>> caboose every time you turn around to try and do something.**** >>> >>> **** >>> >>> Mike**** >>> >>> On Tue, Sep 13, 2011 at 11:22 AM, [email protected] <[email protected]> >>> wrote:**** >>> >>> I'm going to go with sip trunks, thus eliminating the need for vpn. >>> However, I know this will come up again so have one more question. >>> >>> I would more than likely use a separate pfsense box to establish a vpn >>> connection between the remote sipx server, back to my main lan so that I >>> could give it direct access to the mediant. However, wondering if there is >>> any way of doing this which might eliminate having to use a separate pfsense >>> box in addition to the phone server. Perhaps directly on the sipx server >>> itself? >>> >>> So for example, something running on the remote sipx server which would >>> allow it to vpn to one of my pfsense servers back on the main lan, giving it >>> access to the mediant. Maybe OpenVPN running on sipx, something along those >>> lines? >>> >>> Just curious because this situation will probably come up again for us and >>> I'd like to know what's out there. >>> >>> Thanks.,**** >>> >>> >>> >>> >>> >>> >>> On Sun, 11 Sep 2011 17:36:04 -0400, Tony Graziano wrote:**** >>> >>> > PSTN <--PRI--> sipx-branch1 <--ISP--> >>> > >>> > || >>> > >>> > >>> > VPN Tunnel >>> > >>> > || >>> > >>> > >>> > sipxbranch2 >>> > >>> > >>> > it should just be a gateway just like the existing one. the only >>> questions >>> > would be adjusting the ACL to allow that IP network to use it and the >>> > mediant dial plan to handle the other sipdomain equally, and what >>> numbers >>> > to point to which sipx server for DID. >>> > >>> > On Sun, Sep 11, 2011 at 5:28 PM, [email protected] <[email protected]> >>> > wrote: >>> >> On Sun, 11 Sep 2011 13:54:11 -0400, Tony Graziano wrote: >>> >> either make the remote branch remote users or connect the two sites via >>> >> vpn >>> >> and add the new branch sipx server as acl ti the medians and use it as >>> a >>> >> gateway. >>> >> >>> > >>> >> Thanks very much for the input. I have a better idea of what I am after >>> >> now. >>> >> >>> >> >>> >> On Sep 11, 2011 1:34 PM, "[email protected]" <[email protected]> >>> wrote: >>> >>>> without explaining what you have now in a way other than "a really >>> >>>> good >>> >>>> LD >>> >>>> deal". >>> >>>> >>> >>> LD meaning that with our PRI services, we get a good long distance >>> deal. >>> >>> If possible, I'd like to use our current trunks to provide 4 lines to >>> a >>> >>> remote sipx server. >>> >>> >>> >>>> How about stating how your existing gateway or trunk is implemented? >>> >>>> Is >>> >>>> it >>> >>>> a PRI? Is it a trunk? Is there a VPN between the two locations? >>> >>>> >>> >>> I was asking about sipx itself but see how that comes into the >>> picture. >>> >>> >>> >>> The remote location is a small office that will need 4 trunks. >>> >>> If we had to, we would put a gateway there to convert analog phone >>> lines >>> >>> to SIP trunks for sipx. That however adds to the cost. >>> >>> >>> >>> At the main location, we use the mediant 2000 to provide PRI/SIP >>> trunks >>> >>> to our local sipx servers. >>> >>> >>> >>> One option could be allowing the remote server to get it's trunks >>> >>> directly off of the mediant. >>> >>> Another would be to use a virtual trunk provider to get trunks into >>> the >>> >>> remote. >>> >>> >>> >>> My question however, was if I could use one sipx server (at our main >>> >>> location) to provide the 4 trunks needed to the remote sipx server. >>> >>> >>> >>>> Without using a PRI as the gateway or having both of the servers >>> using >>> >>>> the >>> >>>> same sipdomain, it a lot more problematic from both a security and >>> >>>> permissions standpoint. It also depends on the capabilities on the >>> >>>> ISTP >>> >>>> "if" it is a trunk. >>> >>>> >>> >>> We would manage the remote so it could be in the same domain. I would >>> >>> control both LAN's so could just allow the remote and local servers to >>> >>> communicate via firewall rule. >>> >>> >>> >>> Mike >>> >>> >>> >>> >>> >>>> On Sat, Sep 10, 2011 at 1:56 PM, [email protected] < >>> [email protected]> >>> >>>> wrote: >>> >>>> >>> >>>>> Sorry if I've posted this multiple times, had some mailer problems >>> >>>>> and >>> >>>>> don't see it in the list so am reposting. >>> >>>>> >>> >>>> >>> >>>>> --- >>> >>>>> >>> >>>> I have to install a small system at a remote location. The system >>> will >>> >>>> only >>> >>>> have about 4 trucks so makes no sense to order lines/gateway etc. >>> >>>> What I was wondering about is either getting SIP trunks from a >>> >>>> provider >>> >>>> or, >>> >>>> getting them from my main sipx box? >>> >>>> >>> >>>> I have never delved into anything like this and wondering if it is >>> >>>> possible >>> >>>> to extend trunks over to a second (or more?) sipx servers. >>> >>>> Should I be looking at Branches? >>> >>>> >>> >>>> The reason I would do this is because we have a good LD deal so want >>> >>>> to >>> >>>> take advantage of that rather than having to buy trunks. >>> >>>> >>> >>>> >>> >>>> Thanks. >>> >>>> >>> >>>> Mike >>> >>>> >>> >>>> >>> >>>> _______________________________________________ >>> >>>> sipx-users mailing list >>> >>>> [email protected] >>> >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>>> >>> >>>> >>> >>>> -- >>> >>>> ====================== >>> >>>> Tony Graziano, Manager >>> >>>> Telephone: 434.984.8430 >>> >>>> sip: [email protected] >>> >>>> >>> >>>> Fax: 434.465.6833 >>> >>>> >>> >>>> Email: [email protected] >>> >>>> >>> >>>> LAN/Telephony/Security and Control Systems Helpdesk: >>> >>>> Telephone: 434.984.8426 >>> >>>> sip: [email protected] >>> >>>> >>> >>>> Helpdesk Contract Customers: >>> >>>> http://support.myitdepartment.net >>> >>>> >>> >>>> Blog: >>> >>>> >>> >>>> http://blog.myitdepartment.net >>> >>>> >>> >>>> >>> >>>> Linked-In Profile: http://www.linkedin.com/pub/tony- >>> >>>> graziano/14/4a6/7a4 >>> >>>> >>> >>>> >>> >>>> Ask about our Internet faxservices! >>> >>> _______________________________________________ >>> >>> sipx-users mailing list >>> >>> [email protected] >>> >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> > _______________________________________________ >>> > sipx-users mailing list >>> > [email protected] >>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> > >>> > >>> > -- >>> > ====================== >>> > Tony Graziano, Manager >>> > Telephone: 434.984.8430 >>> > sip: [email protected] >>> > Fax: 434.465.6833 >>> > >>> > Email: [email protected] >>> > >>> > LAN/Telephony/Security and Control Systems Helpdesk: >>> > Telephone: 434.984.8426 >>> > sip: [email protected] >>> > >>> > Helpdesk Contract Customers: >>> > http://support.myitdepartment.net >>> > >>> > Blog: >>> > http://blog.myitdepartment.net >>> > >>> > >>> > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>> > >>> > >>> > Ask about our Internet faxservices! >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/**** >>> >>> >>> >>> **** >>> >>> **** >>> >>> -- >>> Michael Picher >>> eZuce >>> Director of Technical Services >>> O.978-296-1005 X2015 >>> M.207-956-0262 >>> @mpicher <http://twitter.com/mpicher> >>> www.ezuce.com**** >>> >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/**** >>> >>> >>> >>> **** >>> >>> ** ** >>> >>> -- >>> Michael Picher >>> eZuce >>> Director of Technical Services >>> O.978-296-1005 X2015 >>> M.207-956-0262 >>> @mpicher <http://twitter.com/mpicher> >>> www.ezuce.com**** >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> <http://support.myitdepartment.net>Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> Ask about our Internet faxservices! >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Michael Picher > eZuce > Director of Technical Services > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
