Hi Carsten,
Patch applied. It works now.
Thanks,
Alexandre.
-Mensagem original-
De: kaiserbo...@googlemail.com [mailto:kaiserbo...@googlemail.com] Em nome
de Carsten Bock
Enviada em: terça-feira, 22 de março de 2011 08:00
Para: Alexandre Abreu
Cc: sr-users@lists.sip-router.org; RTPproxy
Hi Carsten,
After more testing, I just realized that the notification works only if I
use "-f" parameter in RTPPROXY. If I omit this parameter (to run in
background mode), the session timeout but there's no notification sent
(BYE). Why's that?
Thanks,
Alexandre.
-Mensagem original-
De: A
Hello Carsten.
Still no lucky. I just moved the whole rtpproxy/ directory into 3.1 branch
and recompiled and then changed my script to use
rtpproxy_offer()/rtpproxy_answer().
Look:
Mar 15 14:04:38 devel rtpproxy[29111]: INFO:handle_command: new session
e2361a59b4588d51, tag ed382a18;1 requested,
Hi Carsten,
Thank you very much. Finally it is working now.
Quick question: how do you account the BYE sent by the proxy? Since the BYE
itself does not transverse the script...
Thanks,
Alexandre
-Mensagem original-
De: kaiserbo...@googlemail.com [mailto:kaiserbo...@googlemail.com] Em nom
Carsten,
Here it goes:
[root@devel rtpproxy-carsten]# ./rtpproxy -T 10 -f -F -i -l 192.168.200.90
-s udp:*:7722 -d DBUG ERR INFO -n tcp:127.0.0.1:7723
INFO:main: rtpproxy started, pid 22495
rtpproxy: >>> Running Timeout-Process
DBUG:handle_command: received command "22428_8 Uc0,8,101 080b5d23d16
Carsten,
Indeed. Very strange.
Are we running the same RTPPROXY version? How can you start using '-n
tcp:127.0.0.1' without specifying a port?
[root@devel rtpproxy-carsten]# ./rtpproxy -T 10 -f -F -i -l 192.168.200.90
-s udp:*:7722 -d DBUG ERR INFO -n tcp:127.0.0.1
rtpproxy: can't parse host:por
Hi Carsten,
Even with your RTPPROXY tarball I was unable to get this working. Session
remains after RTPPROXY timeout.
I am using KAMAILIO 3.1 branch from GIT and as I told you, I moved the
rtpproxy/ from GIT-MASTER to the Kamailio branch (waiting your backport). Is
there anything else regarding th
Hi Carsten,
I just tested again changing the port 8000 to point to another port. Still
does not work. I am waiting your RTPPROXY tarball to test again.
Thanks,
Alexandre.
-Mensagem original-
De: kaiserbo...@googlemail.com [mailto:kaiserbo...@googlemail.com] Em nome
de Carsten Bock
Enviad
Hello Carsten,
If you use "-n tcp:127.0.0.1" without port you get:
[root@devel ~]# rtpproxy -T 10 -F -i -l 192.168.200.90 -s udp:127.0.0.1 7722
-n tcp:127.0.0.1 -d DBUG
rtpproxy: can't parse host:port in TCP address
rtpproxy: can't start notification thread
As I wrote in my previous mail, I am u
