ProSBC:Stir Shaken - Revision history

Nicole Tan at 18:53, 19 December 2024

2024-12-19T18:53:23Z

← Older revision		Revision as of 14:53, 19 December 2024
Line 63:		Line 63:
	Gateway->Use script: choose the right main script		Gateway->Use script: choose the right main script
	:2. Load routing scripts		:2. Load routing scripts
	*[[:File:~~ClearIP_Query_LCR~~.zip\|Click here to download ClearIP_Query.rb (the fitler script)]]		*[[:File:ClearIP_Query.zip\|Click here to download ClearIP_Query.rb (the fitler script)]]

	*Import the filter script:		*Import the filter script:

Nicole Tan: NT:need to name the zip a different name to point to another file

2024-12-19T18:43:07Z

NT:need to name the zip a different name to point to another file

← Older revision		Revision as of 14:43, 19 December 2024
Line 63:		Line 63:
	Gateway->Use script: choose the right main script		Gateway->Use script: choose the right main script
	:2. Load routing scripts		:2. Load routing scripts
	*[[:File:~~ClearIP_Query~~.zip\|Click here to download ClearIP_Query.rb (the fitler script)]]		*[[:File:ClearIP_Query_LCR.zip\|Click here to download ClearIP_Query.rb (the fitler script)]]

	*Import the filter script:		*Import the filter script:

Nicole Tan: NT: Corrected before_filter :method => :ClearIP_Query

2024-12-09T22:08:44Z

NT: Corrected before_filter :method => :ClearIP_Query

← Older revision		Revision as of 18:08, 9 December 2024
Line 79:		Line 79:
	- Add the "require 'ClearIP_Query' unless defined?(ClearIPQuery)" statement at the top of the main script.		- Add the "require 'ClearIP_Query' unless defined?(ClearIPQuery)" statement at the top of the main script.
	- Add the "include ClearIPQuery" statement in the main routing class.		- Add the "include ClearIPQuery" statement in the main routing class.
	- Add the filter " before_filter :method => :~~ClearIP_query~~" in the main routing class.		- Add the filter " before_filter :method => :ClearIP_Query" in the main routing class.
	* Note: if label routing or other before_filter script are used, please place ClearIP_Query last		* Note: if label routing or other before_filter script are used, please place ClearIP_Query last
	*[[:File:Main_ClearIP.zip\|Refer to Main_ClearIP.rb here to know what it should look like in your existing "main" script]]		*[[:File:Main_ClearIP.zip\|Refer to Main_ClearIP.rb here to know what it should look like in your existing "main" script]]

Nicole Tan at 22:01, 9 December 2024

2024-12-09T22:01:25Z

← Older revision		Revision as of 18:01, 9 December 2024
Line 80:		Line 80:
	- Add the "include ClearIPQuery" statement in the main routing class.		- Add the "include ClearIPQuery" statement in the main routing class.
	- Add the filter " before_filter :method => :ClearIP_query" in the main routing class.		- Add the filter " before_filter :method => :ClearIP_query" in the main routing class.
	* Note: if label routing or other before_filter script are used, please place ~~ClearIP_query~~ last		* Note: if label routing or other before_filter script are used, please place ClearIP_Query last
	*[[:File:Main_ClearIP.zip\|Refer to Main_ClearIP.rb here to know what it should look like in your existing "main" script]]		*[[:File:Main_ClearIP.zip\|Refer to Main_ClearIP.rb here to know what it should look like in your existing "main" script]]

Nicole Tan at 20:33, 8 March 2023

2023-03-08T20:33:49Z

← Older revision		Revision as of 16:33, 8 March 2023
Line 45:		Line 45:

	Upon receiving 302		Upon receiving 302
	ProSBC ~~extracts~~ the ~~CNAM ([V] prefix)) in~~ the PAI header of the 302, and pass it to the next destination (NAP) according to the Routes priority order		ProSBC takes the Identity or the Verstat string from the PAI header of the 302, and pass it to the next destination (NAP) according to the Routes priority order
	Call Source (TDM or SIP) ---Invite or SETUP or IAM ---> ProSBC/TMG ----Invite--> ClearIP		Call Source (TDM or SIP) ---Invite or SETUP or IAM ---> ProSBC/TMG ----Invite--> ClearIP
	ProSBC/TMG < ----302---- ClearIP		ProSBC/TMG < ----302---- ClearIP

Nicole Tan: /* Stir/Shaken Call Flow */

2023-03-08T17:55:39Z

Stir/Shaken Call Flow

← Older revision		Revision as of 13:55, 8 March 2023
Line 16:		Line 16:
	In this call flow scenario the network diagram illustrates the typical layout of the network. This is followed by a detailed description of the call flow.		In this call flow scenario the network diagram illustrates the typical layout of the network. This is followed by a detailed description of the call flow.
	==Stir/Shaken Call Flow==		==Stir/Shaken Call Flow==
	[[Image:STIR_SHAKEN_Summary_CallFlow.jpg\|800px\|~~Network Diagram~~]]		[[Image:STIR_SHAKEN_Summary_CallFlow.jpg\|800px\|Call Flow]]

