Re: [hylafax-users] MT1932ZBA with DTMF DID

[Mat Allgood <mallgood@xxxxxxxxx>]

On Mon, 21 Mar 2005 17:58:55 -0800, Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote:
> The difference here being that the former waits for "OK" and the latter
> does not.
> 
> It's a bit of a dilemma because some modems do this (like those that
> accept AT+VRID=1):
> 
>   <-- AT command
>   --> CallID data (DID or Caller*ID)
>   --> OK
> 
> and some modems do this (like yours):
> 
>   <-- AT command
>   --> OK
>   --> CallID data (DID or Caller*ID)
>
> The former requires that we watch for OK to terminate the CallID data,
> and the latter requires that we don't - relying completely on the answer
> length to terminate the CallID data.  I think, though, that something
> can be done.

I know these features are used by some but not lots of people, but it
seems to me that it would be a good idea to add a configuration
option(s?) to setup what the modem expects back from commands like
this.
 
> Please try the attached patch (against current CVS, but 4.2.1 release
> should be fine, too).  Let me know how it goes.

*SNIP*

> --- hylafax-4.2.1.orig/faxd/ClassModem.c++      Mon Mar 21 08:20:26 2005
> +++ hylafax-4.2.1/faxd/ClassModem.c++   Mon Mar 21 17:52:36 2005
> @@ -1340,12 +1340,13 @@
>                 atCmd(conf.ringResponse, AT_NOTHING);

With this, I am guessing you meant this line to be:
                 atCmd(conf.ringResponse);
Right?  With the first line, hylafax doesn't even try to get [CD]ID.

I will try the patch and tell you how it goes.

Mat Allgood

____________________ 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@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*