[asterisk-commits] mmichelson: branch group/CCSS r238218 - /team/group/CCSS/doc/tex/ccss.tex

[SVN commits to the Asterisk project]

Author: mmichelson
Date: Wed Jan  6 15:24:13 2010
New Revision: 238218

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=238218
Log:
Add note to the CC user's guide about how the minexpiry and maxexpiry
can affect CC's operation.


Modified:
    team/group/CCSS/doc/tex/ccss.tex

Modified: team/group/CCSS/doc/tex/ccss.tex
URL: http://svnview.digium.com/svn/asterisk/team/group/CCSS/doc/tex/ccss.tex?view=diff&rev=238218&r1=238217&r2=238218
==============================================================================
--- team/group/CCSS/doc/tex/ccss.tex (original)
+++ team/group/CCSS/doc/tex/ccss.tex Wed Jan  6 15:24:13 2010
@@ -305,6 +305,15 @@
 device state handling, be sure to set countcalls=yes for all peers and
 to set limitonpeers=yes in the general section of sip.conf
 
+\item When using SIP CC (i.e. native CC over SIP), it is important that
+your minexpiry and maxexpiry values allow for available timers to run
+as little or as long as they are configured. When an Asterisk server
+requests call completion over SIP, it sends a SUBSCRIBE message with
+an Expires header set to the number of seconds that the available
+timer should run. If the Asterisk server that receives this SUBSCRIBE
+has a maxexpiry set lower than what is in the received Expires header,
+then the available timer will only run for maxexpiry seconds. 
+
 \item As with all Asterisk components, CC is not perfect. If you should
 find a bug or wish to enhance the feature, please open an issue on
 https://issues.asterisk.org. If writing an enhancement, please be sure