On Mon, Feb 14, 2011 at 10:39:20PM -0500, Jeff LaCoursiere wrote:
>
> Now this is what I call uptime...
>
> minipbx*CLI> show uptime
> System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
> Last reload: 8 hours, 3 minutes, 51 seconds
>
> Bizarre bug?
Hi. I see that 41 year
On Tue, 15 Feb 2011, Hans Witvliet wrote:
On Tue, 2011-02-15 at 09:01 +, Steve Howes wrote:
On 15 Feb 2011, at 03:39, Jeff LaCoursiere wrote:
minipbx*CLI> show uptime
System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
Last reload: 8 hours, 3 minutes, 51 seconds
Wha
On Tue, 2011-02-15 at 09:01 +, Steve Howes wrote:
> On 15 Feb 2011, at 03:39, Jeff LaCoursiere wrote:
> > minipbx*CLI> show uptime
> > System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
> > Last reload: 8 hours, 3 minutes, 51 seconds
>
> What's the highest current 'genui
On Tuesday 15 February 2011 12:13:37 Jeff LaCoursiere wrote:
> On Tue, 15 Feb 2011, A J Stiles wrote:
> > On Tuesday 15 Feb 2011, Jeff LaCoursiere wrote:
> >> Now this is what I call uptime...
> >>
> >> minipbx*CLI> show uptime
> >> System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46
On Tue, 15 Feb 2011, A J Stiles wrote:
On Tuesday 15 Feb 2011, Jeff LaCoursiere wrote:
Now this is what I call uptime...
minipbx*CLI> show uptime
System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
Last reload: 8 hours, 3 minutes, 51 seconds
Bizarre bug?
I'm guessting
On 15 Feb 2011, at 03:39, Jeff LaCoursiere wrote:
> minipbx*CLI> show uptime
> System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
> Last reload: 8 hours, 3 minutes, 51 seconds
What's the highest current 'genuine' one on-list?..
klein*CLI> core show uptime
System uptime: 2 y
On Tue, 2011-02-15 at 05:57 +, A J Stiles wrote:
> On Tuesday 15 Feb 2011, Jeff LaCoursiere wrote:
> > Now this is what I call uptime...
> >
> > minipbx*CLI> show uptime
> > System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
> > Last reload: 8 hours, 3 minutes, 51 seconds
On Tuesday 15 Feb 2011, Jeff LaCoursiere wrote:
> Now this is what I call uptime...
>
> minipbx*CLI> show uptime
> System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
> Last reload: 8 hours, 3 minutes, 51 seconds
>
> Bizarre bug?
I'm guessting, this is a brand new machine on
Subject: [asterisk-users] uptime
>
>
> Now this is what I call uptime...
>
> minipbx*CLI> show uptime
> System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46
> seconds
> Last reload: 8 hours, 3 minutes, 51 seconds
>
> Bizarre bug?
>
> roo
Now this is what I call uptime...
minipbx*CLI> show uptime
System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds
Last reload: 8 hours, 3 minutes, 51 seconds
Bizarre bug?
root@minipbx:~# asterisk -V
Asterisk 1.4.37
root@minipbx:~# uname -a
Linux minipbx 2.6.32-dockstar #2 Th
I know there has been better uptime than this reported, but I figured
I'll share it anyhow:
@pbx:~# uptime
18:39:07 up 621 days, 9:40, 2 users, load average: 0.00, 0.00, 0.00
pbx:~# cat /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 10
mo
Can someone point me to an agi script that will read back the asterisk
uptime, if such a thing exists?
- Mike
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
There aren't a lot of phones. There are 50-60 SIP phones and SIP
connections to two Cisco PRI gateways. About 10,000 calls / month and
about 15,000 mins of LD/month. I know when I started with *, I head how
it had to be restarted every week and ours just ran and ran.
Justin Tunney wrote:
On 8/26/06, Peder @ NetworkOblivion <[EMAIL PROTECTED]> wrote:
Who says * isn't stable enough for prime time? At least it is on 1.0.3.
What kind of abuse does that box take?
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-use
Our MOH died, so I finally had to kill my * process and restart it.
Interestingly, "stop now" didn't work. I had to kill the process. It
used to work, but it had been up so long that it must have gotten
corrupted somehow. Here is the "show uptime" before I killed it:
Asterisk-A*CLI> show up
inal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Blair
Sent: Tuesday, February 15, 2005 3:49 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Uptime/reliability with SER, Asterisk
Matthew:
2 SER to 2 Asterisk (primary
How do you implement failover?
Thanks
robert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Blair
Sent: Tuesday, February 15, 2005 3:49 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Uptime/reliability
t;[EMAIL PROTECTED]>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
Sent: Tuesday, February 15, 2005 2:48 PM
Subject: Re: [Asterisk-Users] Uptime/reliability with SER, Asterisk
Matthew:
2 SER to 2 Asterisk (primary and secondary for each application) with
3 PSTN gat
gt; >do agents and queues? If so, how do you handle that across multiple *
boxes?
> >
> >THanks,
> >Matthew
> >
> >- Original Message -
> >From: "Steve Blair" <[EMAIL PROTECTED]>
> >To: "Dana Olson" <[EMAIL PROTECTED]>;
AIL PROTECTED]>
To: "Dana Olson" <[EMAIL PROTECTED]>; "Asterisk Users Mailing List -
Non-Commercial Discussion"
Sent: Monday, February 14, 2005 12:27 PM
Subject: Re: [Asterisk-Users] Uptime/reliability with SER, Asterisk
Our SER/Asterisk implementation is extremely
[EMAIL PROTECTED]>; "Asterisk Users Mailing List -
Non-Commercial Discussion"
Sent: Monday, February 14, 2005 12:27 PM
Subject: Re: [Asterisk-Users] Uptime/reliability with SER, Asterisk
>
> Our SER/Asterisk implementation is extremely stable if you define
> stable as the
I really appreciate your reply.
For Asterisk, are you using G729 as your codec, or something more
high-bandwidth (ulaw)?
Is there any definition of stable that you would use that would point
to SER and Asterisk not being "stable"?
Again, thanks for your reply.
--
Dana
On Mon, 14 Feb 2005 13:
Our SER/Asterisk implementation is extremely stable if you define
stable as the ability to deliver a set of features without either
application
crashing. We are a production environment with 75 users total. Asterisk is
only used for voicemail. The only issue we have is that the audio
(greeting or
Could anyone shed any light on how SER and/or Asterisk (stable branch)
has held up for them in that last while?
Are you using SER and/or * in a production environment? Do you ever
restart the software or reboot the system? How many users are
utilizing the system? How many calls per day/concurrentl
24 matches
Mail list logo
