<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.14.3">
</HEAD>
<BODY>
On Tue, 2009-01-13 at 21:09 +0100, Benny Amorsen wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">I wrote a really long email, but it hinged on one thing I need clarified...</FONT><BR>
<BR>
<FONT COLOR="#000000">tir, 13 01 2009 kl. 09:05 -0700, skrev Steve Murphy:</FONT><BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> CDR1: A -> B start: e1a ans: e2 end: e4 Party: B disp: ANSW linkedID: abc9</FONT><BR>
<FONT COLOR="#000000"> CDR2: A start: e1 ans: e1 end: e6 Party: A disp: ANSW linkedID: abc9</FONT><BR>
</BLOCKQUOTE>
<BR>
<FONT COLOR="#000000">We are talking about the "Simple" CDR's, not the leg-based ones, right? If so, why do all the CDR's only call one "Party"? Shouldn't there be a src and a destination? </FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">/Benny</FONT><BR>
<BR>
</BLOCKQUOTE>
Benny--<BR>
<BR>
First, yes, all the examples I gave were for Simple CDR mode.<BR>
<BR>
Next, the notation is simplified. A -> B means channel: A dstchannel: B (A and B are also contractions for stuff like "Dahdi/1-1" or "Sip/bob-1")<BR>
start, ans, end are the 3 times (e2, e3, etc are event times (symbolic); disp is the disposition field. linkedID is described in the doc.<BR>
<BR>
I don't specify src/dest, in the examples, as they really don't convey much without all the background description,<BR>
(if I said src = '101' and dest = '202' you'd have to know the associated contexts, etc. -- a can of worms)---<BR>
but every CDR will specify those fields for the Dial (or whatever else was responsible for activating the channel).<BR>
<BR>
I also didn't spell out stuff like userfield, amaflags, callerid fields, etc; it isn't that they aren't important, it just<BR>
clouds the examples to get too explicit and verbose.<BR>
<BR>
The main thing about these fields is that they are in the list of CDR fields and described in the CDR field section.<BR>
<BR>
The "Party" field says which channel this CDR applies to. I use it because the channel/dstchannel aren't always<BR>
going to involve the channel in question. Usually, tho, Party will either be the channel or the destchannel. Knowing<BR>
which one is the trick.<BR>
<BR>
And, as a side note, the A CDR in my examples usually lacks a dstchannel field, because it's not being activated by a dial--<BR>
it's being activated via an incoming call on an FXO interface. (or an incoming SIP invite, maybe...)<BR>
<BR>
And, if I'm missing info that would really, really, necessary to have, or hard to inject from the dialplan, now is the time<BR>
to fight to make sure that it is in the spec.<BR>
<BR>
murf<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Steve Murphy <<A HREF="mailto:murf@digium.com">murf@digium.com</A>><BR>
Digium
</TD>
</TR>
</TABLE>
</BODY>
</HTML>