[asterisk-dev] [feature requests]: 'zap answer confirmation info' and 'different clis on forking'

[Christian B]

On Mon, 22 May 2006 12:22:49 -0500
Matthew Fredrickson <creslin at digium.com> wrote:

> Confirmation info is available on Zap channels with signaling
> protocols that support it (such as ISDN, E&M, and a few others).
> Loopstart and kewlstart (FXO and FXS) do not support answer
> confirmation (although sometimes it is signaled by a polarity
> reversal or somethign similar). You probably are probably using zap
> analogue lines without answer supervision.

I'm using this with PRIs. Confirmation works, it's only that the
callee doesn't know when to press '#'.
I've also replied to Peter Beckmans post, unfortunately the thread-tree
has broken and my message was out of the context ->
http://lists.digium.com/pipermail/asterisk-dev/2006-May/020837.html

regards
christian

> 
> Matthew Fredrickson
> 
> On May 16, 2006, at 5:15 PM, Peter Beckman wrote:
> 
> > On Tue, 16 May 2006, Christian B wrote:
> >
> >> Uhm, yes, guess so, at least for the second feature, sorry about
> >> that. But i think i'm not wrong on the first feature, the
> >> solutions you posted will not work(see below).
> >>
> >> No, tried this before(as well as the A()-option), this doesn't work
> >> with the "answer confirmation"-parameter as the macro/playback is
> >> not started before the callee has pressed the '#'(=bridging of the
> >> call).
> >
> >  Maybe it is a Zap issue?  Because I do this now.  The Macro begins
> >  execution only when the caller answers, but I am doing that in an
> > IAX channel, not a Zap channel.
> >
> >  It is also possible that the Zap channel cannot detect pickup,
> > and thus
> >  believes it is picked up as soon as it starts ringing.
> >
> >> The result of your example is both phones are ringing, when i
> >> pickup the
> >> zap-phone i hear nothing, then i press the pound and _after_ this
> >> the macro is started (resp. announcement is played), if i don't
> >> press pound
> >> in the first place, nothing will be executed.
> >
> >  Again, I believe this to be a problem with the Zap channel, which
> > may be
> >  your hardware, or may be the way the channel operates with your
> > PSTN. I
> >  don't believe it to be a broken feature in Asterisk.
> >
> >  What is the exact dial String you are using, options and all?
> >
> > Beckman
> > ----------------------------------------------------------------------- 
> > ----
> > Peter Beckman                                                   
> > Internet Guy
> > beckman at purplecow.com                              
> > http://www.purplecow.com/
> > ----------------------------------------------------------------------- 
> > ----<confirmation.txt>_______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > asterisk-dev mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-dev
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > asterisk-dev mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev