[Bug 935] DAD and CID do not match the CallID in rare instances.

http://bugs.hylafax.org/show_bug.cgi?id=935





------- Comment #7 from [email protected]  2010-10-11 21:56 -------
Recognize that by the time the call is answered with ATA that the process is
beyond the point where DynamicConfig can make use of the new CallID
information.  So all that can really be done would be to ensure that the CallID
values in the TIFF and in the faxrcvd call correspond to the latest expression.
 But in case the admin has configured DynamicConfig the two features will get
disparate information.

On top of that xferfaxlog will have been populated already with a CALL record
using the original CallID information.

As I see it the truly *correct* thing would be to hang up to prevent exposing
one user to another user's fax or one user's settings to another user.

What do you think should be done?

I don't see any completely-happy ending here.  If we adjust CallID and let the
fax be received then we'll make a hole in the DynamicConfig - xferfaxlog -
faxrcvd correlation.  If we leave it as-is then one user could get another's
fax.  If we hang up to prevent all of that then someone's going to be unhappy
that there was a failed fax reception.


-- 
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