1 01/14/87 dial_manager_call
 2 
 3 Syntax as a command:  dial_manager_call request {STR1 {STR2} {STR3}}
 4 
 5 
 6 Function:  provides a command interface to the answering service's dial
 7 facility.  All functions that are available through the dial_manager_
 8 subroutine interface are available through this command.
 9 
10 
11 Arguments:
12 request
13    maps into a call to an identically named entry in dial_manager_.
14    Each request requires the use of a particular STR, which is listed
15    in the request description.  A request must be one of the following:
16    allow_dials STR, ad STR
17       requests that the answering service establish a dial line to
18       allow terminals to dial to the calling process.  STR must be a
19       dial_qualifier as described below.
20    dial_out STR1 STR2 {STR3}, do STR1 STR2 {STR3}
21       requests that an auto call channel be dialed to a given telephone
22       number and, if the channel is successfully dialed, that the
23       channel be assigned to the requesting process.  STR1 must be a
24       channel_name and STR2 must be a dial_out_destination as described
25       below.  STR3, which can be omitted, is a reservation_string as
26       described below.
27    privileged_attach STR, pa STR
28       allows a privileged process to attach any terminal that is in the
29       channel master file, and is not already in use.  (See the
30       description of dial_manager_$privileged_attach for information on
31       what access is required.)  The effect is as if that terminal had
32       dialed to the requesting process.  STR must be a channel_name as
33       described below.
34    registered_server STR, rs STR
35       requests that the answering service allow terminals to dial the
36       calling process using only the dial qualifier.  STR must be a
37       dial_qualifier as described below.
38    release_channel STR, rc STR
39       requests the answering service to release the channel specified
40       by channel_name.  This channel must be dialed to the caller at
41       the time of the request.  If the channel was dialed, the channel
42       is returned to the answering service and another access request
43       may be issued.  If the channel is a slave channel, the channel is
44       hung up.  STR must be a channel_name as described below.
45    release_channel_no_hangup STR, rcnh STR
46       is the same as release_channel except that this request does not
47       hang up slave channels.  STR must be a channel_name as described
48       below.
49    release_dial_id STR, rdi STR
50       informs the answering service that your process wishes to prevent
51       further dial connections, but that existing connections should be
52       kept.  You can release later any connections kept with the
53       release_channel request.  STR must be a dial_qualifier as
54       described below.
55    shutoff_dials STR, sd STR
56       informs the answering service that your process wishes to prevent
57       further dial connections and that existing connections should be
58       terminated.  STR must be a dial_qualifier as described below.
59    start_report, start
60       turns on the reporting feature (see "Notes" below).
61    stop_report, stop
62       turns off the reporting feature (see "Notes" below).
63    terminate_dial_out STR, tdo STR
64       requests that the answering service hang up an auto call line and
65       unassign it from the requesting process.  STR must be a
66       channel_name as described below.
67 STR
68    depends on the request.  STR is selected from the following list.
69    (For details on the interpretation of the following qualifiers see
70    the dial_manager_ subroutine.)
71    channel_name
72       is the name of a tty_channel.
73    dial_qualifier
74       is the name for which you are to be a dial server.
75    dial_out_destination
76       is the destination (e.g., phone number) of up to 32 characters.
77    reservation_string
78       is a dial_manager_ reservation string of up to 256 characters.
79 
80 
81 Notes:  This command establishes an event call channel for
82 communication with the answering service.  This event channel and its
83 handler (which is an entry point in dial_manager_call) remain active
84 after the command terminates.  Any events following the command
85 termination, such as channel hang-ups, dial-ups, and dial requests are
86 decoded using convert_dial_message_ and reported on the user_output I/O
87 switch when they happen.  You can turn this reporting feature on (the
88 default) and off by using the start_report and stop_report requests.
89 
90 When the destination specifies an X.25 address you can optionally
91 precede it with "*" or "x29," to indicate that an X.29 (PAD) call
92 should be made.  For example, a destination of
93 
94       x29,3106:mitmul or
95       *3106:mitmul
96 
97 specifies an X.29-type call on TYMNET.