Routes - Revision history

Webmaster: /* Examples */

2012-08-13T14:47:05Z

Examples

← Older revision		Revision as of 14:47, 13 August 2012
Line 58:		Line 58:

	3. Type '''before outbound routing''', Pattern '''6775000''' and Output '''sip:info@taridium.com''' - This rule will transform 6775000 to sip:info@taridium.com. There is no need for an outbound route in this case, since call routing will be performed via DNS records.		3. Type '''before outbound routing''', Pattern '''6775000''' and Output '''sip:info@taridium.com''' - This rule will transform 6775000 to sip:info@taridium.com. There is no need for an outbound route in this case, since call routing will be performed via DNS records.
		+
		+	4. Type '''before inside routing''', Pattern '''123''' and Output '''86''' - This rule will transform 123 to 86. This could be used for example for voicemail access via extension 123.

	== Inbound Blacklist ==		== Inbound Blacklist ==

Webmaster: /* Inbound Routing */

2011-04-20T18:25:56Z

Inbound Routing

← Older revision		Revision as of 18:25, 20 April 2011
Line 8:		Line 8:

	Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.		Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.
		+
		+	[[File:default-inbound.png]]

	=== Auto Extensions ===		=== Auto Extensions ===

Webmaster: /* Outbound Routing */

2011-04-20T18:23:11Z

Outbound Routing

