Sharing features between customers - Revision history

Dcunningham at 03:51, 27 August 2024

2024-08-27T03:51:03Z

← Older revision		Revision as of 03:51, 27 August 2024
Line 14:		Line 14:
	For an example refer to the following customer tree:		For an example refer to the following customer tree:

	<~~code~~>		<pre>
	a		a
	\|		\|
Line 26:		Line 26:
	\|		\|
	H		H
	</~~code~~>		</pre>

	All upper case customers have "Share features with parent" enabled, and all lower case customers do not.		All upper case customers have "Share features with parent" enabled, and all lower case customers do not.

Dcunningham at 03:50, 27 August 2024

2024-08-27T03:50:39Z

← Older revision		Revision as of 03:50, 27 August 2024
Line 13:		Line 13:

	For an example refer to the following customer tree:		For an example refer to the following customer tree:

	<code>		<code>
	a		a
Line 26:		Line 27:
	H		H
	</code>		</code>

	All upper case customers have "Share features with parent" enabled, and all lower case customers do not.		All upper case customers have "Share features with parent" enabled, and all lower case customers do not.

Dcunningham at 22:44, 1 May 2018

2018-05-01T22:44:22Z

← Older revision		Revision as of 22:44, 1 May 2018
Line 1:		Line 1:
	Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number.		Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number.

	However, sometimes you may want to create a customer with branch offices as sub-customers, and allow internal ~~features to be accessible~~ between the sub-customers. For example, one customer may need to be able to dial feature codes within a sibling customer. This can be done with "common routing". To use it:		However, sometimes you may want to create a customer with branch offices as sub-customers, and allow internal access between the sub-customers. For example, one customer may need to be able to dial feature codes within a sibling customer. This can be done with "common routing". To use it:

	# Set System -> Configuration -> "Enable common routing between customers" to Yes.		# Set System -> Configuration -> "Enable common routing between customers" to Yes.

Dcunningham: Created page with "Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number. However, sometimes you may want to create a customer with b..."

2018-05-01T22:43:10Z

Created page with "Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number. However, sometimes you may want to create a customer with b..."

New page

Normally features within one Enswitch customer cannot be accessed by another customer, except by calling a Number.

However, sometimes you may want to create a customer with branch offices as sub-customers, and allow internal features to be accessible between the sub-customers. For example, one customer may need to be able to dial feature codes within a sibling customer. This can be done with "common routing". To use it:

# Set System -> Configuration -> "Enable common routing between customers" to Yes.
# For each sub-customer set "Share features with parent" to Yes.

The logic then used is:

# Call is made in customer with "Share features with parent" enabled.
# Routing engine looks at the calling customer's parent customer to see if it has "Share features with parent" enabled, and if so check it's parent, and so on until the highest level customer with "Share features with parent" enabled is found.
# Routing engine then looks in all sub-customers of that highest level customer, checks if the sub-customer has "Share features with parent" enabled, and if it does then looks in that customer for a number or feature code which matches the destination dialled.

For an example refer to the following customer tree:
<code>
a
|
-------
| | |
b c D
| |
e -------
| |
F G
|
H
</code>
All upper case customers have "Share features with parent" enabled, and all lower case customers do not.

# Customer H makes call. No number in H itself matches the number dialled, so the routing engine recurses upwards until it finds the highest level customer with "Share features with parent" enabled, which is D.
# The routing engine then recurses downwards from D until it finds that customer F contains a feature code matching the number dialled. The call routes to the destination which that feature code in customer F points to.
# Customers a, b, c, and e were not checked because D's parent did not have "Share features with parent" enabled, so D's parent and D's siblings were not checked for a matching number.