Fwd: [Asterisk-Users] Having major issues with TDM2400

[C F]

---------- Forwarded message ----------
From: C F <shmaltz at gmail.com>
Date: Jan 2, 2006 8:17 PM
Subject: Re: [Asterisk-Users] Having major issues with TDM2400
To: BJ Weschke <bweschke at gmail.com>


Here are my results from the test, first the dialplan used:

================begin dialplan example==================
[default]
exten => 698,1,Noop()
exten => 698,2,Dial(Zap/g1/1732xxxxxxx&Zap/g2/1908xxxxxxx,,M(mtest))
;numbers where changed to xxxxxxxx for privacy reasons nothing to do
with pattern matching

[macro-mtest]
exten => s,1,Noop()
exten => s,2,Read(KEY|goodbye|1) ;read one digit while playing the goodbye file
exten => s,3,GotoIf($[${KEY} = 1]?50) ;if it's one then goto pri 50
exten => s,4,Noop()
exten => s,5,Goto(1000) ; else just end this macro (I know that it
would end here without this pri as well)

exten => s,50,Noop()
exten => s,51,Set(MACRO_RESULT=CONGESTION) ;one was pressed so just
play congestion app dial
exten => s,52,Goto(1000)
exten => s,1000,Noop()
===========end dialplan example==================

When I called extension 698, both phones (the 732 and the 908) rang as
soon as I picked up one (i.e. the line was answered), ringing to the
other stopped (ouch). So you were right, I have to post this back to
the list to clarify that it will only work consecutive and not in
parallel.
BTW, I used 2 PRIs in this case not POTS, but it shouldn't make any
difference, since answer is what we are looking for, and we got it.


On 1/2/06, BJ Weschke <bweschke at gmail.com> wrote:
>  Correct. state==AST_STATE_UP != the two call legs (caller and callee)
> being bridged together.
>
>  wait_for_answer is waiting for the first channel to switch to state
> AST_STATE_UP and then it progresses with Macro which then may or may
> not result in the channel actually becoming bridged with the original
> caller.
>
> On 1/2/06, C F <shmaltz at gmail.com> wrote:
> > And as soon as one answers it is NOT bridged (because Macro is first
> > executing), and this fact (that it is not bridged), dosn't change
> > anything?
> >
> > On 1/2/06, BJ Weschke <bweschke at gmail.com> wrote:
> > >  I believe all the other channels get dumped as soon as THAT channel
> > > answers. There's a method inside of app_dial called wait_for_answer
> > > for which the return value is only one channel. It's thunderdome. Many
> > > can enter, only one leaves.  :)
> > >
> > >  Anyway, wait_for_answer must return that one channel pointer before
> > > Maco execution begins.
> > >
> > > On 1/2/06, C F <shmaltz at gmail.com> wrote:
> > > > I can't remember if I actualy tested it, but my understanding is that
> > > > the other phones in an extension that implements the M option should
> > > > still ring even though one answered already, if it is not yet bridged.
> > > > I might be wrong though, please let me know. The only way I realy
> > > > implemented it is with consecutive dialing (pri 1 dials phone1, and
> > > > pri 2 dials phone2 if in the M macro the right key wasn't pressed).
> > > > Now writing all this I can tell you I actualy NEVER tested it on
> > > > multiple channels that are dialed in the same Dial command. So I don't
> > > > really know.
> > > > I guess you are right that the Macro execution doens't start until
> > > > THAT channel answered for THAT channel, but what about the other
> > > > channels? do they get hung up on with the start of the Macro on ANY of
> > > > the channels? or only after bridging?
> > > >
> > > >
> > > >
> > > > On 1/1/06, BJ Weschke <bweschke at gmail.com> wrote:
> > > > >  Does this work? Looking at app_dial.c, it looks like Macro execution
> > > > > on a channel doesn't begin until it has found THE channel that
> > > > > answered first. I could be wrong, and if I am I'd be interested to
> > > > > know it, because then I know where to look to borrow that piece of
> > > > > functionality for forked dialing/ivr in app_followme.c :)
> > > > >
> > > > > ---------- Forwarded message ----------
> > > > > From: C F <shmaltz at gmail.com>
> > > > > Date: Jan 1, 2006 9:23 PM
> > > > > Subject: Re: [Asterisk-Users] Having major issues with TDM2400
> > > > > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > > > > <asterisk-users at lists.digium.com>
> > > > >
> > > > >
> > > > > It will still work using the M option in the dial command, as I wrote
> > > > > before, also look up the follwoing:
> > > > > http://www.voip-info.org/wiki-asterisk+cmd+dial
> > > > > http://bugs.digium.com/view.php?id=5574
> > > > > Using some creativity you can give your client what you promised plus.
> > > > >
> > > > >
> > > > > --
> > > > > Bird's The Word Technologies, Inc.
> > > > > http://www.btwtech.com/
> > > > >
> > > >
> > >
> > >
> > > --
> > > Bird's The Word Technologies, Inc.
> > > http://www.btwtech.com/
> > >
> >
>
>
> --
> Bird's The Word Technologies, Inc.
> http://www.btwtech.com/
>