providing the highest level of communication services

CSTA Events

Hi,

I was looking thru the code (server, client). The events that get passed on:

CSTAAgentEventReceived, CSTACallEvent and TDSDataReceived, they all passed arguments (CallEvent, AgentEvent).

As far as I was checking you code, you pass CallEvent (just the workstring, that you get from server). So there is yet no code to do the parsing into some simple objects for better use on the client side - or am I missing it.

If so I can write this code, and we can add it to the project?

have a nice day
Kristjan

‹ Cisco UCM HiPath3000 makeCall ? ›

See simple example

Submitted by cstachris on Mon, 06/27/2011 - 20:55.

Howdy,

Hmmm... good observation - so if the simple example - http://www.opencsta.org/forums/support/20100204/csta-simple-example-expl... (the last section of code towards the bottom of that page), looked something more like

if( callevent instanceof DeliveredEvent){
parent.handleEvent((DeliveredEvent)callevent);
}

I guess and sending the DeliveredEvent object up to the parent CSTAApplication here http://client.trac.opencsta.org/browser/trunk/src/org/opencsta/apps/obje... -

So perhaps this CSTAApplication interface could look like


handleEvent(DeliveredEvent);
handleEvent(EstablishedEvent);
handleEvent(ConnectionCleared);

That would probably make writing applications on top of it much more 21st century!. Is this how you mean?

Exactly, something like that

Submitted by kristjank on Mon, 06/27/2011 - 21:11.

Exactly,

something like that would be great; even for maybe later, xml implementatios, so it will be still possible to hide the complexity; and the end user works just with already prepared objects...

Where the DeliveredEvent, EstablishedEvent, ConnectionClered and other classes would be simple java beans to use in supporting apps..

what do you suggest?
br
Kristjan

Agreed

Submitted by cstachris on Mon, 06/27/2011 - 21:34.

OK - I'll look at putting that in during the next few days.

As for XML, I don't have a switch to test with for CSTA-XML, although that is just a matter of creating an "engine" or "csta request builder" to output either ASN.1 (hex) or XML for presentation (layer 6).

Thanks for the prod :)
Chris

no problem, but for now I

Submitted by kristjank on Mon, 06/27/2011 - 21:39.

no problem,

but for now I like the implementation you have - so its not such an urgent matter...

so instance of and casting to corrent event - also works... it just make up over it - my suggestion....

thank you for fast help and repies...!

will be in touch...

with br
Kristjan

Oh btw, to your original

Submitted by cstachris on Mon, 06/27/2011 - 23:45.

Oh btw, to your original question at the top, if you find it's quicker to build your own better-event-delivery-to-higher-level-apps, yeah you can contribute, work out how to do it when that bridge needs crossing...

Cheers
Chris

nice. yes it is more

Submitted by cstachris on Mon, 06/27/2011 - 23:36.

nice. yes it is more function over elegance in some places of the project.

..just make up over it..

I like your use of personification to describe the project, very original :)

Chris

;) the more I look at the

Submitted by kristjank on Tue, 06/28/2011 - 06:41.

;) the more I look at the code, the more I like it:)

...and the comment " just make up over it"... that was meant for my idea in the beginning of the thread; cause, it really is just make up, over already gr8 functioning project :)

enjoy and will be in touch...

Kristjan