Child pages
  • Changing the SIP Domain Name for Sipxcom in Release 17.04

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Step 4 - Convert FQDN in Mongo from to


Go into Mongo and issue the following commands - upon completion, exit Mongo and restart the Sipxcom server:

  • Issue Mongo command
  • Issue rs.config() command - you will notice that host name is still
  • Issue the cfg = rs.config() command - which copies the database parameters into a variable
  • Issue the cfg.members[0].host = "" command which changes the voice FQDN host name to in Mongo

  • Issue the "rs.reconfig(cfg,{force:true})" command to apply the new host name to Mongo

  • Issue the rs.config() command again to ascertain the new host name has been applied in Mongo

  • Issue the exit command from Mongo and then restart the Sipxcom server

Step 5 - Check Intranet Domain Field in the Internet Calling Menu

Go to the System→Internet Calling or System->Settings→Internet Calling menu, and if necessary, update the Intranet Domain field with the new domain.

Image Added

Step 6 - Push Sipxcom Server Processes and Validate All Processes are Running

Push the server profile which copies all configuration data from the SQL server into Mongo. Check to ascertain all server processes are running.



7 - Rebuild Phone Profiles and Restart Phones

The phones registered to the Sipxcom voice server currently use as the SIP domain - push all phone profiles which rebuilds the configuration files on the Sipxcom TFTP directory. The phones will need to be manually restarted to pick up the new configuration files and register to the voice server with SIP domain



8 - Test Incoming, Outgoing Calls, Voicemails, Autoattendants, etc

Test a variety of internal and external calls, call forwards, voicemail, autoattendants to ascertain all calls are working properly. If bearer path fails to appear on some calls (e.g. voicemail announcements), and you are testing with a new voice server, then pay attention to your NAT traversal settings:

  • If this is a new system and Sipxbridge is used,for external calls, ascertain the NAT Traversal type is set to IP address, and Public IP address is set to the IP address assigned to the WAN router, assuming Sipxcom is behind a firewall.
  • If this is a new system and unmanaged gateways are used for external calls, then pay attention to the following settings, particularly if voicemail or autoattendant announcements disappear after 30-60 seconds (assume Sipxcom and gateway is behind a firewall):
    • NAT public IP address should be configured to be the Sipxcom private IP address.
    • The Enable NAT traversal and Server behind NAT settings should be disabled.