Traffic Case - Revision history

Sofial: Marked this version for translation

2023-03-02T08:47:53Z

Marked this version for translation

← Older revision		Revision as of 08:47, 2 March 2023
Line 1:		Line 1:
	<translate>		<translate>
	=== Traffic Case ===		=== Traffic Case === <!--T:1-->

			<!--T:2-->
	Traffic cases are set up to define which [[{{Link}}Price List\|price list]] to use for each call. This is needed since different price lists are used for different combinations of [[{{Link}}Traffic Type\|traffic types]], [[{{Link}}Node\|nodes]] and operators.		Traffic cases are set up to define which [[{{Link}}Price List\|price list]] to use for each call. This is needed since different price lists are used for different combinations of [[{{Link}}Traffic Type\|traffic types]], [[{{Link}}Node\|nodes]] and operators.

			<!--T:3-->
	It's important that the traffic cases are defined as accurately as possible, since it's usually the operator price lists that serve as the basis for the internal invoicing.		It's important that the traffic cases are defined as accurately as possible, since it's usually the operator price lists that serve as the basis for the internal invoicing.

			<!--T:4-->
	When setting up the traffic cases, a node and a number of traffic types or complete [[{{Link}}Traffic Category\|traffic categories]] are selected to be connected to the traffic case. This way you may for example connect all international calls that goes out on a specific trunk to a specific price list.		When setting up the traffic cases, a node and a number of traffic types or complete [[{{Link}}Traffic Category\|traffic categories]] are selected to be connected to the traffic case. This way you may for example connect all international calls that goes out on a specific trunk to a specific price list.

Sofial: Created page with " === Traffic Case === Traffic cases are set up to define which price list to use for each call. This is needed since different price lists are used for different combinations of traffic types, nodes and operators. It's important that the traffic cases are defined as accurately as possible, since it's usually the operator price lists that serve as the basis for the internal invoicing. When set..."

2023-01-24T09:39:25Z

Created page with "<translate> === Traffic Case === Traffic cases are set up to define which [[{{Link}}Price List|price list]] to use for each call. This is needed since different price lists are used for different combinations of [[{{Link}}Traffic Type|traffic types]], [[{{Link}}Node|nodes]] and operators. It's important that the traffic cases are defined as accurately as possible, since it's usually the operator price lists that serve as the basis for the internal invoicing. When set..."

New page

<translate>
=== Traffic Case ===

Traffic cases are set up to define which [[{{Link}}Price List|price list]] to use for each call. This is needed since different price lists are used for different combinations of [[{{Link}}Traffic Type|traffic types]], [[{{Link}}Node|nodes]] and operators.

It's important that the traffic cases are defined as accurately as possible, since it's usually the operator price lists that serve as the basis for the internal invoicing.

When setting up the traffic cases, a node and a number of traffic types or complete [[{{Link}}Traffic Category|traffic categories]] are selected to be connected to the traffic case. This way you may for example connect all international calls that goes out on a specific trunk to a specific price list.

</translate>

[[Category:Term{{Langcat|Traffic Case}}]]