.@lists.sip-router.org] De la part de Carsten Bock
> Envoyé : jeudi 22 mai 2014 20:08
> À : Kamailio (SER) - Users Mailing List
> Objet : Re: [SR-Users] RTPProxy timeout
>
> Hi Igor,
>
> it worked pretty well at the time i wrote the patch.
> I've sent the patch to the d
Objet : Re: [SR-Users] RTPProxy timeout
Hi Igor,
it worked pretty well at the time i wrote the patch.
I've sent the patch to the developers of RTPProxy, but i never received a reply
nor comment on the patch. That's why you have to apply the patch yourself.
Kind regards,
Carsten
2014-0
roxy and
> use the timeout functionality?
>
> Regards,
>
> Igor.
>
> -Message d'origine-
> De : sr-users-boun...@lists.sip-router.org
> [mailto:sr-users-boun...@lists.sip-router.org] De la part de Carsten Bock
> Envoyé : jeudi 22 mai 2014 18:25
> À : Kamai
ctionality?
Regards,
Igor.
-Message d'origine-
De : sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] De la part de Carsten Bock
Envoyé : jeudi 22 mai 2014 18:25
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] RTPProxy timeout
Hi Igor,
Hi Igor,
in order to use this feature, you need to apply a patch to RTPProxy.
The patch can be found in the "test" subdirectory in modules/rtpproxy/.
I tried to get the patch into the rtpproxy, but i never got an answer
from the developers of RTPProxy.
Kind regards,
Carsten
2014-05-22 11:21 GMT
Hello,
I can't figure out how the "timeout_socket" should be configured.
I try with the default parameter in the doc:
xmlrpc:http://127.0.0.1:8000/RPC2
I launch RTPProxy like that: -n tcp:127.0.0.1:8000
RTPProxy socket is setup like: "rtpproxy_sock", "udp:127.0.0.1:7722".
It looks like
Hi all,
by the way, the RTPProxy-Repository already contains a fix for this:
author sobomax
Sun, 27 Feb 2011 03:26:31 + (19:26 -0800)
Move initialization of the notification thread after the rtpp_daemon()
call. Threads started before fork(2) may not remain running afterwards.
Reported by
Hi Alexandre,
it took quite a lot of searching, but now it's done. It was a general
RTPProxy/PThread issue.
The problem seems to be, that the PThread is created before the fork
of the main process. Then the Thread waits forever...
Attached an changed main.c + rtpp_defines.h which modifies this
be
Hi Alexandre,
it seem to be a general RTP-Proxy/PThread issue. It seems not to be
related to the XML-RPC notification; the thread, which processes the
timeouts, seems to waits forever... I will check...
Carsten
2011/3/21 Alexandre Abreu :
> Hi Carsten,
>
> After more testing, I just realized tha
Hi,
that is a general Kamailio question.
I think it should work like this:
local_route {
[... do whatever you like here ...]
}
(a route for locally generated requests).
Carsten
2011/3/17 Alexandre Abreu :
> Hi Carsten,
>
> Thank you very much. Finally it is working now.
> Quick question: how
Hi Alexandre,
My version of RTP-Proxy is following:
bock@bock-tde:~/ims/rtpproxy$ ./rtpproxy -v
Basic version: 20040107
Extension 20050322: Support for multiple RTP streams and MOH
Extension 20060704: Support for extra parameter in the V command
Extension 20071116: Support for RTP re-packetizatio
Hi Alexandre,
That is strange:
I run the RTP-Proxy like this (directly from the TAR-File, i sent you)
and Kamailio with attached config-file.
bock@bock-tde:~/ims/rtpproxy$ sudo ./rtpproxy -T 10 -f -F -i -l
127.0.0.1 -s udp:*:2 -d DBUG -n tcp:127.0.0.1
rtpproxy: Timer started.
INFO:main: rtpp
Hi Alexandre,
i don't have a clue, what is going wrong there. The timeout socket,
you provide, must not necessarily point to the Kamailio-XML-RPC-Port,
in my test-cases it just pointed anywhere... (i hope it does not mess
up the XML-RPC Process of Kamailio if you connect there and do
nothing).
I a
Hi,
Sorry for confusion:
You will have to define a Timeout socket, when starting RTP-Proxy (-n,
may be invalid):
bock@bock-tde:~/ims/sr-rtpp/sip-router/modules/rtpproxy/test$ cat
./exec_rtpproxy.txt
./rtpproxy -T 10 -f -F -i -l 127.0.0.1 -s udp:*:2 -d DBUG -n tcp:127.0.0.1
Recent Versions of
14 matches
Mail list logo
