asterisk-java-devel

[Asterisk-java-devel] TMI/Terminus

[Carlos G M. <tr...@hu...>]

Hi,
I've uploaded some files that compose the current state of my agent
status monitor "system" dubbed Terminus.
It's available via CVS at sourceforge, project tmi.

This are 2 programs, a server (TMI.java) which connects to asterisk
using manager and provides a text based "service" on tcp port 4300,
and a client that connects to it (all other .java files, compile to a
jar file) and provides a couple of windows (queue status and agent
status) and a basic filter to see only some of the queues and their agents).

There are some "not a distributable yet" things like:

-manager user/password is burnt in source
-it uses a udp(port 4301) backchannel to tell current status to agents
-"out states" depend on undocumented extensions programming
... and may be others.

It's not using Live (yet?). Sorry about that.
I added some last minute goodies like SIP ip determination (I use IAX
agents) and call final data (to enable call metrics accounting).
All in all I gues it may be helpful for someone.

I was thinking about generating the metrics at the server side (TMI)
but now I'm leaning towards decoupling that as well, by having a TMI
client do the accounting and db insertion.

Feedback is welcome.

-- 
Carlos G Mendioroz  <tr...@hu...>  LW7 EQI  Argentina

Re: [Asterisk-java-devel] TMI/Terminus

[Stefan R. <ste...@re...>]

Hi Carlos,

looks promising!
I think the TMI.java class could be perfectly generalized and merged
into the live API.
Did you already have a look at it and got a first impression of what is
actually duplicated and what is still missing in live?

=Stefan

Carlos G Mendioroz wrote:
> Hi,
> I've uploaded some files that compose the current state of my agent
> status monitor "system" dubbed Terminus.
> It's available via CVS at sourceforge, project tmi.
> 
> This are 2 programs, a server (TMI.java) which connects to asterisk
> using manager and provides a text based "service" on tcp port 4300,
> and a client that connects to it (all other .java files, compile to a
> jar file) and provides a couple of windows (queue status and agent
> status) and a basic filter to see only some of the queues and their agents).
> 
> There are some "not a distributable yet" things like:
> 
> -manager user/password is burnt in source
> -it uses a udp(port 4301) backchannel to tell current status to agents
> -"out states" depend on undocumented extensions programming
> ... and may be others.
> 
> It's not using Live (yet?). Sorry about that.
> I added some last minute goodies like SIP ip determination (I use IAX
> agents) and call final data (to enable call metrics accounting).
> All in all I gues it may be helpful for someone.
> 
> I was thinking about generating the metrics at the server side (TMI)
> but now I'm leaning towards decoupling that as well, by having a TMI
> client do the accounting and db insertion.
> 
> Feedback is welcome.
> 


-- 
reuter network consulting
Neusser Str. 110
50760 Koeln
Germany
Telefon: +49 221 1305699-0
Telefax: +49 221 1305699-90
E-Mail:  ste...@re...
Jabber:  ste...@re...
WWW:     http://www.reucon.com

Steuernummern 215/5140/1791 USt-IdNr. DE220701760

Re: [Asterisk-java-devel] TMI/Terminus

[Carlos G M. <tr...@hu...>]

Stefan Reuter @ 01/03/2008 05:16 -0200 dixit:
> Hi Carlos,
> 
> looks promising!
Thanks!

> I think the TMI.java class could be perfectly generalized and merged
> into the live API.
> Did you already have a look at it and got a first impression of what is
> actually duplicated and what is still missing in live?

Yes, I took a look, but I don't see your "perfect fit" view though :(
As I see it, Live should (and does) hide the (manager) protocol
complexities and expose asterisk objects in a java friendly way.
Functions, listeners, etc.

My problem with that is that asterisk agents are too low level, in fact
they implement part of the agent needed functionality and you are free
to build the rest the way you want. Static/dynamic. Static queues or
dynamic. Outgoing call interaction. Supervision. To name a few.

It would be great to fit ANY model, but may be way too complex.
I want an Agent to be a call center agent, not the asterisk agent 
"channel". I need to have the idea of the agent doing outgoing calls,
out states, login timing, supervisor access (eventually :).

