similar to: pstn hangs up: MWI no message waiting ??

Aloha, I'm finishing up the final touches on this install, and have run into an odd problem. I can't seem to get Caller ID on the analog phone lines working. It's a Digium AEX 410 card. I have Verbose set and a line to print the CID: I have usecallerid=yes and callerid=asreceived set in both chan_dahdi.conf and users.conf [analog] include=>default exten =>

Can anyone tell me what this message means? Got event 17 (Polarity Reversal)... I'm running DAHDI 2.0 with a TDM401 card. Asterisk version 1.6.0. It appears that I get this Polarity Reversal each time an inbound call hangs up. This results in another ring, but no one is there. It appears as an unknown caller, but I believe its a phantom. Thanks, Jim [Oct 10 12:47:54] NOTICE[6669]:

Hi, Using 1.4.26.1 & DAHDI 2.2.0.2, FSK VMWI devices off a TDM840 work fine. With 1.6.1.[45] & same DAHDI, instead of the FSK spill I get a line polarity reversal. Stutter dialtone is generated as expected. Has anyone else seen this? Is there anything special I need to do for 1.6.1 to make FSK MWI work? Thanks, --Barry

Hi ! I ma having trouble with my PTSN line. When I call to my asterisk I get this.. -- Executing [s at from-pstn:3] Hangup("Zap/5-1", "") in new stack == Spawn extension (from-pstn, s, 3) exited non-zero on 'Zap/5-1' -- Hungup 'Zap/5-1' -- Starting simple switch on 'Zap/5-1'[Jan 5 12:45:06] NOTICE[2893]: chan_dahdi.c:6869 ss_thread: Got event 17

i belong to india. i am making pbx using sangoma fxo card. i want that when ever call comes to my PSTN line i should see the no from where call is coming. so i have to configures chan_dahdi.conf according to my region. i checked dahdi.conf and in that they have mentioned for india

So made my first forray into 1.4 and DAHDI and hit a problem. (Not convinced this is a DAHDI issue though...) Testing an analogue line and asterisk sees the caller ID being passed, but then fails to detect ringing. A plain old analogue phone plugged in rings just fine. Console output: == Starting post polarity CID detection on channel 4 -- Starting simple switch on

Hello list, This may or may not be Asterisk related, but if I had hair I'd pull it out over this. I have a TDM400P card in a Dell POWEREDGE 1550 running Asterisk 1.4.30. Everything works great except that every time it rains, I get flooded with this CLI message - == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1'

Hi all, I downloaded a copy of bristuff 0.4.0-RC11 on my Ubuntu 10.04.2 LTS server machine with 2.6.32-24-generic-pae kernel. The prereq.sh script executes without complaints (BTW on my system, libncurses-dev evaluates to libncurses5-dev and libz-dev evaluates to zlib1g-dev). With the asterisk 1.4.41 package that is installed, a make menuselect operation indicates that all dependencies are met

Hello, The company I work for recently purchased 2 Rhino CB24s and a Rhino PCI-E R4T1. The channel banks are plugged into the R4T1, as well as 2 PRIs from our telco. The CB24s are for all internal analog phones. Most of the phones are setup in "batphone mode", which is "immediate=on" in the DAHDI config. They are set up this way because we are an outgoing call

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Making some changes in extensions.conf to test the incoming calls so that these are derived to a SIP extension, I found something that draws attention to me: if I test calling to my PSTN line from a mobile phone, when take the call from the SIP extension (softphone), if the mobile phone releases the call, sofphone do it too without problems,

The TDM410P doesn't support 'hvac', only the obsolete TDM400P supports that option was for the old phones that have a neon light (or equivalent LED+ZENER ciruit). Are other phones off the TDM410P (other than the VTECH) working, or is the Vtech the only model with VMWI available to you. I'm not able to check at the moment, I have copied the asterisk-users list, someone else may

Hi, I am trying to connect a doorbell to a Xorcom device. And the setup is quite simple. But when I push the doorbell all I see on the asterisk cli is: -- Starting simple switch on 'Zap/11-1' [Apr 2 13:00:40] DEBUG[8771]: chan_dahdi.c:6180 ss_thread: not enough digits (and no ambiguous match)... -- Hungup 'Zap/11-1' I defined the extension s,h,i,t,T etc... in my context. Any

Hi all... I have a problem with caller id on my asterisk server. here is my configuration : centos-5, asterisk 1.6.2.1, dahdi-linux-complete-2.2.1, libpri-1.4.10.2 ibm X-3200 series, xorcom astribank (16fxo, 8fxs), 16 line telco (hunting) everything fine until I try to feed my app with caller id. My extensions.conf : [incoming1] exten =>

Callerid issue 1) if you run ztmonitor on the fxo line & call in do you hear the fsk tone if yes then we beleive the CAC is passing fsk 2) in chan_zap->ss_thread around line 4154 (current cvs) if you get to the callerid_feed at least once then if you get to chan_zap->ss_thread->callerid_get around line 4163 (current cvs) does this parse fail

Okay, I can't find what might be causing this. Here is what I got: Asterisk server hooked up to a digital T1 line (full 24-channel) via a Digium card. Verizon has turned on caller ID on the first line (I can guarantee it is on as I can hear the FSK tones on this line but not the others). Using zttool an ZapScan() I have determined the following: 1) The RxB/RxD bits toggle from 1 to 0

Hi all, I've been trying to wrap my mind around this one for several days now. How can I 'debug' the CallerID reception on a Zap/POTS channel? I have a POTS line with CallerID and a Digium TDM11B card right now. I have my signalling set to ks for both sides, can make and receive calls just fine. But I never get CallerID on incoming calls. I get the following messages: Aug 11

Hello, All :) Regarding to incoming caller ID on PSTN line, which one is best supported by asterisk: is it FSK ETSI or FSK US? I bought some caller ID converter hardware (convert DTMF to FSK and vice versa) but still asterisk can not detect it. The converter has a switch FSK ETSI or FSK US This is what I put in /etc/asterisk/chan_dahdi.conf ... cidsignalling=bell cidstart=ring ... If after

Hello everyone, My setup: Debian squeeze Asterisk 1.8, DAHDI, libpri, compiled from source TE110P, attached to a Deutsche Telekom Octopus E Modell 300/800 I'm trying to get MWI for Voicemail working. In the same server I have also got an Eicon DIVA PRI card for testing purposes (it is integrated via CAPI and the chan-capi channel driver into my Asterisk). MWI works just fine there. I

After purchasing the Uniden TRU9480 and then the Panansonic 5672, both of which do not have "phone company" compatible FSK/stutter MWI, I finally got smart and found out just which Panasonic phones have this feature. Only the following 5.8G models in their current line have FXO compatible MWI. I purchased the 5771 unit and one remote. I have confimed it does in fact work with Asterisk

We are using Bellsouth 8867 phones on our TDM400B FXS lines (asterisk-1.0.3). It has a "Voicemail" light, which appears to be MWI (according to the manual it works with voicemail from the telco that sends a FSK signal). The dialtone stutters when a line has voicemail, so I know that I have the mailbox setting right in zapata.conf, but the light doesn't go on. I am also getting