On 14-01-25 09:54 AM, James Wystead wrote:
> First, let me thank all of you for your input - I was looking for some
> sort of an API to interface with Asterisk via REST. Python, Ruby or
> something that we could "webify" using PHP.

It all depends on what you want to do the with API as well...

> Some of you suggested Asterisk 12 - I love the idea, but unfortunately,
> we have an Asterisk 11 install. It seems, and I could be wrong, that
> Asterisk 12 is a whole new 'ball game' so to speak. The big thing is
> pjsip - nice idea and I really like it. It looks like a bit of a
> learning curve and I don't want have to re-learn at this point - I will,
> but not right this second!  However, I have questions:
> 
> 1. Is it necessary to use pjsip for Asterisk 12 as the extension.conf,
> sip.conf has changed gears a little. Can I backtrack to the previous SIP
> stack, which segways into another question:

The chan_sip module has not been removed and works perfectly fine in 12.
You can even use both, provided you bind each to different ports.
Dialplan is also the same as in the past.

> 2.  If this is possible (the above scenario) is it still possible to use
> these new cool features along with the previous SIP stack so that I can
> implement the API?

Depends on what you mean by cool new features. The ARI (Asterisk REST
interface) work is agnostic of channel drivers, it has no specialized
logic for any and any present channel driver can be used with it.

Cheers,

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at:  www.digium.com  & www.asterisk.org

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to