![]() |
> Does the CNID data show in the session log regardless of which ring is > picked up? This is my exact point. the primary number does show the CNID info in the logs. The secondary/distinctive ring does not show in the logs. > > Do you also understand that if you try to use RingVoice to answer fax > calls on a second Distinctive Ring that you won't get what you're > after? Hylafax only answers fax calls and logs cid-data to log files (nothing else) > > We just did that last week; check the archives. yes we did however, that was addressing a different issue (picking up on both rings) Review: My current issue is, cid info for incoming calls on the primary number *is* seen and logged. CID info for incoming calls on the distinctive ring number is *not* seen or logged. :) In addition the same thing happens with the cu -l cuaa1 which makes me think its the telco, but, a standard cid-box shows cid-data for both primary and secondary incoming calls. See my dilemma? The following is in response to LEE's last question.... > "Yes, we're saying the same thing. Which is why you need to use > RingsBeforeAnswer=2 if you intend to use QualifyCID without the Bug 139 patch" We're not trying to use QualifyCID. We need all CID info to be logged via syslogd >Um, this may be a silly question, but your modem is capable of supporting >Caller-ID and you have enabled this support in the modem, right? I.e. on >USR modems you have to issue AT#CID=1 because the default is "disabled". >Or your modem doesn't have Caller-ID support or it's disabled. Maybe I didn't explain well/clear enough... Incoming calls on the primary number= cid info is logged. That would be a good indication that AT#CID=1. yes/no? ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null