search for: eswitches

Hi List, Would someone can to explain me the main difference in SWITCHES or ESWITCHES in AEL. context default { switches { DUNDi/e164; IAX2/box5; }; eswitches { IAX2/context@${CURSERVER}; }; }; All the best, Thiago -- ---------------------------------------------------------------- Thiago Maluf Resende Tel: +55 21 9700-9113 e-mail: malu...

From: Leon Romanovsky <leonro at nvidia.com> Changelog: v1: * Renamed _mlx5_rescan_driver to be mlx5_rescan_driver_locked like in other parts of the mlx5 driver. * Renamed MLX5_INTERFACE_PROTOCOL_VDPA to tbe MLX5_INTERFACE_PROTOCOL_VNET as a preparation to coming series from Eli C. * Some small naming renames in mlx5_vdpa. * Refactored adev index code to make Parav's SF series

OK, some patches in the series add buggy code which is then fixed by follow-up patches, but none of the bugs fixed are severe regressions on common configs (e.g. compiler warnings, lockdep/rt errors, or bugs in new drivers). So I thought it's more important to preserve the credit for the fixes. I had to pull 5 patches from git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux mlx5-next

My phone still says Not-Registered. I have a Polycom SoundPoint 600 SIP phone. Here is my sip.conf file: ; ; SIP Configuration ; [general] context=default ; Default context for incoming calls port=5060 ;added bindport=5060 ; UDP Port to bind to (SIP standard port is 5060) bindaddr=0.0.0.0 ; IP address to bind to (0.0.0.0 binds to all) srvlookup=yes ;

...ial(SIP/cgm); 102 => Dial(SIP/bluecommand); _9XX => ?????????? 500 => Agi(agi://localhost/internal.agi); _8XXX => { NoOp("Calling ${EXTEN}"); Dial(SIP/${EXTEN}); } }; context database { eswitches { Realtime/ContextShouldBeHere@${CURSERVER}; }; } I want it to jump from _9XX to the context database, passing along what context it came from as a parameter. Is this possible at all? Greetings, Christian

On Sat, 17 Feb 2018 09:12:01 -0800, Alexander Duyck wrote: > >> We noticed a couple of issues with this approach during testing. > >> - As both 'bypass' and 'backup' netdevs are associated with the same > >> virtio pci device, udev tries to rename both of them with the same name > >> and the 2nd rename will fail. This would be OK as long as

Hi all, I've put up a blog post with a summary of where network device failover stands and some open issues. Not sure where best to host it, I just put it up on blogspot: https://mstsirkin.blogspot.com/2019/03/virtio-network-device-failover-support.html Comments, corrections are welcome! -- MST

Hi all, I've put up a blog post with a summary of where network device failover stands and some open issues. Not sure where best to host it, I just put it up on blogspot: https://mstsirkin.blogspot.com/2019/03/virtio-network-device-failover-support.html Comments, corrections are welcome! -- MST

Hi Michael, Great blog-post which summarise everything very well! Some comments I have: 1) I think that when we are using the term ?1-netdev model? on community discussion, we tend to refer to what you have defined in blog-post as "3-device model with hidden slaves?. Therefore, I would suggest to just remove the ?1-netdev model? section and rename the "3-device model with hidden

On Tue, Mar 19, 2019 at 02:38:06PM +0200, Liran Alon wrote: > Hi Michael, > > Great blog-post which summarise everything very well! > > Some comments I have: Thanks! I'll try to update everything in the post when I'm not so jet-lagged. > 1) I think that when we are using the term ?1-netdev model? on community discussion, we tend to refer to what you have defined in

On Fri, Feb 16, 2018 at 6:38 PM, Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 16 Feb 2018 10:11:19 -0800, Sridhar Samudrala wrote: >> Ppatch 2 is in response to the community request for a 3 netdev >> solution. However, it creates some issues we'll get into in a moment. >> It extends virtio_net to use alternate datapath when available and >> registered.

On Fri, Feb 16, 2018 at 6:38 PM, Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 16 Feb 2018 10:11:19 -0800, Sridhar Samudrala wrote: >> Ppatch 2 is in response to the community request for a 3 netdev >> solution. However, it creates some issues we'll get into in a moment. >> It extends virtio_net to use alternate datapath when available and >> registered.