If your development sipX system starts to mysteriously malfunction, here
are a couple of things to try:
Symptom: Almost none of the services start.
Problem: Your primary location isn't set correctly.
Fix:
$ psql -U postgres SIPXCONFIG
Welcome to psql 8.2.11, 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=# update "location" set primary_location = true where name =
'Primary';
UPDATE 1
SIPXCONFIG=# \q
$
Symptom: Proxy won't start. Servers display says that it is because
sipXrelay is not running.
Problem: For some reason sipX is set to not start sipXrelay.
Fix:
$ /usr/bin/sipxproc --start SipXrelay
{"SipXrelay"=>true}
$ /usr/bin/sipxproc
{"FreeSWITCH"=>"Disabled",
"SIPRegistrar"=>"Running",
"ParkServer"=>"Running",
"CallResolver"=>"Running",
"ACDServer"=>"Running",
"SIPStatus"=>"Running",
"ConfigServer"=>"Running",
"CallResolver-Agent"=>"Disabled",
"SipXbridge"=>"Disabled",
"MediaServer"=>"Running",
"sipXivr"=>"Running",
"PageServer"=>"Running",
"PresenceServer"=>"Running",
"ResourceListServer"=>"Running",
"SipXrelay"=>"Running", <-----------------------
"SIPXProxy"=>"Running"}
$
Not that these are guaranteed to work, but they seem to have gotten my
system going. Of course, they might fail and you'll have to drop your
database and reconfigure everything by hand.
Dale
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
