[Bug 935] DAD and CID do not match the CallID in rare instances.
[email protected] Sun, 19 Sep 2010 01:15:34 -0400
| Newsgroups | gmane.comp.telephony.fax.hylafax.devel |
|---|---|
| Message-ID | <[email protected]> |
http://bugs.hylafax.org/show_bug.cgi?id=935 ------- Comment #4 from [email protected] 2010-09-19 01:15 ------- It's a shortcoming in the modem's behavior of presenting the Caller ID and DID between rings #1 and #2. If the modem were to present CID and DID *before* the first ring, then there wouldn't be this problem. I tackled this issue with IAXmodem in two ways: 1) I created a AT+VRID command which would allow the application to query the modem for the CID and DID that were associated with the current call. Thus, the application wouldn't have to rely on ring counting. 2) I enforced a "dead" time after a call disconnects when the modem is incapable of receiving more calls... the "dead" time is designed to exceed RING timeout periods which would allow HylaFAX to reset. This prevents one call from coming in on the heels of another and "stealing" the CID/DID from it. I think that the issue you bring up is something that your modem manufacturer (Eicon) would have to address in some fashion as I have done with IAXmodem. I don't really see any way for HylaFAX to get a permanent solution to this on its own. -- Configure bugmail: http://bugs.hylafax.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe [email protected] < /dev/null