[OpenSIPS-Users] rtpproxy timeout notification not working after opensips restart

[Răzvan Crainea]

Hi, Flavio!

I am not sure that you should see that debug message. Have you tried to 
take a trace on port 7891 and see if RTPProxy is sending any message?

Best regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 09/14/2012 08:05 PM, Flavio Goncalves wrote:
> I don't know if anyone has faced this issue.
>
> Rtpproxy timeout notification does not work after opensips restart. 
> When you start opensips and rtpproxy just after, timeout notifications 
> work. If you restart opensips, the session is timed out, but the 
> notification is not sent.
>
>
> ## Session with notification ##
> Sep 14 12:55:13 pulse rtpproxy[21756]: DBUG:handle_command: received 
> command "21814_5 Uc0,2,4,8,18,96,97,98,101 
> f34e3e3a-6c3e16d2 at 192.168.1.148 
> <mailto:f34e3e3a-6c3e16d2 at 192.168.1.148> 187.65.239.2 16476 
> 2632571a830dd372o1;1 ;1 127.0.0.1:7891 <http://127.0.0.1:7891> 
> 327.213594884"
> Sep 14 12:55:13 pulse rtpproxy[21756]: INFO:handle_command: new 
> session f34e3e3a-6c3e16d2 at 192.168.1.148 
> <mailto:f34e3e3a-6c3e16d2 at 192.168.1.148>, tag 2632571a830dd372o1;1 
> requested, type strong
> Sep 14 12:55:13 pulse rtpproxy[21756]: INFO:handle_command: new 
> session on a port 30320 created, tag 2632571a830dd372o1;1
> Sep 14 12:55:13 pulse rtpproxy[21756]: INFO:handle_command: setting 
> timeout handler
> Sep 14 12:55:13 pulse rtpproxy[21756]: INFO:handle_command: 
> pre-filling caller's address with 187.65.239.2:16476 
> <http://187.65.239.2:16476>
> Sep 14 12:55:13 pulse rtpproxy[21756]: DBUG:doreply: sending reply 
> "21814_5 30320 208.109.122.193 "
> Sep 14 12:55:13 pulse rtpproxy[21756]: DBUG:handle_command: received 
> command "21825_5 Lc0,8,101 f34e3e3a-6c3e16d2 at 192.168.1.148 
> <mailto:f34e3e3a-6c3e16d2 at 192.168.1.148> 68.178.255.30 12382 
> 2632571a830dd372o1;1 as7ab4ce16;1"
> Sep 14 12:55:13 pulse rtpproxy[21756]: INFO:handle_command: lookup on 
> ports 30320/30188, session timer restarted
> Sep 14 12:55:13 pulse rtpproxy[21756]: INFO:handle_command: 
> pre-filling callee's address with 68.178.255.30:12382 
> <http://68.178.255.30:12382>
> Sep 14 12:55:13 pulse rtpproxy[21756]: DBUG:doreply: sending reply 
> "21825_5 30188 208.109.122.193 "
> Sep 14 12:56:02 pulse rtpproxy[21756]: INFO:process_rtp: session timeout
> Sep 14 12:56:02 pulse rtpproxy[21756]: INFO:remove_session: RTP stats: 
> 900 in from callee, 1031 in from caller, 1931 relayed, 0 dropped
> Sep 14 12:56:02 pulse rtpproxy[21756]: INFO:remove_session: RTCP 
> stats: 3 in from callee, 0 in from caller, 3 relayed, 0 dropped
> Sep 14 12:56:02 pulse rtpproxy[21756]: INFO:remove_session: session on 
> ports 30320/30188 is cleaned up
> **Sep 14 12:56:02 pulse rtpproxy[21756]: 
> DBUG:reconnect_timeout_handler: connecting timeout socket
>
> This last command does not appear after restarting OpenSIPS
>
> ## Session without notification ##
>
> Sep 14 12:56:45 pulse rtpproxy[21756]: DBUG:handle_command: received 
> command "22071_5 Uc0,2,4,8,18,96,97,98,101 
> ca831a2e-a923ef6d at 192.168.1.148 
> <mailto:ca831a2e-a923ef6d at 192.168.1.148> 187.65.239.2 16478 
> 87ab833a5b79b9d1o1;1 ;1 127.0.0.1:7891 <http://127.0.0.1:7891> 
> 1383.1207396094"
> Sep 14 12:56:45 pulse rtpproxy[21756]: INFO:handle_command: new 
> session ca831a2e-a923ef6d at 192.168.1.148 
> <mailto:ca831a2e-a923ef6d at 192.168.1.148>, tag 87ab833a5b79b9d1o1;1 
> requested, type strong
> Sep 14 12:56:45 pulse rtpproxy[21756]: INFO:handle_command: new 
> session on a port 30194 created, tag 87ab833a5b79b9d1o1;1
> Sep 14 12:56:45 pulse rtpproxy[21756]: INFO:handle_command: setting 
> timeout handler
> Sep 14 12:56:45 pulse rtpproxy[21756]: INFO:handle_command: 
> pre-filling caller's address with 187.65.239.2:16478 
> <http://187.65.239.2:16478>
> Sep 14 12:56:45 pulse rtpproxy[21756]: DBUG:doreply: sending reply 
> "22071_5 30194 208.109.122.193 "
> Sep 14 12:56:45 pulse rtpproxy[21756]: DBUG:handle_command: received 
> command "22063_5 Lc0,8,101 ca831a2e-a923ef6d at 192.168.1.148 
> <mailto:ca831a2e-a923ef6d at 192.168.1.148> 68.178.255.30 10368 
> 87ab833a5b79b9d1o1;1 as472d0201;1"
> Sep 14 12:56:45 pulse rtpproxy[21756]: INFO:handle_command: lookup on 
> ports 30194/30064, session timer restarted
> Sep 14 12:56:45 pulse rtpproxy[21756]: INFO:handle_command: 
> pre-filling callee's address with 68.178.255.30:10368 
> <http://68.178.255.30:10368>
> Sep 14 12:56:45 pulse rtpproxy[21756]: DBUG:doreply: sending reply 
> "22063_5 30064 208.109.122.193 "
> Sep 14 12:57:22 pulse rtpproxy[21756]: INFO:process_rtp: session timeout
> Sep 14 12:57:22 pulse rtpproxy[21756]: INFO:remove_session: RTP stats: 
> 298 in from callee, 405 in from caller, 703 relayed, 0 dropped
> Sep 14 12:57:22 pulse rtpproxy[21756]: INFO:remove_session: RTCP 
> stats: 1 in from callee, 0 in from caller, 1 relayed, 0 dropped
> Sep 14 12:57:22 pulse rtpproxy[21756]: INFO:remove_session: session on 
> ports 30194/30064 is cleaned up
>
>
> Flavio E. Goncalves
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120916/23b0aa43/attachment.htm>