similar to: random hangups: how to debug?

pstn incoming on a TDM400P, sometimes i* won't answer, going into a loop like this: -- Starting simple switch on 'DAHDI/4-1' [Jan 16 10:38:55] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 18 (Ring Begin)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7130 ss_thread: Got event 2 (Ring/Answered)... [Jan 16 10:38:57] NOTICE[5808]: chan_dahdi.c:7299 ss_thread: MWI: Channel 4

-----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,

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 =>

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 =>

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

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]:

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 , Thanks danny nicholas. Finally we get the things done with following. If i specify busypatten=500,500 then asterisk does not recognize hang up signal. After removing it only all are working fine. I choosed 2nd option as per your suggestions. working chan-dahdi.conf: ==================== signalling = fxs_ks busycount = 3 busydetect = yes callprogress = yes progzone=in usecallerid=yes

hello all...I have been trying to get a handle on CallerPres with an analog handset. I have usecallingpres=yes in my chan_dahdi.conf file and when I dial *67 on my analog handset I see Disabling Caller*ID on DAHDI/4-1 but when the call is then forwarded to my outbound SIP provider the RPID header is not correct privacy=off;screen=no instead of full and yes how can I correct this?

Hi all... I'm sorry for repeating my message. I have a problem with caller id on my asterisk server with xorcom astribank. 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. here is the log : --

Aloha, I'm not sure why I'm getting this error, but I can't seem to get chan_dahdi to load. SIP & IAX2 are working fine. Debian 4 w/ 2.6.28 kernel. Asterisk 1.6.1.5, dahdi-linux 2.2.0.2, dahdi-tools-2.2.0 CLI> module load chan_dahdi.so Unable to load module chan_dahdi.so Command 'module load chan_dahdi.so' failed. [Sep 1 10:57:51] WARNING[31696]: pbx.c:4550

Hello, I have a Sangoma A200 analog card with 2 FXO ports. It's working well with asterisk 1.4.22 and Zaptel. I decided to upgrade to asterisk 1.6/dahdi. I compiled and installed, dahdi-linux-2.1.0.4 dahdi-tools-2.1.0.2 libpri-1.4.10 wanpipe-3.4.1 asterisk 1.6.1.1 My analog card is recognized in dahdi_hardware. However, asterisk cannot compile chan_dahdi.so. I've tried passing

after installing asterisk 1.4.23.1 and dahdi-linux-2.1.0.4 and at CLI> module load chan_dahdi.so receive the following: signalling must be specified before any channels are. CLI> Warning [4663]: chan_dahdi.c:11627 process_dahdi: Ignoring signalling Error[4663]: chan_dahdi.c:10946 build_channels: Unable to reconfigure channel '1' Error[4663]:

So, tweaking configs, rebuilding this and that... restarting, twiddling, it works (yeah!), but fails on re-boot to work at all. Consistently, though. I believe it comes down to this: I can call out only *after* I've received a call. So, cold boot. Then: modprobe dahdi modprobe wctc4xxp modprobe wcfxo dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.3

Hello everyone, I am facing a strange problem on my asterisk box (using isdn lines with pri card installed on it). Normal incoming/outgoing calls are working perfectly fine. When a user dial a wrong/out-of-service number they don't hear back any such message like "The number is wrong or user is switched off" in some cases, and it's just a silence for the user. Now while

I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO modules. When I plug one PSTN-line into a FXO-port I am able to receive calls on this line and I can also make calls from an internal SIP-phone to the external PSTN-network. Still I am bothered about something that appears on the CLI when I do a reload chan_dahdi.so : asterisk*CLI> reload chan_dahdi.so -- Reloading module

Hi I have been having a rough time getting a Sangoma A200/Remora FXO/ FXS Analog AFT card set up properly. The main issue is that the card has four ports and as far as I can tell Asterisk is only seeing two. On the two that it recognizes the "Green" FXS ports are not green, they just are not lit. The "RED" FXO ports are indeed red, but from what I have read your not

[2009-05-27 02:06:16.294] WARNING[6971] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway! [2009-05-27 02:06:16.295] VERBOSE[6971] logger.c: [2009-05-27 02:06:16.295] == Primary D-Channel on span 1 up [2009-05-27 02:06:16.301] ERROR[6971] chan_dahdi.c: !! Got a UA, but i'm in state 7 I noticed the above error many days after this at around 2AM. This

Hi all, I am having trouble setting the signalling method for the B410P using DAHDI. Asterisk complains that it has never heard of 'bri_cpe' or 'bri_net' - but it doesn't mind having 'pri_cpe' etc. ERROR[4294]: chan_dahdi.c:11327 process_dahdi: Unknown signalling method 'bri_net' Dahdi - dahdi-linux-complete-2.1.0.4+2.1.0.2 Asterisk - 1.4.23.1 Libpri - 1.4.9