Re: [asterisk-users] zap not getting callerid any more
On Wed, 2008-07-16 at 15:08 +1000, Rob Hillis wrote: I hadn't realised this was for a home server... yes I agree, for a home server the Digium or Sangoma cards are a little too expensive. Indeed. I can't speak for the SPA-3102, but the SPA-3000 I use here at home doesn't do a brilliant job. I suffer from varying amounts of echo on many calls, Oh, that's sad to hear (NPI). I'm sure you'll find it amusing to find out that I was toying with the idea of getting an X100 card for my server. LOL. Unfortunately, they appear to be very hard to find in Australia. I got mine off of Ebay. I ended up getting two in fact due to what is in my opinion Ebay's complicity in fraud. I was in a bidding war with somebody on one auction and when he finally bid past my stop limit, I moved on to another auction and won that one. Then the bidder that I was bidding against in the first auction bailed out and left me holding the bag. Ebay completely let him do it and didn't respond to any of my complaints about it (IIRC -- this was 7+ years ago). Was that person I was bidding against really the seller, driving the price up and then bailing when he noticed I wasn't willing to go higher and he was getting his maximum price for it? I have no proof and will never really know the answer to that question, but it sure makes me wonder. And that Ebay allowed him to bail out of an auction that he clearly won just stinks and considering they get paid as a percentage of the sale price squarely puts them into a conflict of interest. I don't think I've bought anything from Ebay since and I'd never again, not for anything more than $10 or $20 anyway. But I digress. :-) b. signature.asc Description: This is a digitally signed message part ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
On Wed, 2008-07-16 at 09:31 -0400, Brian J. Murrell wrote: IIRC -- this was 7+ years ago Er, I mean 2+ years ago, just to keep the facts straight. b. signature.asc Description: This is a digitally signed message part ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
On Sun, 2008-07-13 at 10:22 -0400, Brian J. Murrell wrote: I have a wildcard 100 xp on my pots line and all was working just fine up until a few days ago when all of a sudden it stopped receiving caller id on incoming calls. I know caller id is being presented on the line as the analog set on the same line always gets it. ... rxgain=10.9 txgain=0.0 To add more information, I tried setting my rxgain back to 0.0 and CID now seems more reliable. So again I went through the process of setting rxgain using a milliwatt number (not at all local however as I can't find one near me) and ztmonitor and had to adjust it down by 4 points to 10.5 to get it close to the magical 14844. CID was again, 100% unreliable. One thing I have noticed is that in the cases where the wildcard cannot determine the CID (i.e. because the rxgain is up around 10.5), I get this in my asterisk console: [Jul 15 08:04:09] NOTICE[26696]: chan_zap.c:6670 ss_thread: Got event 18 (Ring Begin)... And indeed, Asterisk seems to take longer to pass the call to the destination extensions, exactly as if it's struggling to get the CID on the analog line. Does that message from Asterisk mean anything to anyone? b. signature.asc Description: This is a digitally signed message part ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
Brian J. Murrell wrote: One thing I have noticed is that in the cases where the wildcard cannot determine the CID (i.e. because the rxgain is up around 10.5), I get this in my asterisk console: [Jul 15 08:04:09] NOTICE[26696]: chan_zap.c:6670 ss_thread: Got event 18 (Ring Begin)... And indeed, Asterisk seems to take longer to pass the call to the destination extensions, exactly as if it's struggling to get the CID on the analog line. Does that message from Asterisk mean anything to anyone? It means that Asterisk has detected that the line is ringing. The fact that Asterisk pauses after this indicates that it is waiting to receive caller ID information. The chances are that in boosting the receiving audio, you're causing the caller ID information to become distorted - enough so that Zaptel can no longer decode the caller ID properly. X100 cards are notorious for problems. Unless you want to invest in a better card, you may just have to live with the problem. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
On Tue, 2008-07-15 at 22:31 +1000, Rob Hillis wrote: Brian J. Murrell wrote: One thing I have noticed is that in the cases where the wildcard cannot determine the CID (i.e. because the rxgain is up around 10.5), I get this in my asterisk console: [Jul 15 08:04:09] NOTICE[26696]: chan_zap.c:6670 ss_thread: Got event 18 (Ring Begin)... And indeed, Asterisk seems to take longer to pass the call to the destination extensions, exactly as if it's struggling to get the CID on the analog line. Does that message from Asterisk mean anything to anyone? It means that Asterisk has detected that the line is ringing. But I don't get that message when the rxgain is low enough for CID to work, yet the line is still picked up by Asterisk, so Asterisk must still be detecting the line ringing. Why does it print that message only when the rxgain is increased? The fact that Asterisk pauses after this indicates that it is waiting to receive caller ID information. Indeed. The chances are that in boosting the receiving audio, you're causing the caller ID information to become distorted - enough so that Zaptel can no longer decode the caller ID properly. Fair enough, but I'm only increasing to the magical values that are supposed to be ideal for echo cancellation. That seems to be a) incompatible with caller-id and b) it's only when I increase it that high do I get the Got event 18 (Ring Begin)... message. Further to (a) above, my rxgain has been at 10.9 for a long time and everything worked just fine and then one day the CID just stopped working. And further to that, a re-calibration to a milliwatt number showed it was only out by 4 points. Not very much it seems. X100 cards are notorious for problems. Supposedly, yet. But mine has been working peachy up until this out of the blue incident. Unless you want to invest in a better card, you may just have to live with the problem. Which means what, a multiport and multi-hundreds of dollar card? I'm just a home user. I don't have hundreds of dollars to spend on a single piece of phone hardware. I wonder how much using something like an SPA-3102 (with both an FXS and FXO ports) eliminates these problems and brings reliability to the table. b. signature.asc Description: This is a digitally signed message part ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
One thing I have noticed is that in the cases where the wildcard cannot determine the CID (i.e. because the rxgain is up around 10.5), I get this in my asterisk console: [Jul 15 08:04:09] NOTICE[26696]: chan_zap.c:6670 ss_thread: Got event 18 (Ring Begin)... It is odd that it would work one day and not the next. I'd have to say, though that I've seen that rxgain/txgain values beyond +-8 seem to yield unpredictable results in many areas, even if they do get you closer to 14844, and that's even on the cool new cards all the kids are using these days. And now the obligatory: YMMV - Noah ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
On Tue, 2008-07-15 at 12:49 -0400, Noah Miller wrote: It is odd that it would work one day and not the next. Indeed. I'd have to say, though that I've seen that rxgain/txgain values beyond +-8 seem to yield unpredictable results in many areas, Yeah, I was pretty alarmed months ago when I tuned it to 10.9 to get that magical 14844, but there was no echo and CID worked, but given everything was working, didn't really concern myself with it further. even if they do get you closer to 14844, and that's even on the cool new cards all the kids are using these days. And now the obligatory: YMMV Indeed. Things seem to be working again with rxgain at 10.0. Any attempt to push it closer to that 10.5 (from today's calibration) or 10.9 (calibration of a few months ago) yield CID problems again. But I still wonder why the higher values result in chan_zap.c:6670 ss_thread: Got event 18 (Ring Begin)... messages and lower values do not AND YET Asterisk answers the Zap/POTS line in either case. I can't help but think that message and the lack of CID at the higher, calibrated value are related. b. signature.asc Description: This is a digitally signed message part ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] zap not getting callerid any more
Brian J. Murrell wrote: Unless you want to invest in a better card, you may just have to live with the problem. Which means what, a multiport and multi-hundreds of dollar card? I'm just a home user. I don't have hundreds of dollars to spend on a single piece of phone hardware. I hadn't realised this was for a home server... yes I agree, for a home server the Digium or Sangoma cards are a little too expensive. I wonder how much using something like an SPA-3102 (with both an FXS and FXO ports) eliminates these problems and brings reliability to the table. I can't speak for the SPA-3102, but the SPA-3000 I use here at home doesn't do a brilliant job. I suffer from varying amounts of echo on many calls, though oddly enough I've pretty much learnt to ignore it. :) As for Caller ID support, I can't help there - it /does/ support Caller ID, but since I don't really want to pay an extra $6 or so just to get caller ID on a number that usually rings only when telemarketers get around to it, I have no idea how reliable it is. I'm sure you'll find it amusing to find out that I was toying with the idea of getting an X100 card for my server. :) Unfortunately, they appear to be very hard to find in Australia. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] zap not getting callerid any more
I have a wildcard 100 xp on my pots line and all was working just fine up until a few days ago when all of a sudden it stopped receiving caller id on incoming calls. I know caller id is being presented on the line as the analog set on the same line always gets it. What is strange is that this all of a sudden started happening out of the blue. It was working one day and then not the next. No asterisk changes at all in that time frame. I have the following in my zapata.conf: signalling=fxs_ks usecallerid=yes cidsignalling=bell cidstart=ring hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes echotraining=yes rxgain=10.9 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no callerid=asreceived channel = 1 Any ideas what could have happened, or how to go about troubleshooting this? Is there some amount of debug I can enable to see why it's failing? b. signature.asc Description: This is a digitally signed message part ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
