[asterisk-dev] ExternalIVR with sockets on release 1.6.2.0

[Dan Cropp]

Thanks David

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of David Ruggles
Sent: Tuesday, March 02, 2010 3:30 PM
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] ExternalIVR with sockets on release 1.6.2.0

It's been two months since I was working on this, but I don't think I
could pull it from trunk into 1.6.2. But again that's a now long
distant hazy memory so YMMV :-)

On Tue, Mar 2, 2010 at 4:19 PM, Chris Tooley <chris at tooley.com> wrote:
> Dan,
>
> I'm pretty sure that what's in trunk will work fine against 1.6.2, I'd
> venture to say you could probably pull the app_externalivr.c out of
> trunk and use it in 1.6.2. NOTE and WARNING: This is absolutely not
> true for everything or even most things, in fact it might not be true
> for anything.
>
> I've put ExternalIVR to extensive use previously, doing some of the
> original broken tcp socket development. You can blame me for the state
> of 1.6's version.
>
> On Tue, Mar 2, 2010 at 3:11 PM, Dan Cropp <dan at amtelco.com> wrote:
>> Thank you David
>>
>> For the near future, I'll be using a pure development server, so I will download an update from the SVN trunk.
>>
>> Have a great day!
>> Dan Cropp
>>
>>
>> -----Original Message-----
>> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of David Ruggles
>> Sent: Tuesday, March 02, 2010 2:34 PM
>> To: Asterisk Developers Mailing List
>> Subject: Re: [asterisk-dev] ExternalIVR with sockets on release 1.6.2.0
>>
>> Dan,
>>
>> It's good to hear of someone starting to use ExternalIVR, it's one of
>> the under-appreciated, less talked about, application in Asterisk ;-)
>>
>> There are several known bugs and issues that have been fixed in Trunk.
>> If this is a pure development server and it's not that big a deal the
>> easiest path would probably be to use SVN trunk and then 1.8 as soon
>> as it's branched and released. If not, then you'll need to make a
>> series of modifications to app_externalivr.c to fix these bugs. Also,
>> the documention, doc/externalivr.txt, has been updated in Trunk to be
>> accurate and to include information about the changes and enhancements
>> to externalivr.
>>
>> You can see the list of changes here:
>> http://svnview.digium.com/svn/asterisk/trunk/apps/app_externalivr.c?view=log
>>
>> You would need to include the modifications back to revision 230438.
>>
>> If you don't switch to trunk, trunk's version of the documentation can
>> be found here:
>>
>> http://svnview.digium.com/svn/asterisk/trunk/doc/externalivr.txt?view=markup
>>
>> Please reply with any additional questions you may have.
>>
>> David Ruggles
>>
>> On Tue, Mar 2, 2010 at 3:13 PM, Dan Cropp <dan at amtelco.com> wrote:
>>> I am running Asterisk 1.6.2.0 release.
>>>
>>>
>>>
>>> I am able to get the dialplan to execute an external IVR that's in a file.
>>>
>>> exten => 101,1,Verbose(1,Test)
>>>
>>> exten => 101,2,Answer()
>>>
>>> exten => 101,n,ExternalIVR(/root/play_beep.sh)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> However, when I try to have ExternalIVR connect to a socket it is not
>>> working.
>>>
>>> For the server, I execute
>>>
>>> netcat -l -p 2949
>>>
>>>
>>>
>>> The dialplan looks like...
>>>
>>> exten => 101,1,Verbose(1,Test)
>>>
>>> exten => 101,2,Answer()
>>>
>>> exten => 101,n,ExternalIVR(ivr://localhost:2949)
>>>
>>>
>>>
>>>
>>>
>>> It successfully answers the call.  The output is showing...
>>>
>>>
>>>
>>>     -- Executing [101 at phones:3] ExternalIVR("SIP/1000-00000000",
>>> "ivr://localhost:2949") in new stack
>>>
>>> [Mar  2 14:09:41] WARNING[3396]: app_externalivr.c:402 app_exec:
>>> SIP/1000-00000000: Answering channel and starting generator
>>>
>>>   == Spawn extension (phones, 101, 3) exited non-zero on 'SIP/1000-00000000'
>>>
>>>
>>>
>>>
>>>
>>> Does socket ExternalIVR require some additional modules or settings?
>>>
>>>
>>>
>>> Have a great day!
>>>
>>> Dan Cropp
>>>
>>> --
>>> _____________________________________________________________________
>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>>
>>> asterisk-dev mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>
>
>
> --
>
> Chris Tooley
> mobile: 615-525-8067
> Instant Messenger
> MSN: ctooley at ntrc.net
> AIM: mrchristooley
> Yahoo: mrchristooley
> Google Talk: ctooley at gmail.com
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

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