CAS R1 LOOPSTART NETWORK - Revision history

Allyntree at 14:05, 7 September 2022

2022-09-07T14:05:12Z

← Older revision		Revision as of 10:05, 7 September 2022
Line 1:		Line 1:
			{{DISPLAYTITLE:CAS R1 LOOPSTART NETWORK}}

	Loopstart is a CAS R1 variant.		Loopstart is a CAS R1 variant.

Abrassard at 18:58, 8 August 2013

2013-08-08T18:58:56Z

← Older revision		Revision as of 14:58, 8 August 2013
Line 1:		Line 1:
	Loopstart is a CAS R1 variant.		Loopstart is a CAS R1 variant.

	Loopstart is an asymmetrical variant where a ~~FXS (or "~~user") and ~~FXO (or "~~network") sides must be face to face.		Loopstart is an asymmetrical variant where a user and network sides must be face to face.

	Current page describes the Loopstart ~~FXO~~ variant, see the following page for documentation about [[~~CAS_R1_LOOPSTART_FXS~~\|~~Loopstart FXS~~]] variant.		Current page describes the Loopstart network variant, see the following page for documentation about [[CAS_R1_LOOPSTART_USER\|Loop start user side]] variant.

	You can find general documentation about CASR1 scripts in Toolpack in the following page:[[CASr1_scripting]].		You can find general documentation about CASR1 scripts in Toolpack in the following page:[[CASr1_scripting]].
Line 9:		Line 9:
	== Overview ==		== Overview ==

	In the Loopstart variant, ~~FXO~~ side is sending CAS bit B, used to make the user's phone ring, while it receives CAS bit A from user side to report user's phone as "on hook" or "off hook".		In the Loopstart variant, network side is sending CAS bit B, used to make the user's phone ring, while it receives CAS bit A from user side to report user's phone as "on hook" or "off hook".

	Initial CAS bits values:		Initial CAS bits values:
Line 18:		Line 18:
	* Call establishment:		* Call establishment:
	** User calling:		** User calling:
	*** ~~FXO~~ side detects bit A changes to 1, indicating that user's phone is "off hook"		*** Network side detects bit A changes to 1, indicating that user's phone is "off hook"
	*** ~~FXO~~ side sends a dial tone		*** Network side sends a dial tone
	*** ~~FXO~~ side collects the digits entered by the user		*** Network side collects the digits entered by the user
	*** ~~FXO~~ side stops the dial tone (upon first digit)		*** Network side stops the dial tone (upon first digit)
	*** ~~FXO~~ side proceed with the call		*** Network side proceed with the call
	** Network calling:		** Network calling:
	*** ~~FXO~~ side changes bit B to 0 ("ringer on") to make user's phone ring		*** Network side changes bit B to 0 ("ringer on") to make user's phone ring
	*** ~~FXO~~ side toggles bit B from 0 to 1 (0 for 2 seconds, 1 for 4 seconds)		*** Network side toggles bit B from 0 to 1 (0 for 2 seconds, 1 for 4 seconds)
	*** ~~FXO~~ side detects bit A changes to 1, indicating that user's phone is "off hook"		*** Network side detects bit A changes to 1, indicating that user's phone is "off hook"
	*** ~~FXO~~ side changes bit B back to 1		*** Network side changes bit B back to 1
	* Call termination (user side only, network has no way to terminate the call):		* Call termination (user side only, network has no way to terminate the call):
	** ~~FXO~~ side detects bit A changes to 0, indicating that user's phone is "on hook"		** Network side detects bit A changes to 0, indicating that user's phone is "on hook"

	Note: There is no way, in Loopstart variant, for network side to report when the call is answered, or terminated. The caller considers the call answered when the ring tone ends and when someone starts talking. The caller considers the call terminated when the conversation is over, or when it no more hears the remote party.		Note: There is no way, in Loopstart variant, for network side to report when the call is answered, or terminated. The caller considers the call answered when the ring tone ends and when someone starts talking. The caller considers the call terminated when the conversation is over, or when it no more hears the remote party.
Line 57:		Line 57:
	Note that prefix and suffix are rarely used in this variant, as most of the time the user side is not a telephony equipment, but rather a user that manually presses the digits on it's phone. In that case, the prefix will simply be ignored by the CASR1 stack, and the suffix will simply not be reached, causing the "inter_digit_timeout" to trigger and confirm that DNIS complete.		Note that prefix and suffix are rarely used in this variant, as most of the time the user side is not a telephony equipment, but rather a user that manually presses the digits on it's phone. In that case, the prefix will simply be ignored by the CASR1 stack, and the suffix will simply not be reached, causing the "inter_digit_timeout" to trigger and confirm that DNIS complete.

	When ~~FXO~~ side makes outgoing call toward the user, DNIS is not sent at all, and thus prefix/suffix don't apply to transmission of DNIS in this variant.		When Network side makes outgoing call toward the user, DNIS is not sent at all, and thus prefix/suffix don't apply to transmission of DNIS in this variant.


