[Asterisk-Users] No Caller ID from FXO Problem

Damian Minkov damian at space-comm.com
Tue Jun 22 03:34:44 MST 2004


I have problem compiling it

********************************************
chan_zap.c: In function `zt_get_history':
chan_zap.c:768: storage size of `hist' isn't known
chan_zap.c:771: `ZT_GET_HISTORY' undeclared (first use in this function)
chan_zap.c:771: (Each undeclared identifier is reported only once
chan_zap.c:771: for each function it appears in.)
chan_zap.c:768: warning: unused variable `hist'
make[1]: *** [chan_zap.o] Error 1
make[1]: Leaving directory `/usr/src/asterisk/channels'
make: *** [subdirs] Error 1
********************************************






Kevin Walsh wrote:

> Damian Minkov [damian at space-comm.com] wrote:
> 
>>No Caller ID comes from the FXO line ( The caller id is on and is
>>working with a standard phone)
>>
>>in zapata.conf everything looks fine
>>	usecallerid=yes
>>	hidecallerid=no
>>
>>When the call comes in there are some warnings in Asterisk Console
>>
>>     -- Starting simple switch on 'Zap/4-1'
>>Jun 22 11:20:24 NOTICE[213006]: callerid.c:281 callerid_feed: Unknown IE
>>17 Jun 22 11:20:24 NOTICE[213006]: callerid.c:281 callerid_feed: Unknown
>>     IE 48 -- Executing Dial("Zap/4-1", "SIP/phone1000|5|tr") in new stack
>>
> 
> You didn't say, but my highly tuned mind reading powers tell me
> that you're in Bulgaria.
> 
> The Caller*ID is geared toward the North American (Bellcore) system
> and won't work with anything else.  You'll find a patch in the bug
> tracker that creates support for UK (BT) Caller*ID.
> 
> If you know the details of your telco's Caller*ID system then you
> could possibly hack in the support yourself.  Perhaps the UK patch
> would help as a starting point;  You could add some code to handle
> "usecallerid = bg", for instance.
> 




More information about the asterisk-users mailing list