wso531 / asterisk-cti

Automatically exported from code.google.com/p/asterisk-cti
GNU General Public License v3.0
0 stars 0 forks source link

asterisk agents #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I'm testing the cti system and it works quite well! Bravo Bruno!
I was thinking to contact you because I'would like to add some useful 
functions (if you agree) for call center (agent login/logoff). I made a 
little agi script that get the dtmf look in a mysql table end came back 
with the result, it work fine. After that i configured a couple of agents 
(in agents.conf and queues.conf) if I use the agents instead (with agent 
login) of the SIP channels the astctiserver crash (you will find the 
printout of debug in attach). Seems that the server doesn't receive the 
appdata anymore. Do you think that is an Asterisk problem?
Thanks a lot for your help
I'm reacheable also at giuseppe.innamorato@xenialab.it

Original issue reported on code.google.com by giuseppe.innamorato on 2 Oct 2008 at 8:01

Attachments:

GoogleCodeExporter commented 8 years ago
When you use agents instead of SIP channels, you're going against the actual
application design. Infact, the Server use the channel as the key to identify 
the
client and send relevant messages. When You use agents, the channel is slight
different and the way asterisk notifies it's messages should be checked and 
implemented. 
I plan to integrate agents in a future release. Your debug has been anyway 
useful to
patch Server.cs and get the SendMessage function a bit more robust.
I need more details about your tests and configuration to reproduce the bug.

Thank You

Original comment by d4rks...@gmail.com on 2 Oct 2008 at 9:47

GoogleCodeExporter commented 8 years ago
Fixed by Giuseppe Innamorato (Xenialab)

Original comment by d4rks...@gmail.com on 23 Oct 2008 at 10:23

GoogleCodeExporter commented 8 years ago
Hi Bruno,
I'm in a similar situation where I have created agents logon/logoff. The server
doesn't crash in my case however I always get the agent context (through which
they're logged in) instead of the actual call context. 
As a result I miss out on vital incoming callerid and context information. Is 
there a
way to preserve this information? The cti-client doesn't seem to pickup other 
context
information.

Cheers
Eshan

Original comment by eshanvb@gmail.com on 18 Aug 2009 at 12:42

GoogleCodeExporter commented 8 years ago
Okey got over this by using AgentCallbacklogin to use SIP channels and 
listening on
the agent extension, it's all good.

Original comment by eshanvb@gmail.com on 19 Aug 2009 at 6:09