similar to: pjsip segfault problem

Hello, Using Ubuntu Server 12.04 and Asterisk 11.2.1. I'm getting the following error when trying to start asterisk: (Syslog) kernel: [ 1032.713864] asterisk[26918] trap invalid opcode ip:7fc272923076 sp:7fff928cf1b0 error:0 in codec_ilbc.so[7fc272921000+e000] We were running Asterisk on a physical box, but moved it to a virtual environment. That went fine. Asterisk started normally and

Asterisk is on public IP (as described in the first email) i have 10 years experience in voip, 4 years webrtc in production. i know about ICE/STUN/DTLS-SRTP. yes, not every detail but the basic mechanism but i confess. i dont understand WHY Asterisk SOMETIMES switches destination IP in RTP. this is not only about ICE. its about RTP engine too which is Asterisk specific and Asterisk DEBUG is

Hi , We trying to work on Asterisk 12 with sipml5+ PJNATH ,We can able register but calling is not working .The same configuration test with Xlite soft phone it working fine With Regards Prakash -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20131211/9130c2a8/attachment.html>

Le lun. 26 août 2019 à 12:07, Joshua C. Colp <jcolp at digium.com> a écrit : > ... > > libpjnath is the ICE/STUN/TURN library which is used by res_rtp_asterisk > for that functionality. If you're using WebRTC or ICE/STUN/TURN, then you > would be using that library. > Yes, I'm using ICE/STUN/TURN. That explains libpjnath usage. Thank you sharing this here. Now

hi, i have following topology PSTN - Asterisk ---- internet -----  router - jssip client (wss) Asterisk 13.29.1 on public IP, chan_pjsip for wss, chan_sip/udp for SIP connection to PSTN router - public IP/private IP (NAT) jssip client - private IP - sip over websocket to Asterisk PJSIP ~30% of calls has problem with no audio. reason is that Asterisk is sending RTP to private IP of jssip

Hello, I'm working on building Asterisk 11.4.0-rc1 with pjproject 2.1 instead of 2.0 due to a crashing issue resulting from ICE. https://issues.asterisk.org/jira/browse/ASTERISK-21696 Currently, I'm systematically going through each Makefile in every directory in pjproject and changing the paths that exist in the pjproject 2.0 included with Asterisk, so that I can successfully build

I have a CentOS 6.3 machine I installed Asterisk 11, worked fine... I then tried to install on Cents 5.8, seemed to go fine... Then when I placed a call I got this: ast_rtp_instance_new: No RTP engine was found. Do you have one loaded? Did a search and found issues with ARM and this problem but did not help me, not using gtalk or anything. Just call between two polycom phones on local network.

On Tue, Jul 30, 2019 at 11:54:53AM -0400, Michael S. Tsirkin wrote: > On Tue, Jul 30, 2019 at 05:43:29PM +0200, Stefano Garzarella wrote: > > This series tries to increase the throughput of virtio-vsock with slight > > changes. > > While I was testing the v2 of this series I discovered an huge use of memory, > > so I added patch 1 to mitigate this issue. I put it in this

On Wed, Jul 17, 2019 at 01:30:25PM +0200, Stefano Garzarella wrote: > This series tries to increase the throughput of virtio-vsock with slight > changes. > While I was testing the v2 of this series I discovered an huge use of memory, > so I added patch 1 to mitigate this issue. I put it in this series in order > to better track the performance trends. Series: Acked-by: Michael S.

On Tue, Jul 30, 2019 at 05:43:29PM +0200, Stefano Garzarella wrote: > This series tries to increase the throughput of virtio-vsock with slight > changes. > While I was testing the v2 of this series I discovered an huge use of memory, > so I added patch 1 to mitigate this issue. I put it in this series in order > to better track the performance trends. > > v5: > - rebased

This series tries to increase the throughput of virtio-vsock with slight changes. While I was testing the v2 of this series I discovered an huge use of memory, so I added patch 1 to mitigate this issue. I put it in this series in order to better track the performance trends. v5: - rebased all patches on net-next - added Stefan's R-b and Michael's A-b v4:

This series tries to increase the throughput of virtio-vsock with slight changes. While I was testing the v2 of this series I discovered an huge use of memory, so I added patch 1 to mitigate this issue. I put it in this series in order to better track the performance trends. v5: - rebased all patches on net-next - added Stefan's R-b and Michael's A-b v4:

On 2019/5/10 ??8:58, Stefano Garzarella wrote: > While I was testing this new series (v2) I discovered an huge use of memory > and a memory leak in the virtio-vsock driver in the guest when I sent > 1-byte packets to the guest. > > These issues are present since the introduction of the virtio-vsock > driver. I added the patches 1 and 2 to fix them in this series in order > to

On Thu, Apr 04, 2019 at 11:52:46AM -0400, Michael S. Tsirkin wrote: > I simply love it that you have analysed the individual impact of > each patch! Great job! Thanks! I followed Stefan's suggestions! > > For comparison's sake, it could be IMHO benefitial to add a column > with virtio-net+vhost-net performance. > > This will both give us an idea about whether the

On Thu, Apr 04, 2019 at 11:52:46AM -0400, Michael S. Tsirkin wrote: > I simply love it that you have analysed the individual impact of > each patch! Great job! Thanks! I followed Stefan's suggestions! > > For comparison's sake, it could be IMHO benefitial to add a column > with virtio-net+vhost-net performance. > > This will both give us an idea about whether the

While I was testing this new series (v2) I discovered an huge use of memory and a memory leak in the virtio-vsock driver in the guest when I sent 1-byte packets to the guest. These issues are present since the introduction of the virtio-vsock driver. I added the patches 1 and 2 to fix them in this series in order to better track the performance trends. v1:

While I was testing this new series (v2) I discovered an huge use of memory and a memory leak in the virtio-vsock driver in the guest when I sent 1-byte packets to the guest. These issues are present since the introduction of the virtio-vsock driver. I added the patches 1 and 2 to fix them in this series in order to better track the performance trends. v1:

This series tries to increase the throughput of virtio-vsock with slight changes: - patch 1/4: reduces the number of credit update messages sent to the transmitter - patch 2/4: allows the host to split packets on multiple buffers, in this way, we can remove the packet size limit to VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE - patch 3/4: uses

This series tries to increase the throughput of virtio-vsock with slight changes: - patch 1/4: reduces the number of credit update messages sent to the transmitter - patch 2/4: allows the host to split packets on multiple buffers, in this way, we can remove the packet size limit to VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE - patch 3/4: uses

On 2019/4/4 ??6:58, Stefano Garzarella wrote: > This series tries to increase the throughput of virtio-vsock with slight > changes: > - patch 1/4: reduces the number of credit update messages sent to the > transmitter > - patch 2/4: allows the host to split packets on multiple buffers, > in this way, we can remove the packet size limit to >