I see. I guess to be honest, other than some basic things, we've not had any 
problems with sipx in a while so tend to forget the steps when something does 
go wrong.

Still, what could have caused this, has anyone seen anything like it?


On Tue, 29 Jun 2010 21:26:17 -0400, Tony Graziano wrote:
> Yes, well creating a snapshot before restarting services (or right after)
> and including the time period helps bunches (but not if you are running
> 4.0.x as opposed to 4.2.x).
> 
> On Tue, Jun 29, 2010 at 10:27 PM, m...@grounded.net <m...@grounded.net> 
> wrote:
>> Do you mean just jumping and restarting things? Problem is that in a
>> production system, one doesn't often have the luxury of time and the only
>> immediate concern is to get the system back up.
>> 
>> The irony is that just this morning, we had a meeting with a company that
>> is interested in outsourcing IT for it's customer base, including managed
>> phone systems. So of course we were telling them about sipx. Then later
>> in the afternoon, using the system for a conference call with another
>> company, talking about the virtues of VoIP then having this happen is
>> pretty nerve wracking.
>> 
>> Just funny timing that's all.
>> 
>> Mike
>> 
>> 
>> On Tue, 29 Jun 2010 19:00:24 -0400, Tony Graziano wrote:
>>> Not a bump, just not an immediate reply.
>>> 
>>> If a knee-jerk reaction is to restart a service, how can any tool or
>>> logging
>>> help? The snapshot tool, not perfect, can do a lot but "any" tool is
>>> more
>>> powerful if you use it before throwing a hammer at it.
>>> 
>>> I think there are jira issues and improvement requests that actually
>>> address
>>> this.
>>> 
>>> I see no bump except the one caused by the throwing of hammers. My kids
>>> told
>>> me there is a screen in mario bros. With throwing hammers...
>>> ============================
>>> Tony Graziano, Manager
>>> Telephone: 434.984.8430
>>> Fax: 434.984.8431
>>> 
>>> Email: tgrazi...@myitdepartment.net
>>> 
>>> LAN/Telephony/Security and Control Systems Helpdesk:
>>> Telephone: 434.984.8426
>>> Fax: 434.984.8427
>>> 
>>> Helpdesk Contract Customers:
>>> http://www.myitdepartment.net/gethelp/
>>> 
>>> ----- Original Message -----
>>> From: sipx-users-boun...@list.sipfoundry.org
>>> <sipx-users-boun...@list.sipfoundry.org>
>>> To: m...@grounded.net <m...@grounded.net> sipx-users
>>> <sipx-users@list.sipfoundry.org>
>>> Sent: Tue Jun 29 18:40:01 2010
>>> Subject: Re: [sipx-users] All phones expired after conf call
>>> 
>>> bump!
>>> 
>>>> Boy, if there's one suggestion I could make for a next version it
>>>> would be
>>>> powerful problem solving functions instead of having to read logs, log
>>>> this, that, run them through this that :). Some good testing tools to
>>>> help
>>>> find problems FAST would be a fantastic feature.
>>>> 
>>>> Mike
>>>> 
>>> 
>>> _______________________________________________
>>> 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/
>>> 
>> 
>> _______________________________________________
>> 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/


_______________________________________________
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/

Reply via email to