Also, someone needs to speak up firs. Some clients like Windows Messenger implement silence supression. If they are supposed to send a "nat primer" packet to establish a nat association and the supression features results in no packets sent, the communication will be off till someone speaks up.

-jiri

At 12:01 PM 11/26/2003, Bogdan-Andrei IANCU wrote:

Hi,

Your client must support symmetric RTP for rtpproxy to work. It must send and receive media on the same port - that's the only way to make media to cross the NAT; check if you can configure your client to do so.

Bogdan

Oláh István wrote:

...

Hi!

Rtpproxy and nathelper seems to be working, but I cannot hear any audio. The first client waits for media udp packets on port A, and sends media packets from UDP port A+1. Rtpproxy sends the media packets from the second client to the A+1 port, not A. What have I done wrong?

Thanks Oli

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

-- Jiri Kuthan http://iptel.org/~jiri/

On 26-11 20:43, Olle E. Johansson wrote:

Bogdan-Andrei IANCU wrote:

...

Hi,

Your client must support symmetric RTP for rtpproxy to work. It must send and receive media on the same port - that's the only way to make media to cross the NAT; check if you can configure your client to do so.

Updated the Wiki http://www.voip-info.org/tiki-index.php?page=Portaone+rtpproxy

Anyone that knows which clients support symmetric RTP?

Cisco, Mitel, Grandstream, Windows Messenger, X-Lite, Snom, kphone, ATA.

The vast majority of clients available today support symmetric RTP.

Jan.

On Wednesday 26 November 2003 22:35, Olle E. Johansson wrote:

Jan Janak wrote:

...

The vast majority of clients available today support symmetric RTP.

Been googling on "Symmetric RTP", but can't really find a definition in an draft or RFC. Any help?

Means the UA uses the same socket/port for sending and receiving the RTP stream.

Greets Nils

Look for COMEDIA (Connection oriented media).

Jan.

On 26-11 22:58, Olle E. Johansson wrote:

Nils Ohlmeier wrote:

...

On Wednesday 26 November 2003 22:35, Olle E. Johansson wrote:

...

Jan Janak wrote:

...

The vast majority of clients available today support symmetric RTP.

Been googling on "Symmetric RTP", but can't really find a definition in an draft or RFC. Any help?

Means the UA uses the same socket/port for sending and receiving the RTP stream.

I know now, but there's hints of some additional headers in SDP, the active/passive/both stuff - and I can't find documentation on it...

Writing this, I suddenly realise that I should dig in SDP, not RTP... Back to google...

http://www.voip-info.org/tiki-index.php?page=RTP+Symmetric needs a more detailed and better explanation.

/O

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

At 08:43 PM 11/26/2003, Olle E. Johansson wrote:

Bogdan-Andrei IANCU wrote:

...

Hi, Your client must support symmetric RTP for rtpproxy to work. It must send and receive media on the same port - that's the only way to make media to cross the NAT; check if you can configure your client to do so.

Updated the Wiki http://www.voip-info.org/tiki-index.php?page=Portaone+rtpproxy

Anyone that knows which clients support symmetric RTP?

IMHO, vast majority does, I'm not currently aware of any which does not.

-jiri

Nov 26 16:03:35 sip /usr/local/sbin/ser[1923]: BUG: tcp_main_loop: dead child 18

I get the following crash with my SER saying BUG. Is this solved ?

Kannaiyan

SER is only stable from few seconds to few minutes.

Thanks for your help.

Kannaiyan

----- Original Message ----- From: "Andrei Pelinescu-Onciul" pelinescu-onciul@fokus.fraunhofer.de To: "Kannaiyan Natesan" nkans@lycos.co.uk Cc: "Jiri Kuthan" jiri@iptel.org; serusers@lists.iptel.org Sent: Thursday, November 27, 2003 12:11 AM Subject: Re: [Serusers] SER Crash

On Nov 26, 2003 at 20:40, Kannaiyan Natesan nkans@lycos.co.uk wrote:

...

Nov 26 16:03:35 sip /usr/local/sbin/ser[1923]: BUG: tcp_main_loop: dead child 18

I get the following crash with my SER saying BUG. Is this solved ?

This is not the crash cause. This message appears when ser shutdowns because of some error (a segfault in one process can cause this). The message is pretty misleading and I will probably remove it in the next release.

So can you send the full log?

Andrei

If so there might be a workarround: make sure that you enable the

use_domain

parameter of the registrar module.

This settings solved my problem Andrei. Thanks very much. If you could make a seperate page just for parameter setting for every module it will be very great andrei. If you need my help I can do that for you.

I followed the suggestion given by Jiri for multiple domains as below, I think he missed the param for the registrar module which took my head off.

fragments:

# -- multi-domain modparam("domain", "db_mode", 1) modparam("usrloc|group", "use_domain", 1)modparam("registrar","use_domain",1)

...

if (!is_from_local()) { # check against domain-module table .... /* outbound */ break; };

# our domains ...

if (!www_authorize("", "subscriber")) { # challenge if none or invalid credentials www_challenge("", "0"); break; };

Thanks a lot.

Kannaiyan

----- Original Message ----- From: "Andrei Pelinescu-Onciul" pelinescu-onciul@fokus.fraunhofer.de To: "Kannaiyan Natesan" nkans@lycos.co.uk Cc: "Jiri Kuthan" jiri@iptel.org; serusers@lists.iptel.org Sent: Thursday, November 27, 2003 8:49 AM Subject: Re: [Serusers] SER Crash

On Nov 27, 2003 at 01:18, Kannaiyan Natesan nkans@lycos.co.uk wrote:

...

SER is only stable from few seconds to few minutes.

Does it crash? Do you get a coredump?

Do you use a cvs head config with 0.8.12? If so there might be a workarround: make sure that you enable the

use_domain

parameter of the registrar module.

If it still crashes:

Try to start ser with debugging and loggind to stderr: ser -dd -E -w. -f your.cfg 2>/tmp/log (if you use a config not derived from the standard one, you might have to add log_stderror=yes)

Before starting ser, run "ulimit -c unlimited" and make sure ser is allowed to dump core in the current dir (-w .). If you get the core make a tar.gz with it + ser binaries and sources (if you compiled it by yourself) and either put it on some web/ftp site or send it to serhelp@lists.iptel.org.

Andrei