Re: sipgate problem workaround

Hi Peter,

I can just try to guess what code lines you are talking about (a diff
might have been better). IF (as I assume) the code you commented out
lies in the function msg_make_template_reply() this would make me
wonder, BECAUSE this function is solely used for locally processed
requests (phone -> siproxd) and not requests directed to the provider
(phone -> siproxd -> sipgate). A request beeing processed there will
never be sent to the outside world.

So I would be very interested in details what you found out about
sipgate and using VIA headers for authentication. Once the problem is
fully understood, it should be possible to provide a
"clean" fix/workaround that does not break other things.

Regards,
/Thomas


On 17 Jan, Peter Koellner wrote:
> hi!
> 
> I finally managed to make siproxd work with the zyxel P 2000W, a iptables
> firewall and sipgate.de as sip server. They really use the VIA headers
> for authentication purposes and seem to be to dumb to match against all
> entries. furthermore, they seem to be unwilling to change that.
> 
> I guess it is not totally RFC-compliant, but then the whole protocol
> structure does not seem that thoroughly thought through anyway.
> 
> I simply commented out lines 89-100 (copying VIA-headers) from
> sip_utils.c. I would like to put those lines in a SIPGATE_INSANITY
> #ifdef, or what is the preferred method to add such "specials" to the
> code?
> 
> 

-- 
GnuPG: pub  1024D/87BCDC94 2000-03-19 Thomas Ries <[email protected]>
-      Fingerprint = 13D1 19F5 77D0 4CEC 8D3F  A24E 09FC C18A 87BC DC94
-      Key via pgp.openpkg.org / http://www.ries.ch.vu/87BCDC94.pub
VoIP:  sip:17476691342-rne+wJe3e/u3Jhga2bR/9VaTQe2KTcn/@public.gmane.org | sip:[email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBB6/oJCfzBioe83JQRAljcAKC5wRXbCvjE+Da44QHDFC54yjEZBgCfea4N
BngMe3rZIy6gTkA4sxT02cU=
=Z4Xu
-----END PGP SIGNATURE-----