Re: Debug mode changing siproxd behaviour ??

--===============4419820385205989116==
Content-Type: MULTIPART/SIGNED; MICALG=pgp-sha1;
	PROTOCOL="application/pgp-signature";
	BOUNDARY="-1463810047-1714636915-1270243089=:4457"

---1463810047-1714636915-1270243089=:4457
Content-Type: TEXT/PLAIN; CHARSET=iso-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: INLINE

Hello =C9tienne,

First you should really consider upgrading siproxd to the current
version (which meanwhile is 0.8.0 !). Quite a number of changes (and
fixes) have been made that include improvements in RTP processing.

Second, siproxd allows logging (incl. debug information) via TCP
connection - even if runnign in background;
check the 'debug_port' config option.
This should allow you to catch a log the situation.

Good luck and best regards,
/Thmas


On  2 Apr, =C9tienne wrote:
> Hello list,
>=20
> This is the first time I try to use siproxd, and that is on OpenBSD-4.6
> with siproxd-0.5.13p0 from the ports. I'm using the software on my
> gateway to the Internet, and a Nokia N79 as a client (I'm not sure
> that has any impact here).
>=20
> I was in deep trouble trying to place a phone call, with the typical
> error of "the call is placed but I can't hear nothing". To be more
> accurate, testing it by calling the voicemail of the service, I could
> hear like half of a second of the welcome message, then nothing.
> Trying to debug this, I ran siproxd in the foreground, and suspecting
> the firewall (PF) to be badly configured, I used tcpdump to get an
> idea of what was going in and out on both sides of my gateway.
>=20
> Surprisingly, with this setup, I was unable to reproduce the problem,
> everything worked like a charm. As soon as I switched back "daemonize"
> to "1", the problem happened again. As a result, the only log I can
> report is when the problem does not occur. :-( However, when running
> siproxd daemonized, I can see in the network capture that just after
> the beginning of the call, the gateway sends ICMP "port unreachable"
> messages to both the client and the server for every single RTP packet
> received. This doesn't happen when running the proxy in the foreground.
> I have reproduced both case (and got the same results) a couple of
> times before posting this.
>=20
> What can I do ? Thanks for your interest in this.
>=20

---1463810047-1714636915-1270243089=:4457
Content-Type: APPLICATION/PGP-SIGNATURE

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

iD8DBQFLtl8RB2xLpFxU+GURAqbCAJ4nhHGaeVUDkTCbnQHi/Ayu2A0mrACeIHPn
pjly89pdNOGcYNPoorKwPf4=
=Wc1n
-----END PGP SIGNATURE-----

---1463810047-1714636915-1270243089=:4457--


--===============4419820385205989116==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--===============4419820385205989116==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Siproxd-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/siproxd-users

--===============4419820385205989116==--