search for: default_cidrings

...rst long ring */ 4, /* Right after long part */ 3, /* After third chirp */ 2, /* Second spell */ }; Actually, now that I look at the file again, I can also see: Line: 80 /* Typically, how many rings before we should send Caller*ID */ #define DEFAULT_CIDRINGS 1 So, does anyone know if either of these are the things I need to change? and what I need to change them to? I am in Australia, which I think expects callerid at a different time to other countries.... Although other people have told me callerid is working correctly for them....

Hello list, I have an X100P clone card, and I've been trying to get it to receive Telstra Caller-ID without any luck. Hence these two questions:- 1) Will a genuine X100P work? 2) If so, where can I get one in Australia? Cheers, Jon

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 hidecallerid=no callwaiting=no cal...

I have a TDM400 with 2 FXS cards, and a Samsung 6100 DECT base station connected to one of the ports. The base station appears to only support UK (BT) style CLIP Caller ID signalling. Does anyone know if it is possible to configure the ZAP channel to send in this format, or alternatively can you recommend a GAP compatible base station which will handle both BT and Bellcore signalling? A search

Well, I got my nice new 4 port FXS card this afternoon, and with all my other asterisk problems, decided now was a good time to throw it in.... So far, I have dropped it in, done a clean cvs checkout on zapata, zaptel, asterisk, make clean and make install on each. I can load the wcfxs module which finds the card (though one time it failed the register check and locked the machine up, a hard

Seems to have struck a small problem.. Using a t100p & Zhone channel bank.... one extension ringing another.....the following will appear WARNING[18448]: File chan_zap.c, Line 2685 (zt_handle_event): Didn't finish Caller-ID spill. Cancelling. if we are using defaultzone=au change it to us and the problem goes away..... any possible solutions ?? Gary .

From: "hafeez bana" <hafeez_bana+dusers@fastmail.fm> To: asterisk-users@lists.digium.com Date: Wed, 16 Jul 2003 05:17:59 -0800 Subject: Re: [Asterisk-Users] X100P in Australia Reply-To: asterisk-users@lists.digium.com > Thanks for your reply. I tried changing the constant DEFAULT_CIDRINGS to > 2. However I still don't get callerid information. Is this what you were > referring to? > Thanks, > Hafeez You don't have another caller ID device on the line do you? My X100P cards won't recognise the caller ID when my cordless phone is plugged into the line (which...

...fore upgrading to the latest stable CVS. Of course I have (in zapata.conf): usecallerid = yes callwaitingcallerid = yes With defaultzone=gr (zaptel.conf) I was getting: "Didn't finish Caller-ID spill.". I changed defaultzone=us and I also tried with DEFAULT_CIDRINGS=2 (in chan_zap.c). With this setup the error is gone, but the caller id is still not sent to the phones. As I said, callwaitingcallerid is working right. Any ideas? Regards, Costa

Hello All, Can any Australians who have any info or current patches relating to Caller ID in Australia please drop me a line? There is little or no info on the Wiki regarding this topic, although I am aware of a related patch mentioned in the bug tracker. Regards, Rob Barnes

...I try to compile it. Asterisk ends with the lines below. It complains of a newer libpri, but I just did it a step before! What do I miss? chan_zap.c:62:2: #error "You need newer libpri" chan_zap.c:128: error: parse error before '<<' token chan_zap.c:133:1: warning: "DEFAULT_CIDRINGS" redefined chan_zap.c:130:1: warning: this is the location of the previous definition chan_zap.c: In function `zt_call': chan_zap.c:2130: warning: passing arg 2 of `pri_sr_set_useruser' discards qualifiers from pointer target type chan_zap.c: In function `zap_send_keypad_facility_exec...

Scenario, I got some very good help earlier from Joseph getting me up and started but I have a couple of small problems still. Setup: FC2 Asterisk 1.0 Zaptel 1.0, TMP400P, FXS Port 1 FXO Port 4 Analog dialout line and Analog handset plugged in. Problems: 1. Incoming calls work and the phone rings and can be answered no problems, (although I wouldn't mind being able to adjust the ring but

...r, when * answers the line, it does not pick up the initiator, but > the destination number?? e.g. 793 1486 calls 787 0107. For some bizarre > reason, it shows my number being dialled. Why? > > I wanted to ask how this could be, and if it requires me to make changes > to > #define DEFAULT_CIDRINGS 2 or usecallerid=uk. > > Thanks, > Thorsten > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041201/051dca a7/attachment-0001.htm > > ------------------------------ > >...

I've followed the recent thread on caller id with UK British Telecom networks (where the caller id data is delivered before the first ring). My understanding is that if I use a recent CVS head (e.g. CVS-HEAD-09/18/04-17:45:52) and a TDM400 with FXO modules, all I need to do is include the line: usecallerid=uk In my zapata.conf (in the [channels] section) I've done this, but I get: Sep