David, thank you! I just thought that CDR implementation is part of the Astlinux project. It is difficult for me to isolate where each part comes from as I never installed asterisk alone, only as part of specific distro (a...@h, Trixbox, then Astlinux 1.2.xx for a year or two).
And regarding internal CID in outgoing CDR records - I see it working fine on my existent Astlinux box, thats why I'm asking. Though I never used GUI before and did all configurations by hand... Will keep trying, thanx anyway! --- Best Regards, Dmitry On Fri, 2009-09-18 at 08:52 -0400, David Kerr wrote: > Dmitry, > You may be better served by asking these in a more general asterisk > list/forum. Anyway, check your cdr.conf file and look for... > > > usegmtime=no ; log date/time in GMT. Default is "no" > > > make sure it doesn't say 'yes' > > > For CID on outboud calls, normally this would get set to the CID used > on the selected trunk. Again, you may have to configure this > somewhere, but I don't recall exactly where. > > > David > > On Fri, Sep 18, 2009 at 6:09 AM, Dmitry Komarov <d...@dmit.lv> wrote: > Hello, > > I have two strange behaviors with Astlinux built-in CDR (the > same > applies to Asterisk GUI CDR menu). > > First, I have properly configured system-wide timezone > settings: > > TIMEZONE: Europe/Riga > TZ_TIMEZONE: EET-2EEST-3 > > Which actually means GMT+2 timezone and the system time is > absolutely > correct now. But all the records in CDR appear with wrong time > (-2 > hours) as if it's shown in GMT. Looks like CDR does not take > timezone > settings into account?.. > > > Secondly, when a call is made from internal extension out of > external > trunk the CID Name and CID Num fields in CDR are empty while > Extension > fields show correct dialed numbers. > > Not sure if it matters, but I don't use "OutBound CID" > settings in User > Extensions within Asterisk GUI as it should be assigned > depending on the > outgoing trunk (which works properly). > > --- > Best Regards, > Dmitry > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference > in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to > market and stay > ahead of the curve. Join us from November 9-12, 2009. > Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > 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. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ 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. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ 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.
