hi,

I think all here are rather 'new' to this group...

I agree that this group should not spread their focus to wide, but I would prefer to have a well designed API that allows me to run other applications on top of the PBX rather than a 'dialplan language' or some weird scripting.

It is possible to achieve 2 objectives (1) to have a standard PABX which is easy to install and extend with dialplan and (2) have a PABX that can be extended with more sofisticated application modules (complex IVR services etc).

Jan

Curtis Monroe wrote:
How about a _javascript_ that reads the dial plan out of an xml file, or even 
the existing Asterisk config files.

The _javascript_ could also implement the voice message system.

-Curtis.

P.S.   I'm new to the group



On December 12, 2005 01:11 pm, Daniel Swarbrick wrote:
  
Justin Tunney wrote:
    
IMHO, It would be a _HUGE_ mistake to not have a standard extension  
langauge for OpenPBX.  It should be /possible/ to write extensions in  
other languages, (Like AGI lets you do with less sophistication than an  
actual API) but we should pick _one_ language for standard configuration.

      
I couldn't agree more. Multiple dialplan languages is a "nice-to-have", 
not a "necessary". Let's concentrate the manpower we have on a single 
language to begin with.
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

    
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev



  

_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Reply via email to