HylaFAX The world's
most advanced open source fax server
Re: [hylafax-users] Receiving Remote TSI name string (vs. remote number)
I may be off on this one, but I think if the sender doesn't setup their
TSI it will automatically default to the sending number. (?) If the
number is unlisted or has caller ID blocking, it may show as 'UNKNOWN' or
'UNSPECIFIED' or even just blank.
I have received some faxes with an ASCII text TSI, but most are numerical
phone numbers. There was nothing I did on my end to change this, it was
just how they come across.
Steve Friedl's Unixwiz.net Tech Tips writes:
During the initial setup of the call, both stations swap ID strings:
CSI - Called Subscriber Identification
TSI - Transmitting Subscriber Identification
The answering machine announces its CSI string to the caller, and the
caller responds with its TSI string, and they are typically phone
numbers. The fax specification (CCITT T.30 18.104.22.168.4) limits these
strings to 20 characters from the set "digits, space, and +". But in
practice, almost all fax systems allow full ASCII.
Based on what I've been able to research, the receiving end has nothing to
do with the TSI.
> Hello everyone!
> I've checked the archives on items such as "remote TSI", "ascii TSI
> string", "remote identifier", and there doesn't appear to be an exact
> match on our issue (though I certainly could've missed it).
> When receiving faxes, we'd like to use the remote fax machine's identifier
> NAME instead of the NUMBER as the SENDER variable.
> Obviously, our log looks something like this (but nowhere in the logs does
> the ASCII remote identifier name ever show up):
> Dec 27 16:11:05.99: [ 1781]: <-- [9:AT+FRH=3\r]
> Dec 27 16:11:06.74: [ 1781]: --> [7:CONNECT]
> Dec 27 16:11:08.33: [ 1781]: --> [2:OK]
> Dec 27 16:11:08.33: [ 1781]: REMOTE TSI "1234567890"
> Dec 27 16:11:08.33: [ 1781]: <-- [9:AT+FRH=3\r]
> Dec 27 16:11:08.35: [ 1781]: --> [7:CONNECT]
> Dec 27 16:11:08.76: [ 1781]: --> [2:OK]
> Dec 27 16:11:08.76: [ 1781]: REMOTE wants 14400 bit/s
> We're using HylaFAX 4.3.0 in a receive-only setup with Class 1.0 Rockforce
> ____________________ HylaFAX(tm) Users Mailing List
> To subscribe/unsubscribe, click
> On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx <
> *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
____________________ 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*