Round Robin Routing - Revision history

Monica: /* Scenarios */

2013-10-31T14:01:27Z

‎Scenarios

Monica: /* Scenarios */

2013-10-31T14:00:58Z

‎Scenarios

Dana: /* Scenarios */

2013-05-27T14:36:12Z

‎Scenarios

Dana: /* Scenarios */

2012-12-10T10:55:57Z

‎Scenarios

Dana: /* Scenarios */

2012-12-06T11:51:51Z

‎Scenarios

Dana at 11:51, 6 December 2012

2012-12-06T11:51:26Z

Dana: /* Round-robin routing examples */

2012-12-06T11:50:44Z

‎Round-robin routing examples

Dana at 11:49, 6 December 2012

2012-12-06T11:49:42Z

Dana at 13:53, 4 October 2012

2012-10-04T13:53:21Z

Dana: Created page with "=== Round-robin routing === Combining the callfork module with the ''rotate'' function from regexroute it is possible to implement rou..."

2012-10-04T08:52:56Z

Created page with "=== Round-robin routing === Combining the callfork module with the ''rotate'' function from regexroute it is possible to implement rou..."

New page

=== Round-robin routing ===

Combining the [[Call_Forker|callfork]] module with the ''rotate'' function from [[Regular expressions|regexroute]] it is possible to implement round-robin routing, with or without fallback.

Let's suppose we route all numbers starting with 031 through two main SIP providers and we have one H.323 provider as fallback.

We set in regexroute.conf an entry like this:

