asterisk users - Jul 2004 - queue_log question: which endpoint was connected?

Hello list,

as I'm writing a little perl parser for queue_log analysis, I'd like to
know *which* telephone answered a specific queue call. Unfortunately  
app_queue only logs the call id but does not log the call end point. This  
is okay for SIP endpoints, because their call id is something like  
SIP/endpointname-1234 so you can reasonably understand who was on  
answering, but for OH323 I get ID's like OH323/LJ5645 that are meaningless.

Is there a way to extract from some other log the fact that OH323/LJ234  
was a call placed to - say - OH323/345@10.10.3.5? or can I extract it from  
some field of the peer data structure queue_log seems to extract data  
from? (to obtain call id, they gust print peer->name)

Any help will be greatly appreciated.
Thanks
l.




-- 
Creato con M2, il rivoluzionario client e-mail di Opera:  
http://www.opera.com/m2/

lenz wrote:
> 
> Hello list,
> 
> as I'm writing a little perl parser for queue_log analysis, I'd
like to
> know *which* telephone answered a specific queue call. Unfortunately  
> app_queue only logs the call id but does not log the call end point. 
> This  is okay for SIP endpoints, because their call id is something 
> like  SIP/endpointname-1234 so you can reasonably understand who was on  
> answering, but for OH323 I get ID's like OH323/LJ5645 that are
meaningless.
> 
> Is there a way to extract from some other log the fact that OH323/LJ234  
> was a call placed to - say - OH323/345@10.10.3.5? or can I extract it 
> from  some field of the peer data structure queue_log seems to extract 
> data  from? (to obtain call id, they gust print peer->name)
The IP of the connected endpoint can be obtained from the OH323_RADDR
variable. For incoming H.323 calls you can get the name of the channel
and the IP address inside the dialplan, write them to a file and process
them later. For outgoing H.323 calls [Dial(OH323/...)], you can't do it
from the dialplan. In that case the OH323_RADDR variable is accessible
only through the Dial() app.

Anyway, it seems that the name of the OH323 channels needs to be more
useful (added to my TODO list).
> 
> Any help will be greatly appreciated.
> Thanks
> l.

Michael.

Hello list,
I have started writing a little log_queue parser that will display stats  
in a graphical way based on the involved queue(s) and a start/end date.

You can see a sample analysis here: http://demo.xcept.it/xc-ast/XC-AST.htm

Strings are in italian, but I guess the uploaded page it's easy to  
understand (just notice that "Chiamate" is "calls"). First
it reports all
calls taken by an agent, then all aborted calls, then all agents present  
during the given time period.

Any suggestion or criticism is welcome. I am looking for queue_log files  
to try the software.
Yours,
l.


In data Thu, 29 Jul 2004 15:59:39 +0200, lenz <lenz-ml@oinko.net> ha  
scritto:
>
> Hello list,
>
> as I'm writing a little perl parser for queue_log analysis
>
-- 
Creato con M2, il rivoluzionario client e-mail di Opera:  
http://www.opera.com/m2/

lenz [lenz-ml@oinko.net] wrote:
> I have started writing a little log_queue parser that will display stats
> in a graphical way based on the involved queue(s) and a start/end date.
> 
> You can see a sample analysis here: http://demo.xcept.it/xc-ast/XC-AST.htm
> 
Very nice.

-- 
   _/   _/  _/_/_/_/  _/    _/  _/_/_/  _/    _/
  _/_/_/   _/_/      _/    _/    _/    _/_/  _/   K e v i n   W a l s h
 _/ _/    _/          _/ _/     _/    _/  _/_/    kevin@cursor.biz
_/   _/  _/_/_/_/      _/    _/_/_/  _/    _/