ProSBC:CNAM Verification Robocall Analytics - Revision history

Nicole Tan at 20:32, 8 March 2023

2023-03-08T20:32:01Z

← Older revision		Revision as of 16:32, 8 March 2023
Line 23:		Line 23:
	*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 CNAM in PAI header or X-Identity header

	Upon receiving 404 or 503		Upon receiving 404 or 503
	ProSBC returns SIP 503 (or mapping to the TDM cause code) to the Source switch to perform route advance		ProSBC returns SIP 503 (or mapping to the TDM cause code) to the Source switch to perform route advance
Line 40:		Line 39:

	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 extracts the CNAM in PAI header or X-Identity 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
	ProSBC/TMG ----Invite with CNAM ~~([V] prefix))~~ ---Next Routes		ProSBC/TMG ----Invite with CNAM in PAI or X-Identity header --->Next Routes

	=ProSBC Configuration=		=ProSBC Configuration=

Nicole Tan at 17:59, 8 March 2023

2023-03-08T17:59:13Z

← Older revision		Revision as of 13:59, 8 March 2023
Line 13:		Line 13:
	==CNAM Lookup Call Flow==		==CNAM Lookup Call Flow==
	[[Image:CNAM_Lookup.jpg\|800px\|Call Flow]]		[[Image:CNAM_Lookup.jpg\|800px\|Call Flow]]

	~~==Call Flow==~~
	~~[[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 17:58, 8 March 2023

2023-03-08T17:58:30Z

← Older revision		Revision as of 13:58, 8 March 2023
Line 11:		Line 11:
	=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~~==		==CNAM Lookup Call Flow==
	[[Image:~~ClearIP Verification_CNAM_Robocal Analytics~~.jpg\|800px\|~~Network Diagram~~]]		[[Image:CNAM_Lookup.jpg\|800px\|Call Flow]]

	==Call Flow==		==Call Flow==

Luc Morissette: /* Configure Routing Script */

2022-01-28T22:12:28Z

Configure Routing Script

← Older revision		Revision as of 18:12, 28 January 2022
Line 61:		Line 61:
	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.zip\|Click here to download ClearIP_Query.rb (the filter script)]]

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

Nicole Tan at 02:08, 30 September 2021

2021-09-30T02:08:01Z

← Older revision		Revision as of 22:08, 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=

Allyntree: /* Typical Network and Call-Flow Scenario */

2021-09-28T13:49:07Z

Typical Network and Call-Flow Scenario

← Older revision		Revision as of 09:49, 28 September 2021
Line 9:		Line 9:
	*For simple Robocall Mitigation, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC:Robocall_Mitigation		*For simple Robocall Mitigation, please refer to: https://docs.telcobridges.com/tbwiki/ProSBC:Robocall_Mitigation

	=Typical ~~Network and~~ 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 ~~a typical~~ 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 Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]

Allyntree: /* ProSBC Configuration */

2021-09-28T13:48:12Z

ProSBC Configuration

← Older revision		Revision as of 09:48, 28 September 2021
Line 50:		Line 50:
	=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.
	*Initial Common Procedures-The procedures in this section are common to any scenario. You must follow them.		*Initial Common Procedures: The procedures in this section are common to any scenario. You must follow them.
	*Scenario 1: One ClearIP NAP-Follow this section to learn how to configure ProSBC with one ClearIP NAP without a need to differentiate between Inbound and Outbound calls.		*Scenario 1, One ClearIP NAP: Follow this section to learn how to configure ProSBC with one ClearIP NAP without a need to differentiate between Inbound and Outbound calls.
	*Scenario 2: More than one ClearIP NAP-Follow this section to learn how to configure ProSBC in which you have more than one ClearIP NAP and you need to differentiate between Inbound and Outbound calls.		*Scenario 2, More than one ClearIP NAP: Follow this section to learn how to configure ProSBC in which you have more than one ClearIP NAP and you need to differentiate between Inbound and Outbound calls.
	*Final Common Procedures-The procedures in this section are common to all scenarios.		*Final Common Procedures: The procedures in this section are common to all scenarios.

	==Initial Common Procedures==		==Initial Common Procedures==

Allyntree: /* Scenario 2: Two ClearIP NAPs */

2021-09-27T15:34:44Z

Scenario 2: Two ClearIP NAPs

← Older revision		Revision as of 11:34, 27 September 2021
Line 116:		Line 116:
	Priority: 10		Priority: 10

	==Scenario 2: ~~Two~~ ClearIP ~~NAPs~~==		==Scenario 2: More than one ClearIP NAP==
	Follow the procedures in this scenario if you have more than one ClearIP NAP and must differentiate between inbound and outbound calls.		Follow the procedures in this scenario if you have more than one ClearIP NAP and must differentiate between inbound and outbound calls.

Line 160:		Line 160:
	NAP: specific NAPs which carry the outbound traffic		NAP: specific NAPs which carry the outbound traffic
	Remapped NAP: NAP_CLEARIP_OUT		Remapped NAP: NAP_CLEARIP_OUT
	Priority: 10		Priority: 10

	==Final Common Procedures==		==Final Common Procedures==

Allyntree: /* Typical Network and Call-Flow Scenario */

2021-09-27T15:30:56Z

Typical Network and Call-Flow Scenario

← Older revision		Revision as of 11:30, 27 September 2021
Line 10:		Line 10:

	=Typical Network and Call-Flow Scenario=		=Typical Network and Call-Flow Scenario=
	In this call flow scenario the network diagram illustrates the typical layout of the network, followed by a detailed description of a typical 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 a typical call flow.
	==Network Diagram==		==Network Diagram==
	[[Image:ClearIP Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]		[[Image:ClearIP Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]

Allyntree: /* Typical Network and Call-Flow Scenario */

2021-09-27T15:30:41Z

Typical Network and Call-Flow Scenario

← Older revision		Revision as of 11:30, 27 September 2021
Line 10:		Line 10:

	=Typical Network and Call-Flow Scenario=		=Typical Network and Call-Flow Scenario=
	In this call flow scenario a network diagram illustrates the typical layout of the network, followed by a detailed description of a typical call flow.		In this call flow scenario the network diagram illustrates the typical layout of the network, followed by a detailed description of a typical call flow.
	==Network Diagram==		==Network Diagram==
	[[Image:ClearIP Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]		[[Image:ClearIP Verification_CNAM_Robocal Analytics.jpg\|800px\|Network Diagram]]