CallRouting - Revision history

Allyntree: removed needs revising tag

2018-03-08T14:01:03Z

removed needs revising tag

← Older revision		Revision as of 10:01, 8 March 2018
Line 69:		Line 69:
	== Caveats ==		== Caveats ==
	For now only forced transcoding is supported by the CMC server but this might change in the future. Video support in CMC might force the issue because video transcoding is not cheap.		For now only forced transcoding is supported by the CMC server but this might change in the future. Video support in CMC might force the issue because video transcoding is not cheap.

	~~[[category: Needs revising]]~~

Allyntree: Needs revising edit

2018-03-08T14:00:22Z

Needs revising edit

← Older revision		Revision as of 10:00, 8 March 2018
Line 1:		Line 1:
	{{DISPLAYTITLE:Call Routing}}		{{DISPLAYTITLE:Call Routing}}

	~~Routing~~ is important for gateway applications ~~in general~~. ~~The~~ routing ~~block~~ is in charge of ~~giving~~ routes for incoming		Call routing is an important feature for gateway applications. Call routing is in charge of assigning call routes for incoming
	call attributes and~~/or depending~~ on external factors like the time of the day or congestion. ~~The~~ routes are responsible		call attributes and this may change based on external factors like the time of the day or congestion. Call routes are responsible
	of providing call attributes for incoming and outgoing legs; they contain common routing information like the called		for providing call attributes for incoming and outgoing legs; they contain common routing information like the called
	number, the calling number and the network access point.		number, the calling number and the network access point.

Line 36:		Line 36:

	In the default route implementation, the media profile is also changed depending on the transcoding type. This is done		In the default route implementation, the media profile is also changed depending on the transcoding type. This is done
	by the route in GetIncomingAttributes and GetOutgoingAttributes which will instantiate the attribute based on the		by the route in GetIncomingAttributes and GetOutgoingAttributes, which will instantiate the attribute based on the
	transcoding type. This works fine for this initial profile but the leg’s profile may be changed during the call’s life and		transcoding type. This works fine for this initial profile but the leg’s profile may be changed during the call’s life and
	that change must be handled depending on the transcoding type. The attribute class is the one that is aware of the		that change must be handled depending on the transcoding type. The attribute class is the one that is aware of the

Allyntree: Needs revising edit

2018-03-08T13:56:44Z

Needs revising edit

← Older revision		Revision as of 09:56, 8 March 2018
Line 1:		Line 1:
			{{DISPLAYTITLE:Call Routing}}

	Routing is important for gateway applications in general. The routing block is in charge of giving routes for incoming		Routing is important for gateway applications in general. The routing block is in charge of giving routes for incoming
	call attributes and/or depending on external factors like the time of the day or congestion. The routes are responsible		call attributes and/or depending on external factors like the time of the day or congestion. The routes are responsible

Ktrueman: added category

2010-08-24T20:07:34Z

added category

← Older revision		Revision as of 16:07, 24 August 2010
Line 67:		Line 67:
	== Caveats ==		== Caveats ==
	For now only forced transcoding is supported by the CMC server but this might change in the future. Video support in CMC might force the issue because video transcoding is not cheap.		For now only forced transcoding is supported by the CMC server but this might change in the future. Video support in CMC might force the issue because video transcoding is not cheap.

			[[category: Needs revising]]

Ktrueman: /* Caveats */

2009-07-21T18:05:37Z

Caveats

← Older revision		Revision as of 14:05, 21 July 2009
Line 66:		Line 66:

	== Caveats ==		== Caveats ==
	For now only forced transcoding is supported by the CMC server but this might change in the future. Video support		For now only forced transcoding is supported by the CMC server but this might change in the future. Video support in CMC might force the issue because video transcoding is not cheap.
	in CMC might force the issue because video transcoding not cheap.



	~~----~~

	~~Return to the Toolpack [[User Guide]]~~

Ktrueman at 19:32, 7 May 2009

2009-05-07T19:32:54Z

← Older revision		Revision as of 15:32, 7 May 2009
Line 12:		Line 12:
	<li>Forced: always transcode.		<li>Forced: always transcode.
	<li>Only as a fallback: to try to save hardware resources.		<li>Only as a fallback: to try to save hardware resources.
	<li>Disabled: if the the ~~hadware~~ resources are not available.		<li>Disabled: if the the hardware resources are not available.
	</ul>		</ul>

Line 18:		Line 18:
	== Usage ==		== Usage ==

	The default routing implementation routes on only three ~~optionnal criterias~~ (there must be at least one per rule):		The default routing implementation routes on only three optional criteria (there must be at least one per rule):
	<ul>		<ul>
	<li>Called number.		<li>Called number.
Line 34:		Line 34:

	In the default route implementation, the media profile is also changed depending on the transcoding type. This is done		In the default route implementation, the media profile is also changed depending on the transcoding type. This is done
	by the route in GetIncomingAttributes and GetOutgoingAttributes which will ~~instanciate~~ the attribute based on the		by the route in GetIncomingAttributes and GetOutgoingAttributes which will instantiate the attribute based on the
	transcoding type. This works fine for this initial profile but the leg’s profile may be changed during the call’s life and		transcoding type. This works fine for this initial profile but the leg’s profile may be changed during the call’s life and
	that change must be handled depending on the transcoding type. The attribute class is the one that is aware of the		that change must be handled depending on the transcoding type. The attribute class is the one that is aware of the

Ktrueman at 19:32, 7 May 2009

2009-05-07T19:32:01Z

← Older revision		Revision as of 15:32, 7 May 2009
Line 68:		Line 68:
	For now only forced transcoding is supported by the CMC server but this might change in the future. Video support		For now only forced transcoding is supported by the CMC server but this might change in the future. Video support
	in CMC might force the issue because video transcoding not cheap.		in CMC might force the issue because video transcoding not cheap.



	----		----

	Return to the Toolpack [[User Guide]]		Return to the Toolpack [[User Guide]]

Ktrueman at 19:31, 7 May 2009

2009-05-07T19:31:52Z

← Older revision		Revision as of 15:31, 7 May 2009
Line 64:		Line 64:
	}</code>		}</code>


			== Caveats ==
			For now only forced transcoding is supported by the CMC server but this might change in the future. Video support
			in CMC might force the issue because video transcoding not cheap.

	----		----

	Return to the Toolpack [[User Guide]]		Return to the Toolpack [[User Guide]]

Ktrueman at 19:31, 7 May 2009

2009-05-07T19:31:02Z

← Older revision		Revision as of 15:31, 7 May 2009
Line 63:		Line 63:
	}		}
	}</code>		}</code>


			----

			Return to the Toolpack [[User Guide]]

Ktrueman at 19:21, 7 May 2009

2009-05-07T19:21:53Z

← Older revision		Revision as of 15:21, 7 May 2009
Line 56:		Line 56:
	pAttributes = tbnew CTBCMC_CALL_LEG_NT_ATTRIBUTE;		pAttributes = tbnew CTBCMC_CALL_LEG_NT_ATTRIBUTE;
	}break;		}break;

	default:		default:
	{		{