Clustering - Revision history

Monica: /* Settings for parameter prefix */

2013-10-31T13:52:39Z

‎Settings for parameter prefix

Dana: /* Settings for parameter prefix */

2013-05-28T13:29:41Z

‎Settings for parameter prefix

Dana: /* Settings for parameter prefix */

2013-04-04T14:29:18Z

‎Settings for parameter prefix

Dana at 14:28, 4 April 2013

2013-04-04T14:28:19Z

Dana at 13:47, 6 December 2012

2012-12-06T13:47:13Z

Dana at 13:46, 6 December 2012

2012-12-06T13:46:47Z

Dana at 13:46, 6 December 2012

2012-12-06T13:46:25Z

Dana at 10:51, 15 October 2012

2012-10-15T10:51:20Z

Dana: /* Clustering (Yate 2) */

2012-10-15T10:50:14Z

‎Clustering (Yate 2)

Dana at 10:44, 15 October 2012

2012-10-15T10:44:52Z

← Older revision		Revision as of 13:52, 31 October 2013
Line 75:		Line 75:
	* [[Configuring regexp and callto parameters in cluster route module]]		* [[Configuring regexp and callto parameters in cluster route module]]
	* [[Routing]]		* [[Routing]]
		+
		+	[[Category:Routing]] [[Category:Cluster]]

@@ Line 73: / Line 73: @@
 '''See also'''
-*  [[Example using parameters in cluster route module]]
+*  [[Configuring regexp and callto parameters in cluster route module]]
 *  [[Routing]]

← Older revision		Revision as of 14:29, 4 April 2013
Line 74:		Line 74:

	* [[Example using parameters in cluster route module]]		* [[Example using parameters in cluster route module]]
		+	* [[Routing]]

@@ Line 1: / Line 1: @@
 This module allows building clusters of servers for a single domain. All nodes are equivalent and they can be addressed from within the cluster by their [[Node Name]].<br>
-When a user registers (on any protocol) the name of the server it registered to is added in front of the user's location. Later, when a call is to be made to an user the call will be initiated from the same server the user registered to. This avoids problems with firewalls and NAT and with calls accepted only from the registrar the endpoint is connected to.
+When a user registers (on any protocol) the name of the server it registered to is added in front of the user's location.
 ===How it works===

@@ Line 17: / Line 17: @@
 * '''call.execute''' - so calls are forwarded to the server that can place them to the final target
 * '''call.route''' - to detect internal calls within the cluster
 ===Configuration file===

@@ Line 1: / Line 1: @@
 This module allows building clusters of servers for a single domain. All nodes are equivalent and they can be addressed from within the cluster by their [[Node Name]].
 When a user registers (on any protocol) the name of the server it registered to is added in front of the user's location. Later, when a call is to be made to an user the call will be initiated from the same server the user registered to. This avoids problems with firewalls and NAT and with calls accepted only from the registrar the endpoint is connected to.
 The module works by selectively altering resource names in Yate's messages. Relevant parameters are prefixed with the node name of the server that should handle them.
@@ Line 9: / Line 10: @@
 When a resource is to be used (like for target of a call) the node name in the resource is compared with the local node name. If they are the same the call is for the local server so the cluster prefix and node name are simply removed from the resource name. If the resource is remote (node name is not empty and is not the local node name either) the call is forwarded inside the cluster to the desired server.
-Additionally, cluster nodes can be allocated at call time by specifying * as node name. A '''cluster.locate''' message is issued to locate the node serving a specific resource (conference room, parking orbit, etc.) or optionally to allocate a new one
+Additionally, cluster nodes can be allocated at call time by specifying * as node name. A '''cluster.locate''' message is issued to locate the node serving a specific resource (conference room, parking orbit, etc.) or optionally to allocate a new one.
 The following messages are examined:
@@ Line 15: / Line 18: @@
 * '''call.execute''' - so calls are forwarded to the server that can place them to the final target
 * '''call.route''' - to detect internal calls within the cluster
 File clustering.conf:
@@ Line 58: / Line 64: @@
   ;call.cdr=25
-'''Note''': the prefix must be the same on all nodes in a cluster. It can be set to empty, in that case cluster resource names will start with a slash, like: /''nodename''/sip/sip:number@host
+*  [[Example using parameters in cluster route module]]

@@ Line 15: / Line 15: @@
 * '''call.execute''' - so calls are forwarded to the server that can place them to the final target
 * '''call.route''' - to detect internal calls within the cluster
   [general]
   ; Global settings of the clustering module
   ; enabled: boolean: Enable clustering module operation
   ;enabled=true if regexp and callto are set, false if any of them is empty
   ; prefix: string: Prefix used for cluster resources
   ;prefix=cluster
   ; regexp: string: Regular expression describing node name match rules
   ;regexp=
   ; callto: string: Template for forwarding the call to target node
   ;callto=
   ; locate: string: Message used for locating dynamic resources on cluster nodes
   ;locate=cluster.locate
   [priorities]
-  ; Handler priorities for each message
+  ; Handler priorities for each message, applied only on first initialization
   ; call.route: int: Priority of route message handler (on target node)
   ;call.route=50
   ; call.execute: int: Priority of execute message handler (on source node)
   ;call.execute=50
   ; user.register: int: Priority of registration message handler (on registrar)
   ;user.register=50
 '''Note''': the prefix must be the same on all nodes in a cluster. It can be set to empty, in that case cluster resource names will start with a slash, like: /''nodename''/sip/sip:number@host

← Older revision		Revision as of 10:44, 15 October 2012
Line 39:		Line 39:

	'''Note''': the prefix must be the same on all nodes in a cluster. It can be set to empty, in that case cluster resource names will start with a slash, like: /''nodename''/sip/sip:number@host		'''Note''': the prefix must be the same on all nodes in a cluster. It can be set to empty, in that case cluster resource names will start with a slash, like: /''nodename''/sip/sip:number@host
−
−	~~=== Example of regexp and callto settings ===~~
−
−	~~[general]~~
−	~~regexp=^[[:alnum:].-]\+$~~
−	~~callto=sip/sip:cluster/${called}@\0.dom.ain~~
−
−	~~In the above configuration suppose that:~~
−	* We are node '''node1'''
−	* A call comes in for number '''87654321'''
−	* Routing returns '''cluster/node2/sip/sip:321@192.168.0.2;user=phone'''
−	~~The prefix equals '''cluster/''' but the node is not local. The node name '''node2''' is found matching against the regexp so the callto is evaluated by replacing parameters and matched strings.~~
−	* The call is delivered to '''sip:cluster/321@node2.dom.ain'''
−	* On '''node2''' the call can be routed using a [[Regular_expressions#The_regexroute_configuration_file\|regexroute.conf]] rule like:
−
−	~~[default]~~
−	~~^cluster/=${sip_x-callto};billid=${sip_x-billid}~~