Re: Debug mode changing siproxd behaviour ??

--===============3407392610560186354==
Content-Type: MULTIPART/SIGNED; MICALG=pgp-sha1;
	PROTOCOL="application/pgp-signature";
	BOUNDARY="-1463810047-1957747793-1270459087=:4457"

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

Hello =C9tienne,

You should concentrate on the rtp_proxy stuff in the log.

- Can siproxd properly allocate and bind to the RTP ports?
- Are sufficient RTP ports configured (siproxd.cofn)
- Do you see any ERROR or WARNINGs in the log?

Also, you should look at a possible differences in the log of the
working (non-daemonized) and non-working (daemonized) configuration.

You may also correlate the siproxd log with your TCPDUMP traces, i.e. is
the RTP audio sent to the correct (expected by siproxd) ports?

You mention an ICMP port unreachable - what causes this? This *might*
happen if an UA does send RTP traffic to a port that is either:
- not allowed by the packet filter
- nobody is listening on that port
This could indicate issues with symmetric RTP (that should be fixed in a
later version of siproxd).

Other questions:
- Does your UA (phone) use any NAT helpers like STUN or other
  mechanisms? If so, DISABLE.

This should give you some hints where to start.

Regards,
/Thomas

On  3 Apr, =C9tienne wrote:
> On Fri, Apr 02, 2010 at 11:18:09PM +0200, Thomas Ries wrote:
>=20
> Hi Thomas,
>=20
>> 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.
>=20
> I was expecting this, but on a lightweight gateway with no build
> capabilities, I'm pretty much stuck with what is available in OpenBSD
> ports, especially with no other OpenBSD platform at hand in the
> immediate future. I'll certainly look forward to install the latest
> siproxd available, though.
> =20
>> Second, siproxd allows logging (incl. debug information) via TCP
>> connection - even if runnign in background;
>> check the 'debug_port' config option.
>=20
> Thank you, I now have a log. Lots of stuff in it, any advice on what I
> should be looking for, considering the symptoms given earlier ?
>=20
> Thanks a lot, and happy Easter.
>=20


---1463810047-1957747793-1270459087=:4457
Content-Type: APPLICATION/PGP-SIGNATURE

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

iD8DBQFLuarPB2xLpFxU+GURAlgTAJ0UAkXuM2s4hIYkTHcSand/yTgXlACgk64Q
svhCLkTppX0EIL4ay8xBGls=
=ldUM
-----END PGP SIGNATURE-----

---1463810047-1957747793-1270459087=:4457--


--===============3407392610560186354==
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
--===============3407392610560186354==
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

--===============3407392610560186354==--