After changing the IP address on the config page, you always need to Send
Profiles as that generates the config files used by all of the processes.

You may have entered the IP address as an alias of the domain.  If so, you
need to change it also on the System / Domain page.  After making a change
on this page, you again will need to Send Profiles and restart services.

 SIPXCONFIG is a normalized database so the IP address is only stored in the
location table.  All other tables that might need the IP address link to the
location table using the location_id column.  

The CDR records are also stored in the instance of postgres in the database
SIPXCDR.  The IP address is an element of the call_id column, and would also
be found in the caller_contact and callee_contact columns if using SIP
Trunking.  So using grep is not going to provide valid results.

Are there functions that are not working after sending the Server profiles
and restarting the services?  If not, which ones are not working?  That is
what is the most import issue.  

As for pgadmin, you can install and use that tool.  However, you will need
to modify the postgres security file to allow access to the database from a
system other than the local host.  If you do not have experience with that,
I would research thoroughly
(http://www.postgresql.org/docs/7/static/security.htm) so you don't break a
working system.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Tuesday, January 11, 2011 6:43 PM
To: sipx-users
Subject: Re: [sipx-users] Changing IP of a live server

> psql U postgres d SIPXCONFIG

# psql -U postgres -d SIPXCONFIG
Welcome to psql 8.1.22, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help with psql commands
       \g or terminate with semicolon to execute query
       \q to quit

SIPXCONFIG=# select location_id, name, ip_address from location;
 location_id |      name      |  ip_address
-------------+----------------+--------------
           1 | Primary server | 172.16.60.20
(1 row)

SIPXCONFIG=# Enter \q to exit psql
\q: extra argument "to" ignored
\q: extra argument "exit" ignored
\q: extra argument "psql" ignored

> This IP address is managed on the Server / (select Server) / Configure
page
> which a previous post had noted as a step.   If you executed that step,
the
> database should be correct.

I did this the day I changed the IP on the server.

> Did you Send Profiles after changing the IP address through that page?

No, I didn't do that. I only changed the IP and restarted the services which
I thought would amount to the same thing.

> looked back at previous posts and that is the one step that I did not 
> see included in that post.  Sending Profile for the server generates 
> new config files.  You will be required to restart services after sending
profiles.

Not sure if it's too late now but ran this. 
 
> We have also found that you may need to reboot the server instead of 
> just restarting services.

Rebooted, old IP still in db files.


_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to