Hello, the code shows that is added for U command, if to-tag exists:
https://github.com/kamailio/kamailio/blob/master/modules/rtpproxy/rtpproxy.c#L2692 Can you edit the rtpproxy.c and add a log message (e.g., using LM_ERR("..."); ) there and is it is printed by kamailio? Cheers, Daniel On 17/10/15 20:57, Arun Kumar wrote: > Hi > > Rtp Session timeout notification is not working , we tried with > kamailio 4.2 with rtpproxy 2.0 / 1.3 beta/1.2 releases , i think > kamailio rtpproxy is not submitting session timeout socket to rtpproxy > > > kamailio 4.2.0 > ----------------------------------- > > modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722 > <http://127.0.0.1:7722>") > modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:5060/RPC") > > ............... > rtpproxy_manage(); > ................ > > > RtpProxy > ------------------------- > RTPProxy 2.0 > RTPProxy 1.3 Beta with patch given by /Daniel/ > RTPProxy 1.2 > > rtpproxy -F -s udp:127.0.0.1:7722 <http://127.0.0.1:7722> -d DBUG > -f -i -T 10 > > > RTPRoxy Log > ---------------------------------------------------- > DBUG:get_command: received command "4242_9 Uc0,8,101 2479e562440c023d > 192.168.1.103 6074 5410ef73;1" > INFO:handle_command: new session 2479e562440c023d, tag 5410ef73;1 > requested, type strong > INFO:handle_command: new session on a port 45984 created, tag 5410ef73;1 > INFO:handle_command: pre-filling caller's address with > 192.168.1.103:6074 <http://192.168.1.103:6074> > DBUG:doreply: sending reply "4242_9 45984 > " > DBUG:get_command: received command "4242_10 Lc0,101 2479e562440c023d > 192.168.1.102 4002 5410ef73;1 ADqH-A-mLLN0th2gGoopYMK1cy.-ozDf;1" > INFO:handle_command: lookup on ports 45984/36756, session timer restarted > INFO:handle_command: pre-filling callee's address with > 192.168.1.102:4002 <http://192.168.1.102:4002> > DBUG:doreply: sending reply "4242_10 36756 > " > INFO:rxmit_packets: callee's address latched in: 192.168.1.102:4002 > <http://192.168.1.102:4002> (RTP) > INFO:rxmit_packets: callee's address latched in: 192.168.1.102:4003 > <http://192.168.1.102:4003> (RTCP) > INFO:rxmit_packets: caller's address latched in: 192.168.1.103:6075 > <http://192.168.1.103:6075> (RTCP) > INFO:rxmit_packets: caller's address latched in: 192.168.1.103:6074 > <http://192.168.1.103:6074> (RTP) > INFO:process_rtp: session timeout > INFO:remove_session: RTP stats: 328 in from callee, 5 in from caller, > 333 relayed, 0 dropped > INFO:remove_session: RTCP stats: 3 in from callee, 4 in from caller, 7 > relayed, 0 dropped > INFO:remove_session: session on ports 45984/36756 is cleaned up > > > Kamailio RTP log > ----------------------------------------------- > 3(4242) DEBUG: rtpproxy [rtpproxy_funcs.c:148]: check_content_type(): > type <application/sdp> found valid > 3(4242) DEBUG: rtpproxy [rtpproxy.c:2704]: force_rtp_proxy(): proxy > reply: 45984 > > for more log please see attachment > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users