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

[Peter Beckman]

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/
---------------------------------------------------------------------------
-------------- next part --------------
May 16 18:39:32 VERBOSE[688] logger.c:     -- Called 88888 at sipproxy.domain.com
May 16 18:39:32 VERBOSE[688] logger.c:     -- Requested transfer capability: 0x00 - SPEECH
May 16 18:39:32 VERBOSE[688] logger.c:     -- Called G1c/0023777777
May 16 18:39:33 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:39:33 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:39:33 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:39:33 VERBOSE[688] logger.c:     -- Zap/124-1 is proceeding passing it to Zap/14-1
May 16 18:39:33 VERBOSE[688] logger.c:     -- Zap/124-1 is ringing
May 16 18:39:34 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:39:36 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:39:40 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:39:48 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:40:04 VERBOSE[688] logger.c:     -- SIP/sipproxy.domain.com-80f6 is ringing
May 16 18:40:13 VERBOSE[688] logger.c:     -- Zap/124-1 answered Zap/14-1
May 16 18:40:13 VERBOSE[688] logger.c:     -- Playing 'ping' (language 'en')
May 16 18:40:14 VERBOSE[688] logger.c:     -- Attempting native bridge of Zap/14-1 and Zap/124-1
-------------- next part --------------
_______________________________________________
--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