[svn-commits] mmichelson: branch group/CCSS r222103 - /team/group/CCSS/doc/tex/
SVN commits to the Digium repositories
svn-commits at lists.digium.com
Fri Oct 2 16:54:05 CDT 2009
Author: mmichelson
Date: Fri Oct 2 16:54:02 2009
New Revision: 222103
URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=222103
Log:
Commit a bit of progress on the CCSS user guide.
Added:
team/group/CCSS/doc/tex/ccss.tex (with props)
Modified:
team/group/CCSS/doc/tex/asterisk.tex
Modified: team/group/CCSS/doc/tex/asterisk.tex
URL: http://svnview.digium.com/svn/asterisk/team/group/CCSS/doc/tex/asterisk.tex?view=diff&rev=222103&r1=222102&r2=222103
==============================================================================
--- team/group/CCSS/doc/tex/asterisk.tex (original)
+++ team/group/CCSS/doc/tex/asterisk.tex Fri Oct 2 16:54:02 2009
@@ -147,6 +147,9 @@
\chapter{Security Framework}
\input{security-events.tex}
+\chapter{Call Completion Supplementary Services}
+ \input{ccss.tex}
+
\chapter{Development}
\section{Backtrace}
\input{backtrace.tex}
Added: team/group/CCSS/doc/tex/ccss.tex
URL: http://svnview.digium.com/svn/asterisk/team/group/CCSS/doc/tex/ccss.tex?view=auto&rev=222103
==============================================================================
--- team/group/CCSS/doc/tex/ccss.tex (added)
+++ team/group/CCSS/doc/tex/ccss.tex Fri Oct 2 16:54:02 2009
@@ -1,0 +1,142 @@
+\section{Introduction}
+
+ A new feature for Asterisk 1.6.4 is Call Completion Supplementary
+Services. This document aims to explain the system and how to use it.
+In addition, this document examines some potential troublesome points
+which administrators may come across during their deployment of the
+feature.
+
+\section{What is CCSS\?}
+
+ Call Completion Supplementary Services (often abbreviated "CCSS" or
+simply "CC") allow for a caller to let Asterisk automatically alert him
+when a called party has become available, given that a previous call to
+that party failed for some reason. The two services offered are Call
+Completion on Busy Subscriber (CCBS) and Call Completion on No Response
+(CCNR).
+ To illustrate, let's say that Alice attempts to call Bob. Bob is
+currently on a phone call with Carol, though, so Alice hears a busy
+signal. In this situation, assuming that Asterisk has been configured
+to allow for such activity, Alice would be able to request CCBS. Once
+Bob has finished his phone call, Alice will be alerted. Alice can then
+attempt to call Bob again.
+
+\section{Glossary of Terms}
+
+ In this document, we will use some terms which may require
+clarification. Most of these terms are specific to Asterisk, and are by
+no means standard.
+
+CCBS: Call Completion on Busy Subscriber. When a call fails because the
+recipient's phone is busy, the caller will have the opportunity to
+request CCBS. When the recipient's phone is no longer busy, the caller
+will be alerted. The means by which the caller is alerted is dependent
+upon the type of agent used by the caller.
+
+CCNR: Call Completion on No Response. When a call fails because the
+recipient does not answer the phone, the caller will have the opportun-
+ity to request CCNR. When the recipient's phone becomes busy and then
+is no longer busy, the caller will be alerted. The means by which the
+caller is alerted is dependent upon the type of the agent used by the
+caller.
+
+Agent: The agent is the entity within Asterisk that communicates with
+and acts on behalf of the calling party.
+
+Monitor: The monitor is the entity within Asterisk that communicates
+with and monitors the status of the called party.
+
+Generic Agent: A generic agent is an agent that uses protocol-agnostic
+methods to communicate with the caller. Generic agents should only be
+used for phones, and never should be used for "trunks."
+
+Generic Monitor: A generic monitor is a monitor that uses protocol-
+agnostic methods to monitor the status of the called party. Like with
+generic agents, generic monitors should only be used for phones.
+
+Native Agent: The opposite of a generic agent. A native agent uses
+protocol-specific messages to communicate with the calling party.
+Native agents may be used for both phones and trunks, but it must be
+known ahead of time that the device with which Asterisk is communica-
+ting supports the necessary signaling.
+
+Native Monitor: The opposite of a generic monitor. A native monitor
+uses protocol-specific messages to subscribe to and receive notifica-
+tion of the status of the called party. Native monitors may be used
+for both phones and trunks, but it must be known ahead of time that
+the device with which Asterisk is communicating supports the
+necessary signaling.
+
+Offer: An offer of CC refers to the notification received by the caller
+that he may request CC.
+
+Request: When the caller decides that he would like to subscribe to CC,
+he will make a request for CC. Furthermore, the term may refer to any
+outstanding requests made by callers.
+
+Recall: When the caller attempts to call the recipient after being
+alerted that the recipient is available, this action is referred to
+as a "recall."
+
+\section{How to Use CC}
+
+\subsection{The Initial Call}
+
+ The only requirement for the use of CC is to configure an agent for
+the caller and a monitor for at least one recipient of the call.
+This is controlled using the cc\_agent\_policy for the caller and the
+cc\_monitor\_policy for the recipient. For more information about these
+configuration settings, see configs/samples/ccss.conf.sample. If the
+agent for the caller is set to something other than "never" and at
+least one recipient has his monitor set to something other than
+"never," then CC will be offered to the caller at the end of the
+call.
+
+ Once the initial call has been hung up, the configured
+cc\_offer\_timer for the caller will be started. If the caller wishes to
+request CC for the previous call, he must do so before the timer
+expires.
+
+\subsection{Requesting CC}
+
+ Requesting CC is done differently depending on the type of agent
+the caller is using.
+
+ With generic agents, the CallCompletionRequest application must be
+called in order to request CC. There are two different ways in which
+this may be called. It may either be called before the caller hangs up
+during the initial call, or the caller may hang up from the initial
+call and dial an extension which calls the CallCompletionRequest
+application. If the second method is used, then the caller will
+have until the cc\_offer\_timer expires to request CC.
+
+ With native agents, the method for requesting CC is dependent upon
+the technology being used, coupled with the make of equipment. It may
+be possible to request CC using a programmable key on a phone or by
+clicking a button on a console. If you are using equipment which can
+natively support CC but do not know the means by which to request it,
+then contact the equipment manufacturer for more information.
+
+\subsection{Monitoring the Called Party}
+
+ Once the caller has requested CC, then Asterisk's job is to monitor
+the progress of the called parties. It is at this point that Asterisk
+allocates the necessary resources to monitor the called parties.
+
+ A generic monitor uses Asterisk's device state subsystem in order
+to determine when the called party has become available. For both CCBS
+and CCNR, Asterisk simply waits for the phone's state to change to
+a "not in use" state from a different state. Once this happened, then
+Asterisk will consider the called party to be available and will alert
+the caller.
+
+ A native monitor relies on the network to send a protocol-specific
+message when the called party has become available. When Asterisk
+receives such a message, it will consider the called party to be
+available and will alert the caller.
+
+ Note that since a single caller may dial multiple parties, a monitor
+is used for each called party. It is within reason that different called
+parties will use different types of monitors for the same CC request.
+
+\subsection{Alerting the Caller}
Propchange: team/group/CCSS/doc/tex/ccss.tex
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: team/group/CCSS/doc/tex/ccss.tex
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
Propchange: team/group/CCSS/doc/tex/ccss.tex
------------------------------------------------------------------------------
svn:mime-type = text/plain
More information about the svn-commits
mailing list