Yjinglechan - Revision history

Monica at 09:14, 4 November 2013

2013-11-04T09:14:12Z

2013-06-10T09:16:41Z

‎Routing example

2013-06-10T09:14:04Z

‎Server mode

2013-06-10T09:13:14Z

‎Server mode

2013-06-10T07:37:03Z

2013-06-07T11:13:11Z

2013-06-07T10:43:16Z

2013-06-07T10:39:29Z

‎Server mode

2013-06-07T07:59:56Z

‎Client mode

2013-06-07T07:59:12Z

← Older revision		Revision as of 09:14, 4 November 2013
Line 236:		Line 236:

	* [[Telephony]]		* [[Telephony]]
		+
		+	[[Category:Jingle]] [[Category:Server]] [[Category:Client]]

@@ Line 225: / Line 225: @@
 ===Routing example===
-Route a call 125 to the user 'remoteuser' at server 'remotedomain.com'
+When calling 125 route to the user 'remoteuser' at server 'remotedomain.com'
    ^125$=jingle/remoteuser@remotedomain.com;callerprompt=Hello, this is a call from ME

@@ Line 18: / Line 18: @@
 By default if yjinglechan is loaded Yate will run in server mode.
-The domains, the resources must be set in this case.
+The domains and resources must be set in this case.
 When a call is done using just the caller number, the jingle module will choose the first domain and resource and send the information to the other module to handle the call.

@@ Line 16: / Line 16: @@
 ==Server mode==
-By default if module yjinglechan is loaded will make Yate run in server mode.
+By default if yjinglechan is loaded Yate will run in server mode.
 The domains, the resources must be set in this case.
-When a call is done using just the caller number, the jingle module will choose the first domain and resource and sends the information to the other module to handle the call.
+When a call is done using just the caller number, the jingle module will choose the first domain and resource and send the information to the other module to handle the call.
-For a call to reach the destination, needs to have set a full JID (Jabber ID). If called is user@domain, then the module will request subscription and will probe user presence, to obtain a resource to call.
+For a call to reach the destination, it needs to have set a full JID (Jabber ID). If called is user@domain, then the module will request subscription and will probe user presence, to obtain a resource to call.
-Yate in Jingle server mode can automatically respond to the subscription requests, also the presence is send.
+Yate in Jingle server mode can automatically respond to the subscription requests, and send presence information.
 == Client mode==

@@ Line 1: / Line 1: @@
-This module supports the Jingle protocol.
+This module supports the Jingle protocol. The configuration file for Jingle channel module is yjinglechan.conf.
-The configuration file for Jingle channel module is yjinglechan.conf.
+By default the module detects Yate's run mode and behaves accordingly (as a Server, if is not set, otherwise reads run mode from configuration file).
-By default the Jingle channel detects Yate run mode and behaves accordingly (as a Server,if is not set otherwise from configuration file).
+To use it in client mode disable parameter '''servermode''' from [general] section.
-To use it in client mode in [general] section disable parameter '''servermode'''.
+See in the next image a configuration of Yate Server with Jingle configured in server mode. The clients can be SIP, IAX, Jabber or H323 for one side and Jingle or other clients for the other side. In those cases the mapping of the called number must be done from routing modules.
-−
-See in the next image a configuration of Yate Server with Jingle configured in server mode, the clients can be SIP, IAX, Jabber or H323 for one side and Jingle or other clients for the other side. In those cases from routing modules, the mapping of the called number must be done.
 [[File:jingleserver_config.png]]

@@ Line 8: / Line 8: @@
 To use it in client mode in [general] section disable parameter '''servermode'''.
-See in the next image a configuration of Yate as Jingle Server, the clients can also be SIP, IAX, Jabber or H323 for one side and Jingle or other clients for the other side. In those cases from routing modules, the mapping of the called number must be done.
+See in the next image a configuration of Yate Server with Jingle configured in server mode, the clients can also be SIP, IAX, Jabber or H323 for one side and Jingle or other clients for the other side. In those cases from routing modules, the mapping of the called number must be done.
 [[File:jingleserver_config.png]]
-Here is a configuration example when Yate is set in Jingle client mode:
+Here is a configuration example when Yate Server is in Jingle client mode:
 [[File:jingleclient_config.png]]

@@ Line 35: / Line 35: @@
   servermode=no
-  '''Note:''' If you intend to use the jabberserver module, and you set the same domain as the server, keep in mind that the jingle channel will handle all jingle iq stanzas when running in server mode.
+  '''Note:''' If you intend to use the jabberserver module, and you set the same domain as the server, keep in mind that the jingle channel
   Jabberserver module must not be loaded when using Yate in client mode.