On Monday 13 April 2009 11:14:14 am Eric Chamberlain wrote:
> On Apr 13, 2009, at 8:52 AM, Tilghman Lesher wrote:
> > On Sunday 12 April 2009 02:34:10 am Julian Lyndon-Smith wrote:
> >> Eric Chamberlain wrote:
> >>> On Apr 11, 2009, at 12:53 AM, Julian Lyndon-Smith wrote:
> Eric Chamberlain wr
On Apr 13, 2009, at 8:52 AM, Tilghman Lesher wrote:
> On Sunday 12 April 2009 02:34:10 am Julian Lyndon-Smith wrote:
>> Eric Chamberlain wrote:
>>> On Apr 11, 2009, at 12:53 AM, Julian Lyndon-Smith wrote:
Eric Chamberlain wrote:
>>
>> [snip]
>>
>>> Thank you, that bug does have useful inform
On Sunday 12 April 2009 02:34:10 am Julian Lyndon-Smith wrote:
> Eric Chamberlain wrote:
> > On Apr 11, 2009, at 12:53 AM, Julian Lyndon-Smith wrote:
> >> Eric Chamberlain wrote:
>
> [snip]
>
> > Thank you, that bug does have useful information.
> >
> > We are working on moving from res_config_odbc
Eric Chamberlain wrote:
>
> On Apr 11, 2009, at 12:53 AM, Julian Lyndon-Smith wrote:
>
>> Eric Chamberlain wrote:
[snip]
>
> Thank you, that bug does have useful information.
>
> We are working on moving from res_config_odbc to res_config_curl, so
> all asterisk requests go through our django back
On Apr 11, 2009, at 12:53 AM, Julian Lyndon-Smith wrote:
> Eric Chamberlain wrote:
>> Is there any documentation that explains res_config_curl?
>>
>
> We use the 1.4 backported version - it works so well I just can't sing
> it's praises enough. We use it for realtime voicemail and realtime
> queu
Eric Chamberlain wrote:
> Is there any documentation that explains res_config_curl?
>
We use the 1.4 backported version - it works so well I just can't sing
it's praises enough. We use it for realtime voicemail and realtime
queues / queue members.
Have a look at bug #11747 for some docume
Is there any documentation that explains res_config_curl?
Specifically, the format of realtime calls made to the web server and
what the return string for each call should look like?
--
Eric Chamberlain
___
-- Bandwidth and Colocation Provided
