Hi, nothing strange in the relay logs.
Also with your suggested startup order i cannot reproduce the problem. I created a workarround by setting the startupsequence of sipxbridge from 85 to 99 to start last in sequence. That works for now but i do not now if this is safe to do. Any idea? GJ -----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens Douglas Hubler Verzonden: woensdag 5 december 2012 15:45 Aan: Discussion list for users of sipXecs software Onderwerp: Re: [sipx-users] sipxecs 4.6 - sipxbridge requires manual restart after each server reboot. > On Tue, Dec 4, 2012 at 6:04 PM, glomos-info <[email protected]> wrote: >> 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. I wonder if it's the start sequence with the relay service. Can you check relay logs? Also, maybe check scenario where you restart services in this order to try to reproduce the error stop sipxbridge stop sipxproxy stop sipxrelay start sipxbridge start sipxrelay start sipxproxy _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
