Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000328 [Yate - Yet Another Telephony Engine] module minor sometimes 2012-12-11 18:49 2013-02-21 13:20
Reporter fed View Status public  
Assigned To
Priority normal Resolution open  
Status new   Product Version 4.x
Summary 0000328: wrong sequence of call.cdr messages
Description When yate gets INVITE then CANCEL, call.cdr sequence is confused.
call.cdr "finalize" then call.cdr "initialize".
As a result , some broken cdr records.

Additional Information
Tags No tags attached.
Attached Files ? file icon yate.log_cdr_bug [^] (9,565 bytes) 2012-12-11 18:49

- Relationships

-  Notes
asymetrixs (reporter)
2013-02-21 13:20


as far as I have learned CDR messages are handled asynchron and their order may change. This is to get best performance and not waste CPU time by adhere to a certain order. We have the same behavior in SQL and implemented a way to handle this like:
-> Check if CDR record exists
yes -> Update if not already ended
no -> Insert record

Here is an MySQL example for that: [^]

- Issue History
Date Modified Username Field Change
2012-12-11 18:49 fed New Issue
2012-12-11 18:49 fed File Added: yate.log_cdr_bug
2013-02-21 13:20 asymetrixs Note Added: 0000512

Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker