26 Nov
2003
26 Nov
'03
11:40 a.m.
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
26 Nov
26 Nov
12:01 p.m.
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(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
1:51 p.m.
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:
--
Jiri Kuthan http://iptel.org/~jiri/
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(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers 
8:43 p.m.
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?
/Olle
8:47 p.m.
On 26-11 20:43, Olle E. Johansson wrote:
Bogdan-Andrei IANCU wrote:
Cisco, Mitel, Grandstream, Windows Messenger, X-Lite, Snom, kphone,
ATA.
The vast majority of clients available today support symmetric RTP.
Jan.
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?
10:35 p.m.
Jan Janak wrote:
On 26-11 20:43, Olle E. Johansson wrote:
Been googling
on "Symmetric RTP", but can't really find a definition in an
draft or RFC. Any help?
/O
Bogdan-Andrei IANCU wrote:
Cisco, Mitel, Grandstream, Windows Messenger, X-Lite, Snom, kphone,
ATA.
The vast majority of clients available today support symmetric RTP. 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? 
10:37 p.m.
On Wednesday 26 November 2003 22:35, Olle E. Johansson wrote:
Jan Janak wrote:
Means the UA uses the same socket/port for sending and receiving the RTP
stream.
Greets
Nils
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?
10:58 p.m.
Nils Ohlmeier wrote:
On Wednesday 26 November 2003 22:35, Olle E. Johansson
wrote:
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
Jan Janak wrote:
Means the UA uses the same socket/port for sending and receiving the RTP
stream. 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?
27 Nov
27 Nov
1:54 p.m.
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:
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(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Jan Janak wrote:
Means the UA uses the same socket/port for sending and receiving the RTP
stream. 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?
2:57 p.m.
Jan Janak wrote:
Look for COMEDIA (Connection oriented media).
Thank you, Jan!
For those of you that want to learn more:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-comedia-05.txt
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/12…
/Olle
26 Nov
26 Nov
8:56 p.m.
At 08:43 PM 11/26/2003, Olle E. Johansson wrote:
Bogdan-Andrei IANCU wrote:
IMHO, vast majority does, I'm not currently aware of any which does not.
-jiri
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? 
9:40 p.m.
New subject: [Serusers] SER Crash
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
27 Nov
27 Nov
1:11 a.m.
New subject: [Serusers] SER Crash
On Nov 26, 2003 at 20:40, Kannaiyan Natesan <nkans(a)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
2:18 a.m.
New subject: [Serusers] SER Crash
SER is only stable from few seconds to few minutes.
Thanks for your help.
Kannaiyan
----- Original Message -----
From: "Andrei Pelinescu-Onciul" <pelinescu-onciul(a)fokus.fraunhofer.de>
To: "Kannaiyan Natesan" <nkans(a)lycos.co.uk>
Cc: "Jiri Kuthan" <jiri(a)iptel.org>rg>; <serusers(a)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(a)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
9:49 a.m.
New subject: [Serusers] SER Crash
On Nov 27, 2003 at 01:18, Kannaiyan Natesan <nkans(a)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(a)lists.iptel.org.
Andrei
2:27 p.m.
New subject: [Serusers] SER Crash
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(a)fokus.fraunhofer.de>
To: "Kannaiyan Natesan" <nkans(a)lycos.co.uk>
Cc: "Jiri Kuthan" <jiri(a)iptel.org>rg>; <serusers(a)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(a)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(a)lists.iptel.org.
>
>
> Andrei
>
7464
days inactive
7465
days old
16 comments
8 participants
participants (8)
-
Andrei Pelinescu-Onciul -
Bogdan-Andrei IANCU -
Jan Janak -
Jiri Kuthan -
Kannaiyan Natesan -
Nils Ohlmeier -
Olle E. Johansson -
Oláh István