Call transfer - Revision history

Allyntree at 14:18, 8 September 2022

2022-09-08T14:18:34Z

Luc Morissette: Added diagrams

2016-08-08T19:57:16Z

Added diagrams

← Older revision		Revision as of 15:57, 8 August 2016
Line 42:		Line 42:
	* Call transfer request leg is hung-up		* Call transfer request leg is hung-up
	* Audio is joined between the remaining leg and the ''Transfer Target''		* Audio is joined between the remaining leg and the ''Transfer Target''

			[[image:ISDN_to_SIP_call_transfer_from_outgoing_leg_%28Refer%29.png]]
			[[image:SIP_to_ISDN_call_transfer_from_incoming_leg.png]]

	==== Complete call flow ====		==== Complete call flow ====

Luc Morissette: Added incoming leg Refer

2016-08-08T19:21:42Z

Added incoming leg Refer

← Older revision		Revision as of 15:21, 8 August 2016
Line 35:		Line 35:
	In this mode, the call transfer request is processed locally by Toolpack. The call transfer is processed as follows:		In this mode, the call transfer request is processed locally by Toolpack. The call transfer is processed as follows:
	==== Simplified call flow ====		==== Simplified call flow ====
	* Incoming call ~~(''Transferee'')~~ is routed and joined to an outgoing call leg ~~(''Transferor'')~~		* Incoming call is routed and joined to an outgoing call leg
	* ~~Outgoing call leg send a~~ call transfer request		* A call transfer request is received from incoming or outgoing call leg
	* A new outgoing call leg (''Transfer Target'') is routed and made		* A new outgoing call leg (''Transfer Target'') is routed and made
	* Audio is unjoined between ~~''Transferee''~~ and ~~''Transferor''~~		* Audio is unjoined between incoming and outgoing call leg
	* ''Transfer Target'' answers		* ''Transfer Target'' answers
	* ~~''Transferor''~~ is hung-up		* Call transfer request leg is hung-up
	* Audio is joined between ~~''Transferee''~~ and ''Transfer Target''		* Audio is joined between the remaining leg and the ''Transfer Target''

	==== Complete call flow ====		==== Complete call flow ====

Luc Morissette: /* Simplified call flow */

2016-08-08T19:13:50Z

Simplified call flow

← Older revision		Revision as of 15:13, 8 August 2016
Line 35:		Line 35:
	In this mode, the call transfer request is processed locally by Toolpack. The call transfer is processed as follows:		In this mode, the call transfer request is processed locally by Toolpack. The call transfer is processed as follows:
	==== Simplified call flow ====		==== Simplified call flow ====
	* Incoming call (''Transferee'') is routed and joined to an outgoing call leg (''~~Tranferor~~'')		* Incoming call (''Transferee'') is routed and joined to an outgoing call leg (''Transferor'')
	* Outgoing call leg send a call transfer request		* Outgoing call leg send a call transfer request
	* A new outgoing call leg (''Transfer Target'') is routed and made		* A new outgoing call leg (''Transfer Target'') is routed and made

Rblanchet: /* Supported call transfer protocols */

2012-07-16T14:43:24Z

Supported call transfer protocols

← Older revision		Revision as of 10:43, 16 July 2012
Line 12:		Line 12:
	== Supported call transfer protocols ==		== Supported call transfer protocols ==
	* SS7: Not supported		* SS7: Not supported
	* ISDN: ~~Using Q.931~~ Facility IE		* ISDN: 4ESS-5ESS Facility message containing a codeset 6 Facility IE
	* CASR2: Not supported		* CASR2: Not supported
	* SIP: Using SIP Refer		* SIP: Using SIP Refer

Abrassard: /* Call transfer terms: */

2012-07-16T14:10:40Z

Call transfer terms:

← Older revision		Revision as of 10:10, 16 July 2012
Line 5:		Line 5:
	* ''Transferor'': The outgoing call leg that is initiating the call transfer request, and that gets disconnected once the transfer has been completed.		* ''Transferor'': The outgoing call leg that is initiating the call transfer request, and that gets disconnected once the transfer has been completed.
	* ''Transfer Target'': The second outgoing call leg, which is later made and joined to the ''Transferee''		* ''Transfer Target'': The second outgoing call leg, which is later made and joined to the ''Transferee''

			* ''Redirecting number'': Number from which the call is tranferred from (called number of the ''Transferor'')
			* ''Redirection number'': Number toward which the call transfer is made
			* ''Original called number'': Called number that the ''Transferee'' was originally calling

	== Supported call transfer protocols ==		== Supported call transfer protocols ==

