Re: [Asterisk-java-users] Problem with UniqueId and originate command

[Ben H. <bra...@gm...>]

I tried the bristuff patches, but everything is glommed into one patch
that seems to be incompatible with my sangoma card :-(

I back-ported the 1.85 patch to a fresh 1.0.7, only to realize that it
only affects the OriginateSuccess event or the OriginateFailure event,
and does nothing for the response. This would still be somewhat useful
as the OriginateSuccess/Failure events have the ActionID in it and
that could be used to track the call progress and get the UniqueId.

I checked out the latest manager.c (CVS 1.97) and there is still
nothing for uniqueid in the response.

I'm working on a method to do an originate and listen for the events.
This should be compatible with future versions of asterisk that at
least have the UniqueId in the Originate related events. I'll post
some code and interim * patches when I have it working.

Thanks again for the help and thanks for asterisk-java :-)
- Ben

On 5/16/05, Ben Hencke <bra...@gm...> wrote:
> I was running CVS-v1-0-04/07/05
> I will get 1.0.7 and use the bristuff patches and save some time :-)
> Thanks for the info!
> - Ben
>=20
>=20
> On 5/16/05, Stefan Reuter <sr...@re...> wrote:
> > Hi Ben,
> >
> > sorry for the late response.
> >
> > > There is no UniqueId in the manager response. I did some digging, and
> > > I don't think it is in any released version of asterisk. Googling the
> > > lists, it looks like it was added in manager.c CVS version 1.85, but
> > > Asterisk 1.0.7 only has 1.74.2.1
> > Yes thats what I found too.
> > I am using the bristuff patches from junghanns.net. These include the
> > UniqueId for the Response to OriginateAction.
> >
> > What version of Asterisk are you using? 1.0.7?
> >
> > =3DStefan
> >
> >
> > BodyID:212166270.2.n.logpart (stored separately)
> >
> >
>