Various spelling errors fixed in docs
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@2175 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
parent
dbe3dea363
commit
2cbef73a27
|
@ -13,7 +13,7 @@ separated text file.
|
|||
Applications
|
||||
------------
|
||||
|
||||
* Asterisk cmd setaccount: Set accound code for billing
|
||||
* Asterisk cmd setaccount: Set account code for billing
|
||||
* Asterisk cmd NoCDR: Make sure no CDR is saved for a specific call
|
||||
* Asterisk cmd resetCDR: Reset CDR
|
||||
* Asterisk cmd authenticate - Authenticates and sets the account code
|
||||
|
@ -36,7 +36,7 @@ Fields of the CDR in Asterisk
|
|||
8. lastapp: Last application if appropriate (80 characters)
|
||||
9. lastdata: Last application data (arguments) (80 characters)
|
||||
10. start: Start of call (date/time)
|
||||
11. answer: Anwer of call (date/time)
|
||||
11. answer: Answer of call (date/time)
|
||||
12. end: End of call (date/time)
|
||||
13. duration: Total time in system, in seconds (integer), from dial to hangup
|
||||
14. billsec: Total time call is up, in seconds (integer), from answer to hangup
|
||||
|
|
|
@ -31,7 +31,7 @@ and H.323, some of which are:
|
|||
* High performance, low overhead protocol
|
||||
When running on low-bandwidth connections, or when running
|
||||
large numbers of calls, optimized bandwidth utilization is
|
||||
imperitive. IAX uses only 4 bytes of overhead
|
||||
imperative. IAX uses only 4 bytes of overhead
|
||||
|
||||
* Internationalization support
|
||||
IAX transmits language information, so that remote PBX
|
||||
|
@ -198,7 +198,7 @@ these packets, improving voice quality.
|
|||
|
||||
> register => <name>[:<secret>]@<host>[:port]
|
||||
|
||||
Any number of registery entries may be instantiated in the general
|
||||
Any number of registry entries may be instantiated in the general
|
||||
section. Registration allows Asterisk to notify a remote Asterisk server
|
||||
(with a fixed address) what our current address is. In order for
|
||||
registration to work, the remote Asterisk server will need to have a
|
||||
|
@ -244,7 +244,7 @@ One or more context lines may be specified in a user, thus giving the user
|
|||
access to place calls in the given contexts. Contexts are used by
|
||||
Asterisk to divide dialing plans into logical units each with the ability
|
||||
to have numbers interpreted differently, have their own security model,
|
||||
auxilliary switch handling, and include other contexts. Most users are
|
||||
auxiliary switch handling, and include other contexts. Most users are
|
||||
given access to the default context. Trusted users could be given access
|
||||
to the local context for example.
|
||||
|
||||
|
@ -265,7 +265,7 @@ whereas:
|
|||
> deny = 192.168.0.0/255.255.255.0
|
||||
> permit = 0.0.0.0/0.0.0.0
|
||||
|
||||
would not deny anyone since the final rule would permit anyone, thsu
|
||||
would not deny anyone since the final rule would permit anyone, thus
|
||||
overriding the denial.
|
||||
|
||||
If no permit/deny rules are listed, it is assumed that someone may connect
|
||||
|
@ -283,7 +283,7 @@ You may select which authentication methods are permitted to be used by
|
|||
the user to authenticate to us. Multiple methods may be specified,
|
||||
separated by commas. If md5 or plaintext authentication is selected, a
|
||||
secret must be provided. If RSA authentication is specified, then one or
|
||||
more key names must be specifed with "inkeys"
|
||||
more key names must be specified with "inkeys"
|
||||
|
||||
If no secret is specified and no authentication method is specified, then
|
||||
no authentication will be required.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
GENERAL ENCHANCEMENTS TO EXTENSION LOGIC :
|
||||
GENERAL ENHANCEMENTS TO EXTENSION LOGIC :
|
||||
|
||||
QUOTING:
|
||||
|
||||
|
@ -9,7 +9,7 @@ comma does not terminate the field.
|
|||
|
||||
Also, characters special to variable substitution, expression evaluation, etc
|
||||
(see below), can be quoted. For example, to literally use a $ on the
|
||||
string "$1231", quote it with a preceeding \. Special characters that must
|
||||
string "$1231", quote it with a preceding \. Special characters that must
|
||||
be quoted to be used, are [ ] $ " \. (to write \ itself, use \\).
|
||||
|
||||
VARIABLES:
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
Extensions are routed according to priority, and may be based on any set
|
||||
of digits, #, and *. For each extension, several actions may be listed
|
||||
and each given a priority. When each action completes, it generally moves
|
||||
to the next priority (except for some modules which use explicity GOTO's.
|
||||
to the next priority (except for some modules which use explicitly GOTO's.
|
||||
Extensions frequently have data they pass to the executing application
|
||||
(most frequently a string). There are some reserved application names:
|
||||
|
||||
|
@ -18,5 +18,5 @@ Also, there are some extensions with important meanings:
|
|||
|
||||
And finally, the extension context "default" is used when either a) an
|
||||
extension context is deleted while an extension is in use, or b) a specific
|
||||
starting extension handler has not been defined (unless overrridden by the
|
||||
starting extension handler has not been defined (unless overridden by the
|
||||
low level channel interface).
|
||||
|
|
|
@ -11,7 +11,7 @@ Adding "/n" at the end of the string will make the Local channel not do a native
|
|||
|
||||
* Purpose:
|
||||
|
||||
The Local channel construct can be used to establish dialling into any part of the dialplan.
|
||||
The Local channel construct can be used to establish dialing into any part of the dialplan.
|
||||
|
||||
Imagine you have a TE410P in your box. You want to do something for which you must use a Dial statement (for instance when dropping files in /var/spool/outgoing) but you do want to be able to use your dialplans least-cost-routes or other intelligent stuff. What you could do before we had chan_local was create a cross-link between two ports of the TE410P and then Dial out one port and in the other. This way you could control where the call was going.
|
||||
|
||||
|
|
|
@ -12,7 +12,7 @@ receive this class of "event".
|
|||
|
||||
Command Syntax
|
||||
--------------
|
||||
Mangement communication consists of tags of the form "header: value",
|
||||
Management communication consists of tags of the form "header: value",
|
||||
terminated with an empty newline (\r\n) in the style of SMTP, HTTP, and
|
||||
other headers.
|
||||
|
||||
|
|
|
@ -7,9 +7,9 @@ interface. Typically this is done in its own thread. When a RING is
|
|||
detected, the backend should create a channel structure and then call
|
||||
ast_pbx_start() on that channel, which will create a thread to monitor
|
||||
that interface. At this point, the PBX and/or applications it launches
|
||||
will manage the interface, and it need not be montored by the
|
||||
will manage the interface, and it need not be monitored by the
|
||||
aforementioned thread. When the applications are finished, the requisite
|
||||
hangup function will be called, at which the channel can be considered to
|
||||
be no longer valid, and the thread that controls it will immenantly be
|
||||
be no longer valid, and the thread that controls it will imminently be
|
||||
terminated.
|
||||
|
||||
|
|
|
@ -3,8 +3,8 @@ All modules must have at least the following functions:
|
|||
int load_module():
|
||||
|
||||
Do what you need to do when you get started. This function
|
||||
returns 0 on sucess and non-zero on failure (it is not considered loaded
|
||||
if it failes.
|
||||
returns 0 on success and non-zero on failure (it is not considered loaded
|
||||
if it fails.
|
||||
|
||||
int unload_module():
|
||||
|
||||
|
@ -12,7 +12,7 @@ int unload_module():
|
|||
features, you should give them a softhangup in an effort to keep the
|
||||
program from crashing. Generally, unload_module is only called when the
|
||||
usecount is 0 or less, but the user can force unloading at their
|
||||
discression, and thus a module should do its best to comply (although in
|
||||
discretion, and thus a module should do its best to comply (although in
|
||||
some cases there may be no way to avoid a crash). This function should
|
||||
return 0 on success and non-zero on failure (i.e. it cannot yet be
|
||||
unloaded).
|
||||
|
|
Loading…
Reference in New Issue