similar to: Problems using chan_sebi and Huawei E169G

Hi! I'm trying to use dongle in my Asterisk But appear for me all time this error [Feb 12 13:49:10] ERROR[13347]: chan_dongle.c:442 do_monitor_phone: [dongle0] timedout while waiting 'OK' in response to 'AT' -- [dongle0] Error initializing Dongle -- [dongle0] Dongle has disconnected -- [dongle0] Trying to connect on /dev/ttyUSB1... -- [dongle0] Dongle has

Yes, I used IMEI. But in CLI appearing nothing and it not register. 2016-02-12 14:27 GMT-02:00, Shabbir abbasi <shabbirabbasi92 at gmail.com>: > have you tried imei discovery > imei=123456789012345 > > > write imei number instaed of 12345... > > On Fri, Feb 12, 2016 at 8:51 PM, Vitor Mazuco <vitor.mazuco at gmail.com> > wrote: > >> Hi! >>

Yes I used. The problem can be the version of Asterisk? I use Asterisk 13 instead of 11. 2016-02-12 14:31 GMT-02:00, Shabbir abbasi <shabbirabbasi92 at gmail.com>: > have changed this > [dongle0] > audio=/dev/ttyUSB1 > data=/dev/ttyUSB2 > > To > > [dongle0] > imei=123456789012345 > > and imei exact same as on your device ? > > On Fri, Feb 12, 2016

Commit d9e7972619334 "hwrng: add randomness to system from rng sources" added a call to rng_get_data() from the hwrng_register() function. However, some rng devices need initialization before data can be read from them. This commit makes the call to rng_get_data() depend on no init fn pointer being registered by the device. If an init function is registered, this call is made after

Commit d9e7972619334 "hwrng: add randomness to system from rng sources" added a call to rng_get_data() from the hwrng_register() function. However, some rng devices need initialization before data can be read from them. This commit makes the call to rng_get_data() depend on no init fn pointer being registered by the device. If an init function is registered, this call is made after

Hi All, I was made aware today that some of my calls coming in are not going to voicemail... Below are some logs, and the macro that should run on the incoming_pstn context for that extension. I can see that theres a non-zero exit before it gets to voicemail, but I've no idea why. In this case theres 2 SIP clients to sim-call. On other occasions it works fine. In the CDR logs, I can see

Some RNG devices may not be ready to give early randomness at probe() time, and hence lose out on the opportunity to contribute to system randomness at boot- or device hotplug- time. This commit schedules a delayed work item for such devices, and fetches early randomness after a delay. Currently the delay is 500ms, which is enough for the lone device that needs such treatment: virtio-rng. CC:

On Fri, Jul 4, 2014 at 10:34 PM, Amit Shah <amit.shah at redhat.com> wrote: > Commit d9e7972619334 "hwrng: add randomness to system from rng sources" > added a call to rng_get_data() from the hwrng_register() function. > However, some rng devices need initialization before data can be read > from them. > > This commit makes the call to rng_get_data() depend on no

On Fri, Jul 4, 2014 at 10:34 PM, Amit Shah <amit.shah at redhat.com> wrote: > Commit d9e7972619334 "hwrng: add randomness to system from rng sources" > added a call to rng_get_data() from the hwrng_register() function. > However, some rng devices need initialization before data can be read > from them. > > This commit makes the call to rng_get_data() depend on no

Commit d9e7972619334 "hwrng: add randomness to system from rng sources" added a call to rng_get_data() from the hwrng_register() function. However, some rng devices need initialization before data can be read from them. Also, the virtio-rng device does not behave properly when this call is made in its probe() routine - the virtio core sets the DRIVER_OK status bit only on a successful

From 2334d90a3b9f8b9207163e9e0fad714e88a28771 Mon Sep 17 00:00:00 2001 From: Rusty Russell <rusty@rustcorp.com.au> Date: Wed, 7 Nov 2007 21:02:22 +1100 Subject: [PATCH] virtio: An entropy device, as suggested by hpa. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- Documentation/lguest/lguest.c | 53 +++++++++++++++ drivers/char/hw_random/Kconfig | 10 +++

From 2334d90a3b9f8b9207163e9e0fad714e88a28771 Mon Sep 17 00:00:00 2001 From: Rusty Russell <rusty@rustcorp.com.au> Date: Wed, 7 Nov 2007 21:02:22 +1100 Subject: [PATCH] virtio: An entropy device, as suggested by hpa. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- Documentation/lguest/lguest.c | 53 +++++++++++++++ drivers/char/hw_random/Kconfig | 10 +++

Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block

From: Asias He <asias at redhat.com> This module contains the common code and header files for the following virtio-vsock and virtio-vhost kernel modules. Signed-off-by: Asias He <asias at redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com> --- v3: * Remove unnecessary 3-way handshake, just do REQUEST/RESPONSE instead of REQUEST/RESPONSE/ACK * Remove

This module contains the common code and header files for the following virtio-vsock and virtio-vhost kernel modules. Signed-off-by: Asias He <asias at redhat.com> --- include/linux/virtio_vsock.h | 200 +++++++ include/uapi/linux/virtio_ids.h | 1 + include/uapi/linux/virtio_vsock.h | 70 +++ net/vmw_vsock/virtio_transport_common.c | 992

Dear All, Thank you for taking the time to read this post - I am *confused!* as to why my asterisk setup does not work as it should. I have an ISDN 30 connection for telephony, a Sangoma card, and asterisk installed. Incoming calls, and outgoing calls work 100%. Making an international call, results in silence, or the error message all circuits are busy Numbers being passed to the trunk for

Stefan Hajnoczi <stefanha at redhat.com> writes: > From: Asias He <asias at redhat.com> > > This module contains the common code and header files for the following > virtio-vsock and virtio-vhost kernel modules. General comment checkpatch has a bunch of warnings about 80 character limits, extra braces and BUG_ON usage. > > Signed-off-by: Asias He <asias at

Stefan Hajnoczi <stefanha at redhat.com> writes: > From: Asias He <asias at redhat.com> > > This module contains the common code and header files for the following > virtio-vsock and virtio-vhost kernel modules. General comment checkpatch has a bunch of warnings about 80 character limits, extra braces and BUG_ON usage. > > Signed-off-by: Asias He <asias at

From: Asias He <asias at redhat.com> This module contains the common code and header files for the following virtio-vsock and virtio-vhost kernel modules. Signed-off-by: Asias He <asias at redhat.com> --- include/linux/virtio_vsock.h | 207 ++++ include/uapi/linux/virtio_ids.h | 1 + .../uapi/linux/{virtio_ids.h => virtio_vsock.h} |

On Thu, Jun 27, 2013 at 04:00:01PM +0800, Asias He wrote: > This module contains the common code and header files for the following > virtio-vsock and virtio-vhost kernel modules. > > Signed-off-by: Asias He <asias at redhat.com> > --- > include/linux/virtio_vsock.h | 200 +++++++ > include/uapi/linux/virtio_ids.h | 1 + >