Re: access log format

Hi,

Yes, as mentioned previously we need to parse these records to get them
to the db. Over which we can then send various queries.

Guillaume Cottenceau wrote:

Alok Vaidya <alok 'at' routesms.com> writes:

Hi,

Sorry I didn't get you.

Are you programmatically looking for sent/failed SMS by looking
at Kannel logs?

Guillaume Cottenceau wrote:

Alok Vaidya <alok 'at' routesms.com> writes:

Hi,

Thanks for replying. Yes I checked the documentation we can certainly have a
custom format, but it is about the events that I talking here like "Sent SMS"/
"FAILED SMS"/"Discarded SMS" etc., I see some changes there. Mostly I have
figured them out but, I fail to understand some other entries which I have
mentioned below as also I want to know more such changes.

Let me elaborate why this causes problems. Our parser uses patterns such as
"Failed SMS" to search for current (14.2 box) entries, now this event logging
has changed to "FAILED SEND SMS" naturally this will not be picked up and hence
we loose on such entries. That's my point here.

I might be a little off topic, but why not using the mechanism
made for that kind of things, e.g. receiving delivery reports
from Kannel? It is supported, lets you ask what information you
need, and is of course "supported" accross versions.

begin:vcard
fn:Alok Vaidya
n:Vaidya;Alok
org:RouteSms Solutions Limited;Technology
adr:Mind Space, Malad (West);;Office 401, Evershine Mall, New Link Road, ;Mumbai;MAH;400069;India
email;internet:[email protected]
title:Team Leader
tel;work:40337676-640
x-mozilla-html:TRUE
url:www.routesms.com
version:2.1
end:vcard