Hi Josh, Thank you for your analysis. Few days ago, I notice buffer overflow in log. I already closed port 5060 from outside world, only accessible from LAN and VPN connection only.
R Afifi On Mon, May 2, 2011 at 10:17 PM, Josh M. Patten <[email protected]>wrote: > What you are seeing is likely related to a bug in sipXproxy that would > basically cause all requests to be ignored if a buffer overflow occurred (I > think?) which would seem like a system outage, but was actually not. Next > time this happens try restarting JUST the SIP proxy service. If this fixes > the issue upgrading to 4.4 should help resolve the issue. > > > > From my analysis this usually occurs during a DoS attack. Do you have/need > port 5060 open to the outside world? > > > > Josh Patten > > Brazos County Network Engineer > > 979.361.4676 > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Rachmat Afifi > *Sent:* Sunday, May 01, 2011 8:40 AM > *To:* Discussion list for users of sipXecs software > *Subject:* Re: [sipx-users] Services are stopping and not responding after > few days > > > > Hi Todd, > > Thank you for your input. I notice that I'm not able to call to office > (calling to PSTN number) - AutoAttendant is not responding. The sipXecs > connected with Mediant1000 (6 analog lines). > > I'll do your suggestion first before restarting all services. > > Thanks for your input. > > On Sun, May 1, 2011 at 3:09 PM, Todd Hodgen <[email protected]> wrote: > > Before restarting all services, try to determine if it is just incoming > calls, or all calls. Try calling auto attendant or voicemail. Are you > using the Internal Bridge? If so, I’d try restarting SIP trunks first to > see if you have failed trunks, rather than a failed PBX. > > > > If restarting SIP trunks resolves the issue, I would look at your ITSP > provider and its compatibility with the sipXbridge and the associated > configuration. > > > > There is information on the wiki – http://wiki.sipfoundry.org > > > > I’d do a logrotate (found on wiki) when it is failed, then try a call that > is failing. From the Command line, in var/log/sipxpbx I’d run > merge-logs. Then, open merged.xlm from /var/log/sipxpbx. There is a > sipviewer that can be downloaded – info on the wiki. This viewer will > allow you to look at the sip messaging for the failed call, and will > probably direct you to where the issue is. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Rachmat Afifi > *Sent:* Sunday, May 01, 2011 1:00 AM > *To:* [email protected] > *Subject:* [sipx-users] Services are stopping and not responding after few > days > > > > Dear all, > > Sometimes (2 times now with 7-10 days range interval) I have to restart ALL > services under System/Server using web based interface because when I try to > call to our office PSTN number, I do not have response from Auto Attendant. > After I restart it, it working normally. > > Which log file that I should take a look in sipXecs 4.2.1 ? > > Sincerely, > > R Afifi > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1209 / Virus Database: 1500/3607 - Release Date: 04/30/11 > > > _______________________________________________ > 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/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
