[Asterisk-Users] Problems with Caller ID on FXO

[Chris Hirsch]

And a followup for some debug messages for ManxPower (2nd time since I 
can't seem to get all the details :-) ):

FXO Card Installed:
[root at bean asterisk]# cat /proc/zaptel/1
Span 1: WCFXO/0 "Wildcard X101P Board 1"

           1 WCFXO/0/0 FXSKS (In use)

Analog Line:
AT&T Broadband coming over cable and then into standard phone lines. 
Caller ID on other phones works fine.

Asterisk Version is Latest from CVS as of around 09:30 MST today:

This is the output when I receive a call:
*CLI>     -- Starting simple switch on 'Zap/1-1'
NOTICE[262161]: File callerid.c, Line 238 (callerid_feed): Caller*ID 
failed checksum
ERROR[262161]: File callerid.c, Line 192 (callerid_feed): fsk_serie made 
mylen < 0 (-30)
WARNING[262161]: File chan_zap.c, Line 4340 (ss_thread): CallerID feed 
failed: Success
WARNING[262161]: File chan_zap.c, Line 4357 (ss_thread): CallerID 
returned with error on channel 'Zap/1-1'
NOTICE[262161]: File app_dial.c, Line 502 (dial_exec): Unable to create 
channel of type 'IAX'
  == Everyone is busy at this time
WARNING[262161]: File pbx.c, Line 1810 (ast_pbx_run): Timeout, but no 
rule 't' in context 'inbound-analog'
    -- Hungup 'Zap/1-1'

I understand the problem with the IAX stuff since I don't have that 
quite configured yet....

Chris Hirsch wrote:

> I'm still 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 4314 (ss_thread): Got event 2 
> (Ring/Answered)...
>
> My zaptel.conf:
> fxsks=1
> loadzone = us
> defaultzone=us
>
> My zapata.conf:
> [channels]
> language=en
> context=inbound-analog
> signalling=fxs_ks
> usecallerid=yes
> echocancel=yes
> echocancelwhenbridged=yes
> channel => 1
>
> Now I just realized that I haven't set up my sound card on this 
> computer and I'm seeing
>  WARNING[98311]: File chan_oss.c, Line 232 (sound_thread): Read error 
> on sound device: Resource temporarily unavailable
>
> Is that necessary to somehow read the caller id burst?
>
> Eric Wieling wrote:
>
>>On Fri, 2003-10-03 at 13:28, Chris Hirsch wrote:
>>  
>>
>>>failed checksum
>>>NOTICE[262161]: File chan_zap.c, Line 4314 (ss_thread): Got event 2 
>>>(Ring/Answered)...
>>>    
>>>
>>
>>I've only seen this message when using callprogress=yes and/or
>>busydetect=yes.  Set them to no.
>>
>>  
>>
>
>-- 
>Do pediatricians play miniature golf on Wednesdays?
>
>
>http://ccicolorado.org
>Exceptional Dogs for Exceptional People - Help Out Today!
>
>  
>

-- 
If at first you don't succeed,then skydiving isn't for you


http://ccicolorado.org
Exceptional Dogs for Exceptional People - Help Out Today!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20031006/bc6de31b/attachment.htm