16 Mar
2011
16 Mar
'11
6:03 p.m.
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:*:22222 -d DBUG -n tcp:127.0.0.1
rtpproxy: Timer started.
INFO:main: rtpproxy started, pid 4203
[... Kamailio connects to RTP-Proxy...]
DBUG:handle_command: received command "4259_8
UAc98,97,99,104,3,0,8,9,96 56f0f83a-5373-46a1-b6f6-9ce2f93e68d5
195.71.4.203 4008 5371f039-40d0-4944-aae7-6f75071a2f8c;1"
INFO:handle_command: new session 56f0f83a-5373-46a1-b6f6-9ce2f93e68d5,
tag 5371f039-40d0-4944-aae7-6f75071a2f8c;1 requested, type strong
INFO:handle_command: new session on a port 45508 created, tag
5371f039-40d0-4944-aae7-6f75071a2f8c;1
INFO:handle_command: pre-filling caller's address with 195.71.4.203:4008
DBUG:doreply: sending reply "4259_8 45508 127.0.0.1
"
DBUG:handle_command: received command "4259_9 LAc98,96
56f0f83a-5373-46a1-b6f6-9ce2f93e68d5 195.71.4.203 4000
5371f039-40d0-4944-aae7-6f75071a2f8c;1
9915df0c-30fc-49c5-aa8a-c86b4242c094;1
xmlrpc:http://localhost:8000/RPC2"
INFO:handle_command: lookup on ports 45508/45238, session timer restarted
INFO:handle_command: setting custom timeout handler
(xmlrpc:http://localhost:8000/RPC2)
INFO:handle_command: pre-filling callee's address with 195.71.4.203:4000
DBUG:doreply: sending reply "4259_9 45238 127.0.0.1
"
INFO:process_rtp: session timeout
ERR:rtpp_notify_schedule: XMLRPC xmlrpc:http://localhost:8000/RPC2
INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: session on ports 45508/45238 is cleaned up
ERR:do_timeout_notification: Timeout socket: xmlrpc:http://localhost:8000/RPC2
And it works for me:
U 2011/03/16 16:50:14.350721 127.0.0.1:5060 -> 127.0.0.1:15061
BYE sip:2@127.0.0.1:15061;ob SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK06e9.245e2dd7.0.
To: sip:2@localhost;tag=5371f039-40d0-4944-aae7-6f75071a2f8c.
From: sip:1@localhost;tag=9915df0c-30fc-49c5-aa8a-c86b4242c094.
CSeq: 7905 BYE.
Call-ID: 56f0f83a-5373-46a1-b6f6-9ce2f93e68d5.
Content-Length: 0.
User-Agent: kamailio (3.2.0-dev2 (x86_64/linux)).
Max-Forwards: 70.
.
U 2011/03/16 16:50:14.350801 127.0.0.1:5060 -> 127.0.0.1:15060
BYE sip:1@127.0.0.1:15060;transport=UDP;ob SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK06e9.345e2dd7.0.
To: sip:1@localhost;tag=9915df0c-30fc-49c5-aa8a-c86b4242c094.
From: sip:2@localhost;tag=5371f039-40d0-4944-aae7-6f75071a2f8c.
CSeq: 7905 BYE.
Call-ID: 56f0f83a-5373-46a1-b6f6-9ce2f93e68d5.
Content-Length: 0.
User-Agent: kamailio (3.2.0-dev2 (x86_64/linux)).
Max-Forwards: 70.
.
[...]
Maybe, you can add some more debug-info from RTP-Proxy...
And can you verify, that the RTP-Proxy is not trying to send the request?
Kind regards,
Carsten
2011/3/16 Alexandre Abreu <alexandre.abreu(a)redt.com.br>br>:
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 this feature that should also should be moved
(beyond rtpproxy/)?
Thanks,
Alexandre
--
Carsten Bock
http://www.ng-voice.com
mailto:carsten@ng-voice.com