ProSBC:Authentication Redirect - Revision history

Nicole Tan: NT: Need to point to a different script file

2024-12-19T19:06:21Z

NT: Need to point to a different script file

← Older revision		Revision as of 15:06, 19 December 2024
Line 69:		Line 69:
	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 at 20:29, 8 March 2023

2023-03-08T20:29:23Z

← Older revision		Revision as of 16:29, 8 March 2023
Line 11:		Line 11:
	=Call-Flow Scenario=		=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~~==		==LCR Routing Call Flow==
	[[Image:ClearIP LCR Routing _Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]		[[Image:ClearIP LCR Routing _Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]

	~~==Call Flow==~~
	~~4b.~~
	~~[[Image:ClearIP 302 with CNAM.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 at 04:10, 8 March 2023

2023-03-08T04:10:33Z

← Older revision		Revision as of 00:10, 8 March 2023
Line 100:		Line 100:
	[[Image:service_type.jpg\|800px]]		[[Image:service_type.jpg\|800px]]
	*Set the value to "AUTHENTICATION" for CLEARIP NAPs		*Set the value to "AUTHENTICATION" for CLEARIP NAPs


			===Add prosbc_routing in RoutesColumn ===
			Routes Columns->Create New Routes Column
			Name->prosbc_routing
			Type attributes -> YES\|NO
			Default ->YES
			[[Image:prosbc_routing.jpg\|800px]]
			*Set the value to "YES" for ProSBC routing

	==Scenario 1:One ClearIP NAP==		==Scenario 1:One ClearIP NAP==

Nicole Tan at 04:05, 8 March 2023

2023-03-08T04:05:23Z

← Older revision		Revision as of 00:05, 8 March 2023
Line 43:		Line 43:
	Call Source (TDM or SIP) <---SIP 603 or REL with 21 -------- ProSBC/TMG < ----603---- ClearIP		Call Source (TDM or SIP) <---SIP 603 or REL with 21 -------- ProSBC/TMG < ----603---- ClearIP

	Upon receiving 302		Upon receiving 302:
			4d: 302 with CNAM ( [V] prefix) in PAI header (P-Asserted-Identity ):
	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 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
	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
Line 49:		Line 50:
	ProSBC/TMG ----Invite with CNAM ([V] prefix)) ---Next Routes		ProSBC/TMG ----Invite with CNAM ([V] prefix)) ---Next Routes

			4e: 302 with list of the destination IP in the contact headers:
			e.g. Contact: <sip:Coolwave66886688914506558993@8.8.8.8>;q=0.99, <sip:C2A1Internet6688914506558993@8.8.8.8>;q=0.98,
			<sip:A3BC66886688914506558993@8.8.8.8>;q=0.97
			ProSBC composes list of the routes according to the Contact list of the returned 302 message and send the call to them with reroute retry function
			Call Source (TDM or SIP) ---Invite or SETUP or IAM ---> ProSBC/TMG ----Invite--> ClearIP
			ProSBC/TMG < ----302---- ClearIP
			ProSBC/TMG ----Invite--> called@IP of the first contact list with reroute retry function



	=ProSBC Configuration=		=ProSBC Configuration=
	This section provides the ProSBC configuration procedures for the solution. They are grouped into 4 main sections.		This section provides the ProSBC configuration procedures for the solution. They are grouped into 4 main sections.

Nicole Tan at 03:52, 8 March 2023

2023-03-08T03:52:05Z

← Older revision		Revision as of 23:52, 7 March 2023
Line 12:		Line 12:
	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==		==Network Diagram==
	[[Image:ClearIP ~~Verification_CNAM_Robocal~~ Analytics.jpg\|800px\|Network Diagram]]		[[Image:ClearIP LCR Routing _Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]

	==Call Flow==		==Call Flow==
			4b.
	[[Image:ClearIP 302 with CNAM.jpg\|800px\|Call Flow]]		[[Image:ClearIP 302 with CNAM.jpg\|800px\|Call Flow]]

Nicole Tan at 03:45, 8 March 2023

2023-03-08T03:45:42Z

← Older revision		Revision as of 23:45, 7 March 2023
Line 9:		Line 9:
	*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

	=~~Typical~~ Call-Flow Scenario=		=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==		==Network Diagram==

Nicole Tan at 03:36, 8 March 2023

2023-03-08T03:36:23Z

← Older revision		Revision as of 23:36, 7 March 2023
Line 2:		Line 2:

	=Introduction=		=Introduction=
	This document provides instructions to configure a ProSBC to operate with the TransNexus/ClearIP server for ~~verification with~~ CNAM and ~~Robocall Analytics~~.		This document provides instructions to configure a ProSBC to operate with the TransNexus/ClearIP server for a combination of Robocall Analytics, Stir/Shaken Authenticating/Verification, CNAM query and LCR routing from ClearIP.
	TransNexus/ClearIP is a SIP redirect server that provides advanced Least Cost Routing (LCR), fraud control and STIR (Secure Telephony Identity Revisited) / SHAKEN (Secure Handling of Asserted information using toKENs) features. <br/>		TransNexus/ClearIP is a SIP redirect server that provides advanced Least Cost Routing (LCR), fraud control and STIR (Secure Telephony Identity Revisited) / SHAKEN (Secure Handling of Asserted information using toKENs) features. <br/>

Nicole Tan at 16:06, 23 May 2022

2022-05-23T16:06:18Z

← Older revision		Revision as of 12:06, 23 May 2022
Line 1:		Line 1:
	{{DISPLAYTITLE:ProSBC Configuration for 302 Redirect ~~plus Stir/Shaken~~ with Transnexus ClearIP service}}		{{DISPLAYTITLE:ProSBC Configuration for 302 Redirect routing with Transnexus ClearIP service}}

	=Introduction=		=Introduction=

Nicole Tan at 02:07, 30 September 2021

2021-09-30T02:07:21Z

← Older revision		Revision as of 22:07, 29 September 2021
Line 7:		Line 7:
	ProSBC 3.0.90 or a later version is needed to support verification with CNAM and Robocall Analytics with TransNexus.		ProSBC 3.0.90 or a later version is needed to support verification with CNAM and Robocall Analytics with TransNexus.

	*For ~~simple Robocall Mitigation~~, please refer to: https://docs.telcobridges.com/tbwiki/~~ProSBC:Robocall_Mitigation~~		*For other configurations with all Transnexus/ClearIP Solutions, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC_With_Transnexus_Solutions

	=Typical Call-Flow Scenario=		=Typical Call-Flow Scenario=

Nicole Tan at 02:06, 30 September 2021

2021-09-30T02:06:13Z

Show changes