similar to: CALLERID problems asterisk segfaults

Hello list. I have a question about how to read the incoming calls' callerid on an FXO interface of a TDM 400 analog card; (it's one of those RED modules). Now -may this is the complexity adding step..- I have a GSM gateway attached to this FXO thing; incoming calls are processed as they should. But both when peeking on the CLI, as well as in the phone display I do not see the caller id.

I've updated to the latest CVS as of today (and rebuilt RedHat 9). My setup is as follows: Wildcard X101P - channel 1 TDM400P - channels 2-3 - fxs cards with fxo signalling, channels 4-5 - fxo cards with fxs signalling I got CallerID to work on channel 4 with an old CVS, despite the usual "Didn't finish CallerID spill" message. However, as soon as I insert the following

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

Asterisk Users, I am running a Debian "Etch" system with Asterisk 1.4.11 with a TDM03B card. Once in awhile, I get this error on the Asterisk, which causes my channels to be busy/congested, leaving me with just one channel to recieve and make calls: NOTICE[31454]: chan_zap.c:6367 ss_thread: Got event 17 (Polarity Reversal)... WARNING[31454]: chan_zap.c:6499 ss_thread: CallerID

Dear all. I have a tdm400p with an FXO module in slot 4 and an FXS module in slot 1. I have not configured the FXS port in an attempt to keep things simple. The problem is that when I call the POTS number (assigned by phone company) asterisk is seeing the call but then not doing anything with it. The verbose output from asterisk is as follows:

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

<font size="2">I've got an odd situation where callerid is only picked up every other call.&nbsp; Is there anything I can do so callerid works on all calls?<br><br>I'm seeing the channel hangs up during a call<br><br>&nbsp; == Starting post polarity CID detection on channel 4<br>&nbsp;&nbsp;&nbsp; -- Starting simple switch

Hi, Trying to trace an asterisk hang on a production (it had to be didn't it) system. The last thing before it crashed was [Mar 16 12:32:42] DEBUG[7754] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 4 [Mar 16 12:54:34] DEBUG[7754] chan_zap.c: Ignore switch to REVERSED Polarity on channel 2, state 4 [Mar 16 12:54:35] DEBUG[7754] chan_zap.c: Ignore switch to REVERSED

I am using version: CVS-v1-0-12/13/04-18:46:23 with a TDM400p (2 fxo, 2 fxs ports) and I keep getting errors along with phantom calls: Dec 21 16:02:07 NOTICE[5872]: chan_zap.c:5363 ss_thread: Got event 17 (Polarity Reversal)... Dec 21 16:02:14 WARNING[5872]: chan_zap.c:5434 ss_thread: CallerID returned with error on channel 'Zap/4-1' my analog phone reads caller ID info fine when

Hello Fellows! I have a TDM2400 and I can't put it to work. Every time it receive a call the Asterisk handle it and call the SIP phone; when people pick up the fone they don't hear nothing and the caller hear the phone rings and nothing happens. In Asterisk console I can see the message answered by the SIP's phone. I lost a lot of time trying to solve this problem without success :(.

Hi, I'm running Asterisk 1.0.8 on Gentoo, with an X100P (clone) card, and I'm having problems with Caller ID. I have run clidtest, and it seems happy enough, returning:- server clidtest # ./clidtest /dev/zap/1 Number: 0412222222, Name: MOBILE (that number's fake.) However, I'm not getting the caller ID passed through with *. Sometimes I get a "failed checksum" like

Hi, I'm running Asterisk 1.0.8 on Gentoo, with an X100P (clone) card, and I'm having problems with Caller ID. I have run clidtest, and it seems happy enough, returning:- server clidtest # ./clidtest /dev/zap/1 Number: 0412222222, Name: MOBILE (that number's fake.) However, I'm not getting the caller ID passed through with *. Sometimes I get a "failed checksum" like

Using the latest SVN of zaptel and asterisk, I can no longer receive incoming analog calls. The caller just hears it ringing but Asterisk doesn't pick up. I am seeing these error messages: [Apr 9 09:38:02] WARNING[16564]: chan_zap.c:6470 ss_thread: CallerID returned with error on channel 'Zap/2-1' [Apr 9 09:38:50] WARNING[16570]: chan_zap.c:6470 ss_thread: CallerID

Hi There, We have a Asterisk 1.4 box with a X100P card connected to a analog line with Caller ID serrvices enabled on it. When an incoming call appears we get the following in the log: -- Starting simple switch on 'Zap/1-1' -- Detecting post-CID distinctive ring [Apr 15 10:38:07] NOTICE[7151]: chan_zap.c:6469 ss_thread: Got event 18 (Ring Begin)... [Apr 15 10:38:07] NOTICE[7151]:

HI, im having problem with callerid. Im using tdm2400P and i get this from asterisk logs -- Starting simple switch on 'Zap/4-1' [Mar 24 02:07:48] ERROR[2358]: callerid.c:564 callerid_feed: fsk_serie made mylen < 0 (-1) [Mar 24 02:07:48] WARNING[2358]: chan_zap.c:6416 ss_thread: CallerID feed failed: Success [Mar 24 02:07:48] WARNING[2358]: chan_zap.c:6516 ss_thread: CallerID

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

I'm getting this error on incoming calls on my X100P cards: -- Starting simple switch on 'Zap/1-1' Oct 7 15:49:19 ERROR[74769]: callerid.c:260 callerid_feed: fsk_serie made mylen < 0 (-2) Oct 7 15:49:19 WARNING[74769]: chan_zap.c:5369 ss_thread: CallerID feed failed: Success Oct 7 15:49:19 WARNING[74769]: chan_zap.c:5411 ss_thread: CallerID returned with error on channel

Hi list! I'm not getting incoming CallerID in The Netherlands on my TDM11B. Everything was configures according to the docs at digium.com. The error on the console is this: Feb 13 16:49:40 ERROR[16123]: callerid.c:260 callerid_feed: fsk_serie made mylen < 0 (-84) Feb 13 16:49:40 WARNING[16123]: chan_zap.c:5396 ss_thread: CallerID feed failed: Success Feb 13 16:49:40 WARNING[16123]:

[root@www root]# cat /proc/zaptel/1 Span 1: WCFXO/0 "Wildcard X101P Board 1" 1 WCFXO/0/0 FXSKS (In use) Asterisk CVS-HEAD-02/13/05-00:32:03, Copyright (C) 1999 - 2005 Digium. Feb 15 22:33:48 NOTICE[3002]: callerid.c:307 callerid_feed: Caller*ID failed checksum Feb 15 22:33:51 ERROR[3002]: callerid.c:261 callerid_feed: fsk_serie made mylen < 0 (-6) Feb 15 22:33:51