IF I were you (and I'm not), I would install it on a domain I own (or plan to own). I would also suggest to install on a subdomain if email and other services are hosted elsewhere (i.e. yahoo, google, etc.).
SIPDOMAIN is not something you can easily change after installation, so plan carefully. It is necessary with sipxecs. On Sat, Jan 1, 2011 at 8:14 PM, bob gailer <[email protected]> wrote: > On 1/1/2011 3:16 PM, Todd Hodgen wrote: > > sipXecs is an enterprise telephone system. As such, it will generally be > > installed on a companies domain. You would give it a host name on that > > domain. SipXecs.bobgailer.com as an example. > > I am installing it for now in my SOHO. I have no domain (that I am aware > of). Eventually it might go into a small non-profit office. Again, no > domain that I am aware of, just a bunch of Windows workstations on a > LAN. Or do I not understand "domain"? > > On the front page of sipfoundry.org there is a large graphic with a link > to > > a book about the sipXecs system. It's a great starter book. > > Great. I will jump into it. Now I see the fine print "Get the book!" I > see it is a Packt Publication. I hope they did a much better job than > Garrison's trixbox CE 2.6 book. > > There are reviews of the book on Amazon and The Michigan Telephone blog > - a bit discouraging. > The blog compares "the book" against the bloggers working knowledge of tribox for a home application. He also never installed or used sipxecs. He's a home user. That's not what sipxecs is, so I don't know that the blog opinion matters, as does the blogger. The one review the Amazon poster had was looking for an engineering book, but the book is clearly positioned for a beginner primer to sipx to get the system up and running and assumes good conceptual use and practice or network basic, not necessarily and engineer, so the amazon poster said "I'm an engineer, I expected more"... the book is not positioned for engineers necessarily, but many have used it. > > The user web is access by the same method you use to access the > > administrator web. Simply enter the username and password for the user > you > > want to access. > > OK I will try that. > > Voip.ms works fine with sipXecs. Yes, FXO and FXS is supported, but > not > > from within the server. They need to be standalone gateways - Audio > Codes, > > Patton are a examples. > > > Good. > > > Personally, I'd re-install if the domain name is messed up by using > > yahoo.com. It takes 20 minutes, and it's a good exercise to help learn > the > > system better. > > > OK will do. What do I use for a domain name if (as I think) I have no > domain? > > Either get a domain or use ".loc" or ".local", but also realize using a non-routable domain limits your feature set and a reinstall would have to take place in order to change that if a non-routeable domain were used. > -- > Bob Gailer > 919-636-4239 > Chapel Hill NC > > _______________________________________________ > 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.326.5325 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
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