Line 63:		Line 63:
	* [[CASr1_scripting#ACTION_WAIT_ANI\|Options for receiving DNIS]]		* [[CASr1_scripting#ACTION_WAIT_ANI\|Options for receiving DNIS]]

	== Detailed information about the Loopstart ~~FXS~~ script and state machines ==		== Detailed information about the Loopstart network side script and state machines ==
	For more detailed information about how this script is implemented (various states, and options), please refer to the "~~loopstart_fxo~~.lua" script provided with Toolpack.		For more detailed information about how this script is implemented (various states, and options), please refer to the "loopstart_network.lua" script provided with Toolpack.

Abrassard: moved CAS R1 LOOPSTART FXO to CAS R1 LOOPSTART NETWORK: Renamed page NETWORK rather then FXO due to confusion in FXS vs FXO signification.

2013-08-08T18:53:30Z

moved CAS R1 LOOPSTART FXO to CAS R1 LOOPSTART NETWORK: Renamed page NETWORK rather then FXO due to confusion in FXS vs FXO signification.

← Older revision	Revision as of 14:53, 8 August 2013
(No difference)

Abrassard at 16:03, 8 August 2013

2013-08-08T16:03:18Z

← Older revision		Revision as of 12:03, 8 August 2013
Line 3:		Line 3:
	Loopstart is an asymmetrical variant where a FXS (or "user") and FXO (or "network") sides must be face to face.		Loopstart is an asymmetrical variant where a FXS (or "user") and FXO (or "network") sides must be face to face.

	Current page describes the Loopstart FXO variant, see the following page for documentation about [[CAS_R1_LOOPSTART_FXS\|Loopstart FXS] variant.		Current page describes the Loopstart FXO variant, see the following page for documentation about [[CAS_R1_LOOPSTART_FXS\|Loopstart FXS]] variant.

	You can find general documentation about CASR1 scripts in Toolpack in the following page:[[CASr1_scripting]].		You can find general documentation about CASR1 scripts in Toolpack in the following page:[[CASr1_scripting]].

Abrassard at 16:00, 8 August 2013

2013-08-08T16:00:33Z

← Older revision		Revision as of 12:00, 8 August 2013
Line 63:		Line 63:
	* [[CASr1_scripting#ACTION_WAIT_ANI\|Options for receiving DNIS]]		* [[CASr1_scripting#ACTION_WAIT_ANI\|Options for receiving DNIS]]

	== Detailed information about the Loopstart ~~FOX~~ script and state machines ==		== Detailed information about the Loopstart FXS script and state machines ==
	For more detailed information about how this script is implemented (various states, and options), please refer to the "loopstart_fxo.lua" script provided with Toolpack.		For more detailed information about how this script is implemented (various states, and options), please refer to the "loopstart_fxo.lua" script provided with Toolpack.

Abrassard at 15:49, 8 August 2013

2013-08-08T15:49:25Z

@@ Line 4: / Line 4: @@
 Current page describes the Loopstart FXO variant, see the following page for documentation about [[CAS_R1_LOOPSTART_FXS|Loopstart FXS] variant.
 == Overview ==
@@ Line 30: / Line 32: @@
 Note: There is no way, in Loopstart variant, for network side to report when the call is answered, or terminated. The caller considers the call answered when the ring tone ends and when someone starts talking. The caller considers the call terminated when the conversation is over, or when it no more hears the remote party.

Abrassard: Created page with "Loopstart is a CAS R1 variant. Loopstart is an asymmetrical variant where a FXS (or "user") and FXO (or "network") sides must be face to face. Current page describes the Loo..."

2013-08-08T15:36:52Z

Created page with "Loopstart is a CAS R1 variant. Loopstart is an asymmetrical variant where a FXS (or "user") and FXO (or "network") sides must be face to face. Current page describes the Loo..."

New page

Loopstart is a CAS R1 variant.

Loopstart is an asymmetrical variant where a FXS (or "user") and FXO (or "network") sides must be face to face.

Current page describes the Loopstart FXO variant, see the following page for documentation about [[CAS_R1_LOOPSTART_FXS|Loopstart FXS] variant.

== Overview ==

In the Loopstart variant, FXO side is sending CAS bit B, used to make the user's phone ring, while it receives CAS bit A from user side to report user's phone as "on hook" or "off hook".

Initial CAS bits values:
* Bit A (from user) is 1 ("on hook")
* Bit B (from network) is 1 ("ringer off")

Summary of the Loopstart call flow:
* Call establishment:
** User calling:
*** FXO side detects bit A changes to 1, indicating that user's phone is "off hook"
*** FXO side sends a dial tone
*** FXO side collects the digits entered by the user
*** FXO side stops the dial tone (upon first digit)
*** FXO side proceed with the call
** Network calling:
*** FXO side changes bit B to 0 ("ringer on") to make user's phone ring
*** FXO side toggles bit B from 0 to 1 (0 for 2 seconds, 1 for 4 seconds)
*** FXO side detects bit A changes to 1, indicating that user's phone is "off hook"
*** FXO side changes bit B back to 1
* Call termination (user side only, network has no way to terminate the call):
** FXO side detects bit A changes to 0, indicating that user's phone is "on hook"

Note: There is no way, in Loopstart variant, for network side to report when the call is answered, or terminated. The caller considers the call answered when the ring tone ends and when someone starts talking. The caller considers the call terminated when the conversation is over, or when it no more hears the remote party.