glomos-info
2012-12-04 20:04:50 UTC
Hi,
We are running sipx 4.6 in a test environment to evaluate for production purposes.
The systems works ok but we encounter a strange problem, that after a server reboot the sipxbridge service does not allow external calls go out over our siptrunk and incoming calls are bounced with an 'internal server error'.
The sipxbridge log does not show strange entries and the sipxbridge service seems to be running.
However without changing any settings a simple '/etc/init.d/sipxbridge restart' will fix this problem in a few seconds.
What could be wrong?
We use centos 6 with latest updates, also sipxecs 4.6 fully updated.
Gerrit-Jan Dijkstra
Glomos BV
We are running sipx 4.6 in a test environment to evaluate for production purposes.
The systems works ok but we encounter a strange problem, that after a server reboot the sipxbridge service does not allow external calls go out over our siptrunk and incoming calls are bounced with an 'internal server error'.
The sipxbridge log does not show strange entries and the sipxbridge service seems to be running.
However without changing any settings a simple '/etc/init.d/sipxbridge restart' will fix this problem in a few seconds.
What could be wrong?
We use centos 6 with latest updates, also sipxecs 4.6 fully updated.
Gerrit-Jan Dijkstra
Glomos BV