Thanks, i realize that tracing when it is not working probably would be the best. But like i said, i restarted the services and it all works perfectly now without any change in config. Sorry, that is why i am sceptic about registration being the problem.
Checked top, low load, no process taking much cpu. Sendmail pops up sometimes 2-3% cpu...shouldn't be a problem. Nothing in dmesg, messages or anywhere else. Starting sipxpbx service is without errors. Services in gui looking good. So, what you are saying: Next time it suddenly fails...trace a call before restarting. I'll try to do that. The other "errors" i had in my snippets are no problem then i gather. There is nothing in the CDR logs from the time when "nothing" worked and there was no ring trying to call another station. I have to play it safe, maybe a cron job to restart the machine every night....or something. I'll trace next time it doesn't work. More ideas? Thank you! //Ola The call trace should generate an XML file, which can be attached. The XML file can be viewed by running sipviewer on a separate machine and opening the file. You have only provided snippets. > > http://sipxecs.sipfoundry.org/temp/sipXecs/sipviewer-install.jar > > Ensure the phone is registered in sipxconfig. Check your running > system for anything unusual via 'top'. Make sure the system passes > preflight tests. When viewing the server processes from sipxconfig, is > any service showing a problem? When you call from one station to the > other does the other end ring? Does the attempt show in the CDR logs? > > A call trace would be helpful. > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
