Man page - pagermap(5)
Packages contains this manual
- choptest(8)
- probemodem(8)
- faxsend(8)
- status(5)
- dialtest(8)
- faxqclean(8)
- recvstats(8)
- hfaxd(8)
- hylafax-config(5)
- pollrcvd(8)
- doneq(5)
- xferfaxlog(5)
- faxmodem(8)
- wedged(8)
- sendq(5)
- notify(8)
- xferfaxstats(8)
- jobcontrol(8)
- pdf2fax(8)
- tiff2fax(8)
- cqtest(8)
- ondelay(8)
- dialrules(5)
- faxquit(8)
- mkcover(8)
- hylafax-shutdown(5)
- faxinfo(8)
- hylafax-info(5)
- hylafax-log(5)
- tagtest(8)
- faxgetty(8)
- faxwatch(8)
- faxstate(8)
- faxlock(8)
- tiffcheck(8)
- faxconfig(8)
- pagermap(5)
- faxaddmodem(8)
- ps2fax(8)
- tsi(5)
- hylafax-server(5)
- hosts.hfaxd(5)
- faxcron(8)
- faxq(8)
- faxabort(8)
- faxadduser(8)
- faxanswer(8)
- pagesend(8)
- recvq(5)
- typetest(8)
- faxdeluser(8)
- lockname(8)
- faxrcvd(8)
- faxmsg(8)
- faxsetup(8)
- tsitest(8)
apt-get install hylafax-server
Manual
PAGERMAP
NAMEDESCRIPTION
EXAMPLES
SEE ALSO
NAME
pagermap - SNPP pager identifier mapping file
DESCRIPTION
The file etc/pagermap (by default) is used by the SNPP support in hfaxd (8) to map pager identifiers specified with the PAGE directive to IXO/TAP or SMS service providers and optionally a Pager Identification Number ( PIN ). (The ability to specify a PIN makes it possible to define aliases for pagers.) Note that etc/pagermap may be called a different name; the filename is specified with the PagerIDMapFile configuration parameter read by hfaxd (8).
The pagermap file is comprised of one or more lines of the following format:
< pattern > < dialstring >[/< pin >]
Each line specifies a < pattern > that is matched against a client-specified pager identifier string. A pattern may be a plain string or a POSIX 1003.2 extended regular expression; plain strings must compare exactly while regular expressions are unanchored and any substring match constitutes a ββhitββ. Regular expressions are distinguished from plain strings by the presence of one or more of the magic characters ββ[]*.Λ$-+{}()ββ. The < dialstring > identifies the IXO/TAP or SMS service provider to contact for delivery or, if < dialstring > is the string ββrejectββ (case insensitive) then the pager identifier is rejected. If the optional < pin > is specified then it used to deliver the page instead of the client-specified identifier.
If the matching expression is a regular expression the optional < pin > may reference the entire string matched by the regular expression with the ββ&ββ character. Substrings matched with the ββ(...)ββ constructs may be referenced by using ββ\ n ββ where n is a single numeric digit between 1 and 9 that refers to the n -th matched substring; c.f. re_format (7), sed (1), etc.
hfaxd processes lines in the mapping file sequentially; the first line with a pattern that matches the pager identifier is used to deliver or reject the page. Lines that begin with a ββ#ββ are treated as comments and discarded. Leading whitespace on a line is also ignored.
EXAMPLES
The following defines an alias for ββsamββ, submits all destinations with a leading ββSkyββ to a particular IXO/TAP service provider, and otherwise rejects the pager ID. (Note that using alphabetics in dial strings requires a dialstring rules file that understands how to map alphabetics to key codesβor one that passes them through verbatim.)
# a simple mapping example sam 5551212/99 Sky(.*) 1800SkyTel/\1 .* reject
SEE ALSO
hfaxd (8), hylafax-server (5)