[asterisk-users] UK -999 dialing issue
Tilghman Lesher
tilghman at mail.jeffandtilghman.com
Thu Feb 14 11:31:01 CST 2008
On Thursday 14 February 2008 07:55:08 SIP wrote:
> Gordon Henderson wrote:
> > On Thu, 14 Feb 2008, Phil Knighton wrote:
> >> [softoption-zap]
> >>
> >> exten => _0[123456789].,1,NoOp(${EXTEN})
> >> exten => _0[123456789].,2,Dial(Zap/g0/${EXTEN},,j)
> >> exten => _0[123456789].,103,Dial(IAX2/Gradwell/44${EXTEN:1},,)
> >> exten => _00[1-9].,1,Dial(IAX2/Gradwell/${EXTEN:2},,)
> >> exten => _90[123456789].,1,Dial(IAX2/Gradwell/44${EXTEN:2},,)
> >
> > OMG!!!
> >
> > You're selecting 2 different output channels depending on the number
> > dialled!!!
> >
> > (UK or international)...
> >
> > That's ... LCR!!!
> >
> > In ... Dialplan!!!
> >
> > And according to a recent thread, that's like ... impossible, not
> > recommended, really really hard, with databases and external hardware
> > required, etc. (!!!)
>
> Not impossible. I think the explanation was that it was ugly. And...
> well... that is. Now, imagine sorting through a list of 500,000
> possible dialing prefixes (something we have) instead of 3 or 4. Tell me
> that would be clean and pretty without a DB lookup.
>
> Anyone can LCR 2 routes in a dialplan, but that's hardly an effective
> example of LCR.
Right, and as soon as you add func_odbc to the mix, it becomes easy to query
such a database in the dialplan.
--
Tilghman
More information about the asterisk-users
mailing list