HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Problem with inbound routing, still



On 2004.07.13 15:17 Ulf Zimmermann wrote:

Jul 12 16:40:00.80: [ 1659]: SESSION BEGIN 00016515 15105800929
Jul 12 16:40:00.80: [ 1659]: HylaFAX (tm) Version 4.1.8
Jul 12 16:40:00.80: [ 1659]: <-- [23:AT+VRID=10+FCC=,,,,1;A\r]
Jul 12 16:40:01.08: [ 1659]: --> [15:NDID=5105800931]
Jul 12 16:40:01.08: [ 1659]: --> [15:NMBR=6505561217]
Jul 12 16:40:06.79: [ 1659]: --> [74:+FHT: FF 03 40 2E 63 6E 49 20 72
65
74 6E >
Jul 12 16:40:07.08: [ 1659]: --> [26:+FHT: FF 13 80 00 EE FA 00]
Jul 12 16:40:07.56: [ 1659]: --> [4:+FCO]

In the modem config I got this:

QualifyCID:             etc/cid         # you must create this file
ModemResetCmds:         "AT#CID=10"
CIDNumber:              "NMBR="
CIDName:                "NDID="
CIDNumberAnswerLength:  10
#ModemAnswerCmd:                ATA
ModemAnswerCmd:         AT+VRID=10+FCC=,,,,1;A

Interesting. This configuration will facilitate grepping the data from the log, but if like using the AT+VRID command (in case faxgetty misses the data) you can use:


RingResponse: AT+VRID
RingsBeforeResponse: 2

Which should reproduce the information in the server log. They may be 4.2.0-only options, however.

In other words, faxgetty doesn't parse CIDName and CIDNumber from the response to the ModemAnswerCmd. (What you are doing will facilitate putting the data in the session log, but it won't make faxgetty any more able for it. That's what RingResponse and RingsBeforeResponse are for.) FaxGetty only looks for caller-id/DID information while looking for RINGs or in response to the RingResponse setting.

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




Project hosted by iFAX Solutions