Abrassard at 14:04, 16 July 2012

2012-07-16T14:04:26Z

@@ Line 42: / Line 42: @@
 * Initial call establishment:
 ** Incoming call is received (the ''Transferee'')
-** Routing is made (based on incoming leg's called number), outgoing call is made (the ''Transferor'')
+** [[Tmedia_Routing|Routing]] is made (based on incoming leg's called number), outgoing call is made (the ''Transferor'')
-** Early media is handled (according to profile):
+** [[Early_Media|Early media]] is handled (according to profile):
 *** Ring tone may be played to ''Transferee'' if appropriate
 *** Or Audio data path may be joined between ''Transferee'' and ''Transferor'' call legs if ''Transferor'' advertized early media
-** Route retry is handled:
+** [[Route_retry|Route retry]] is handled:
 *** In case of failure of a route, or in case of timeout, next mathing route is attempted
 ** ''Transferor'' answers the call
@@ Line 53: / Line 53: @@
 ** A ''Call Transfer Request'' is received from the ''Transferor''
 ** ''Call Transfer Progress'' is sent back to the ''Transferor''
-** Routing is made (using retirection number), a new outgoing call is made (the ''Transfer Target'')
+** [[Tmedia_Routing|Routing]] is made (using retirection number), a new outgoing call is made (the ''Transfer Target'')
 ** Audio data path is unjoined between ''Transferee'' and ''Transferor''
 ** Optionally, the ''Transferor'' is hungup (according to profile)
-** Early media is handled (according to profile):
+** [[Early_Media|Early media]] is handled (according to profile):
 *** Ring tone may be played to ''Transferee'' if appropriate
 *** Or Audio data path may be joined between ''Transferee'' and ''Transferor'' call legs if ''Transferor'' advertized early media
-** Route retry is handled:
+** [[Route_retry|Route retry]] is handled:
 *** In case of failure of a route, or in case of timeout, next mathing route is attempted
 * Call transfer fails (Call transfer timeout, or explicit termination of ''Transfer Target'' before it's answered)

Abrassard at 13:56, 16 July 2012

2012-07-16T13:56:46Z

@@ Line 24: / Line 24: @@
 == Call transfer modes ==
 === Call transfer forwarding ===
 === Call transfer processing ===

Abrassard: Created page with "Toolpack software provides call transfer support, either by relaying call transfer requests and responses between two bridges call legs, or by locally processing the call tran..."

2012-07-16T13:32:45Z

Created page with "Toolpack software provides call transfer support, either by relaying call transfer requests and responses between two bridges call legs, or by locally processing the call tran..."

New page

Toolpack software provides call transfer support, either by relaying call transfer requests and responses between two bridges call legs, or by locally processing the call transfer (making a new outgoing call leg, joining incoming call leg to the new outgoing call, dropping the original outgoing call leg).

== Call transfer terms: ==
* ''Transferee'': The incoming call leg, that is initially speaking with the ''Transferor'', then later transferred to the ''Transfer Target''.
* ''Transferor'': The outgoing call leg that is initiating the call transfer request, and that gets disconnected once the transfer has been completed.
* ''Transfer Target'': The second outgoing call leg, which is later made and joined to the ''Transferee''

== Supported call transfer protocols ==
* SS7: Not supported
* ISDN: Using Q.931 Facility IE
* CASR2: Not supported
* SIP: Using SIP Refer

== Toolpack configuration ==
The Call transfer behavior is configured per profile. In the web portal:
* Click on ''Profiles'' in the left menu
* Select the profile to edit: the profile used on the ''Transferor'' call leg (outgoing call leg)
* Expand section 'Call Transfer Options'
* Choose appropriate options:
** ''Call Transfer Mode'': Indicates if call transfer requests from outgoing leg must be relayed to incoming leg, or locally processed
** ''Terminate Transferor immediately'': When checked, the ''Transferor'' all leg is immediately terminated when new outgoing call leg is made. Otherwise, it's terminated only once the ''Transfer Target'' answers, and may be re-joined later with ''Transferee'' if ''Transfer Target'' fails or times out.
** ''Call Transfer timeout'': Timeout waiting for ''Transfer Target'' to answer before declaring the call transfer as failed.

== Call transfer modes ==
=== Call transfer forwarding ===

=== Call transfer processing ===

← Older revision		Revision as of 10:18, 8 September 2022
Line 1:		Line 1:
			{{DISPLAYTITLE:Call Transfer}}
	Toolpack software provides call transfer support, either by relaying call transfer requests and responses between two bridges call legs, or by locally processing the call transfer (making a new outgoing call leg, joining incoming call leg to the new outgoing call, dropping the original outgoing call leg).		Toolpack software provides call transfer support, either by relaying call transfer requests and responses between two bridges call legs, or by locally processing the call transfer (making a new outgoing call leg, joining incoming call leg to the new outgoing call, dropping the original outgoing call leg).

Line 6:		Line 7:
	* ''Transfer Target'': The second outgoing call leg, which is later made and joined to the ''Transferee''		* ''Transfer Target'': The second outgoing call leg, which is later made and joined to the ''Transferee''

	* ''Redirecting number'': Number from which the call is ~~tranferred~~ from (called number of the ''Transferor'')		* ''Redirecting number'': Number from which the call is transferred from (called number of the ''Transferor'')
	* ''Redirection number'': Number toward which the call transfer is made		* ''Redirection number'': Number toward which the call transfer is made
	* ''Original called number'': Called number that the ''Transferee'' was originally calling		* ''Original called number'': Called number that the ''Transferee'' was originally calling
Line 28:		Line 29:
	== Call transfer modes ==		== Call transfer modes ==
	=== Call transfer forwarding ===		=== Call transfer forwarding ===
	In this mode, call transfer request, call transfer progress, and call transfer response messages are simply being forwarded between the two bridged call legs. Toolpack is not taking any local decision. It's expected that other ~~equipments~~ in the network will process the call transfer request and respond to it.		In this mode, call transfer request, call transfer progress, and call transfer response messages are simply being forwarded between the two bridged call legs. Toolpack is not taking any local decision. It's expected that other equipment in the network will process the call transfer request and respond to it.

	If the incoming call leg is using a protocol that's not supported for call transfer, the call transfer request will be ignored.		If the incoming call leg is using a protocol that's not supported for call transfer, the call transfer request will be ignored.
Line 52:		Line 53:
	** [[Early_Media\|Early media]] is handled (according to profile):		** [[Early_Media\|Early media]] is handled (according to profile):
	*** Ring tone may be played to ''Transferee'' if appropriate		*** Ring tone may be played to ''Transferee'' if appropriate
	*** Or Audio data path may be joined between ''Transferee'' and ''Transferor'' call legs if ''Transferor'' ~~advertized~~ early media		*** Or Audio data path may be joined between ''Transferee'' and ''Transferor'' call legs if ''Transferor'' advertised early media
	** [[Route_retry\|Route retry]] is handled:		** [[Route_retry\|Route retry]] is handled:
	*** In case of failure of a route, or in case of timeout, next mathing route is attempted		*** In case of failure of a route, or in case of timeout, next mathing route is attempted
Line 62:		Line 63:
	** [[Tmedia_Routing\|Routing]] is made (using retirection number), a new outgoing call is made (the ''Transfer Target'')		** [[Tmedia_Routing\|Routing]] is made (using retirection number), a new outgoing call is made (the ''Transfer Target'')
	** Audio data path is unjoined between ''Transferee'' and ''Transferor''		** Audio data path is unjoined between ''Transferee'' and ''Transferor''
	** Optionally, the ''Transferor'' is ~~hungup~~ (according to profile)		** Optionally, the ''Transferor'' is hung up (according to profile)
	** [[Early_Media\|Early media]] is handled (according to profile):		** [[Early_Media\|Early media]] is handled (according to profile):
	*** Ring tone may be played to ''Transferee'' if appropriate		*** Ring tone may be played to ''Transferee'' if appropriate
	*** Or Audio data path may be joined between ''Transferee'' and ''Transferor'' call legs if ''Transferor'' ~~advertized~~ early media		*** Or Audio data path may be joined between ''Transferee'' and ''Transferor'' call legs if ''Transferor'' advertised early media
	** [[Route_retry\|Route retry]] is handled:		** [[Route_retry\|Route retry]] is handled:
	*** In case of failure of a route, or in case of timeout, next mathing route is attempted		*** In case of failure of a route, or in case of timeout, a next mathing route is attempted
	* Call transfer fails (Call transfer timeout, or explicit termination of ''Transfer Target'' before it's answered)		* Call transfer fails (Call transfer timeout, or explicit termination of ''Transfer Target'' before it's answered)
	** ''Transfer Target'' leg is terminated		** ''Transfer Target'' leg is terminated