Nicole Tan at 17:55, 8 March 2023

2023-03-08T17:55:12Z

← Older revision		Revision as of 13:55, 8 March 2023
Line 15:		Line 15:
	=Typical Call-Flow Scenario=		=Typical Call-Flow Scenario=
	In this call flow scenario the network diagram illustrates the typical layout of the network. This is followed by a detailed description of the call flow.		In this call flow scenario the network diagram illustrates the typical layout of the network. This is followed by a detailed description of the call flow.
	==~~Network Diagram~~==		==Stir/Shaken Call Flow==
	[[Image:~~ClearIP Stir Shaken~~.jpg\|800px\|Network Diagram]]		[[Image:STIR_SHAKEN_Summary_CallFlow.jpg\|800px\|Network Diagram]]

	~~==Call Flow==~~
	~~[[Image:Shaken 302 with Identity.jpg\|800px\|Call Flow]]~~

	1. The ProSBC receives an inbound call from the Service Provider.		1. The ProSBC receives an inbound call from the Service Provider.

Nicole Tan: NT: updated the content to make it clearer

2022-05-20T21:01:07Z

NT: updated the content to make it clearer

← Older revision		Revision as of 17:01, 20 May 2022
Line 23:		Line 23:
	1. The ProSBC receives an inbound call from the Service Provider.		1. The ProSBC receives an inbound call from the Service Provider.

	2. ProSBC forwards the call to ClearIP for ~~verification with CNAM and~~ Robocall Analytics		2. ProSBC forwards the call to ClearIP for Authentication or Verification or Robocall Analytics

	3. ClearIP performs ~~a verification~~, CNAM lookup, Robocall Analytics, and then sends one of the following responses to ProSBC		3. ClearIP performs Authentication or Verification, CNAM lookup, Robocall Analytics, and then sends one of the following responses to ProSBC

	*SIP 404 Not Found: No fraud is detected. This is not a robocall.		*SIP 404 Not Found: No fraud is detected. This is not a robocall.
	*SIP 503 Service unavailable: No fraud is detected. This is not a robocall.		*SIP 503 Service unavailable: No fraud is detected. This is not a robocall.
	*SIP 603 Decline: Fraud is detected. Block the call.		*SIP 603 Decline: Fraud is detected. Block the call.
	*SIP 302 with ~~CNAM ( [V] prefix)~~ in PAI header (P-Asserted-Identity )		*SIP 302 with Identity for Authentication, or Verstat in PAI header (P-Asserted-Identity ) for Verification. Or CNAM in PAI header

	Upon receiving 404 or 503		Upon receiving 404 or 503
Line 50:		Line 50:
	Call Source (TDM or SIP) ---Invite or SETUP or IAM ---> ProSBC/TMG ----Invite--> ClearIP		Call Source (TDM or SIP) ---Invite or SETUP or IAM ---> ProSBC/TMG ----Invite--> ClearIP
	ProSBC/TMG < ----302---- ClearIP		ProSBC/TMG < ----302---- ClearIP
	ProSBC/TMG ----Invite with CNAM ~~([V] prefix)) ---Next Routes~~		ProSBC/TMG ----Invite with Identity for Authentication, or Verstat in PAI header for Verification, Or CNAM in PAI header

	=ProSBC Configuration=		=ProSBC Configuration=

Miguel Celis Salgado at 02:29, 28 April 2022

2022-04-28T02:29:02Z

← Older revision		Revision as of 22:29, 27 April 2022
Line 8:		Line 8:

	*For other configurations with all Transnexus/ClearIP Solutions, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC_With_Transnexus_Solutions		*For other configurations with all Transnexus/ClearIP Solutions, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC_With_Transnexus_Solutions
	*In case you are new to STIR-SHAKEN technology is highly recommended to watch the explanatory webinar available in our YouTube ~~channels~~:		*In case you are new to STIR-SHAKEN technology is highly recommended to watch the explanatory webinar available in our YouTube channel:

Miguel Celis Salgado at 01:20, 28 April 2022

2022-04-28T01:20:33Z

← Older revision		Revision as of 21:20, 27 April 2022
Line 8:		Line 8:

	*For other configurations with all Transnexus/ClearIP Solutions, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC_With_Transnexus_Solutions		*For other configurations with all Transnexus/ClearIP Solutions, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC_With_Transnexus_Solutions
	*In case you are new to STIR/SHAKEN technology is highly recommended to watch the explanatory webinar available in our YouTube channels:		*In case you are new to STIR-SHAKEN technology is highly recommended to watch the explanatory webinar available in our YouTube channels: