Hi,

I have rtpproxy 1.2.1 working with kamailio 3.1.0 using the nathelper
interface. Everything seems to work O.K. but I get a delete request
failed message - I guess when I call unforce_rtp_proxy on a BYE.

My command line for rtpproxy is:
/usr/local/sbin/rtpproxy -u rtpproxy -s udp:localhost:7722 -r
/var/spool/rtpproxy -m 8000 -M 8100 -a -i -S /tmp -F -l x.x.x.x -R -P -d
INFO

In the following log I see that there is an earlier 'handle_delete:
forcefully deleting session'  message. Am I doing something wrong?

Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: new session
a86c4138-5275...@10.60.5.11, tag 1e0e6920b3951072o0;1 requested, type strong
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: new session on
a port 9820 created, tag 1e0e6920b3951072o0;1
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_copy: starting
recording RTP session on port 9820
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_copy: starting
recording RTP session on port 0
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: pre-filling
caller's address with 10.60.5.10:9128
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: adding strong
flag to existing session, new=1/0/0
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: lookup on
ports 9820/0, session timer restarted
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: pre-filling
caller's address with 10.1.39.12:9820
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: adding strong
flag to existing session, new=1/0/0
Dec  2 13:40:39 mc2 rtpproxy[11689]: INFO:handle_command: lookup on
ports 9820/0, session timer restarted
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:handle_command: lookup on
ports 9820/9610, session timer restarted
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:handle_command: pre-filling
callee's address with 10.1.39.198:8008
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:handle_command: lookup on
ports 9820/9610, session timer restarted
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:handle_command: pre-filling
callee's address with 10.1.39.12:9610
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:rxmit_packets: caller's
address filled in: 10.60.5.10:9128 (RTP)
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:rxmit_packets: guessing RTCP
port for caller to be 9129
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:rxmit_packets: callee's
address filled in: 10.1.39.198:8008 (RTP)
Dec  2 13:40:43 mc2 rtpproxy[11689]: INFO:rxmit_packets: guessing RTCP
port for callee to be 8009
Dec  2 13:40:54 mc2 rtpproxy[11689]: INFO:handle_delete: forcefully
deleting session 1 on ports 9820/9610
Dec  2 13:40:54 mc2 rtpproxy[11689]: INFO:remove_session: RTP stats: 373
in from callee, 374 in from caller, 747 relayed, 0 dropped
Dec  2 13:40:54 mc2 rtpproxy[11689]: INFO:remove_session: RTCP stats: 0
in from callee, 0 in from caller, 0 relayed, 0 dropped
Dec  2 13:40:54 mc2 rtpproxy[11689]: INFO:remove_session: session on
ports 9820/9610 is cleaned up
Dec  2 13:40:54 mc2 rtpproxy[11689]: INFO:handle_command: delete request
failed: session a86c4138-5275...@10.60.5.11, tags
974c5a2e80f32102i0/1e0e6920b3951072o0 not found

_______________________________________________
Users mailing list
Users@rtpproxy.org
http://lists.rtpproxy.org/mailman/listinfo/users

Reply via email to