Single most important tip for troubleshooting config server
components is inspect log files by searching of running tail
-f
command while servers are running. Unless specified, all log
files go into one of these two locations
/usr/local/sipx/var/log/sipxpbx/
/var/log/sipxpbx/
${JBOSS_HOME}/jboss/log/server.log
- Web page error,
EJB errors. Log file for 90% of configuration system operations${JBOSS_HOME}/server/sipx/conf/log4j.xml
and
change
the debug flag: param name="Threshold" value="DEBUG"
or "INFO"
and restart processes.sipdbtest display credentialYou should see your basic user edits in this list.
install-cert.sh
file. Lastly, check the timestamp of the credentials.xml
file to see if time is after your change.cd `sipx-config --jdk`
bin/keytool -list -keystore jre/lib/security/cacerts -storepass changeit | grep mykey
su - SIPXPBXUSER profilegenerator.shwhere SIPXPBXUSER is the daemon sipX user account (default is 'sipx')
psql -U postgres PDS -c "update users set password='' where display_id = 'superadmin';"
sds.log
for SIP and SIP stack level messages to phone devices. This log
contains SIP messages so you can use the sipviewer to display
graphically the SIP messages.
syslog2siptrace < sds.log > sds-siptrace.xml
sipviewer sds-siptrace.xml
PDSMessages.log
for communication of
user, permission and credential datasets to other sipX servers.bin/profilepublisher.sh
and change the
debug flag: PDS_DEBUG=-Dpds.debug=true
and restart
processses. su - SIPXPBXUSER profilepublisher.shwhere SIPXPBXUSER is the daemon sipX user account (default is 'sipx')
profilewriter.log
bin/profilewriter.sh
and change the
debug flag: PDS_DEBUG=-Dpds.debug=true
and restart
processses su - SIPXPBXUSER profilewriter.shwhere SIPXPBXUSER is the daemon sipX user account (default is 'sipx')
su - SIPXPBXUSER startrmireg.shwhere SIPXPBXUSER is the daemon sipX user account (default is 'sipx'). Personally, I've never seen an error here, but it's worth noting.