{|width="85%" class="wikitable"
| ^031.*$=fork $(rotate,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
|}

We defined a list of two SIP call targets inside a rotate function. We also use a global (persistent between calls) variable conveniently named $idx031 so we remember it only rotates calls to the 031 prefix. Any other global variable name could be used.

The H.323 fallback route is placed outside the rotate function so it's always called last. The ''maxcall'' parameter of the message applies to all outgoing calls. There is currently no way of setting separate parameters for each individual call.

The first call comes in - let's suppose for 0310123. The initial value of variable $idx031 is undefined so zero will be assumed.
The following targets will be tried in sequence, each for 20 seconds (set by the maxcall parameter):

SIP: sip:0310123@provider1.net
SIP: sip:0310123@provider2.net
H.323: 10100310123@provider3.net

The first that answers will continue the call. If any of them fails the call will attempt the next target.
A side effect of the ''rotate'' function is to update the value of the global $idx031 variable. Since we defined only two rotation targets the value will cycle between the values 0 and 1.

Now a call comes in for 0319876. Since the previous call has changed $idx031 to 1 the attempted targets will be:

SIP: sip:0319876@provider2.net
SIP: sip:0319876@provider1.net
H.323: 10100319876@provider3.net

Finally, if instead of ''rotate'' we use the ''index'' function we will get round-robin routing without fallback between the two SIP providers, only with H.323 fallback route. Suppose we route:

{|width="85%" class="wikitable"
| ^031.*$=fork $(index,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
|}

The same incoming calls will generate outgoing calls to:

SIP: sip:0310123@provider1.net
H.323: 10100310123@provider3.net

and respectively:

SIP: sip:0319876@provider2.net
H.323: 10100319876@provider3.net

← Older revision		Revision as of 14:01, 31 October 2013
Line 61:		Line 61:
	* [[Routing]]		* [[Routing]]

−	[[Category:Routing]] [[~~Catebory~~:Fallback routing]]	+	[[Category:Routing]] [[Category:Fallback routing]]

← Older revision		Revision as of 14:00, 31 October 2013
Line 60:		Line 60:
	* [[Regular expressions]]		* [[Regular expressions]]
	* [[Routing]]		* [[Routing]]
		+
		+	[[Category:Routing]] [[Catebory:Fallback routing]]

← Older revision		Revision as of 14:36, 27 May 2013
Line 59:		Line 59:
	* [[Call Forker]]		* [[Call Forker]]
	* [[Regular expressions]]		* [[Regular expressions]]
		+	* [[Routing]]

@@ Line 57: / Line 57: @@
 '''See also'''
-* [[Call_Forker]]
+* [[Call Forker]]
 * [[Regular expressions]]

← Older revision		Revision as of 11:51, 6 December 2012
Line 58:		Line 58:

	* [[Call_Forker]]		* [[Call_Forker]]
−	* [[[[Regular expressions]]	+	* [[Regular expressions]]

@@ Line 18: / Line 18: @@
 The H.323 fallback route is placed outside the rotate function so it's always called last. The ''maxcall'' parameter of the message applies to all outgoing calls. There is currently no way of setting separate parameters for each individual call.
-====Scenarios examples====
+====Scenarios====
 The first call comes in - let's suppose for 0310123. The initial value of variable $idx031 is undefined so zero will be assumed.
@@ Line 42: / Line 42: @@
   ^031.*$=fork $(index,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
-====Scenarios examples====
+====Scenarios====
 The same incoming calls will generate outgoing calls to:

@@ Line 2: / Line 2: @@
 Combining the [[Call_Forker|callfork]] module with the ''rotate'' function from [[Regular expressions|regexroute]] it is possible to implement round-robin routing, with or without fallback.
-== Round-robin routing examples ==
+== Round-robin routing cases ==
 ===Round-robin routing with fallback===

@@ Line 1: / Line 1: @@
 Combining the [[Call_Forker|callfork]] module with the ''rotate'' function from [[Regular expressions|regexroute]] it is possible to implement round-robin routing, with or without fallback.
 Let's suppose we route all numbers starting with 031 through two main SIP providers and we have one H.323 provider as fallback.
@@ Line 8: / Line 11: @@
   ^031.*$=fork $(rotate,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
 We defined a list of two SIP call targets inside a rotate function. We also use a global (persistent between calls) variable conveniently named $idx031 so we remember it only rotates calls to the 031 prefix. Any other global variable name could be used.
 The H.323 fallback route is placed outside the rotate function so it's always called last. The ''maxcall'' parameter of the message applies to all outgoing calls. There is currently no way of setting separate parameters for each individual call.
 The first call comes in - let's suppose for 0310123. The initial value of variable $idx031 is undefined so zero will be assumed.
@@ Line 29: / Line 36: @@
   H.323: 10100319876@provider3.net
-Finally, if instead of ''rotate'' we use the ''index'' function we will get round-robin routing without fallback between the two SIP providers, only with H.323 fallback route. Suppose we route:
+===Round-robin routing without fallback===
   ^031.*$=fork $(index,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
 The same incoming calls will generate outgoing calls to:
@@ Line 42: / Line 53: @@
   SIP: sip:0319876@provider2.net
   H.323: 10100319876@provider3.net

@@ Line 7: / Line 7: @@
 We set in regexroute.conf an entry like this:
-{|width="85%" class="wikitable"
+  ^031.*$=fork $(rotate,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
-|  ^031.*$=fork $(rotate,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
-|}
 We defined a list of two SIP call targets inside a rotate function. We also use a global (persistent between calls) variable conveniently named $idx031 so we remember it only rotates calls to the 031 prefix. Any other global variable name could be used.
@@ Line 18: / Line 16: @@
 The following targets will be tried in sequence, each for 20 seconds (set by the maxcall parameter):
-SIP: sip:0310123@provider1.net
+ SIP: sip:0310123@provider1.net
-SIP: sip:0310123@provider2.net
+ SIP: sip:0310123@provider2.net
-H.323: 10100310123@provider3.net
+ H.323: 10100310123@provider3.net
 The first that answers will continue the call. If any of them fails the call will attempt the next target.
@@ Line 27: / Line 25: @@
 Now a call comes in for 0319876. Since the previous call has changed $idx031 to 1 the attempted targets will be:
-SIP: sip:0319876@provider2.net
+ SIP: sip:0319876@provider2.net
-SIP: sip:0319876@provider1.net
+ SIP: sip:0319876@provider1.net
-H.323: 10100319876@provider3.net
+ H.323: 10100319876@provider3.net
 Finally, if instead of ''rotate'' we use the ''index'' function we will get round-robin routing without fallback between the two SIP providers, only with H.323 fallback route. Suppose we route:
-{|width="85%" class="wikitable"
+ ^031.*$=fork $(index,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
-| ^031.*$=fork $(index,$idx031,| sip/sip:\0@provider1.net,| sip/sip:\0@provider2.net) | h323/1010\0@provider3.net;maxcall=20000
-|}
 The same incoming calls will generate outgoing calls to:
-SIP: sip:0310123@provider1.net
+ SIP: sip:0310123@provider1.net
-H.323: 10100310123@provider3.net
+ H.323: 10100310123@provider3.net
 and respectively:
-SIP: sip:0319876@provider2.net
+ SIP: sip:0319876@provider2.net
-H.323: 10100319876@provider3.net
+ H.323: 10100319876@provider3.net