← Older revision		Revision as of 18:23, 20 April 2011
Line 25:		Line 25:

	Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. A pattern can match the dialed extension and/or a specific caller ID. This allows you to use specific outbound routes for a phone. See also [[#Pattern Matching\|Pattern Matching]].		Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. A pattern can match the dialed extension and/or a specific caller ID. This allows you to use specific outbound routes for a phone. See also [[#Pattern Matching\|Pattern Matching]].
		+
	[[File:default-outbound.png]]		[[File:default-outbound.png]]

Webmaster: /* Outbound Routing */

2011-04-20T18:22:46Z

Outbound Routing

← Older revision		Revision as of 18:22, 20 April 2011
Line 25:		Line 25:

	Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. A pattern can match the dialed extension and/or a specific caller ID. This allows you to use specific outbound routes for a phone. See also [[#Pattern Matching\|Pattern Matching]].		Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. A pattern can match the dialed extension and/or a specific caller ID. This allows you to use specific outbound routes for a phone. See also [[#Pattern Matching\|Pattern Matching]].
		+	[[File:default-outbound.png]]
		+

	Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.		Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.

Webmaster: /* Examples */

2009-08-19T22:47:57Z

Examples

← Older revision		Revision as of 22:47, 19 August 2009
Line 48:		Line 48:
	===Examples===		===Examples===

-	1. Type '''before outbound routing''', Pattern '''_NXXXXXX''' and Output '''+1212${EXTEN}''' - This rule will transform any 7 digit numbers to an E.164 pattern within the 212 area code ~~prefixed~~. You will now have to match the newly formatted number in your outbound routes.	+	1. Type '''before outbound routing''', Pattern '''_NXXXXXX''' and Output '''+1212${EXTEN}''' - This rule will transform any 7 digit numbers to an E.164 pattern within the 212 area code. You will now have to match the newly formatted number in your outbound routes.

		+	2. Type '''before outbound routing''', Pattern '''_9NXXXXXX''' and Output '''+1212${EXTEN:1}''' - This rule will transform any 8 digit numbers starting with 9 to an E.164 pattern within the 212 area code. You will now have to match the newly formatted number in your outbound routes.

-	2. Type '''before outbound routing''', Pattern '''6775000''' and Output '''sip:info@taridium.com''' - This rule will transform 6775000 to sip:info@taridium.com. There is no need for an outbound route in this case, since call routing will be performed via DNS records.	+	3. Type '''before outbound routing''', Pattern '''6775000''' and Output '''sip:info@taridium.com''' - This rule will transform 6775000 to sip:info@taridium.com. There is no need for an outbound route in this case, since call routing will be performed via DNS records.

	== Inbound Blacklist ==		== Inbound Blacklist ==

Webmaster: /* Variables */

2009-08-19T22:46:11Z

Variables

← Older revision		Revision as of 22:46, 19 August 2009
Line 44:		Line 44:
	In extension transformations you can use the '''${EXTEN}''' variable in the output field if you need to transform the incoming pattern.		In extension transformations you can use the '''${EXTEN}''' variable in the output field if you need to transform the incoming pattern.

-	For the caller ID fields you can use '''${CALLERID(num)}''' or '''${CALLERID(name)}''', '''${NAME}''', '''${NUM}''' respectively.	+	For the caller ID fields you can use '''${CALLERID(num)}''', '''${CALLERID(name)}''', '''${NAME}''' or '''${NUM}''' respectively.
-		+
-		+

	===Examples===		===Examples===

Webmaster: /* Transformations */

2009-08-19T22:45:55Z

Transformations

← Older revision		Revision as of 22:45, 19 August 2009
Line 40:		Line 40:
	The difference between '''before inside routing''' and '''before outbound routing''' is that the transformation inside is applied before any of the local extensions are looked up, whereas '''before outbound routing''' it will be applied after all internal options have been exhausted.		The difference between '''before inside routing''' and '''before outbound routing''' is that the transformation inside is applied before any of the local extensions are looked up, whereas '''before outbound routing''' it will be applied after all internal options have been exhausted.

-	~~You~~ can use the '''${EXTEN}''' variable in the output field if you need to transform the incoming pattern.	+	=== Variables ===
		+
		+	In extension transformations you can use the '''${EXTEN}''' variable in the output field if you need to transform the incoming pattern.
		+
		+	For the caller ID fields you can use '''${CALLERID(num)}''' or '''${CALLERID(name)}''', '''${NAME}''', '''${NUM}''' respectively.
		+
		+

	===Examples===		===Examples===

Webmaster: /* Outbound Routing */

2009-08-11T14:37:14Z

Outbound Routing

← Older revision		Revision as of 14:37, 11 August 2009
Line 24:		Line 24:
	== Outbound Routing ==		== Outbound Routing ==

-	Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. See also [[#Pattern Matching\|Pattern Matching]].	+	Outbound routes allow you to specify where to find certain extensions/destinations, either fully qualified or by means of a pattern. A pattern can match the dialed extension and/or a specific caller ID. This allows you to use specific outbound routes for a phone. See also [[#Pattern Matching\|Pattern Matching]].

	Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.		Note that in certain cases the position of your route needs to be adjusted. This will for example be the case when you have overlapping number patterns.

Webmaster: /* Inbound Blacklist */

2009-08-11T13:14:11Z

Inbound Blacklist

← Older revision		Revision as of 13:14, 11 August 2009
Line 51:		Line 51:
	== Inbound Blacklist ==		== Inbound Blacklist ==

-	The inbound blacklist blocks specific incoming caller ID's. Caller ID's can be fully qualified or based on number patterns. See also [[#Pattern Matching\|Pattern Matching]]. Entries can be temporarily disabled [[Image:block-off.gif]] or enabled [[Image:block.gif]]	+	The inbound blacklist blocks specific incoming caller ID's. Caller ID's can be fully qualified or based on number patterns. See also [[#Pattern Matching\|Pattern Matching]]. Entries can be temporarily disabled [[Image:block-off.gif]] or enabled [[Image:block.gif]].

	== Pattern Matching ==		== Pattern Matching ==

Webmaster: /* Inbound Blacklist */

2009-08-11T13:13:25Z

Inbound Blacklist

← Older revision		Revision as of 13:13, 11 August 2009
Line 51:		Line 51:
	== Inbound Blacklist ==		== Inbound Blacklist ==

-	The inbound blacklist, blocks incoming caller ID's. Caller ID's can be fully qualified or based on number patterns. See also [[#Pattern Matching\|Pattern Matching]].	+	The inbound blacklist blocks specific incoming caller ID's. Caller ID's can be fully qualified or based on number patterns. See also [[#Pattern Matching\|Pattern Matching]]. Entries can be temporarily disabled [[Image:block-off.gif]] or enabled [[Image:block.gif]]

	== Pattern Matching ==		== Pattern Matching ==