On December 4, 2004 08:43 am, Rich Adamson wrote:
> Looks like the command is documented in the current config samples.
Yeah I see that now. :-)
> Since the comments use words like "doesn't work with all telcos",
> could this have something to do with detecting busy when a call
> reaches a desti
On Sat, 4 Dec 2004, Rich Adamson wrote:
> > The mind boggles -- PRI is *always* out of band.
>
> Looks like the command is documented in the current config samples.
>
> I'm not knowledgable/experienced (as yet) on where it is actually used,
> but just reading the comments in the config sample le
> On December 3, 2004 03:36 pm, Andrew Kohlsmith wrote:
> > exten => 1234,1,Dial(Zap/g1/5551234,,g)
> > exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is
> > ${DIALSTATUS})
> >
> > Why, if 5551234 is busy, is DIALSTATUS set to CHANUNAVAIL? Should it not
> > be BUSY?
>
> Brian W
On December 3, 2004 03:36 pm, Andrew Kohlsmith wrote:
> exten => 1234,1,Dial(Zap/g1/5551234,,g)
> exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is
> ${DIALSTATUS})
>
> Why, if 5551234 is busy, is DIALSTATUS set to CHANUNAVAIL? Should it not
> be BUSY?
Brian West pointed me at
Just throwing this out here, hopefully someone can tell me why.
*CLI> show version
Asterisk CVS-HEAD-11/17/04-10:16:38 built by [EMAIL PROTECTED] on a i686
running
Linux
Zap/g1 is pri_cpe to Bell Canada
5551234 is a normal POTS line I have busied out (handset offhook)
exten => 1234,1,Dial(Zap/
