[asterisk-dev] GSoC 2010

Mat Murdock mmurdock at kimballequipment.com
Mon Feb 1 16:56:12 CST 2010


I wonder if we could make this more user friendly where you can add a 
variable on each line and the returning xml would be returned into 
variables named by their xml tags.  In the example below two variables 
would be sent to a php page via post and the resulting page would be an 
xml page with a tag named "age".  Anyway just an idea.

exten => _X.,n,rest(test);
exten => _X.,n,Set (rest(test,first_name) ="John")
exten => _X.,n,Set (rest(test,last_name) ="Doe")
exten => _X.,n,rest_submit(test,http://somehost/controller/function.php)
exten => _X.,n,NoOp(${rest(test,age)})

I hope I'm making some sense here.

Mat Murdock

On 2/1/2010 4:47 AM, Nir Simionovich wrote:
> Hi Russell,
>
>    Here's an ideas I've been toying around lately, trying to figure out
> the best way to do this.
> In general, at AstriDevCon 2008 I was under the impression that writing
> an XML-RPC client
> application for Asterisk is applicable, however, as the format of
> XML-RPC requests is fairly
> dynamic, maintaining the configuration files for these is fairly
> problematic.
>
>    In that respect, I've been toying around with the idea of creating an
> func_rest function,
> that works something like this:
>
>    rest(URL, POST_VAR1^POST_VAR2^POST_VAR3^etc)
>
>    The returned result will be a well formulated XML, that is then turned
> into an Asterisk hash.
> For example, let's look at something like this:
>
>    exten =>  _X.,n,Set(RestHash =
> ${rest(http://somehost/controller/function,VarName1^VarName2^VarName3)})
>
>    In the above, we are actually telling the function to activate the
> REST interface at http://somehost/controller/function,
> and passing the variables VarName1 through 3 via HTTP_POST to the
> controller. Now, imagine that we get back
> and XML that contains two variables, xmlvar1 and xmlvar2. We end up with
> RestHash(xmlvar1) with RestHash(xmlvar2).
> Or some other methodology to return the hash variables back into the
> channel structure.
>
>    My main issue with this concept is time, as while I've been toying
> with some lines of code that start doing it using CURL,
> I have no time to continue this, so my sources are way out-dated (start
> with 1.4.16) - merging back into existing strucutres
> will be just too much work - easier to re-write correctly.
>
>    In general, I don't believe knowledge of Asterisk is required in order
> to write this function, although it can really
> help the developer. I know for fact that if I would sit down to work on
> this full time, I'll finish this within 2-3 weeks
> time (I'm a little C rusty), however, a college guy can finish it in the
> same time frame - in my opinion.
>
> Cheers,
>    Nir S
>
> Russell Bryant wrote:
>    
>> Greetings,
>>
>> Google's Summer of Code (GSoC) program is on again for 2010 [1].  The
>> organization application period is March 8th - March 12th.  I plan on
>> putting in an application for the Asterisk project again this year.  In
>> the mean time, I would like everyone to think about a couple of things.
>>
>> First, I'd like those that are committers in the Asterisk project to
>> consider your interest and availability for being a mentor.  If you'd
>> like to discuss this in any detail, feel free to contact me directly.
>>
>> Second, we need to build a project ideas list.  Projects that are good
>> candidates for this list are very well defined and are appropriate in
>> scope for a student with programming experience, but potentially little
>> or no Asterisk experience to complete in a Summer.  Feel free to throw
>> out ideas now, but I will also bring it up again closer to the
>> application date.
>>
>> Thanks,
>>
>> [1]
>> http://groups.google.com/group/google-summer-of-code-discuss/browse_thread/thread/d839c0b02ac15b3f
>>
>>
>>      
>
>    

-- 
Mat Murdock
Kimball Equipment Company
801.972.2121
mmurdock at kimballequipment.com


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




More information about the asterisk-dev mailing list