similar to: Continuously ringing Zap/4-1 TDM11B All of a sudden ?[Urgent Pls]

Displaying 20 results from an estimated 600 matches similar to: "Continuously ringing Zap/4-1 TDM11B All of a sudden ?[Urgent Pls]"

2005 Feb 13
0
No CallerID on TDM11B?
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]:
2007 Aug 02
1
A simple IVR extension problem
Hi list, I am running TDM11b + Asterisk-1.4.9 + Zaptel-1.4.4 + Libpri-1.4.1 on CentOS 5. I am having trouble to make my simple IVR extension work, here is relevant config: zapata.conf ---- context=incoming signalling=fxs_ks channel => 4 context=internal signalling=fxo_ks channel => 1 ----- extensions.conf: ---- [office] exten => s,1,Dial(Zap/1,30) [home] exten =>
2004 Aug 11
1
CallerID Debug On Zap/POTS Channel
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
2004 Jun 09
0
curious (and incorrect) caller*id behavior
Hi- I have an FXO module in my TDM400P configured to receive caller*id (see zapata.conf below). I get a curious behavior: When I call this line with my cell phone, I see caller ID received just fine, with no warnings or errors.. When I call from another landline, I get different results: calling from external line, caller ID off: WARNING[1233021872]: chan_zap.c:4980 ss_thread: CallerID
2004 Jul 13
1
caller id problem on incominc call to x100p
hi, when i call asterisk (on x100p) i got this : CLI> -- Starting simple switch on 'Zap/7-1' Jul 13 15:03:34 ERROR[311316]: callerid.c:192 callerid_feed: fsk_serie made mylen < 0 (-9) Jul 13 15:03:34 WARNING[311316]: chan_zap.c:4735 ss_thread: CallerID feed failed: Success Jul 13 15:03:34 WARNING[311316]: chan_zap.c:4777 ss_thread: CallerID returned with error on channel
2008 Mar 23
1
zap callerid problem
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
2005 Aug 01
1
X100P/Caller ID: clidtest works, * complains [repost]
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
2005 Jul 22
1
X100P not answering
I have an Asterisk server running todays CVS (updated it just in case that was the problem). It has 3 X100P cards. The first two lines I use as my normal work lines and the third is my fax line which I use with SpanDSP. I run Fedora Core 4. I have a problem that the third X100P does not answer the call. From the console I can see that there is an incoming call with the following: --
2005 Feb 15
0
X100p + cell socket no callerid
[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
2005 Jul 29
0
X100P/Caller ID: clidtest works, * complains
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
2003 Sep 20
2
False RING (incoming call) on Digium X101P FXO
I have a normal backup phone (and an alarm panel) sharing the POTS line with the Digium X101P FXO: | | Wall |>---+------X101P FXO as Zap/5 | | | Phone & Alarm Whenever the Phone is used, Asterisk sees a 'false ring' signal immediately when the phone is hung up. The Alarm panel dials out nightly at around 1AM, and each time it completes the call, Asterisk
2004 May 07
0
caller id detection
Hi! I know that is a very posted matter but i have a question: Some one can translate that messages for me? what is the mean of that messages? can i do something to correct this and get the caller id to work? May 7 11:26:19 ERROR[1288925632]: callerid.c:192 callerid_feed: fsk_serie made mylen < 0 (-22) May 7 11:26:19 WARNING[1288925632]: chan_zap.c:4609 ss_thread: CallerID feed failed:
2004 Jul 12
1
CID not appearing via X100P
Hi Folks, Prior to upgrading my Zaptel sources everything was working fine. I have a X100P connected to my analogue line. The handset port of the X100P is connected to my desk phone's line 2 input. When the analogue line rings I see the CID on my line 2 but not from Asterisk on line 1 via the Cicso ATA. This used to work fine until I upgraded the sources. I get this when watching the
2004 Sep 08
0
transfer on a zaptel FXO port
I am attempting to transfer a number that comes in on an FXO port back out the same port. The service has 3 way calling and transfer and these options are specified in zapata.conf . Some config... zapata.conf ------------ [channels] ; context=incoming signalling=fxs_ks echocancel=yes echocancelwhenbridged=yes relaxdtmf=yes rxgain=1.5 txgain=1.5 immediate=no busydetect=yes callprogress=no
2004 Oct 07
0
CallerID X100P
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
2005 Aug 05
0
CallerID Problems.
Hi everyone. I need to get CallerID to route incoming calls, but i keep getting this on the CLI for the callerid ================================= -- Starting simple switch on 'Zap/1-1' Aug 5 13:18:50 ERROR[2756]: callerid.c:260 callerid_feed: fsk_serie made mylen < 0 (-85) Aug 5 13:18:50 WARNING[2756]: chan_zap.c:5434 ss_thread: CallerID feed failed: Success Aug 5 13:18:50
2006 Feb 12
2
Zap, Caller ID problem
Dear All, I've got a weird problem with my asterisk box which has fxo interfaces (TDM400). Well, the problem is that the interface answers the call, but no caller id is being received. Also, sometimes this error happens: fsk_serie made mylen < 0 Any idea what is going on? Thanks, Kaveh __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has
2006 Nov 27
1
Caller ID issues
I am going to be on site at one of my recent installs tomorrow and I am hoping to fix an issue with the caller id. I would like suggestions for possible problem areas and so I thought I would give as much details as I can. The system has a Sangoma A200D card in it with 4 FXO ports and 2 FXS, The incoming pstn lines are all 3 part of a hunt group and At&t has confirmed the settings for caller
2007 Jul 01
1
Asterisk strange behaviour
Hi all I?m a newbie to asterisk and I have install and configure asterisk 1.4.5 I have made some test and have face a strange behaviour I hava a simple dialplan when a call is receive from PTSN, [PSTN] exten => s,1,Answer() exten => s,2,Playback(intro-sicx) ; Listen to your voice exten => s,3,Dial(SIP/steph) exten => s,4,Hangup() I got the following when a call is
2005 Feb 10
0
Context fails so falling back to extension "s" ?
I realize it's bad form, but I'd really appreciate some hand holding here. AMP is making me pull my hair out and the mountain of configuration data in extensions.conf is starting to get to me... I have the first channel configured in zapata.conf to "take" incoming contexts to "from-pstn". I'm using AMP neat "Incoming Calls" configuration page and