[asterisk-commits] file: branch file/chan_jingle2 r365603 - /team/file/chan_jingle2/configs/

Tue May 8 11:34:59 CDT 2012

Author: file
Date: Tue May  8 11:34:55 2012
New Revision: 365603

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=365603
Log:
Add sample configuration file for chan_jingle2. This also documents behavior and how some aspects work, which are important to understnad.

Added:
    team/file/chan_jingle2/configs/jingle2.conf.sample   (with props)

Added: team/file/chan_jingle2/configs/jingle2.conf.sample
URL: http://svnview.digium.com/svn/asterisk/team/file/chan_jingle2/configs/jingle2.conf.sample?view=auto&rev=365603
==============================================================================

--- team/file/chan_jingle2/configs/jingle2.conf.sample (added)
+++ team/file/chan_jingle2/configs/jingle2.conf.sample Tue May  8 11:34:55 2012
@@ -1,0 +1,73 @@
+; Sample configuration file for chan_jingle2
+
+; Transports
+;
+; There are three different transports and protocol derivatives supported by chan_jingle2. They are (in preference)
+; Jingle using ICE-UDP, Google Jingle, and Google-V1.
+;
+; Jingle as defined in XEP-0166 supports the widest range of features. It is referred to as "ice-udp" in this file. This is
+; the specification that Jingle clients implement.
+;
+; Google Jingle follows the Jingle specification for signaling but uses a custom transport for media. It is suppored
+; by the Google Talk Plug-in in gmail and by some other Jingle clients. It is referred to as "google" in this file.
+;
+; Google-V1 is the original Google Talk signaling protocol which used an initial very preliminary version of Jingle.
+; It also uses the same custom transport as Google Jingle for media. It is suppored by Google Voice, some other Jingle
+; clients, and the Windows Google Talk client. It is referred to as "google-v1" in this file.
+;
+; Incoming sessions will automatically switch to the correct transport once it has been determined.
+;
+; Outgoing sessions are capable of determining if the target is capable of Jingle or a Google transport if the target is
+; in the roster. Unfortunately it is not possible to differentiate between a Google Jingle or Google-V1 capable resource
+; until a session initiate attempt occurs. If a resource is determined to use a Google transport it will initially use
+; Google Jingle but will fall back to Google-V1 if required.
+;
+; If an outgoing session attempt fails due to failure to support the given transport chan_jingle2 will fall back in preference
+; order listed at the beginning of this document until all transports have been exhausted.
+;
+
+; Dialing and Resource Selection Strategy
+;
+; Placing a call through an endpoint can be accomplished using the following dial string:
+;
+; Jingle2/<endpoint name>/<target>
+;
+; When placing an outgoing call through an endpoint the requested target is searched in the roster list. If present
+; the first Jingle or Google Jingle capable resource is specifically targetted. Since the capabilities of the resource are
+; known the outgoing session initation will disregard the configured transport and use the determined one.
+;
+; If the target is not found in the roster the target will be used as-is and a session will be initiated using the
+; transpor specified in this configuration file. If no transport has been specified the endpoint defaults to ice-udp.
+;
+
+; Video Support
+;
+; Support for video does not need to be explicitly enabled. Configuring any video codec on your endpoint will
+; automatically enable it.
+
+; DTMF
+;
+; The only supported method for DTMF is RFC2833. This is always enabled on audio streams and negotiated if possible.
+
+; Default template for endpoints, to be included in their definition
+[default](!)
+disallow=all ;
+allow=ulaw
+allow=h264
+context=default ; Default context that incoming sessions will land in
+
+; Sample configuration entry for Jingle
+[jingle-endpoint](default)
+protocol=ice-udp                ; Change the default protocol of outgoing sessions to Jingle ICE-UDP
+allow=g722                      ; Add G.722 as an allowed format since the other side may support it
+connection=local-jabber-account ; Connection to accept traffic on and send traffic out
+
+; Sample configuration entry for Google Talk
+[gtalk-endpoint](default)
+protocol=google          ; Since this is a Google Talk endpoint we want to offer Google Jingle for outgoing sessions
+connection=gtalk-account
+
+; Sample configuration entry for Google Voice
+[gvoice](default)
+protocol=google-v1        ; Google Voice uses the original Google Talk protocol
+connection=gvoice-account

Propchange: team/file/chan_jingle2/configs/jingle2.conf.sample
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: team/file/chan_jingle2/configs/jingle2.conf.sample
------------------------------------------------------------------------------
    svn:keywords = Author Date Id Revision

Propchange: team/file/chan_jingle2/configs/jingle2.conf.sample
------------------------------------------------------------------------------
    svn:mime-type = text/plain