For the time being, it has IP (mostly for status info to the agent 
phone, but may also be used for mapping, session auth, etc) state and 
login time. Out states and outgoing call tracking need specific
configuration, I see no way of generalizing that...

> 
> =Stefan
> 
-Carlos
-- 
Carlos G Mendioroz  <tr...@hu...>  LW7 EQI  Argentina

Re: [Asterisk-java-devel] TMI/Terminus

[Martin S. <ma...@be...>]

Hi Carlos (again :),

The Live API is built on top of the Manager API, which has the
"low-level" you're looking for.

Here's what Stefan is thinking you could do (I think :),
  1. If there's something in the Manager API missing that you would use
(I doubt anything is missing from there), you could ensure the
Asterisk-Java Manager API contains it.
  2. You could translate from the AJ Manager API and Asterisk agents to
the Live API and Call center agents.
  3. Your app could then manage MUCH less generic state per agent, and
everyone else would get the benefit of as much generalization as
possible.

I think you'll find also that other folks are working on Agent-centric
features here for AJ too. Either way, I look forward to eventually
taking the time to toy with Terminus :)

Martin Smith, Systems Developer
ma...@be...
Bureau of Economic and Business Research
University of Florida
(352) 392-0171 Ext. 221 

 

> -----Original Message-----
> From: ast...@li... 
> [mailto:ast...@li...] On 
> Behalf Of Carlos G Mendioroz
> Sent: Saturday, March 01, 2008 4:13 PM
> To: ast...@li...
> Subject: Re: [Asterisk-java-devel] TMI/Terminus
> 
> Stefan Reuter @ 01/03/2008 05:16 -0200 dixit:
> > Hi Carlos,
> > 
> > looks promising!
> Thanks!
> 
> > I think the TMI.java class could be perfectly generalized and merged
> > into the live API.
> > Did you already have a look at it and got a first 
> impression of what is
> > actually duplicated and what is still missing in live?
> 
> Yes, I took a look, but I don't see your "perfect fit" view though :(
> As I see it, Live should (and does) hide the (manager) protocol
> complexities and expose asterisk objects in a java friendly way.
> Functions, listeners, etc.
> 
> My problem with that is that asterisk agents are too low 
> level, in fact
> they implement part of the agent needed functionality and you are free
> to build the rest the way you want. Static/dynamic. Static queues or
> dynamic. Outgoing call interaction. Supervision. To name a few.
> 
> It would be great to fit ANY model, but may be way too complex.
> I want an Agent to be a call center agent, not the asterisk agent 
> "channel". I need to have the idea of the agent doing outgoing calls,
> out states, login timing, supervisor access (eventually :).
> 
> For the time being, it has IP (mostly for status info to the agent 
> phone, but may also be used for mapping, session auth, etc) state and 
> login time. Out states and outgoing call tracking need specific
> configuration, I see no way of generalizing that...
> 
> > 
> > =Stefan
> > 
> -Carlos
> -- 
> Carlos G Mendioroz  <tr...@hu...>  LW7 EQI  Argentina
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Asterisk-java-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/asterisk-java-devel
> 

Re: [Asterisk-java-devel] TMI/Terminus

[Stefan R. <ste...@re...>]

Martin Smith wrote:
>   2. You could translate from the AJ Manager API and Asterisk agents to
> the Live API and Call center agents.
>   3. Your app could then manage MUCH less generic state per agent, and
> everyone else would get the benefit of as much generalization as
> possible.

Yes that was my idea. The goal of the live API is to be easier to use
but not to provide less features than the Manager API.

Of course there will still be specific logig on top of live that
implements missing pieces that are not available in Asterisk. This
should be possible the same way you do it currently with the Manager
API, but it will (hopefully) be easier.

=Stefan

-- 
reuter network consulting
Neusser Str. 110
50760 Koeln
Germany
Telefon: +49 221 1305699-0
Telefax: +49 221 1305699-90
E-Mail:  ste...@re...
Jabber:  ste...@re...
WWW:     http://www.reucon.com

Steuernummern 215/5140/1791 USt-IdNr. DE220701760