similar to: caller id problem on incominc call to x100p

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

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

Hi, I have Asterisk 1.4.18 and I have been running call center queues on it. Today it suddenly stopped adding inbound calls to queues. I am facing with following error: app_queue.c:3939 queue_exec: unable to join queue "myqueue" In extension file: Queue(myqueue|t|||120) And my agents are joining in following

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

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

please help!!! I am dialing into our asterisk server(TDM400p) from the psnt. I hear our voicemail message and I press the extention 1000. The Polycom ip phone in the office rings. I pickup but neither side can hear one another. What have I done wrong? thanks sip.conf: [general] context=local-access ; Default context for incoming calls bindport=5060

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

The SM56 MODEM manual says it does. But when used with zaptel 1.2.12, nothing shows up. Yuan Liu

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

dear all, i am looking to enable CALLERID on an Asterisk system comprising a X101P FXO interface connecting to BT PSTN in the uk seems this is supported by the interface but there seems to be varying information on how to enable it in zapata.conf 1. usecallerid=uk 2. ukcallerid=yes being two of the configuration statements offered TIA GT

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

Hello I have couple issues with AAH. 1.5 1. Flash panel doesn't show proper status. Sometime accessing with IP seems to work and it shows current line status etc. Sometimes accessing with hostname of the asterisk server seems to show lines, but it doesn't show off hook etc when we pickup a extension and talk. In /var/www/html/panel/op_server.cfg I have tried setting manager_host to all

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

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

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

hello, i have a problem starting asterisk with one x100p digium and two hfc chipset isdn cards with bri-stuff.0.0.2. "ztcfg -vv" shows me a this info: Zaptel Configuration ====================== SPAN 1: CCS/ AMI Build-out: 399-533 feet (DSX-1) Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: Individual Clear channel (Default) (Slaves: 02) Channel 03:

It might have a noticeable effect on clients. I encountered (probably triggered by this in some way?) that I was unable to het the 'read' bit set in macOS Mail.app. Maybe (as I am doing HA with round robin) the Mail.app client got to one dovecot repository on one tcp connection and then on the other. Is there a reason why syncing tis move from new to cur is a bad idea? Gerben Wierda

I can confirm this in a slightly different setting, but still using two-way sync between two dovecots. On e is 2.3.19.1 running on macOS Monterey, the other is 2.3.20 running in an alpine container on Ubuntu. Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A IT Strategy <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise?Architecture