Actions

Toolpack:Call Routes Settings E: Difference between revisions
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Tmedia, Tdev, and Tsig Web Portal 3.2: Call Routes Settings}}
{{DISPLAYTITLE:Tmedia, Tdev, and Tsig Web Portal 3.2: Call Route Settings}}


=Routes=
__NOTOC__


==Static Route==
=Static Route=
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Add routes
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Add routes
Line 11: Line 11:
|}
|}


==''Routing Script''==
=Routing Script=
TelcoBridges provides a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps. Please select one of the following examples according to your needs. You may modify it when necessary.
TelcoBridges provides a wide variety of routing script examples, from which customers can apply directly in their web configuration, according to their needs, by following a few simple steps. Select one of the following examples according to your needs. You may modify it when necessary.


'''*Flexible NOA:''' Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.
'''*Flexible NOA:''' Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.
Line 42: Line 42:




<div class="mw-collapsible mw-collapsed" data-collapsetext="Configuring Audio Prompts" data-expandtext="Audio Prompts" style="width: 400px;">
'''Audio Prompts'''


{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
Line 51: Line 51:
|}
|}


</div>
<br><br>


==Label Routing==
=Label Routing=


This section assumes:
This section assumes:
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routing script is already implemented''' (you just need to add the label routing functionality)
* '''The routeset definition and digimap files are already created'''
* '''The routeset definition and digimap files are created.'''


{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Add label routing functionality
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Add label routing functionality
Line 69: Line 65:
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Assign_Routing_Script_DB_Files_to_Gateway_Application_E|Assign Routing/Script Files to the Gateway Application]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Digitmap_Files_C|Add the Digit Map Files to the System]]
*[[Toolpack:Add_Edit_Digitmap_Files_RestFul_A|Add/Edit the Digit Map Files to the System with RestFul API]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Add_Routeset_Definition_Files_C|Add the Routset Definition Files to the System]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Defintion/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Assign_Definition_Digitmap_Files_per_NAP_E|Assign Definition/Digitmap Files on a per NAP Basis]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Generate_Dynamic_Routes_D|Generate Dynamic Routes]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}
|}
|STYLE="vertical-align: top"|
 
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Update definition/digitmap files
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |Update definition/digitmap files
Line 84: Line 81:
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
*[[Toolpack:Activating_the_Configuration D|Activate configuration]]
|}
|}
|}


==RADIUS Authorization and Authentication==
=RADIUS Authorization and Authentication=
{|
 
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="240" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization
! width="240" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization
Line 99: Line 94:
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}
|STYLE="vertical-align: top"|
 
{| cellpadding="5" border="1" class="wikitable"
{| cellpadding="5" border="1" class="wikitable"
! width="300" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization (with custom dictionary)
! width="300" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" |RADIUS Authorization (with custom dictionary)
Line 111: Line 106:
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
*[[Toolpack:Enable_Routing_Script_E|Enable Routing Script]]
|}
|}
|}
 
<headertabs/>
'''{{#switchtablink:Call Route|Return to Web Portal 3.2 Home Page|Tmedia_Tsig_Tdev_Tutorial_Guide_v3.2}}'''

Latest revision as of 06:11, 12 September 2022



[edit]

TelcoBridges provides a wide variety of routing script examples, from which customers can apply directly in their web configuration, according to their needs, by following a few simple steps. Select one of the following examples according to your needs. You may modify it when necessary.

*Flexible NOA: Remap the Calling/Called NOA flexibly based on the routes. It should cover most of the NOA requests since the routes include the calling/called remapping as well.

*Prefix NOA: Remapp Calling/Called NOA according to the prefix of the calling/called number, manipulate calling/called number. For calling number, if it is a privacy call, use the number in P-Asserted-Identity line or Remote-Party-ID line as the calling number to remap the NOA and do the manipulation.


Flexible NOA Prefix NOA


Audio Prompts

Audio Prompts


Return to Web Portal 3.2 Home Page

Retrieved from "https://docs.telcobridges.com/w/index.php?title=Toolpack:Call_Routes_Settings_E&oldid=31970"