Rare error when trying to call

A couple of days ago everything was working fine. Now, after having installed fail2ban (and uninstalling it since I got these errors) audio doesn’t get through. I did rtp set debug on and I get this:

Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012799, ts 1061160, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003779, ts 1061320, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012800, ts 1061320, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003780, ts 1061480, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012801, ts 1061480, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003781, ts 1061640, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012802, ts 1061640, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003782, ts 1061800, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012803, ts 1061800, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003783, ts 1061960, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012804, ts 1061960, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003784, ts 1062120, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012805, ts 1062120, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003785, ts 1062280, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012806, ts 1062280, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003786, ts 1062440, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012807, ts 1062440, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003787, ts 1062600, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012808, ts 1062600, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003788, ts 1062760, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012809, ts 1062760, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003789, ts 1062920, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012810, ts 1062920, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003790, ts 1063080, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012811, ts 1063080, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003791, ts 1063240, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012812, ts 1063240, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003792, ts 1063400, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012813, ts 1063400, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003793, ts 1063560, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012814, ts 1063560, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003794, ts 1063720, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012815, ts 1063720, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003795, ts 1063880, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012816, ts 1063880, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003796, ts 1064040, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012817, ts 1064040, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003797, ts 1064200, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012818, ts 1064200, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003798, ts 1064360, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012819, ts 1064360, len 000160)
Got RTP packet from 192.168.1.59:55292 (type 00, seq 003799, ts 1064520, len 000160)
Sent RTP packet to 192.168.1.38:53226 (type 00, seq 012820, ts 1064520, len 000160)

Where 192.168.1.59 is the client in the same LAN as Asterisk and 192.168.1.38 is another client outside Asterisk’s LAN but inside another NAT aswell. I suppose that this IP (192.168.1.38) should be the public one instead of the private one. When doing “sip show peers” it shows the public one…so I don’ know where the error is. Asterisk is sending the rtp media to the wrong IP right? To the private one.

In the Asterisk CLI I got the following WARNINGS:

[2012-02-20 12:58:32] WARNING[5525]: ccss.c:830 ast_set_ccbs_available_timer: 0 is an invalid value for ccbs_available_timer. Retaining value as 4800
– Executing [[email protected]:4] Set(“SIP/103-00000006”, “CALLCOMPLETION(ccnr_available_timer)=”) in new stack
[2012-02-20 12:58:32] WARNING[5525]: ccss.c:800 ast_set_ccnr_available_timer: 0 is an invalid value for ccnr_available_timer. Retaining value as 7200
– Executing [[email protected]:5] Set(“SIP/103-00000006”, “CALLCOMPLETION(cc_callback_macro)=ccss-default”) in new stack
– Executing [[email protected]:6] ExecIf(“SIP/103-00000006”, “1?Set(CALLCOMPLETION(cc_recall_timer)=)”) in new stack
[2012-02-20 12:58:32] WARNING[5525]: ccss.c:815 ast_set_cc_recall_timer: 0 is an invalid value for ccnr_available_timer. Retaining value as 20

Does this have anything to do with my issue?

Thanks!

Did you configure the NAT properly in SIP settings?

Yes. Everything is as the last time it worked (everything I can see). I don’ know if maybe something changed when installing and configuring fail2ban.

I’m thinking that not being able to get the rtp from one side to the other could be related to the Asterisk server. I mean, the firewall could have been modificated when installing and configuring fail2ban. I have a script that opens all needed ports (5060, 10001-2000, ssh, etc.) But it won’t work either. Now, without running the cript, when doing iptables -L I get:

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Does this config allow any traffic in?