[OpenSIPS-Users] "incorrect port 0 in reply from rtp proxy' error appears after DoS attack

[Andrew Pogrebennyk]

Hi,
I've recently experienced an opensips outage. As I see from the logs 
there was a brief DoS attack by sipvicious, then the attacker was 
blocked by fail2ban. But after that appeared a huge number of " 
incorrect port 0 in reply from rtp proxy" errors and the calls weren't 
going through. I was not able to monitor this myself, eventually the 
opensips was restarted. I'm going to upgrade from 1.6.2 to 1.6.4 and 
enable rtpproxy debug so as to get more info next time that it happens. 
I'm just wondering now if it this some known bug. Thanks,

 > grep ERROR opensips.log
> May 17 11:53:42 sip /usr/sbin/opensips[26161]: ERROR:core:parse_cseq: expecting CSeq EoL
> May 17 11:53:42 sip /usr/sbin/opensips[26161]: ERROR:core:parse_cseq: bad cseq
> May 17 11:53:42 sip /usr/sbin/opensips[26161]: ERROR:core:get_hdr_field: bad cseq
> May 17 11:53:42 sip /usr/sbin/opensips[26162]: ERROR:core:parse_cseq: expecting CSeq EoL
> May 17 11:53:42 sip /usr/sbin/opensips[26157]: ERROR:core:parse_cseq: expecting CSeq EoL
> May 17 11:53:42 sip /usr/sbin/opensips[26159]: ERROR:core:parse_cseq: expecting CSeq EoL
> May 17 11:53:42 sip /usr/sbin/opensips[26162]: ERROR:core:parse_cseq: bad cseq
> May 17 11:53:42 sip /usr/sbin/opensips[26157]: ERROR:core:parse_cseq: bad cseq
> May 17 11:53:42 sip /usr/sbin/opensips[26161]: ERROR:core:pv_get_callid: cannot parse Call-Id header
> ...
> May 17 11:54:06 sip /usr/sbin/opensips[26164]: ERROR:core:pv_get_callid: cannot parse Call-Id header
> May 17 11:54:06 sip /usr/sbin/opensips[26162]: ERROR:core:pv_get_callid: cannot parse Call-Id header
> May 17 11:54:06 sip /usr/sbin/opensips[26155]: ERROR:tm:t_lookup_request: too few headers
> May 17 11:54:06 sip /usr/sbin/opensips[26156]: ERROR:tm:t_lookup_request: too few headers
> May 17 11:54:06 sip /usr/sbin/opensips[26155]: ERROR:core:parse_cseq: expecting CSeq EoL
> May 17 11:54:07 sip /usr/sbin/opensips[26156]: ERROR:core:parse_cseq: expecting CSeq EoL
> May 17 11:54:07 sip /usr/sbin/opensips[26155]: ERROR:core:parse_cseq: bad cseq
> May 17 11:54:07 sip /usr/sbin/opensips[26156]: ERROR:core:parse_cseq: bad cseq
> May 17 11:54:07 sip /usr/sbin/opensips[26155]: ERROR:core:get_hdr_field: bad cseq
> May 17 11:54:07 sip /usr/sbin/opensips[26156]: ERROR:core:get_hdr_field: bad cseq
> May 17 11:54:07 sip /usr/sbin/opensips[26155]: ERROR:core:pv_get_callid: cannot parse Call-Id header
> May 17 11:54:07 sip /usr/sbin/opensips[26156]: ERROR:core:pv_get_callid: cannot parse Call-Id header
> May 17 11:55:01 sip /usr/sbin/opensips[26156]: ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy
> May 17 11:55:02 sip /usr/sbin/opensips[26165]: ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy
> May 17 11:55:02 sip /usr/sbin/opensips[26157]: ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy
> May 17 11:55:03 sip /usr/sbin/opensips[26155]: ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy
> May 17 11:55:04 sip /usr/sbin/opensips[26159]: ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy
> May 17 11:55:07 sip /usr/sbin/opensips[26165]: ERROR:nathelper:force_rtp_proxy_body: incorrect port 0 in reply from rtp proxy

-- 
Sincerely,
Andrew Pogrebennyk