[asterisk-dev] Attended transfers in queue_log
Mark Michelson
mmichelson at digium.com
Thu Jun 12 11:47:52 CDT 2008
I just finished merging a change into the trunk branch which corrects a
long-standing deficiency of the queue_log: the inability to log attended transfers.
A bit of background: prior to the merge, a blind transfer made by a queue member
would show up in the queue_log as a TRANSFER event. Attended transfers, however,
due to the limitations of what information was available to app_queue, did not
log a TRANSFER event. Instead, they appeared as a COMPLETECALLER event. With the
recent addition of a "fixup" phase to datastores during channel masquerades, I
realized that this could facilitate a means by which to correctly log an
attended transfer in the queue_log. Yesterday, I created a branch to make this a
reality and this morning I merged the branch into trunk.
Now the question arises: should this change also be merged into 1.4? My thinking
is that the majority of users would be very happy to see attended transfers
properly logged in the queue_log. The big thing holding me back right now is
that there are many third-party applications that use the data in the queue_log
to generate statistics. While I don't know of the specifics of these
applications' internals, I know that any sort of change to what is expected may
cause problems. To any who have written such apps, would such a change cause a
problem? Would it actually be helpful? Thanks in advance for your replies.
Mark Michelson
More information about the asterisk-dev
mailing list