[asterisk-users] Asterisk 'Hosting'

Rushowr rushowr at phreaker.net
Thu Aug 17 13:50:03 MST 2006


-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Douglas
Garstang
Sent: Thursday, August 17, 2006 4:39 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [asterisk-users] Asterisk 'Hosting'

> -----Original Message-----
> From: Douglas Garstang
> Sent: Thursday, August 17, 2006 2:17 PM
> To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
> Subject: RE: [asterisk-users] Asterisk 'Hosting'

**snip**

> > I spent 8+ hours a day, 5+ days per week for over 6 months thinking 
> > how these functions fit within the realm of Asterisk. At every 
> > single turn, after going down every single path, there where 
> > limitations that forced us to backtrack and evaluate a different 
> > approach. A script that could handle call routing, in conjection 
> > with MySQL and stored procedures was the only way to implement our 
> > requirements. The MySQL command had limitations, realtime was way 
> > too resource intensive, unreliable and undocumented and so on. 
> > Yep... i definitely haven't thought about this at all.
> 
> Oops. I almost forgot intra-organisational 4 digit extension dialling. 
> Not just company, but organisational, where a company may have 
> multiple organisational units. It might be possible to hack together a 
> flat intra-business 4 digit extension dial lookup in the native 
> dialplan, but trying to make it a multi-level organisation lookup 
> would be pure hell... unless you farm the task out to a more advanced 
> scripting langauge like python, perl whatever.

>I see the MySQL dial plan command still doesn't support stored procedures
either, 
>unless you hack around with the source.

I've just recently come up against this limitation. Care to share info/code
concerning making stored procs work with the addon?





More information about the asterisk-users mailing list