[asterisk-dev] Hold-Unhold information in queue-log
cwinay at yahoo.com
Tue Feb 15 08:21:19 CST 2011
There seems to be a bit of confusion regarding some the callid terminology.
We need to log the channel-id of the member's channel when the hold/unhold events occur (struct ast_channel *chan -> uniqueid to be precise)
In the update_status function in app_queue.c, we get the interface and the updated status.
static int update_status(const char *interface, const int status)
Using the interface, the function iterates through queues to find the member and sets the member's status. At this point, how should we get the channel-id associated with the member?
--- On Thu, 10/2/11, Stefan Schmidt <sst at sil.at> wrote:
From: Stefan Schmidt <sst at sil.at>
Subject: Re: [asterisk-dev] Hold-Unhold information in queue-log
To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
Date: Thursday, 10 February, 2011, 4:02 PM
Am 10.02.11 11:25, schrieb winay chaudhari:
> We are trying to modify asterisk code to log events in queue-log when an agent puts a call on hold. (Asterisk 1.6 & 1.8)
> 1. Call comes into the system.
> 2. Call is put in a queue.
> 3. Agent in the queue takes the call.
> 4. Agent puts the call on hold
> 5. Agent takes the call off hold
> We want to log the events for 4 and 5 along with the queue-name, callid & agent
> We tried including the log in update_status method of app_queue.c but somehow we managed to get all fields but callid. Where can we get all the 4 fields required in the log viz queue-name, callid, agent & event?
Its just a guess but i think you are on the wrong channel to look for
you have two possible ways.
1) in your extensions.conf before dialing the queue just do something
then you should see the callidincoming var also on the agent channel .
2) or you try to get this information over the bridged channel, but
thats IMHO the not so easy way.
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev