I think the question is WHY do you want the sipdomain to be the same as the domain name of your company. Realize its a two-edged sword with XMPP. XMPP with openfire can only be the sipdomain (not an alias). Since most of my customers ahve XMPP service hosted elsewhere, it's more desirable to use a subdomain as the sipdomain. We can always alias the sipdomain (just not the xmpp domain).
On Mon, Apr 2, 2012 at 5:04 PM, Stiles Watson <[email protected]>wrote: > So as an example: > > I want to use the company domain for the sip domain and I want the sip sub > net to be the same as the LAN (192.168.111.xxx), during install, when asked > for the Network settings, I enter > > Hostname: sipx.mycompany.com > IP: 192.168.111.111 (static IP of sipX server) > Netmask: 255.255.255.0 > Gateway: 192.168.111.1 (static LAN IP of my Sonicwall firewall) > > I then select "No - sipx.mycompany.com SHOULD be my DNS server" to > install DNS on the sipX server. > > On the next screen I then enter the IP addresses of two DNS servers on the > Internet. > b > Then when asked if I have a DHCP server on my network, I select "No - > sipx.mycompany.com SHOULD be my DHCP server." Now, for my setup, the > Sonicwall has DHCP running on it but only for static IPs within a specified > range. So after the install, I edit the dhcpd.conf file and change the > range of the DHCP server on sipX so there is no overlap. This allows all > dynaic IPs to be handled by the sipX server. > > I then select, "First Server" > > Then when asked for SIP domain, do I have to enter mycompany.com OR is > entering sipx.mycompany.com expectable? > mycompany.com should already be on the screen automatically when running the setup script. What is required to get where you want is to hit ENTER and not change that to a hostname. > > I then select "Reboot" > > On my first login after reboot, I perform a "yum update," reboot again, > and then begin the sipX config via the web interface. > I always send a profile to the server and make sure stuff works before you update. When you update, you should shutdown sipx services first. Then again, I do not run the install script before I yum... i exit out of the install script and do a yum update, reboot and run the install script after the code is in place so sipx only has to initialize one time. I think it saves time, but not sure it matters. I do think it's cleaner that way. > > Is there anything wrong with this example? > > I think if you are running AD inside, this is a good case of WHY you would use a subdomain, and create a forward zone in bind in sipx to point to the AD domain, and vice versa. > Stiles > > > > On 04/02/2012 04:27 PM, Tony Graziano wrote: > > When you setup sipx, the most reliable way to configure it is: > > sipdomain.tld > and hostname.sipdomain.tld as two different values. > > when a phone registers it should register to > "[email protected]"<[email protected]> > > Ultimately it DOES NOT MATTER where DHCP and DNS come from, so long as > it is accurate and works without delays. For best performance on a single > system and if there are no network reasons "not to", you are best off to > let sipx handle both services or contains sipx services on its own vlan so > it doesn't interfere. I normally use a subdomain for sipx services, but not > always, and that's "my" way of doing it. > > If the phone is registering to the hostname, the phone MWI is to the > domain name and its not answering the challenge for MWI subscription > BECAUSE the subscriber IS [email protected], NOT [email protected]. > > The reality is all of this is a big exhale... it's all in the wiki. > While there are numerous threads, they all point back to the same issue. > DNS. > > This is how I would do i if I were you, but I am not you (since people > tire of my "if it were me..."). > > I do this the same each and every time. I never have registration > issues. I never have MWI issues and I never have issues calling inside to > other subscribers. > > > > On Mon, Apr 2, 2012 at 4:09 PM, Stiles Watson <[email protected]>wrote: > >> On the install of 4.4, I used the hostname and had the installer install >> DHCP and DNS as well. There are no other DNS servers on the network. This >> is why I do not understand why I have to 'fix' my DNS. Isn't sipX supposed >> to config everything correctly on install (assuming I entered the right >> values during setup)? >> >> If using hostname is a valid setup, than why did ext to ext calls not >> work without adding DNS aliases under System>Domain (per Tod's >> instructions). Tony said I should not have to do that, but instead I needed >> to fix my DNS, and, if I understand his last email on this correctly, this >> is why the v-mail indicator LED does not work. But, again, if the install >> set up the DNS config and I made no changes then why is DNS broken? >> >> Right now everything works except the v-mail indicator (I've not >> completed remote phone testing). >> >> So, being willing to do whatever is needed to get sipX up and running, I >> honestly do not care if I use domain or hostname for setup. Can I easily >> switch from using hostname to domain without doing a reinstall? >> >> I'm happy to fix my DNS if someone will help me understand why it was >> broken to begin with being that it is the only DNS server on the network >> and it was using the default config. >> >> Stiles >> >> >> >> On 04/01/2012 06:46 PM, Michael Picher wrote: >> >> You have to pick a method when you setup the system... You either setup >> with a domain or you setup with a host name. if you setup with a domain >> and then try to move to a host name, that's different... >> >> Mike >> >> On Fri, Mar 30, 2012 at 3:04 PM, Stiles Watson <[email protected]>wrote: >> >>> I'll be happy to fix whatever is broken, but please help me understand >>> first. >>> >>> Are you saying that the problem results from my extensions registering >>> as [email protected] instead of [email protected]? >>> >>> In a previous post I was told by someone that if I have no intention of >>> adding additional servers, I can use host.domain.com as the sip domain >>> during install instead of domain.com and this is a perfectly acceptable >>> solution and that this results in basically an A record setup instead of a >>> SRV record setup. Is this not the case? >>> >>> You've mentioned a few time that I need to "Fix my DNS," which I'm very >>> willing to do, but I've also been told that the DNS should be setup >>> correctly on install since I'm installing DNS on the same server during the >>> sipX install. There are no other DNS servers on the network. >>> >>> If I have to go back to [email protected] do I have to do another >>> reinstall or is there another way to switch over? >>> >>> Stiles >>> >>> >>> On 03/30/2012 02:21 PM, Tony Graziano wrote: >>> >>> Its the fact you are registering to the host name instead of the domain. >>> >>> Fix your DNS. >>> On Mar 30, 2012 1:41 PM, "Stiles Watson" <[email protected]> wrote: >>> >>>> I just noticed that since I upgraded sipX to 4.4 and my Polycom IP 335 >>>> phones to firmware 3.2.6 and BootROM 4.2.2, I no longer get a v-mail >>>> notification on the Phones. The message indicator LED does not flash and >>>> there is no indication on the display except "1 new missed call". >>>> >>>> I do not know enough yet to know if the issue is with sipX/Polycom >>>> interoperability or with firmware or with the BootROM. >>>> >>>> Any clues? >>>> >>>> Stiles >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> >>> 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 [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/ >>> >> >> >> >> -- >> Michael Picher, Director of Technical Services >> eZuce, Inc. >> >> 300 Brickstone Square >> >> Suite 201 >> >> Andover, MA. 01810 >> O.978-296-1005 X2015 >> M.207-956-0262 >> @mpicher <http://twitter.com/mpicher> >> www.ezuce.com >> >> >> ------------------------------------------------------------------------------------------------------------ >> There are 10 kinds of people in the world, those who understand binary >> and those who don't. >> >> >> >> _______________________________________________ >> sipx-users mailing [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 > ~~~~~~~~~~~~~~~~~~ > 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].**net<[email protected]> > > Helpdesk Customers: > http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net> > Blog: http://blog.myitdepartment.net > > > _______________________________________________ > sipx-users mailing [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 ~~~~~~~~~~~~~~~~~~ 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/
