[asterisk-users] Caller ID issues

[Eric "ManxPower" Wieling]

The NOTICEs indicate that Caller*ID should be getting into the system. 
I don't know what else to suggest.

Bruce Reeves wrote:
> Are there different error messages for too high or too low. The reason I 
> ask
> is I tried making some adjustments and running ztmonitor while calling a
> line and what I saw was that when the rxgain was pretty high
> 
> Nov 27 16:24:07 ERROR[7877]: callerid.c:276 callerid_feed: fsk_serie made
> mylen < 0 (-117)
> 
> But when I got it extremely low I got
> 
> Nov 27 16:37:48 NOTICE[7907]: callerid.c:325 callerid_feed: Caller*ID 
> failed
> checksum
> 
> However if I got some where in the middle according to ztmonitor I only 
> got:
> 
> Nov 27 16:37:28 NOTICE[7903]: chan_zap.c:6073 ss_thread: Got event 18 (Ring
> Begin)...
> Nov 27 16:37:31 NOTICE[7903]: chan_zap.c:6073 ss_thread: Got event 2
> (Ring/Answered)...
> 
> I still never got the caller id.
> 
> 
> On 11/27/06, Eric ManxPower Wieling <eric at fnords.org> wrote:
>>
>> CallerID (in the USA and Canada) comes in as a 1200 or 2400 baud FSK
>> burst, just like a modem.  If the volume is too high the audio gets
>> distorted, if it is too low it is distorted.
>>
>> Bruce Reeves wrote:
>> > How does the gain play into the callerid? And would the gain being to
>> low
>> > actually effect all 3 lines not just the first 2?
>> >
>> > On 11/27/06, Eric ManxPower Wieling <eric at fnords.org> wrote:
>> >>
>> >> adjust your rxgain up or down
>> >>
>> >> Anton Frolov wrote:
>> >> >
>> >> > Bruce Reeves wrote:
>> >> >
>> >> >> Nov 21 16:54:09 ERROR[6039] caller id.c: fsk_serie made mylen < 0
>> (-9)
>> >> >> Nov 21 16:54:09 WARNING[6039] chan_zap.c: CallerID feed failed:
>> >> Success
>> >> >> Nov 21 16:54:09 WARNING[6039] chan_zap.c: CallerID returned with
>> error
>> >> >> on channel 'Zap/1-1'
>> >> >
>> >> > I have exactly the same problem with 1.2 debian (Ubuntu) package and
>> a
>> >> > TDM400P card (2 FXO + 2 FXS). The only difference is that "feed
>> failed:
>> >> > Success" is logged as a warning and not as an error.
>> >> >
>> >> > Since I'm just started to use asterisk, I presumed it happens
>> >> because of
>> >> > a misconfig.
>> >> _______________________________________________
>> >> --Bandwidth and Colocation provided by Easynews.com --
>> >>
>> >> asterisk-users mailing list
>> >> To UNSUBSCRIBE or update options visit:
>> >>    http://lists.digium.com/mailman/listinfo/asterisk-users
>> >>
>> >
>> >
>> >
>> >
>> > 
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > --Bandwidth and Colocation provided by Easynews.com --
>> >
>> > asterisk-users mailing list
>> > To UNSUBSCRIBE or update options visit:
>> >    http://lists.digium.com/mailman/listinfo/asterisk-users
>> >
>> >
>> > 
>> ------------------------------------------------------------------------
>> >
>> > This message has been 'sanitized'.  This means that potentially
>> > dangerous content has been rewritten or removed.  The following
>> > log describes which actions were taken.
>> >
>> > Sanitizer (start="1164664455"):
>> >   Part (pos="3296"):
>> >     Part (pos="133"):
>> >       SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>> >         Match (names="unnamed.txt", rule="1"):
>> >           Enforced policy: accept
>> >
>> >     Part (pos="1411"):
>> >       SanitizeFile (filename="unnamed.html, filetype.html",
>> mimetype="text/html"):
>> >         Match (names="unnamed.html, filetype.html", rule="3"):
>> >           ScanFile (file="/tmp/att-456b5e87-RJ8-unnamed.html"):
>> >             Scan succeeded, file is clean.
>> >
>> >           Enforced policy: unknown
>> >
>> >         Match (names="unnamed.html, filetype.html", rule="4"):
>> >           Enforced policy: accept
>> >
>> >       Note: Styles and layers give attackers many tools to fool the
>> >       user and common browsers interpret Javascript code found
>> >       within style definitions.
>> >
>> >       Rewrote HTML tag: >>_div_<<
>> >                     as: >>_p__DEFANGED_div_<<
>> >       Rewrote HTML tag: >>_span class="gmail_quote"_<<
>> >                     as: >>_DEFANGED_span class="gmail_quote"_<<
>> >       Rewrote HTML tag: >>_/span_<<
>> >                     as: >>_/DEFANGED_span_<<
>> >       Rewrote HTML tag: >>_blockquote class="gmail_quote"
>> style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt
>> 0.8ex; padding-left: 1ex;"_<<
>> >                     as: >>_blockquote class="gmail_quote"
>> DEFANGED_style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 
>> 0pt
>> 0pt 0.8ex; padding-left: 1ex;"_<<
>> >       Rewrote HTML tag: >>_/div_<<
>> >                     as: >>_/p__DEFANGED_div_<<
>> >
>> >   Part (pos="6513"):
>> >     SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>> >       Match (names="unnamed.txt", rule="1"):
>> >         Enforced policy: accept
>> >
>> >   Total modifications so far: 5
>> >
>> >
>> > Anomy 0.0.0 : Sanitizer.pm
>> > $Id: Sanitizer.pm,v 1.94 2006/01/02 16:43:10 bre Exp $
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> 
> ------------------------------------------------------------------------
> 
> This message has been 'sanitized'.  This means that potentially
> dangerous content has been rewritten or removed.  The following
> log describes which actions were taken.
> 
> Sanitizer (start="1164668563"):
>   Part (pos="3399"):
>     Part (pos="133"):
>       SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>         Match (names="unnamed.txt", rule="1"):
>           Enforced policy: accept
> 
>     Part (pos="5326"):
>       SanitizeFile (filename="unnamed.html, filetype.html", mimetype="text/html"):
>         Match (names="unnamed.html, filetype.html", rule="3"):
>           ScanFile (file="/tmp/att-456b6e93-2CF-unnamed.html"):
>             Scan succeeded, file is clean.
> 
>           Enforced policy: unknown
> 
>         Match (names="unnamed.html, filetype.html", rule="4"):
>           Enforced policy: accept
> 
>       Note: Styles and layers give attackers many tools to fool the
>       user and common browsers interpret Javascript code found
>       within style definitions.
>       
>       Rewrote HTML tag: >>_div_<<
>                     as: >>_p__DEFANGED_div_<<
>       Rewrote HTML tag: >>_span class="gmail_quote"_<<
>                     as: >>_DEFANGED_span class="gmail_quote"_<<
>       Rewrote HTML tag: >>_/span_<<
>                     as: >>_/DEFANGED_span_<<
>       Rewrote HTML tag: >>_blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"_<<
>                     as: >>_blockquote class="gmail_quote" DEFANGED_style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"_<<
>       Rewrote HTML tag: >>_/div_<<
>                     as: >>_/p__DEFANGED_div_<<
> 
>   Part (pos="17048"):
>     SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>       Match (names="unnamed.txt", rule="1"):
>         Enforced policy: accept
> 
>   Total modifications so far: 5
> 
> 
> Anomy 0.0.0 : Sanitizer.pm
> $Id: Sanitizer.pm,v 1.94 2006/01/02 16:43:10 bre Exp $