yaps.doc

使用Modem发送网上传呼

          affects only the message (and depending on the protocol the
          pagerid) and allows transforming illegal characters to valid
          ones.
          
   convert <text>
          This is comma seperated list of direct change entries of the
          convertion table. If you want to include more than one pair,
          the block construct using curly brackets ({..}) must be used.
          Each line contains a source and a destination character, i.e.
          if the source character is encountered in a message, the
          destination character is used for it. There are also some
          predefined convertion rules, which all starts with an asterisk:
          
          + *no-control control characters are suppressed
          + *control control characters are inserted literal
          + *no-8bit no characters with 8'th bit set are included
          + *8bit use also characters with 8'th bit set.
          + *numeric only numeric characters are allowed.
            
   cost <text>
          This string is used to calculate the costs for each call. The
          description is a comma seperated list of variables with equal
          sign seperated optional value. These variables are currently
          implemented:
          
        fixed
               This tells the software, that the cost are fixed per call,
               i.e. no real calculation takes place according to the used
               entities.
        entity-length=<entity>
               This is the length of one entity. This is interpreted as a
               floating point number.
        max-entities=<count>
               Some providers only charge until a maximum of entites had
               been used and stop then charging.
        dial-overhead=<seconds>
               The counter starts before dialing. Typically it takes some
               time from dialing to the first billed entity. This time
               can be specified using this variable.
        cost=<cost>
               This is the cost per entity (or the whole cost on fixed
               charging services). This is a floating point number.
        unit=<string>
               This string is appended in the logfile for the currency.
               This is only of cosmetic value.
        remainder=<digits>
               This is the number of digits after the point in the cost
               display. This value is typical two.
        timetable=<description>
               If a timetable entry is given, then the cost are
               calculated depending on weekday and time. On fixed
               charging services the value describes the complete costs
               for the call, in the other case the value is the
               entity-length for this day/time. The description is a
               semi-colon seperated list of single entries of the form:
               <Weekday(s)><from>-<to>=<value>
               Each weekday is a two letter sequence (So, Mo, Tu, We, Th,
               Fr, Sa) and there are three special "weekdays": Wk for
               working days (monday to friday), Ss for weekend (saturday
               and sunday) and al for all days. A typical example may
               look like: Wk0800-1800=12;Wk1800-0800=24;Ss=24, but this
               could be written shorter as: =24;Wk0800-1800=12 because
               the first entry is taken as the default, if no match is
               found. And the construct =24 does not contain any weekday,
               so it is invalid for any regular check.
               
   force <bool>
          If a feature is requested, but this service do not support it,
          the message will still be delivered, if this variable is set to
          True.
          
   can-delay <bool>
          Set this to True, if the service provider accepts a delay for
          sending the message.
          
   can-expire <bool>
          Set this to True, if the service provider allowes the setting
          of an expiration timestamp.
          
   can-rds <bool>
          Set this to True, if the service provider allowes the request
          for a delivery status.
          
   rds <bool>
          Set this to True, if can-rds is True and you always want to get
          a delivery status.
          
   check-call-id <check>
          The caller id must match the check expression.
          
   check-pager-id <check>
          Each pager id must match the check expression.
          
Modem section

   Each modem should have its own section. Following entries are
   currently supported:
   
   device <text>
          The filename for the device where the modem is attached to.
          
   lock-prefix <text>
          This is the pathname to prefix the basename of the modemdevice
          to create lockfiles. This can be used to enable more than one
          application to use the modem.
          
   lock-method <text>
          This is a comma seperated list of locking mechanism. Currently
          these flags are supported:
          
          + ascii PID is stored as ASCII text in lockfile.
          + binary PID is stored in machine representation in lockfile.
          + lower converts device part of lockfile to lower case.
          + upper converts device part of lockfile to upper case.
          + sysv4 append SysV4 style infos to lockfile instead of the
            basename of the device.
          + timeout=<secs> tries to lock the device secs seconds.
            
   init <text>
          This is the init sequence to initialize the modem.
          
   dial <text>
          This is the dial sequence to dial a phone number with the
          modem. An \L in the string will be replaced by the phone
          number.
          
   timeout <num>
          This is the default timeout to wait for responses of the modem.
          
   reset <text>
          This is the sequence to reset the modem.
          
   local-init <text>
          This is used to customize an existing modem entry for different
          purpose (e.g. force a specific connect rate, etc.)
          
   Beside this the section may contain protocol specific entries to adapt
   the protocol for this service.
   
