Nick, Have you verified there is no firewall on the opensips server with iptables -L I believe the dump pulls the packets before they go through iptables. So what you capture may be just dropped by iptables and not reaching opensips. Though really that shouldn't be a problem since iptables should be keeping track of the conversation and allowing replies. If there are active rules, try iptables -F to see if no firewall makes a difference.
Dave On Tue, May 17, 2011 at 8:11 AM, Razvan Crainea <[email protected]> wrote: > Hi Nick, > > Can you send me the tcpdump trace just when OpenSIPS sends the offer and > waits for the reply? > > Regards, > Razvan > > > > On 05/17/2011 05:23 PM, [email protected] wrote: >> >> Dear Razvan! >> >> Exactly! >> And it is worst that opensips hang for 15-20 minutes and stop responding >> on client requests (REGISTER/OPTIONS/INVITE/etc) and only write in log ERROR >> messages. >> If I restart opensips then it see response, begin response on client >> request and write that rtpproxy found: >> INFO:rtpproxy:rtpp_test: rtp proxy <udp:rtp proxy ip:22222> found, support >> for it enabled >> >> On Tue, 17 May 2011 16:06:22 +0300, Razvan Crainea wrote: >> >>> Hi Nick, >>> So you can see RTPProxy's reply with tcpdump, but OpenSIPS doesn't and >>> signals that error? >>> >>> On 05/17/2011 03:24 PM, [email protected] [12]wrote: >>> >>>> Dear Razvan! I don't have firewall between rtpproxy and opensips at all >>>> so this is not a problem. rtpproxy are on same LAN and in the same >>>> broadcast. Also I run tcpdump when this errors appear and I see packets >>>> in both direction. Regarding downgrading rtpproxy, I just replace >>>> rtpproxy binary without changing anything. On Tue, 17 May 2011 14:39:07 >>>> +0300, Razvan Crainea wrote: >>>> >>>>> Hello Nick, It seems that RTPProxy responds to your queries, but >>>>> OpenSIPS doesn't receive them properly. So probably there is somebody >>>>> in the middle blocking the messages, most likely a firewall. Have you >>>>> changed the socket when tried with the older version? Regards, Razvan >>>>> On 05/17/2011 02:01 PM, [email protected] [9][9]wrote: >>>>> >>>>>> Dear Razvan! Unfortunately my mail client strip some chars. The >>>>>> real string was:May 13 17:10:51 /usr/sbin/opensips[7990]: >>>>>> ERROR:rtpproxy:send_rtpp_command: proxydoes not respond, disable it >>>>>> I think there is some bug in rtpproxy, because I downgrade rtpproxy >>>>>> to older version with ag-project patches from opensips.org site and >>>>>> have not such locks anymore. On Tue, 17 May 2011 11:23:17 +0300, >>>>>> Razvan Crainea wrote: >>>>>> >>>>>>> Hello Nick, Have you removed the RTPProxy IP from the logs, or >>>>>>> these are the exactly error logs that OpenSIPS provide? Regards, >>>>>>> Razvan On 05/13/2011 07:35 AM, [email protected] >>>>>>> [3][3][3]wrote: >>>>>>> >>>>>>>> Dear All! opensips + rtpproxy latest from trunk. I catch >>>>>>>> strange opensips locks. Opensips stop responding and output to >>>>>>>> syslog only these errors: May 10 13:21:47 >>>>>>>> /usr/sbin/opensips[3662]: ERROR:rtpproxy:send_rtpp_command: >>>>>>>> proxy :22222> does not respond, disable it May 10 13:21:48 >>>>>>>> /usr/sbin/opensips[3661]: ERROR:rtpproxy:send_rtpp_command: >>>>>>>> proxy :22222> does not respond, disable it May 10 13:22:05 >>>>>>>> /usr/sbin/opensips[3660]: ERROR:rtpproxy:send_rtpp_command: >>>>>>>> proxy :22222> does not respond, disable it ... May 10 13:29:22 >>>>>>>> /usr/sbin/opensips[5428]: ERROR:rtpproxy:send_rtpp_command: >>>>>>>> proxy :22222> does not respond, disable it I tried increase >>>>>>>> debug level through fifo but verbosity don't increase. In >>>>>>>> rtpproxy in debug mode I have these messages: >>>>>>>> DBUG:handle_command: received command "3660_595 >>>>>>>> Uc8,0,18,4,3,110,97,101 0e70ed1b54b0727d20297cdf7da7ae33@:5060 >>>>>>>> 12290 as6c1cbf1f;1" INFO:handle_command: new session >>>>>>>> 0e70ed1b54b0727d20297cdf7da7ae33@:5060, tag as6c1cbf1f;1 >>>>>>>> requested, type strong INFO:handle_command: new session on a >>>>>>>> port 13184 created, tag as6c1cbf1f;1 INFO:handle_command: >>>>>>>> pre-filling caller's address with :12290 DBUG:doreply: sending >>>>>>>> reply "3660_595 13184 " DBUG:handle_command: received command >>>>>>>> "3660_596 Uc0,8,18,3,101 0e70ed1b54b0727d20297cdf7da7ae33@:5060 >>>>>>>> 16496 as1a95022b;1 as6c1cbf1f;1" INFO:handle_command: adding >>>>>>>> strong flag to existing session, new=1/0/0 INFO:handle_command: >>>>>>>> lookup on ports 13184/18324, session timer restarted >>>>>>>> INFO:handle_command: pre-filling callee's address with :16496 >>>>>>>> DBUG:doreply: sending reply "3660_596 18324 " >>>>>>>> DBUG:handle_command: received command "3662_610 Uc0,8,18,3,101 >>>>>>>> 0e70ed1b54b0727d20297cdf7da7ae33@:5060 16496 as1a95022b;1 >>>>>>>> as6c1cbf1f;1" INFO:handle_command: adding strong flag to >>>>>>>> existing session, new=1/0/0 INFO:handle_command: lookup on >>>>>>>> ports 13184/18324, session timer restarted DBUG:doreply: >>>>>>>> sending reply "3662_610 18324 " DBUG:handle_command: received >>>>>>>> command "3661_605 Uc0,8,18,3,101 >>>>>>>> 0e70ed1b54b0727d20297cdf7da7ae33@:5060 16496 as1a95022b;1 >>>>>>>> as6c1cbf1f;1" INFO:handle_command: adding strong flag to >>>>>>>> existing session, new=1/0/0 INFO:handle_command: lookup on >>>>>>>> ports 13184/18324, session timer restarted DBUG:doreply: >>>>>>>> sending reply "3661_605 18324 ... " DBUG:handle_command: >>>>>>>> received command "3661_607 Uc0,8,18,3,101 >>>>>>>> 0e70ed1b54b0727d20297cdf7da7ae33@:5060 16496 as1a95022b;1 >>>>>>>> as6c1cbf1f;1" INFO:handle_command: adding strong flag to >>>>>>>> existing session, new=1/0/0 INFO:handle_command: lookup on >>>>>>>> ports 13184/18324, session timer restarted DBUG:doreply: >>>>>>>> sending reply "3661_607 18324 " DBUG:handle_command: received >>>>>>>> command "3662_613 Uc0,8,18,3,101 >>>>>>>> 0e70ed1b54b0727d20297cdf7da7ae33@:5060 16496 as1a95022b;1 >>>>>>>> as6c1cbf1f;1" INFO:handle_command: adding strong flag to >>>>>>>> existing session, new=1/0/0 INFO:handle_command: lookup on >>>>>>>> ports 13184/18324, session timer restarted DBUG:doreply: >>>>>>>> sending reply "3662_613 18324 " DBUG:handle_command: received >>>>>>>> command "3660_599 Uc0,8,18,3,101 >>>>>>>> 0e70ed1b54b0727d20297cdf7da7ae33@:5060 16496 as1a95022b;1 >>>>>>>> as6c1cbf1f;1" INFO:handle_command: adding strong flag to >>>>>>>> existing session, new=1/0/0 INFO:handle_command: lookup on >>>>>>>> ports 13184/18324, session timer restarted DBUG:doreply: >>>>>>>> sending reply "3660_599 18324 >>>>>>>> _______________________________________________ Users mailing >>>>>>>> list [email protected] [1] [1] [1] >>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [2] >>>>>>>> [2] [2] >>>>>> >>>>>> Links: ------ [1] mailto:[email protected] [4] [4] [2] >>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [5] [5] >>>>>> [3] mailto:[email protected] [6] [6] >>>>>> _______________________________________________ Users mailing list >>>>>> [email protected] [7] [7] >>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [8] [8] >>>> >>>> _______________________________________________ Users mailing list >>>> [email protected] [10] >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users [11] >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > -- > Razvan Crainea > OpenSIPS Developer > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- David Singer _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
