Home » Forums » Community Edition » Help

No clue..

eblundell191
Posts: 2
 Member Since:
2011-11-01
Submitted by eblundell191 on Thu, 01/12/2012 - 11:19am.

I have googled this, and small pieces of it to find what the problem may be. I cannot find anything. Thanks guys, anything helps :)

Here is a piece of my log file:

[2012-01-12 10:16:17] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:18] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:19] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:20] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:21] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:31] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:32] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:33] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:34] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:35] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:45] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:46] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:47] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:48] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:49] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:16:59] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:00] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:01] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:02] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:03] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cd768 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:13] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:14] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:15] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:16] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted
[2012-01-12 10:17:17] WARNING[3726] chan_sip.c: sip_xmit of 0xa1cdd80 (len 491) to 10.1.10.37:5061 returned -1: Operation not permitted

‹ Unable to receive incoming phone calls phonebook directory can't find names ›


JimmLee
Posts: 14
 Member Since:
2011-12-20
It may be due to permission problem
Fri, 01/13/2012 - 9:05am

This could be due to permission problems. Those who run asterisk as non-root for the sake of safety usually witness these kind of issues. Meanwhile, this could be due to a sip peer also, which is trying to register outside to some voip service provider like Axvoice, Vonage or packet 8. check your sip.conf and comment any sip peers then do a sip reload and check if the issue persists.



VertexData
Posts: 1
 Member Since:
2012-05-01
For me it was due to the iptables firewall - after reboot
Tue, 05/01/2012 - 7:35am

My system was working fine until I rebooted the system and then immediately ran into this problem. I realized that I had disabled the iptables firewall on my asterisk server but did NOT save the iptables after flushing the iptables rules. The reboot of the system has brought the iptables rules back in and prevented the system communications.

The solution is to run the following at the the Linux command prompt.

sudo iptables -F
sudo service iptables save

The first command removes the iptables rules and the second one makes sure that the rules are permanently removed so that a subsequent reboot of the system will not run into this error again!

My asterisk is behind a NAT device and I do not need to run the firewall from security point of view but you need to consider your system security and you may want appropriately configure the firewall to allow the legitimate traffic instead of simply removing all the iptables rules.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.