On Wed, 2006-01-18 at 12:38 +0200, David Schwartz wrote:
> What is needed, however, IMHO is a deeper look into
call detail record
> generation as a separate track (not part of logging) as
CDR's are of a
> different nature than ordinary logs (database
dependencies, rating,
> etc.). I believe that this should probably be addressed
in repro as
> well.
In sipXpbx, we defined a module that produces logs of call
state events
- basically the relevant parts of a SIP message passing
through the
proxy - and logs them. These can then be post-processed to
produce CDRs
by working out which set of events constitutes a 'call'.
Depending on
the configuration, this might also include combining call
state event
logs from multiple redundant proxies.
The call state event log we produced is an XML file; I now
think that
was not a good choice (and may change it) - it would be
better to define
a database schema and make each event a row in an SQL
database table.
While the specifics of our implementation are not directly
portable, the
functional spec [1] might be useful in that it specifies
what events
need to be collected and the algorithm for resolving calls
from those
events. The only request that's come up for data not
included in what
we have now is logging when a call goes on and off 'hold'.
This would
mean peeking into the SDP...
This is something that sipXpbx would need to re-implement to
adopt
repro, so it's definitely something we're interested in
contributing to.
[1] http://scm.sipfoundry.org/rep/si
pX/main/sipXproxy/doc/cdr/call-state-events.html
--
Scott Lawrence tel:+1-781-938-5306;ext=162 or
sip:slawrence pingtel.com
Consulting Engineer - Pingtel Corp. http://www.pingtel.com/
sipXpbx project coordinator - SIPfoundry http://www.sipfoundry.
org/sipX
_______________________________________________
repro-devel mailing list
repro-devellist.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/repro-devel
|