realize gateways, recordings and AA settings and such will be lost. This will only culminate in having:
users, phones, user and phone groups, pin's, sip passwords and associated data. However, sending profiles to phones gets you a long way if you are not in production yet. On Mon, Mar 19, 2012 at 3:24 AM, Tony Graziano <[email protected] > wrote: > > > On Mon, Mar 19, 2012 at 2:25 AM, IT Manager <[email protected]>wrote: > >> Hi Dave and Tony,**** >> >> ** ** >> >> Thanks for the info – we are configured against the AD integrated domain >> – so changing this environment is going to be difficult (to put it mildly!). >> **** >> >> ** ** >> >> However, I haven’t rolled out the SIPx server yet to users – but I have >> created the profiles/users/config etc. **** >> >> ** ** >> >> If I am going to rebuild the Sip server is it easiest to do this as >> follows?**** >> >> **· **Reinstall from scratch the SIP Server – allow it to have >> its own DNS Server >> > Yes > >> **** >> >> **· **Give it a sub-domain of sip.mydomain.org with server name >> sipx.sip.mydomain.org and point it’s DNS resolution to our ISP DNS >> > OK > >> **** >> >> **· **Upload my backup from the previous install (or will this >> overwrite the domain settings etc) – or just bite the bullet and reprogram >> from scratch – it is always easier second time round… J >> > No. Do an export and edit it to remove the superadmin user and manually > edit the PIN for the users then import it. > >> **** >> >> **· **When provisioning phones – give them the dns of the SIPX >> server – not my AD one **** >> >> ** ** >> >> Is this my path to success, wealth, prosperity etc…?**** >> >> ** ** >> >> My firewall is an IPFire one which I believe runs dnsmasq (although my AD >> hands out DHCP). It may be that I have to rethink my DHCP strategy as well >> as my AD one. >> > Your windows dhcpd can hand out the DNS server for ALL devices as the > firewall. Just tell the firewall to resolve sip.mydomain.org to the IP > address of the sipx server. > >> **** >> >> ** ** >> >> Laurie**** >> >> ** ** >> >> ** ** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Black, Dave >> (CallPoint Canada) >> *Sent:* 17 March 2012 00:27 >> >> *To:* Discussion list for users of sipXecs software >> *Subject:* Re: [sipx-users] Sipxservices**** >> >> ** ** >> >> As Tony advised, you would probably be best served by separating your >> SipXecs voice domain from AD in the long run, however this doesn’t help you >> out right now unless you are prepared to rebuild either SipXecs or AD >> environments. **** >> >> ** ** >> >> Given that your AD domain controller role and DNS role are residing on >> the same windows machine, and assuming DNS is AD integrated, would be the >> root cause of your start up issues, coupled with SipXecs being configured >> so that it is dependent on AD DNS instead of its own. **** >> >> ** ** >> >> I know this is getting out of the realm of this list, but if SipXecs >> systems are being configured against Windows AD DNS, then a pointer in a >> windows direction won’t hurt.. If a secondary DNS server hosting the AD >> zone is unavailable during a windows domain controller boot, which would be >> the case because of power failure, then AD will crawl at starting up. >> There are a few ways to solve this problem, (assuming your AD forest is in >> good shape), probably the easiest way is to switch your AD integrated DNS >> zone to a standard zone instead of AD integrated. You will lose some of >> the security and replication features which is why most people run a AD >> integrated DNS zone, but your choices are limited given there isn’t a >> secondary site with AD DNS available during boot, other common solutions >> include running a replicated AD domain controller with DNS integrated in a >> secondary site that would remain up during power failures.**** >> >> ** ** >> >> Hope this helps.**** >> >> ** ** >> >> Dave Black **** >> >> ** ** >> >> ** ** >> >> ** ** >> >> *From:* [email protected] >> [mailto:[email protected]] *On Behalf Of *Tony >> Graziano >> *Sent:* March-15-12 6:08 AM >> *To:* Discussion list for users of sipXecs software >> *Subject:* Re: [sipx-users] Sipxservices**** >> >> ** ** >> >> If you had installed sipx on its own domain (preferably subdomain) it can >> have its own DNS and not be involved with that of your AD domain.**** >> >> ** ** >> >> In your case, I think I would have done this AND made sipx the primary >> DNS server for your office by adding a forward zone for your AD domain. I >> prefer to do this at the firewall, because then the phone look to the >> firewall for DNS and forward everything OUT execept the AD domain (goes >> directly to windows server) and the sipx subdomain (goes directly to sipx >> server).**** >> >> ** ** >> >> What are the capabilities of the firewall you have there?**** >> >> On Thu, Mar 15, 2012 at 5:35 AM, IT Manager <[email protected]> >> wrote:**** >> >> Hi Todd,**** >> >> Thanks – we do have an inverter system for the whole office that I am >> trying to get to shutdown things in an orderly fashion – however it hasn’t >> been happening as yet. In the meantime I have tried to set the startup >> delay for the sipx server to be way after the booting of the AD controller >> (DNS machine), but that I am already at 5 minutes delay and it’s still not >> working.**** >> >> Should I try to reconfigure the SIPX server to do it’s own DNS and have >> the phones ignore the AD DNS entirely? Would this fix the issue?**** >> >> Also, I am still learning my way around linux/sipx and so finding logs if >> it’s not in the WebUI could be a problem – can you point me where to look >> and what to look for?**** >> >> Laurie**** >> >> **** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Todd Hodgen >> *Sent:* 15 March 2012 09:21 >> *To:* 'Discussion list for users of sipXecs software' >> *Subject:* Re: [sipx-users] Sipxservices**** >> >> **** >> >> Have you considered a UPS product that has orderly shutdown capability? >> There are some that will do controlled shutdown and startup of select >> devices and in your selected order. You could have it turn up your DNS >> services first, with sipXecs system coming back online after a selected >> timeframe, then followed by your POE switches that feed phones.**** >> >> **** >> >> A detailed review of the logs after a power failure should help >> understand what is failing.**** >> >> **** >> >> *From:* [email protected] >> [mailto:[email protected]] *On Behalf Of *IT Manager >> *Sent:* Wednesday, March 14, 2012 11:10 PM >> *To:* [email protected] >> *Subject:* [sipx-users] Sipxservices**** >> >> **** >> >> Dear All,**** >> >> **** >> >> I am struggling with something and am not sure of the method to fix it. * >> *** >> >> **** >> >> Bit of background first: We are in Africa and so the power situation here >> is not great – we do have battery backup power, but it doesn’t last long >> enough to keep systems running throughout the night. So basically every >> time the backup fails, everything crashes. Then when power is restored all >> the servers boot up again and most things start up ok. This brings me to >> the problem I am having with SIPX.**** >> >> **** >> >> It starts up fine and looking at the services it seems that everything is >> running OK. However, none of the phones (GXP2000) or soft phone (Xlite) >> will register with the system. If I restart all the services then things go >> back to normal and the registrations work just fine.**** >> >> **** >> >> I *think* that the problem lies with the DNS: Because my AD DNS servers >> take quite a while to start up, I think that the SIPX server starts faster >> than them. In some way this causes something to fail in the SIP server. >> What exactly that is I don’t know and am not sure where to look.**** >> >> **** >> >> Any thoughts as to where to look or possible solutions to the situation?* >> *** >> >> **** >> >> Laurie**** >> >> **** >> >> PS this is one of the reasons I can’t roll it out to the office yet - if >> I have to manually reset it every time power returns.**** >> >> **** >> >> **** >> >> [image: Description: D:\Shared Documents\MAF\MAF Art\5X-FRM-sig.jpg]**** >> >> Laurie Nason**** >> >> IT Manager**** >> >> Mission Aviation Fellowship Uganda**** >> >> [image: Description: D:\Shared Documents\MAF\MAF Art\International MAF >> Logo - White-sig.png]**** >> >> Online Info: www.maf-uganda.org **** >> >> **** >> >> >> _______________________________________________ >> 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 >> ~~~~~~~~~~~~~~~~~~ >> Linked-In Profile: >> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> Ask about our Internet Fax services! >> ~~~~~~~~~~~~~~~~~~**** >> >> ** ** >> >> LAN/Telephony/Security and Control Systems Helpdesk:**** >> >> Telephone: 434.984.8426**** >> >> sip: [email protected]**** >> >> ** ** >> >> Helpdesk Customers: http://myhelp.myitdepartment.net**** >> >> Blog: http://blog.myitdepartment.net**** >> >> _______________________________________________ >> 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 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~ > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
<<image001.jpg>>
<<image002.png>>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
