[Freeswitch-users] State of GUIs

[Gabriel Gunderson]

2012/3/9 João Mesquita <jmesquita at freeswitch.org>:
> You don't handle a dynamic dialplan on this? I am not very fond of Django
> and it has been a while since I last touched it so excuse me if I am
> mistaken.

Sorry you're not a fan of Django. I really enjoy it :) It keeps us
productive and helps us get things done.

Anyway, most of the dynamic stuff built for mod_xml_curl is for
configuration and CDRs.  If you're familiar with Django, you'll see
that Parseltone gives you some-pre built views that provide a little
logic and create the context to render the templates in. You have the
actual templates. You have some models that provide a data backend for
some of the more obvious configs (IVRs, ACLs etc.) and the Admin
configuration to make it all pretty. You can find most of that with
the link I shared earlier.

Again, at it's current state, it's just a helpful collections of
Python modules that all have to do with some aspect of FreeSWITCH,
nothing more.

Besides Django stuff, there is a pretty nice Event Socket library:
https://parseltone.org/browser/trunk/parseltone/eventsocket

The Twisted stuff is further along than the Django stuff, but even so,
there is so much more we want to do with it. One cool thing about the
current EventSocket stuff is that it has 3 modes of operation... each
one a little more advanced than the last:

1) Raw Event Socket: Just connect and handle the passing of the data.
2) Basic Event Socket: Adds parsing of responses, methods for api and
bgapi and well... basic operation.
3) Event Socket This adds the neat feature of tying FreeSWITCH's bgapi
and Twisted's deferreds together.

One last think we're getting ready to add is a WSGI component that
fits between any WSGI client/server (so you don't have to use it with
Django, but because it's WSGI, you can). For example, a Flask user
could put this between Apache's mod_wsgi and Flask. Anyway, it
captures all of the POST data and any other information from
mod_xml_curl, saves it and then passes it on to Django/Flask/etc. for
processing. It then gets the response and saves it to a database so
the it can be examined at a later time. It also can display that data
using it's own web interface.  Fun stuff.

Well, I shouldn't get too off topic.  Anyone who is interested should
consider hitting me off-list.


Gabe

Hope someone finds something useful there :)

We'll get back on it when we have time... heh.


Gabe