Re: [Asterisk-java-users] Originate and multiple variables

[Eduard M. <ed...@ba...>]

Another possible cause:
I'm doing Originate to a local channel, like Local@/XXXXX@outcoming
Originate extension then is s, context [connected]
In extensions I have=20
[outcoming]
exten =3D> _XXXX,1,UserEvent(LocalChannel)
exten =3D> _XXXX,2,Dial(Zap/g2/${EXTEN})
exten =3D> _XXXX,3,Hangup
[connected]

exten =3D> s, 3,UserEvent(Foo| callId: ${callId})

I'm doing this things because with the LocalChannel userEvent I have the re=
al=20
name of the local channel in my java application and I can cancel the=20
originate (hanging up this channel) and when is connected, Foo tells me the=
=20
real zap channel answered.
OriginateSuccesfulEvent doesn't tell me the real channel, and with originat=
e=20
action with a Zap group channel I don't have the channel until is answered=
=20
(so I can't cancel the originate while is ringing)

El Jueves, 6 de Julio de 2006 10:05, Stefan Reuter escribi=F3:
> Edu wrote:
> > As commented in Asterisk wiki, Originate syntax and variables differ in
> > 1.0 and 1.2, so I think that there is the problem so only want to confi=
rm
> > this behaviour :)
>
> Asterisk-Java takes this into account, so it usually works with 1.0 and
> 1.2. Does Asterisk-Java recognize your production server as 1.0?
> (according to the logs)
>
> =3DStefan