I'd be interested in what Loway would have to say about this (or any
other reporting systems). ATTENDEDTRANSFER already uses 4 data fields,
so I don't have any issue if CONNECT sets the 4th data field to
linkedid. I don't see this as a format change, if we were talking about
adding a 5th data field I'd feel be differently (since no verb has 5
data fields).
On 01/12/2018 04:11 PM, Matt Fredrickson wrote:
On Thu, Jan 11, 2018 at 6:00 AM, marek cervenka <cerva...@gmail.com> wrote:
hi,
because of some call analytics we need linkedid in queue_log
if we create patch for it (app_queue), will you accept it?
My preferences are that any changes to the queue log format would be
done in master only. That being said, tests are always welcome
(master or not). The queue applications is one of the areas of code
that are full of traps, partially due to the fact that we don't have
much testing around it.
Anybody else have any thoughts about this?
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
