Caller ID woes

I posted awhile back about caller id reception problems. I had difficulties receiving caller id info for calls from my work, in which we use Time Warner Telecom, and from cellphones on Cingular and Cincinnati Bell (randomly). Regular landline calls work just fine, and called from Verizon Wireless are fine.

I upgraded to the latest Zaptel (1.2.13) thinking (hoping, actually!) that it may be a bug, but it still happens.

Here is an excerpt from the console log:

Nov 29 13:54:03 ERROR[18470]: callerid.c:276 callerid_feed: fsk_serie made mylen < 0 (-9)
Nov 29 13:54:03 WARNING[18470]: chan_zap.c:6105 ss_thread: CallerID feed failed: Success
Nov 29 13:54:03 WARNING[18470]: chan_zap.c:6149 ss_thread: CallerID returned with error on channel 'Zap/1-1'
    -- Executing NoOp("Zap/1-1", """ <>") in new stack
    -- Executing Wait("Zap/1-1", "10") in new stack
    -- Executing NoOp("Zap/1-1", """ <>") in new stack
    -- Executing Answer("Zap/1-1", "") in new stack
    -- Executing NoOp("Zap/1-1", """ <>") in new stack
    -- Executing PlayTones("Zap/1-1", "ring") in new stack
    -- Executing Wait("Zap/1-1", "5") in new stack
    -- Executing GotoIf("Zap/1-1", "1?inbound|s-inv|1") in new stack
    -- Goto (inbound,s-inv,1)
    -- Executing NoOp("Zap/1-1", "Incoming call with invalid Caller ID info") in new stack
    -- Executing PlayTones("Zap/1-1", "info") in new stack
    -- Executing Wait("Zap/1-1", "1") in new stack
    -- Executing Playback("Zap/1-1", "were-sorry&privacy-unident&please-hang-up-and-try-again") in new stack
    -- Playing 'were-sorry' (language 'en')
    -- Playing 'privacy-unident' (language 'en')
    -- Playing 'please-hang-up-and-try-again' (language 'en')
    -- Executing Congestion("Zap/1-1", "") in new stack
  == Spawn extension (inbound, s-inv, 5) exited non-zero on 'Zap/1-1'
    -- Hungup 'Zap/1-1'

Can anyone shed any light onto the error messages at the top of the log?

There are a few things I have noted about our caller id at work…

  • It is only 7 digits (3 digit prefix “-” 4 digit internal exten)
  • No name is transmitted
  • Works fine on incoming calls to my cell phone

We are on a Nortel Option 11c with a PRI. I am beginning to think that Time Warner Telecom is sending out the faulty data.

Any thoughts or comments? I’m not sure how TWTC and AT&T (my POTS provider) interact with caller id…or whether it is our phone switch butchering it to begin with.

My thought process here is to have invalid caller id calls rejected, but then whitelist numbers from work to bypass all the filtering I have programmed in * so I can get the calls quickly.

Thanks for all your help!
Mike