similar to: Local channel that runs a custom app... why immediate hangup?

Hi Folks, I'm trying to use my mobile as a trunk via bluetooth - calls done in a softphone go thru GSM network and calls destinated to my mobile are answered at the softphone. I have asterisk configured to do so but I'm facing an issue - Audio is audible but it?s not intelligible. I feel like the audio is breaking. Below is the asterisk log. I also get lots of ?hci_scodata_packet: hci0

Dear all on a debian amd64 i've installed (from source) asterisk 1.4.30 On the system we have in average 50 concurrent calls in queue and 40 sip members. I'm experiencing an apparently random problem: sometimes some users receive 2 calls from asterisk, apparently ignoring the ringinuse=no settings. It appears on users that are members of many queues As you can see from the log, the

Hi I am experiencing Asterisk Crash. Log got stopped when asterisk crashed. Please help me to identify the reason and fix this issue. Asterisk: 1.8.20 I am using AMI and fastAGI to control the call. Some part of dial plan is also defined in extensions.conf I am experiencing this crash when app_meetme conference functionality is used with more than 3 parties. I faced this issue with

With virtio-1, we support more than 32 feature bits. Let's make vdev->guest_features depend on the number of supported feature bits, allowing us to grow the feature bits automatically. We also need to enhance the internal functions dealing with getting and setting features with an additional index field, so that all feature bits may be accessed (in chunks of 32 bits). vhost and migration

With virtio-1, we support more than 32 feature bits. Let's make vdev->guest_features depend on the number of supported feature bits, allowing us to grow the feature bits automatically. We also need to enhance the internal functions dealing with getting and setting features with an additional index field, so that all feature bits may be accessed (in chunks of 32 bits). vhost and migration

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

With virtio-1, we support more than 32 feature bits. Let's make vdev->guest_features depend on the number of supported feature bits, allowing us to grow the feature bits automatically. We also need to enhance the internal functions dealing with getting and setting features with an additional index field, so that all feature bits may be accessed (in chunks of 32 bits). vhost and migration

With virtio-1, we support more than 32 feature bits. Let's make vdev->guest_features depend on the number of supported feature bits, allowing us to grow the feature bits automatically. We also need to enhance the internal functions dealing with getting and setting features with an additional index field, so that all feature bits may be accessed (in chunks of 32 bits). vhost and migration

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

With virtio-1, we support more than 32 feature bits. Let's extend both host and guest features to 64, which should suffice for a while. vhost and migration have been ignored for now. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/9pfs/virtio-9p-device.c | 2 +- hw/block/virtio-blk.c | 2 +- hw/char/virtio-serial-bus.c | 2 +-

Hello, my configuration is the following: a TDM400P board with an fxs and fxo daughter boards on it. I thus connect a fax to my FXS port, after having verified that this port was correctly functioning. For this, I had tried before with a simple phone, and with some basic voicemail exten scripts. Here is my simple dialplan for my fax reception: exten => 300,1,Ringing() exten =>

About once a week or so my Asterisk box stops responding to all phones. I can pull up the console, do whatever I want at the CLI but the only way to get things working again is to restart Asterisk altogether. I finally cranked verbose & debugging way up (and watched my log files go from 1mb/day to 100mb/day), but below I believe contains my problem. The next line is 1.5 minutes later where I

Hi there! Trying to originate and dial a number using Zap-8, used to work, but now it just fails. I enabled all debug I found in the source-code and this is the output from asterisk. Can someone understand something from the debug-output what is wrong and direct me to what the problem might be? The setup is correct, trust me, it worked some hours ago, haven't changed anything. Just dialing

I'm tying to use park and announce for call park on Asterisk 1.4.2 but I'm having trouble getting it to work properly. This use to work with an older version of Asterisk. A telephone on the PSTN calls an IP phone. The IP phone is assigned extension 3-8396. 3-8396 answers the call and attempts to perform a blind transfer to x700, the parking lot number. The transfer gets to Asterisk,

Hi, I'm having problems with the voicemail, the app keeps exiting in 3-5 seconds. Any considerations will be appreciated. Thanks, D.K. Debug messages: Apr 18 20:53:41 DEBUG[26150] pbx.c: Launching 'Goto' Apr 18 20:53:41 DEBUG[26150] pbx.c: Launching 'VoiceMail' Apr 18 20:53:41 DEBUG[26129] chan_sip.c: Checking device state for peer XXX Apr 18 20:53:41 DEBUG[26129]

Hi, I've uploaded a new patch at https://issues.asterisk.org/view.php?id=16732which adds two new AMI commands, called "DeviceStateSet" and "DeviceStateGet". These commands let you update Custom device states, and read all devicestates from AMI. It would be very nice if someone could help me test this feature, and report back to the issue tracker. To test, log into AMI

Hello. Dovecot is not binding or listening on port 993 when I start it. $ sudo netstat -tlnp | grep -c 993 0 Dovecot starts fine and runs without complaints. $ sudo service dovecot restart Restarting IMAP/POP3 mail server: dovecot. $ sudo tail /var/log/mail.log Apr 4 13:42:39 mwjones dovecot: master: Warning: Killed with signal 15 (by pid=16238 uid=0 code=kill) Apr 4 13:42:39 mwjones

I am doing a little application to originate a call through Asterisk via AMI (Perl Asterisk::Manager). It logs in successfully, does an originate command with Exten: 0020 (which is set up to answer and wait for 60 then hang up) Channel: SIP/5101234567 at test-host (which comes to my desktop machine also running Asterisk). At the target machine I see only a CANCEL to which it immediately responds

Hello, I need to detect both fax and answer machine, and it should be valuable that the detection will be run by the Diva card itself. So : - I read Diva Documentation, and I found that the Diva could send some specific DTMF, if I had "[..] enabled [this functionnality] by the application for a designated controller through a manufacturer request command 9 [...]", but I didn't