ASCII based protocol

   A \C is replaced with the caller id, if available. If request a
   delivery report is switched on, a \R is replaced with 1, else with 0.
   
   asc-timeout <num>
          This is the default timeout for sequences when communicating
          with the remote side.
          
   asc-login <text>
          This is the sequence to login to the remote service.
          
   asc-logout <text>
          This is the sequence to logout from the remote service.
          
   asc-pagerid <text>
          This is the sequence to embedded the pager id to be sent. \P is
          replaced with the pager id.
          
   asc-message <text>
          Dito for the message, \M is replaced with the message.
          
   asc-next <text>
          This is the sequence to start the next transmission.
          
   asc-sync <text>
          If we get out of sync, then this sequence should bring us back
          to a stage as if we had just loged in.
          
Script specific

   script-type <text>
          This is the scripting language to choose. Currently these are
          supported: SLang, Lua.
          
   script-name <text>
          This is the name (e.g. the name of the variable containing) the
          script. If the name starts with a slash or a plus sign, then
          the value is treated as a filename from where the script should
          be read. The plus sign is stripped off before opening the file.
          
   scr-login <text>
          This is the function/label where to start at login. If the
          caller id is available (and the language supports it) the
          caller id is passed as an argument.
          
   scr-logout <text>
          Dito for logout.
          
   scr-pagerid <text>
          Dito for sending the pagerid. The pagerid is passed as an
          argument.
          
   scr-message <text>
          Dito for sending the message. The message is passed as an
          argument.
          
   scr-next <text>
          Dito to go to the next message.
          
   scr-sync <text>
          Dito to sync to a definite state (i.e. as if we had just loged
          in.)
          
TAP specific

   tap-t1, tap-t2, tap-t3, tap-t4, tap-t5 <num>
          This is the timeout for each stage defined in the TAP
          specification. See there for details.
          
   tap-n1, tap-n2, tap-n3 <num>
          This is the retry count for each stage defined int the TAP
          specification. See there for details.
          
   tap-login-count <num>
          This is the number of tries to login to the remote service.
          
   tap-logout-count <num>
          This is the number of tries to logout from the remote service.
          
UCP specific

   ucp-timeout <num>
          This is the time to wait for an answer from the remote system.
          The documentation says that this could be about 40 to 60
          seconds. This depends on the provider.
          
   ucp-retry <num>
          This specifies how often a message should be sent, until the
          program gives up.
          
   ucp-extend <bool>
          If this is True then the extend UCP implementation is used,
          i.e. the more complex, but more flexibel protocol (currently
          only possible on german cellular phone provider Mannesmann D2.)
          
   ucp-ds-timeout <num>
          Wait a maximum of this value seconds for receiving of the
          delivery status.
          
Alias section

   The entries in this section are not able to access the global entries.
   Each entry contains an alias name with its real number.
   
                                 Command Line
                                       
   Yaps support several command line parameter which can overwrite the
   possibly used default values in the configuration files. Following
   options are understood by this program (on some systems, there are is
   also support for long options):
   
   -C <configfile>, --config=<configfile>
          Use cfgfile instead of the default global configuration file
          /etc/yaps.rc.
          
   -s <service>, --service=<service>
          Use paging service service instead of the default of the
          configuration file.
          
   -t, --truncate
          If this is set, then a message is truncated, if it is longer
          than the allowed limit of the choosen service.
          
   -c <callid>, --call-id=<callid>
          Use callid as the caller id.
          
   -S <signature>, --signature=<signature>
          If signature appending is enabled by the service, use this
          string as the signature.
          
   -l <logfile>, --logfile=<logfile>
          Write status of transmission to logfile.
          
   -L <logstr>, --logstring=<logstr>
          This is used to select the messages written to the logfile. See
          above unter the configuration entry logstring for a detailed
          description.
          
   -f, --force
          Force sending of messages, even if -d/-e/-r is not supported by
          the service.
          
   -d <date>, --delay=<date>
          If the service supports it, the message is delayed and sent at
          date.
          
   -e <date>, --expire=<date>
          If the service supports it, the message is deleted, if this
          date is reached and the message had not been transmitted until
          then.
          
   -r, --request-delivery-status
          If the service supports it, a delivery status is requested.
          
   -R <fname>, --final-report=<fname>
          A final report is written to fname (or stdout, if fname is -.)
          This feature is useful to check which message had been
          delivered successfully or not.
          
   -z <fname>, --message-file=<fname>
          Reads pager-ids and messages form fname. Each line contains one
          pair, seperated by whitespace(s).
          
   -v, --verbose