I'm having similar errors too. Customers are also complaining that their connection dropped. Could this be related? (That's the only error that occured when that connection dropped)
(using asterisk 1.6.2.8) Kenny -- tel: +32 476 780 692 On 10 Jun 2010, at 13:52, Jonas Kellens wrote: > I'm getting a lot of these on the CLI : > > [Jun 10 13:41:36] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b381bb0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:37] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b381bb0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:38] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b381bb0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:39] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b381bb0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:40] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b381bb0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:50] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b393130 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:51] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b393130 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:52] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b393130 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:53] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b393130 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:41:54] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b393130 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:42:04] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b33dad0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:42:05] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b33dad0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:42:06] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b33dad0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > [Jun 10 13:42:07] WARNING[4286]: chan_sip.c:1817 __sip_xmit: sip_xmit of > 0x1b33dad0 (len 554) to 192.168.12.120:2056 returned -1: Operation not > permitted > > What can I do to stop this ?? > > What I usually do is restart Asterisk. After 5 to 8 restarts, it goes away... > This can not be "good practise". > > Using Asterisk 1.4.30 and sip realtime. > > > Jonas. > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
