similar to: "auto fallthrough" hangup on 1.2.1

Displaying 20 results from an estimated 4000 matches similar to: ""auto fallthrough" hangup on 1.2.1"

2006 Jan 14
3
1.2.1 "Silence suppression is disabled" what the hell?
I upgraded from 1.0.9 to 1.2.1. In 1.0.9 everything worked perfect. Now, I call in my IVR, and after navigating in menus when I get dialtone for dialing extension, Sound is choppy and I get bunch of messagess: -- Silence suppression is disabled (option_silence_suppression=0 chan->timingfd=30) -- Silence suppression is disabled (option_silence_suppression=0 chan->timingfd=30) -- Silence
2006 Jan 14
2
1.2.1 "Silence suppression is disabled" whatthehell?
I looks like someone decided to bundle a patch that hasn't been merged yet. Good for testing, not so good for initial impressions. In /etc/asterisk/asterisk.conf add or uncomment this: [options] ;silence_suppression=yes And see if that helps. You need a timing source for it to work, which is why it is disabled by default, but the logging might be a bit chatty in any case. Dan
2006 Jan 06
2
Voice mail messages aren't sent to e-mail
Voice-mail messages aren't sent to e-mail address. I have two Asterisk servers, first one is upgraded from 1.0.RC2 to 1.0.9, and second one is from 1.0.7 to 1.0.9. Both Asterisk have EXACTLY same "voicemail.conf" configuration, but second Asterisk don't sending voice mail messages through e-mail! I'm using almost default "voicemail.conf" with just one mailbox
2006 Jan 14
4
Ugly echo cancel, with Bristuff/Zaphfc
I'm using bristuffed Asterisk with ISDN/ZAPHFC I have VERY ugly (outgoing) sound through ISDN/HFC if echocancel=yes in zapata.conf, but without echocancel I have bad (incoming) echo Through PSTN/FXO sound is ok with or without echocancel. I tried other echo cancellers (in zconfig.h) two times: ECHO_CAN_KB1 (this was default) ECHO_CAN_MARK2 ECHO_CAN_MG2 after any change I compiled (make
2006 Feb 28
1
why incoming DATA CALLS are answered as VOICE by asterisk IVR?
When incoming DATA call arrive on ISDN BRI, asterisk (zaphfc) recognise that this is DATA call, but answering anyway (playing IVR messages, etc...) How to stop that? I want that only VOICE calls are answered, and DATA/FAX to be ignored. (I'm using Asterisk 1.2.1 Brisftuffed 0.3.0-PRE-1f, ZapHFC) Log: -- Accepting data call from 'XXXXXXXX' to '3001' on channel 0/2, span 1
2005 Jun 14
2
# no longer working
Hi list, For months everything worked super here in our setup. This week I implemented some new idea in our webbased calendar system. I thought it would be nice to have an option that tells asterisk you are not available for calls during an appointment. For this to work I could no longer use the ringgroup setup: Dial(SIP/10&SIP/11&SIP/12,40,tr) So I thought, why not use the Local channel
2006 Mar 09
4
IVR woes
Hello all. I'm having a problem debugging an IVR I'm building. I can't see any reason this shouldn't be working. Firstly the asterisk version is: Asterisk SVN-trunk-r7230 built by root @ localhost.localdomain on a i686 running Linux on 2006-02-17 22:44:48 UTC Basically the problem is this. While the playbacks are happening you can push any one of the options and to happily
2007 Mar 21
3
Solaris Dovecot dovecot dovecot-1.0.rc27
To all, I am using Dovecot on solaris 10. Home directories are mounted using NFS. However, they are not readable by root. I compiled Dovecot from the source. I set the following environment variables: export LDFLAGS='-L/local/software/openssl/lib -R/local/software/openssl/lib' export CPPFLAGS=-I/local/software/openssl/include Then I ran gmake and the gmake install. In the server
2016 Jun 28
2
id username output ADDC and Member.
> > I love diving : ) > Ok mathias, Can you explain this. This i dont get.... Why is this output so different, and i dont mean the difference with NTDOMAIN\.. See the groups differences... between a ADDC and a member server.. Samba 4.4.3 ADDC id someusername uid=10002(NTDOMAIN\someusername) gid=10000(NTDOMAIN\domain users) groups=10000(NTDOMAIN\domain
2020 Jun 04
4
clang 10 -Wimplicit-fallthrough
Hi. I upgraded my main build host and the clang -Werror builds started failing. This is because clang 10's -Wimplicit-fallthrough doesn't understand /* FALLTHROUGH */ but rather requires __attribute__((fallthrough)): clang -Wall -O2 [...] -Wimplicit-fallthrough [...] -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_DEFAULT_SOURCE -DHAVE_CONFIG_H -c /openbsd-compat/base64.c
2018 Nov 01
2
RFC Enable -Wimplicit-fallthrough for clang as well as GCC
Great! Thanks everyone for the input, I'm going to start splitting up the patch. I'll send out the non-mechanical parts separately. On Wed, Oct 31, 2018 at 10:03 PM Chris Lattner <sabre at nondot.org> wrote: > On Oct 31, 2018, at 2:24 PM, Reid Kleckner <rnk at google.com> wrote: > > Alex Kornienko proposed enabling this warning back in 2012 here: >
2006 Feb 07
1
MFC/R2 in Brazil
I don?t know if the last message was with content. So, I sent again. I have installed a Digium card TE210P and unicall for use MFC/R2. I think that it?s all right but I can?t make and receive calls. I?m using asterisk 2.1 with the patch made by Jos? P. Leit?o and the follow libs: libsupertone-0.0.2 libunicall-0.0.3 libmfcr2-0.0.3 zaptel 2.1 My number is 34318300. The Telco send me only 8300.
2008 Sep 01
3
[LLVMdev] Unresolveable fallthrough functions
Hello, > ready> ERROR: Program used external function 'putchard' which could not be > resolved! > Any idea of what could be wrong? Please make sure you're using C linkage for such functions, due to mangling the name of function being emitted is not "putchard". Something like this: extern "C" void putchard(char c) { ... } Or, just provide a mapping
2006 Jan 13
1
CALLERIDNUM::3 do not working on 1.2.1
I upgraded from 1.0.9, to 1.2.1. I was using this line exten => s,1,gotoif($[${CALLERIDNUM::3} = 066]?mycity,1:other,1) it selecting calls if callerid begins with some number pattern (from some city) But, it's not working anymore in Asterisk 1.2.1 when I test this with noop(${CALLERIDNUM::3}) I get full callerid, not just first 3 numbers like it use to be on 1.0.9 Why?
2004 Dec 13
1
incoming call from pstn to fxo not working with Asterisk
When somebody call me on my pstn # cable connected to my fxo card it does not work when I check my computer the following error shows Connected to Asterisk CVS-v1-0-12/05/04-19:46:25 currently running on asterisk1 (pid = 2160) Verbosity is atleast 3 -- Remote UNIX connection -- Starting simple switch on 'Zap/1-1' == Starting Zap/1-1 at incoming,s,1 failed so falling
2004 Dec 02
3
fallthrough extension.
Hi all, I'm trying to sort out my dial plan. What I'm wanting is something like the following - a bit simplified but hopefully you'll get the idea. 1) match internal extensions: dial them 2) anything else: send out zap 1 is easy :) it's 2 that's giving me problems. I had hoped that the 'i' extension would act as a catchall extension but it seems to only do that from
2013 Apr 18
3
Having difficulty exporting display
Hello, This is my issue, my remote machine (CentOS 6.3, hosted in Azure windows environment) has an application that I need to test on my local box (CentOS 6.4, a laptop behind a router). Now, this is what I'm doing and the issue that I'm encountering: Local: $ xhost + $ ssh -X someusername at somehostname.net -p 49283 Remote: $ export DISPLAY=192.168.1.6:0.0 $ xclock ... and nothing,
2007 Jan 09
1
Asterisk 1.2.11 - ResponseTimeout being ignored
All - this is probably a simple problem, but I've been pulling my hair out trying to figure out what I'm doing wrong. I'm building a *simple* IVR menu. Here it is: [main-menu] exten => s,1,Answer exten => s,2,SetMusicOnHold(default) exten => s,3,DigitTimeout(5) exten => s,4,ResponseTimeout(30) exten => s,5,Background(logic-main) exten =>
2008 Sep 01
0
[LLVMdev] Unresolveable fallthrough functions
Anton Korobeynikov wrote: > > Hello, > >> ready> ERROR: Program used external function 'putchard' which could not >> be >> resolved! >> Any idea of what could be wrong? > Please make sure you're using C linkage for such functions, due to > mangling the name of > function being emitted is not "putchard". Something like this: >
2020 Jul 07
3
[PATCH][next] drm/nouveau: Use fallthrough pseudo-keyword
Replace the existing /* fall through */ comments and its variants with the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary fall-through markings when it is the case. [1] https://www.kernel.org/doc/html/latest/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through Signed-off-by: Gustavo A. R. Silva <gustavoars at kernel.org> ---