ClearFoundation

Yes, thank you, this is the right decision. I managed to get access to the control system

But my joy was short. Now I have a problem with the administrator password. How to enter it again? I found the tips on (forum.sipfoundry.org) but apparently there is no overlap in the version of the program.

In order to reset the superadmin password, stop sipxecs:

"/etc/init.d/sipxecs stop"

Then su - to the sipxchange user:

"su - sipxchange"

Run the following command:

"sipxconfig.sh --database reset-superadmin"

Then, exit out of the sipxchange account by typing:

"exit"

Now, access the sipxconfig web interface and use superadmin as the username and leave the password field blank.

Access the superadmin's user properties and set the password.

I hope that helps!

Alex
--
I live to serve

Thank you all turned out. (-:
I've read, there is a problem when the server has more than one interface. this is so?

SipXecs does prefer only one interface. If there are multiple interfaces, it prefers to use eth0. However, it is possible to get it working on eth1, for example,

I've found that if all of the files in the /etc/sipxpbx directory that contain the server's IP address (there are 19) have the same IP address that appears in the sipxconfig interface under "System - Servers," it will work. So for example, if under "System - Servers" my server has an IP address of 192.168.55.10 but the files in the /etc/sipxpbx directory have an IP address of 10.2.2.11 (which probably came from my initial setup), I can change the IP address in those files to 192.168.55.10 by using the sed command. Here's an example of changing the necessary files in that directory:

First stop sipxecs:

/etc/init.d/sipxecs stop

cd /etc/sipxpbx

Change the files:

sed -i 's/10.2.2.11/192.168.55.10/g' callresolver-config
sed -i 's/10.2.2.11/192.168.55.10/g' domain-config
sed -i 's/10.2.2.11/192.168.55.10/g' fallbackrules.xml
sed -i 's/10.2.2.11/192.168.55.10/g' forwardingrules.xml
sed -i 's/10.2.2.11/192.168.55.10/g' freeswitch/conf/dialplan/sipX_context.xml
sed -i 's/10.2.2.11/192.168.55.10/g' mappingrules.xml
sed -i 's/10.2.2.11/192.168.55.10/g' nattraversalrules.xml
sed -i 's/10.2.2.11/192.168.55.10/g' registrar-config
sed -i 's/10.2.2.11/192.168.55.10/g' sipxbridge.xml
sed -i 's/10.2.2.11/192.168.55.10/g' sipxconfig-netif
sed -i 's/10.2.2.11/192.168.55.10/g' sipxopenfire.xml
sed -i 's/10.2.2.11/192.168.55.10/g' sipxpage.properties
sed -i 's/10.2.2.11/192.168.55.10/g' sipxpark-config
sed -i 's/10.2.2.11/192.168.55.10/g' sipxpresence-config
sed -i 's/10.2.2.11/192.168.55.10/g' sipXproxy-config
sed -i 's/10.2.2.11/192.168.55.10/g' sipxrest-config.xml
sed -i 's/10.2.2.11/192.168.55.10/g' sipxrls-config
sed -i 's/10.2.2.11/192.168.55.10/g' sipxsaa-config
sed -i 's/10.2.2.11/192.168.55.10/g' status-config

Make sure your DNS mappings point to the proper IP address also!

Then, you should start sipxecs.

Now, when you check the services of the server under "System - Server" everything should be running.

Please be advised that this has worked for me in my test environments but it has not been tested long-term in a production environment. I make no guarantees that this will always work perfectly for you or anyone.

Hello,
Trying to put Sipxecs. This is that i get when i go to 192.168.1.3:8443/sipxconfig

HTTP ERROR: 404

/sipxconfig Not Found

RequestURI=/sipxconfig

Powered by Jetty://



Any help?

FYI we got SOGo and A website running on the server too.

ports are
9433
9080

Kris, I'm sorry for not responding to your posts sooner. Did you get this worked out?