Re: [Asterisk-java-users] asterisk java and astmanproxy

[Aaron E. <aar...@gm...>]

Hey Ga=EBtan,

I would like to get my hands on the patch if it means I can use
asterisk-java in combination with astmanproxy.

I really like using asterisk-java but would like to avoid implementing
my own proxy. Further, astmanproxy seems to have the feature set we
are looking for...

thx,
aaron

On 10/1/07, Ga=EBtan Minet <gm...@ea...> wrote:
> Hi
>
> Indeed I ran into this problem with astmanproxy some weeks ago too.
>
> IIRC I saw at least those problems:
>
> - the protocol identifier bug you solved
> - that actionId problem. ActionId is only ignored during
> authentication because this is handled internally by astmanproxy.
> Further comunication is ok.
> - the credentials are not case sensitive, astmanproxy converts the
> username and password to lowercase from client to proxy and from
> proxy to asterisk.
>
> I ended modifying the astmanproxy sources to have it work. Changes
> are minor.
> This is not the place to discuss this but if someone needs it I'll
> hapily send him the patch.
>
>
> Regards
>
> Gaetan
>
>
> On 02 Aug 2007, at 00:04, Stefan Reuter wrote:
>
> > Hi,
> >
> > astmanproxy does not honor the ActionId attribute.
> > The following is a log of an attempt to connect:
> >
> > root@samael:~# ngrep port 1234
> > interface: eth0 (10.13.0.0/255.255.255.0)
> > filter: (ip or ip6) and ( port 1234 )
> > ####
> > T 10.13.0.101:1234 -> 10.13.0.57:33060 [AP]
> >   Asterisk Call Manager Proxy/1.21..
> >
> > ##
> > T 10.13.0.57:33060 -> 10.13.0.101:1234 [AP]
> >   action: Challenge..actionid: 1246657009_0#..authtype: MD5....
> >
> > ##
> > T 10.13.0.101:1234 -> 10.13.0.57:33060 [AP]
> >   Response: Success
> >
> > #
> > T 10.13.0.101:1234 -> 10.13.0.57:33060 [AP]
> >   ..
> >
> > #
> > T 10.13.0.101:1234 -> 10.13.0.57:33060 [AP]
> >   Challenge: 168169277
> >
> > ##
> > T 10.13.0.101:1234 -> 10.13.0.57:33060 [AP]
> >   ....
> >
> > ####
> >
> > Asterisk-Java sends an actionId (1246657009_0#) but astmanproxy drops
> > it. Therefore Asterisk-Java has no chance to relate the response to
> > the
> > request and you receive the timeout exception.
> >
> >> This appears to be a timing issue and so may not appear on all
> >> systems
> >> or everytime the call is run.
> >> I'm doing further investigation to try and create a patch.
> >>
> >> If anyone knows how to lodge a support request on astmanproxy I
> >> would be
> >> interested.
> >
> > No I don't. I had a conversation with david some time ago but the
> > without success getting these things fixed.
> > I think astmanproxy would need some serious design changes to be
> > usable
> > for a larger audience...
> >
> > =3DStefan
> >
> > P.S. I've updated the latest version of Asterisk-Java to accept the
> > protocol identifier but that won't help much until at least the action
> > id issue is resolved.
> >
> > --
> > reuter network consulting
> > Neusser Str. 110
> > 50760 Koeln
> > Germany
> > Telefon: +49 221 1305699-0
> > Telefax: +49 221 1305699-90
> > E-Mail:  ste...@re...
> > Jabber:  ste...@re...
> >
> > Steuernummern 215/5140/1791 USt-IdNr. DE220701760
> >
> > ----------------------------------------------------------------------
> > ---
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a
> > browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Asterisk-java-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/asterisk-java-users
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Asterisk-java-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/asterisk-java-users
>