Maybe it's just me... I don't like putting anything in the wild...
-----Original Message-----
From: Alan McKay [mailto:[email protected]]
Sent: Friday, August 21, 2009 10:38 AM
To: Picher, Michael
Cc: sipx-users
Subject: Re: [sipx-users] architecture decisions for new install
> Usually the problem with trunking is with voice prioritization.
> Consider a separate internet connection just for voice services (easy
> fix for larger installs).
Oh, I forgot to mention that they tried this - they separated out the
cable modem connection just for the VOIP. But since nobody seems to
have many details, I really do not know what the issue was.
> The Data Center is probably a good location if you are using SIP
> trunking as well... not such a good solution if your only connectivity
> is only through local PSTN.
So what about setting up SipX "in the wild" and turning on the local
firewall? Will that work these days?
> sendmail
I have not yet installed the latest ISO so thanks for the info. My
choice of postfix was mainly because I am already familiar with it.
We are migrating mail servers so I can still pick whatever I want.
So I have a few options here that I see.
(1) use the SipX ISO as-is, and go with sendmail
(2) use the SipX ISO and turn off sendmail, add postfix (will this
break anything?)
(3) use a standard CentOS install but with Postfix and add the SipX
RPMs (is this easy to do?)
I'm thinking that the data center is the way to go here.
thanks,
-Alan
--
"Don't eat anything you've ever seen advertised on TV"
- Michael Pollan, author of "In Defense of Food"
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
