similar to: Caller*ID failed checksum?

Dear All, I am a newbie about asterisk. I have 1x X100P card 3x Sip phone I got aware of problem, after I saw the caller id on my sip phone. I noticed that if I receive a call from GSM Operator A, I can see caller id. But any other operator, I got no caller id, even my direct PSTN service operator. So at that moment I was using *1.0.9. than I changed to asterisk@home 1.3(1.0.9). I got same

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

For some thime now I have been trying to get some sense out of Caller ID on PSTN lines in AU and have been getting no where. Now, at last, I seem to be getting something, even though it is an error message (line 5 below). All and any guidance would be welcome. -- Starting simple switch on 'Zap/1-1' Jan 10 09:36:38 NOTICE[18384]: chan_zap.c:5514 ss_thread: Got event 2

Hey all...for whatever reason my caller id doesn't appear to be working. My setup is simple (Wildcard FXO and thats it) and I'm just expecting the Caller ID to show up on the console. I'm seeing this: *CLI> -- Starting simple switch on 'Zap/1-1' NOTICE[262161]: File callerid.c, Line 238 (callerid_feed): Caller*ID failed checksum NOTICE[262161]: File chan_zap.c, Line

Nicol?s Gudi?o <asternic@gmail.com> wrote: >>> Paul, 1.0.5 stable suffers from caller id issues as well, at least for >>> SIP channels. What fixed things for me was swapping in app_dial.c from >>> 1.0.2 stable (didn't try others). You could also just diff app_dial.c >>> between versions to find the problem but I took the lazy way out the >>>

Any body used patch, http://bugs.digium.com/bug_view_page.php?bug_id=0001719 to get the callerid for BT Line. I applied the patch successfully but could not get it to work. Any help. Here are the logs: -- Starting simple switch on 'Zap/1-1' Jun 17 18:22:31 NOTICE[426000]: chan_zap.c:4811 ss_thread: Got event 2 (Ring/Answered)... Jun 17 18:22:34 NOTICE[426000]: chan_zap.c:4811

Caller*ID used to work as some point, but I can't seem to get it going these days. The card is a x101p. I've tried going up and down the rxgain scale. Can the txgain effect it at all? When I plug in a phone into the line with a splitter it can decode caller id with no problems. Reading through the mailing list archives hasn't given me any move clues. Any ideas?

I have set up my asterisk PBX to provide a double-ring for outside calls, and a single ring for station-to-station. (I'm talking about ZAP stations in this email). I had to go into one of the .c files and tell it to expect the Caller ID between the 2nd and 3rd rings in order to get the double-ring scenario to work. My problem is that, in making this change, I now don't see Caller ID on

I am having problems getting incoming caller id to work on a Telstra Onramp 10. I have changed "/DEFAULT_CIDRINGS 2"/ Is there something i'm missing ? My Cisco 7960 just shows "asterisk" Thanks, Nathan [zapata.conf] context=incoming usecallingpres=yes relaxdtmf=no rxgain=0.0 txgain=0.0 busydetect=no pridialplan=local usecallerid=yes callerid=asreceived

Hello People, I was wondering if you could take a look at this script, exten => 505,1,dial(iax2/6311${EXTEN},t,25) exten => 505,2,playback(pls-wait-connect-call) exten => 505,3,set(NewCaller=${CALLERID(num)}) exten => 505,4,Set(CALLERID(num)=0${CALLERID(num)}) exten => 505,5,dial(Zap/g1/c/0296389675,20,r) exten => 505,6,Set(CALLERID(num)=${NewCaller}) exten

Hello list, I'm observing what I believe to be inconsistent behaviour regarding "Newstate" AMI events for the "Ringing" state. As such I come to you asking for experience or advice: am I wrong or should I file a bug ? I present you a short introduction which I feel is relevant; however, if you want to go straight to my technical question, please scroll

Hello, I'm wondering why asterisk is not transferring the callerid to the sip device. Scenario as follows: sangoma <---> zaptel <---> asterisk <---> sip <---> SIP-Device zaptel is reporting the callerid, but in the sip packages the sip-address shows unknown as user part, as this sip debug package shows: Executing Dial("Zap/62-1",

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

I am trying to understand the relationship between loadzone and callerid. I am located in New Zealand and have noticed the following behaviour: Case A zaptel.conf loadzone = nz defaultzone = nz The Zap extension rings with NZ-style ringing but caller id doesn't work (message: Didn't finish Caller-ID spill). This is the case whether the call is external from Zap FXO or internal from SIP.

This is with an x100p (the motorola chipset) Two problems. Looks like CALLERIDNAME is being used uninitialized. On my other phones the callerid is fine and my buttset shows that the callerid passes the checksum. This is the relevant portion of extensions.conf exten => s,1,Answer exten => s,2,SetCallerID(H ${CALLERIDNAME} <${CALLERIDNUM}>) exten => s,2,Dial(${MGCP_ALL}) Here is

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 can't seem to hide and/or set my caller ID from *. I'm using a quite recent (three weeks or so) CVS with an E400P card. I have pridialplan=unknown in zapata.conf and I'm based in the UK. The relevant bit of pri debug looks like this (reformatted to fit 80 char width): > Calling Number (len= 4) [ Ext: 0 > TON: Unknown Number Type (0) >

I have a line from BT (UK) connected to my asterisk system, on a TDM400P. I am able to see either distinctive ring cadences or caller ID but not both. If I try to enable both, all drings show up as 0,0,0. This is a pain because, if I make a call out over that line and the number I call is busy, I can elect to camp on it (ringback), which results in a different cadence of ring when the called

I was just on 70minute call (IAX2 -> Internet -> IAX2) and during that time I heard several "pops", or "clicks". Each time it happened, I saw the following message: Aug 19 15:36:36 NOTICE[1173711792]: rtp.c:429 ast_rtp_read: RTP: Received packet with bad UDP checksum Any ideas what causes these, and why they turn in to a "pop", instead of just silence, or a