Re: [asterisk-users] warning : sip_xmit

2010-06-10 Thread Kenny Gryp
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


[asterisk-users] SIP: match_auth_username=yes doesn't seem to work

2010-06-03 Thread Kenny Gryp
Hi,

I'm trying to get the match_auth_username=yes sip configuration working.
It's mentioned as an experimental new feature of 1.6.2.x. (I'm using 1.6.2.8)

The sip.conf example states:
; if available, match user entry using the
; 'username' field from the authentication line
; instead of the From: field.

But still I've been unable to authenticate using username username but with 
the VOIP number 02111.

Is this a bug or am I doing something wrong?


Here's the packet that's received:

REGISTER sip:sip.provider.be:5060 SIP/2.0
Max-Forwards: 70
Content-Length: 0
Via: SIP/2.0/UDP 11.11.11.11:5060;branch=z9hG4bK66d4f754a
Call-ID: 2e409c83a33ba68e9ec8d01416c3c...@11.11.11.11
From: username sip: 02...@sip.provider.be:5060;tag=25137d7a16de03f
To: username sip:02...@sip.provider.be:5060
CSeq: 1481488189 REGISTER
Contact: fulladsl sip: 02...@11.11.11.11:5060;expires=300
Allow: NOTIFY, REFER, OPTIONS, INVITE, ACK, CANCEL, BYE
Authorization:Digest 
response=48c35d36d1d994110615e715ef5ea23d,username=username,realm=asterisk,nonce=26a5abaa,algorithm=MD5,uri=sip:sip.provider.be:5060
User-Agent: Brcm-Callctrl/v1.7.1.1 MxSF/v3.6.2.5

And asterisk reply's with:
SIP/2.0 403 Forbidden (Bad auth)



Kenny




-- 
_
-- 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