Re: [asterisk-users] __sip_xmit Returned -1 Invalid Argument

Brian Wilson wrote: I've been getting slammed with these messages on my console lately. ed -1: Invalid argument [2016-05-31 10:09:40] WARNING[16249]: chan_sip.c:3775 __sip_xmit: sip_xmit of 0x7f05140803f0 (len 559) to 192.168.1.45:0 returned -1: Invalid argument

[asterisk-users] __sip_xmit Returned -1 Invalid Argument

I've been getting slammed with these messages on my console lately. ed -1: Invalid argument [2016-05-31 10:09:40] WARNING[16249]: chan_sip.c:3775 __sip_xmit: sip_xmit of 0x7f05140803f0 (len 559) to 192.168.1.45:0 returned -1: Invalid argument [2016-05-31 10:09:40] WARNING[16249]: chan_sip.c:3775

[asterisk-users] Performance Note: Creating Local channels with ARI

Over the past week we've noticed that, when bridging a local channel created with ARI, audio processing uses excessive amounts of CPU time. After some digging, we determined the cause, have some recommendations, and have a patch up for review. The cause: When you create a local channel via ARI

Re: [asterisk-users] How to set outgoing sip callid ?

In sip.conf [devicename] callerid="Jon Doe" <+123456789> or in extensions.conf exten => 1234,Set(CALLERID(all)="Jon Doe" <+123456789>) exten => 1234,n,Dial(SIP/ -- _ -- Bandwidth and Colocation Provided by

[asterisk-users] How to set outgoing sip callid ?

Calling linphone from asterisk 13.9.1.: Dial(SIP/@sip.linphone.org) And it works. But on the linphone side the caller is: @ipaddress or 2502@45.123.987.4 Is there any way to make it more descriptive, at least for the sip user name ? I tried setting SIPCALLID, which had no effect.

Re: [asterisk-users] Need stronger SRTP ciphers (256 bit)

Kevin Long wrote: Some more information (would love some thoughts on this, I have never submitted a patch yet). Groundwire (Popular SIP app) supports the following cipher suites for SRTP: AES_CM_128_HMAC_SHA1_32 AES_CM_128_HMAC_SHA1_80 AES_CM_192_HMAC_SHA1_32 AES_CM_192_HMAC_SHA1_80