Ok so the system uptime reset it again and the call log also cleared... The
system did not show any sign of a crash. the only thing I notice in the logs
is this:
Sep 29 22:23:46 pbx daemon.info ntpd[2370]: synchronized to LOCAL(0),
stratum 5
Sep 29 22:23:46 pbx daemon.notice ntpd[2370]: kernel time sync status change
0001
Sep 29 22:23:46 pbx user.warn kernel: set_rtc_mmss: can't update from 5 to
53
Sep 29 22:23:53 pbx user.warn kernel: set_rtc_mmss: can't update from 5 to
53
Sep 29 22:23:56 pbx user.warn kernel: set_rtc_mmss: can't update from 5 to
53
Sep 29 22:24:03 pbx user.warn kernel: set_rtc_mmss: can't update from 5 to
54
Sep 29 22:24:13 pbx user.warn kernel: set_rtc_mmss: can't update from 5 to
54
Sep 29 22:24:23 pbx user.warn kernel: set_rtc_mmss: can't update from 5 to
54
Sep 29 22:24:33 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
54
Sep 29 22:24:43 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
54
Sep 29 22:24:50 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
54
Sep 29 22:24:52 pbx daemon.info ntpd[2370]: synchronized to 70.86.250.6,
stratum 2
Sep 29 22:24:53 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
54
Sep 29 22:25:00 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
55
Sep 29 22:25:10 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
55
Sep 29 22:25:20 pbx user.warn kernel: set_rtc_mmss: can't update from 6 to
55
Sep 29 22:25:30 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
55
Sep 29 22:25:40 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
55
Sep 29 22:25:47 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
55
Sep 29 22:25:50 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
55
Sep 29 22:25:57 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
55
Sep 29 22:26:07 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
56
Sep 29 22:26:17 pbx user.warn kernel: set_rtc_mmss: can't update from 7 to
56
Sep 29 22:26:27 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
56
Sep 29 22:26:37 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
56
Sep 29 22:26:44 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
56
Sep 29 22:26:47 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
56
Sep 29 22:26:54 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
56
Sep 29 22:27:04 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
57
Sep 29 22:27:14 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
57
Sep 29 22:27:24 pbx user.warn kernel: set_rtc_mmss: can't update from 8 to
57
Sep 29 22:27:34 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
57
Sep 29 22:27:41 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
57
Sep 29 22:27:44 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
57
Sep 29 22:27:51 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
57
Sep 29 22:28:01 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
58
Sep 29 22:28:11 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
58
Sep 29 22:28:21 pbx user.warn kernel: set_rtc_mmss: can't update from 9 to
58
Sep 29 22:28:31 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
58
Sep 29 22:28:38 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
58
Sep 29 22:28:41 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
58
Sep 29 22:28:48 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
58
Sep 29 22:28:58 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
58
Sep 29 22:29:08 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
59
Sep 29 22:29:18 pbx user.warn kernel: set_rtc_mmss: can't update from 10 to
59
Sep 29 22:29:28 pbx user.warn kernel: set_rtc_mmss: can't update from 11 to
59
Sep 29 22:29:35 pbx user.warn kernel: set_rtc_mmss: can't update from 11 to
59
Sep 29 22:29:38 pbx user.warn kernel: set_rtc_mmss: can't update from 11 to
59
Sep 29 22:29:45 pbx user.warn kernel: set_rtc_mmss: can't update from 11 to
59
Sep 29 22:29:55 pbx user.warn kernel: set_rtc_mmss: can't update from 11 to
59
Sep 29 22:39:51 pbx daemon.notice ntpd[2370]: time reset +0.136490 s
Sep 29 22:43:09 pbx daemon.info ntpd[2370]: synchronized to LOCAL(0),
stratum 5
Sep 29 22:45:19 pbx daemon.info ntpd[2370]: synchronized to 70.86.250.6,
stratum 2
What can be causing this?
On Thu, Sep 29, 2011 at 3:46 PM, Fernando Fuentes
<digitaldis...@gmail.com>wrote:
> Michael,
>
> Please email me directly with details please.
> I am interested.
>
> Thank You.
>
>
> On Thu, Sep 29, 2011 at 2:32 PM, Michael Graves <mgra...@mstvp.com> wrote:
>
>> I have a Portech MV 370 gsm to sip gateway that I'd be happy to sell.
>>
>> Sent from T-Mobile G2 with Google
>>
>> Michael Keuter <li...@mksolutions.info> wrote:
>>
>> >Am 29.09.2011 um 19:08 schrieb David Kerr:
>> >>
>> >> Interesting. This would be a way to provided for emergency backup
>> should your regular network connection go down (like happened to me a few
>> weeks ago when Hurricane (or was it Tropical Storm) Irene came through the
>> northeast.) The box is pretty cheap too.
>> >>
>> >> The real question is whether GSMopen module can be made to work with
>> Astlinux. Someone would need to take a look and try to build it. Would
>> depend greatly on what dependencies it has on other packages.
>> >>
>> >> David
>> >>
>> >>
>> >> On Thu, Sep 29, 2011 at 7:49 AM, Geoff Bowditch <
>> geoff.bowdi...@gmail.com> wrote:
>> >> I was looking for a GSM gateway to attach to Astlinux. Has anyone
>> successfully used a Mobigater with Astlinux?
>> >>
>> >> Looks like is uses USB interface and gsmopen module.
>> >>
>> >> Regards,
>> >> geoff
>> >
>> >David,
>> >
>> >it doesn't look very good, found that:
>> >
>> >http://www.gsmopen.org/node/117#comment-427
>> >
>> >http://www.gsmopen.org/celliax_for_asterisk
>> >
>> >Michael
>> >
>> >http://www.mksolutions.info
>> >
>> >
>> >
>> >
>> >
>>
>> >------------------------------------------------------------------------------
>> >All the data continuously generated in your IT infrastructure contains a
>> >definitive record of customers, application performance, security
>> >threats, fraudulent activity and more. Splunk takes this data and makes
>> >sense of it. Business sense. IT sense. Common sense.
>> >http://p.sf.net/sfu/splunk-d2dcopy1
>> >_______________________________________________
>> >Astlinux-users mailing list
>> >Astlinux-users@lists.sourceforge.net
>> >https://lists.sourceforge.net/lists/listinfo/astlinux-users
>> >
>> >Donations to support AstLinux are graciously accepted via PayPal to
>> pay...@krisk.org.
>> >
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> _______________________________________________
>> Astlinux-users mailing list
>> Astlinux-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to
>> pay...@krisk.org.
>>
>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
