Well I’ve heard this one before. I believe AMI has made a major step forward since it was first added to the asterisk trunk. I believe that it can be considered a rather safe option when you need to send commands to an asterisk server through it. I have created various production applications (Dialers, Queue Monitors/Actions, etc) through the AMI that for the load they are getting they never had any issues.

However if you were to read events from asterisk, through lets say a web application I would think twice of my implementation. I wouldn’t want for each web connection to have one connection to the AMI, and I would probably implement a proxy in-between so that asterisk will send the events to the proxy and have the proxy distribute the messages to the web clients. (One idea that comes to mind easily is have the proxy receive the messages, send them to a message queue system like RabbitMQ and then via a fanout queue to spread the message to all clients listening)

What are you thinking of building?

Well it took me a while but I’ve crafted something up for you to check out. You can find it here: Simple Channel Monitoring via Shift8

You are right. I will try to come up with something in the next few days and I’ll post it here

Shift8 seem to be a very interesting project but it lack of examples and documentation as you told in TODO list.
Anyway, I would try it in a faster bit but to do so I should have a minimal GUI (web frontend).
Thus, can you provide an example of a little web client that monitor the Asterisk channels status in real time?
I think it will be a good starting point for everyone would try and assist you in the project expansion.
Every project can be a good project if it has a good community and more effort as possible.

Thank you.
Massimiliano

Well if you feel like contributing any part you are most welcome to do so!

As for your question, in any applications I’ve build using Shift8 I’ve never had any problems with the Manager disconnecting. Maybe it is AJAM that does a difference (since Shift8 is using AJAM). Give it a try and we could work any issues out!

First,
I can try to help coding small php tasks in my spare time (hope i’ll have one)

2nd, I’m using the old PHP AGI API and one of problems i experience is an occasional manger’s logging off. Is it an issue that you familiar with/was fixed? or is it my own bug?

Tnx! David R.

Could you give me examle how to ( if possible ) get uniqueid of call generated with originate.

Thanks
Pawel

You could use Shift8 to create an AMI proxy, but you need to pass the asterisk manager session id back and forth. You could use the getCookie(), setCookie() functions from Shift8 so that the connection will remain open.

You are also responsible for keeping the connection open with the AMI by ping()ing the asterisk library and then use waitEvent() to retrieve all events generated by the Asterisk

Remember to close the PHP session after saving/reading the cookie, because Sessions in PHP are locking and when you do a WaitEvent() will lock the session until that terminates. (It took me a while to figure that out. Thankfully there is Xdebug Profiler )