[asterisk-bugs] [Asterisk 0013857]: Periodic and returned: sip_xmit returned -1: Operation not permitted

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13857 
====================================================================== 
Reported By:                alephlg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13857
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-07 04:22 CST
Last Modified:              2008-11-19 16:25 CST
====================================================================== 
Summary:                    Periodic and returned: sip_xmit returned -1:
Operation not permitted
Description: 
[Nov  6 19:28:28] WARNING[4460] chan_sip.c: sip_xmit of 0x75a490 (len 801)
to 172.16.7.143:5060 returned -1: Operation not permitted

This log is on 2-10 hours on all day. All incident is resolved by self but
the clients not calling on server so long. The port of 5060 has asterisk
and not listing other process.
This problem is not exist on other, equivalent server.

====================================================================== 

---------------------------------------------------------------------- 
 (0095117) putnopvut (administrator) - 2008-11-19 16:25
 http://bugs.digium.com/view.php?id=13857#c95117 
---------------------------------------------------------------------- 
"Operation not permitted" indicates a permissions issue. Unfortunately, I'm
having difficulty narrowing down why a call to sendto(2) would result in an
EPERM error. 

Since you have another server where there is no problem, check to be sure
that whatever user is running Asterisk has the same permissions on both
servers. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-19 16:25 putnopvut      Note Added: 0095117                          
======================================================================