Raymond, I like the concept. Is the name "Long Call" appropiate? As this is really an error condition isn't it?
Al -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dans, Raymond (CAR:9D30) Sent: Wednesday, February 04, 2009 9:55 AM To: [email protected] Subject: [sipX-dev] XECS-2153 - CDRs shows 0 seconds duration for calls thathave been active for 10 hours or more This issue deals with the case of the Proxy Call State Event Observer missing an end of call (BYE) message. To trap this type of scenario, CDR will periodically check for calls that have been active for a long time (ie. > 8 hours is the current default) and when it finds one, it will close the CDR record and write it to the database. This issue deals with the fact that the record shows a total time of 0 seconds and a call status of "Completed". To resolve this issue, I'd like to do 2 things: 1. Provide a total time value which represents the current long call timeout value. Even though putting in this value is not accurate (since we don't know when the call ended or even if it has ended), it is better for Call Accounting to have something other than 0 in it. 2. Instead of marking the call as "Completed" to introduce a new Status type of "Long Call". Putting in a total time value of the cur While I'm in the code adding a new Status type of "Long Call", I'd also like to add another type "Transferred" in hopes of adding support/detection for this in the near future (btw. This will then require translations for each of these new status types into all languages we support). If there are no objections, I'll proceed today with the necessary changes in both CDR and in sipXconfig. Raymond _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
