![]() |
Lee- Patrice's explanation + fix has not solved the problem. As I was suspecting looking at his indication and looking at my symptoms, they are not one in the same thing. I added the patch, rebuilt, etc., but even looking at the patch, it was obvious it was not targeting my issue. It is still the case that when I use distinctive rings, with my two rings being "RING A" and "RING B", and when I set RingFax: "RING B", I still am getting hylafax answering with RING A. The fact that CID was being set with Ring data told me that there is somewhat of a bug in parsing the incoming modem data stream. That somehow even though I did not have CID set on for my modem, hylafax was still parsing the first string as CID information. In any event, I will continue to try debugging rather than use my less than optimal hack. Unfortunately though I am a C person, I am not a C++ programmer. Sunil -----Original Message----- From: hylafax-users-bounce@hylafax.org [mailto:hylafax-users-bounce@hylafax.org] On Behalf Of Lee Howard Sent: Tuesday, September 03, 2002 7:03 PM To: savkar@inthespace.com Cc: hylafax-users@hylafax.org Subject: Re: [hylafax-users] Update on Problem with Distinctive Ring-- hacked faxgetty On 2002.09.03 15:29 Sunil William Savkar wrote: > I am still mystified as to why the information as to the ring type is > getting into the cid variables. Patrice did a very good job explaing this, and even told you how to fix it. Lee. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.* ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*