Allyntree at 14:38, 24 May 2024

2024-05-24T14:38:09Z

← Older revision		Revision as of 10:38, 24 May 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:Script Parameters Definition}}		{{DISPLAYTITLE:Script Parameters Definition}}
			<a href="#" id="hideToc">Hide TOC</a>
	=== Noa values ===		=== Noa values ===
	The text below represents the value normally used by routing script.<br>		The text below represents the value normally used by routing script.<br>

Allyntree at 15:19, 3 April 2024

2024-04-03T15:19:48Z

← Older revision		Revision as of 11:19, 3 April 2024
Line 300:		Line 300:
	*<tt>dnic</tt> (public Data Network ID, value 3, SS7 only)		*<tt>dnic</tt> (public Data Network ID, value 3, SS7 only)
	*<tt>mnic</tt> (public land mobile network, value 6, SS7 only)		*<tt>mnic</tt> (public land mobile network, value 6, SS7 only)

			[[Image:BackToMain.png\|thumb\|center\|400px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: Created page with "{{DISPLAYTITLE:Script Parameters Definition}} === Noa values === The text below represents the value normally used by routing script.
Incase it's required to use a value that's not defined in the text values below, a integer can be provided and will be used "as-is" in the signaling message.
Example numeric values for the SS7 protocol are shown in parenthesis.

`unknown_number (2 or 0x2)` `international_number (4 or 0x4)` *`national_n..."`

2024-03-29T16:04:19Z Created page with "{{DISPLAYTITLE:Script Parameters Definition}} === Noa values === The text below represents the value normally used by routing script. Incase it's required to use a value that's not defined in the text values below, a integer can be provided and will be used "as-is" in the signaling message. Example numeric values for the SS7 protocol are shown in parenthesis. *<tt>unknown_number (2 or 0x2)</tt> *<tt>international_number (4 or 0x4)</tt> *<tt>national_n..." New page {{DISPLAYTITLE:Script Parameters Definition}} === Noa values === The text below represents the value normally used by routing script. Incase it's required to use a value that's not defined in the text values below, a integer can be provided and will be used "as-is" in the signaling message. Example numeric values for the SS7 protocol are shown in parenthesis. *<tt>unknown_number (2 or 0x2)</tt> *<tt>international_number (4 or 0x4)</tt> *<tt>national_number (3 or 0x3)</tt> *<tt>subscriber_number (1 or 0x1)</tt> *<tt>network_specific (5 or 0x5)</tt> *<tt>network_routing_national_format (7 or 0x7)</tt> *<tt>network_routing_international_format (8 or 0x8)</tt> *<tt>abbreviated_number (6 or 0x6)</tt> *<tt>subscriber_number_operator_requested (113 or 0x71)</tt> *<tt>national_number_operator_requested (114 or 0x72)</tt> *<tt>international_number_operator_requested (115 or 0x73)</tt> *<tt>no_number_present_operator_requested (116 or 0x74)</tt> *<tt>no_number_present_cut_through_call_to_carrier (117 or 0x75)</tt> *<tt>test_line_test_code (119 or 0x77)</tt> *<tt>non_unique_subscriber_number (113 or 0x71)</tt> *<tt>non_unique_national_number (115 or 0x73)</tt> *<tt>non_unique_international_number (116 or 0x74)</tt> *<tt>call_950_number (118 or 0x76)</tt> *<tt>special_number (115 or 0x73)</tt> *<tt>national_number_with_transit_network_selection (116 or 0x74)</tt> *<tt>international_number_with_transit_network_selection (117 or 0x75)</tt> Those values will be remapped to the protocol specific NOA value. To provide protocol specific value: *<tt>call_params[:called_noa] = 0x70</tt> or *<tt>call_params[:called_noa] = 112</tt> === Npi values === *<tt>unknown_number</tt> *<tt>isdn</tt> *<tt>telephony</tt> *<tt>private</tt> *<tt>data</tt> *<tt>telex</tt> *<tt>national</tt> === Calling Display Type values === *<tt>unspecified</tt> => Type is unspecified. *<tt>calling_party_name</tt> => Type is 0xB1. Those values will be remapped to the protocol specific Display Information Type value. To provide protocol specific value: *<tt>call_params[:calling_display_type] = 0xB1</tt> or *<tt>call_params[:calling_display_type] = 177</tt> === Calling Display value === *<tt>call_params[:calling_display] = "Roger Fluffy"</tt> === Presentation values for Calling number, Calling Subscriber (Generic Number), Redirecting Number, Original Called Number (OCN) and Location Number === The text below represents the value normally used by routing script. Incase it's required to use a value that's not defined in the text values below, a integer can be provided and will be used "as-is" in the signaling message. Example numeric values for the SS7 protocol are shown in parenthesis. *<tt>unspecified</tt> *<tt>not_available (0x2)</tt> *<tt>allowed (0x0)</tt> *<tt>restricted (0x1)</tt> *<tt>addr_restricted</tt> *<tt>name_restricted</tt> === Calling Party Category === The text below represents the value normally used by routing script. In case it's required to use a value that's not defined in the text values below, a integer can be provided and will be used "as-is" in the signaling message. Mapping from routing script to SS7/CAS R2/SIP {| cellspacing="1" cellpadding="1" border="1" |- ! scope="col" | '''Routing Script string ''' ! scope="col" | '''SS7 raw value ''' ! scope="col" | '''R2 CAS scripts''' ! scope="col" | '''Default Rx CAS''' ! scope="col" | '''default Tx CAS''' ! scope="col" | '''SIP "cpc=" ''' |- | subscriber | 0xa | CATEGORY_SUBSCRIBER | 1 and 7 | 7 | ordinary |- | subscriber_with_priority | 0xb | CATEGORY_SUBSCRIBER_WITH_PRIORITY | 2 and 9 | 2 | priority |- | operator_french | 0x1 | CATEGORY_OPERATOR_FRENCH | 5 | 5 | operator |- | operator_english | 0x2 | CATEGORY_OPERATOR_ENGLISH (5) | 5 | 5 | operator |- | operator_german | 0x3 | CATEGORY_OPERATOR_GERMAN (5) | 5 | 5 | operator |- | operator_russian | 0x4 | CATEGORY_OPERATOR_RUSSIAN (5) | 5 | 5 | operator |- | operator_spanish | 0x5 | CATEGORY_OPERATOR_SPANISH (5) | 5 | 5 | operator |- | data | 0xc | CATEGORY_DATA | 6 and 8 | 6 | datacall |- | test | 0xd | CATEGORY_TEST | 3 | 3 | test |- | payphone | 0xf | CATEGORY_PAYPHONE | none | 7 | payphone |- | unknown | 0x0 | CATEGORY_UNKNOWN | 4, 11 to 15 | 7 | unknown |- | unspecified | 0xa | invalid | none | none | invalid |} [[CAS_R2_scripting#Category_meanings|Link to calling party categories used in CAS R2 scripts]] === Screening values for Calling number, Calling Subscriber (Generic Number), and Location Number === The text below represents the value normally used by routing script. In case it is required to use a value that is not defined in the text values below, an integer can be provided and will be used "as-is" in the signaling message. Example numeric values for the SS7 protocol are shown in parenthesis. *<tt>unspecified</tt> *<tt>no (0x0)</tt> *<tt>pass (0x1)</tt> *<tt>fail (0x2)</tt> *<tt>network_provided (0x3)</tt> === Redirecting indicator values === SS7: *<tt>no_redirection</tt> *<tt>call_rerouted</tt> *<tt>call_rerouted_all_restricted</tt> *<tt>call_diverted</tt> *<tt>call_diverted_all_restricted</tt> *<tt>call_rerouted_restricted</tt> *<tt>call_diverted_restricted</tt> *<tt>spare</tt> === Redirecting number, Original Called Number and Diversion Reason === ISDN: *<tt>unknown</tt> *<tt>busy</tt> *<tt>no_reply</tt> *<tt>deflection</tt> *<tt>dte_out_of_order</tt> *<tt>forwarding_by_called_dte</tt> *<tt>unconditional</tt> SS7: *<tt>unknown</tt> *<tt>busy (SIP: user-busy)</tt> *<tt>no_reply (SIP: no-answer)</tt> *<tt>unconditional</tt> *<tt>deflection</tt> *<tt>deflection_immediate</tt> *<tt>mobile_not_reachable</tt> === OLI (originating line information) values === The OLI parameter is a string that represents an integer value from 0 to 255. === Information Transfer Capability values === information_transfer_capability: *<tt>digital</tt> *<tt>restricted_digital</tt> *<tt>digital_with_tones</tt> *<tt>speech</tt> *<tt>3_1_khz_audio</tt> *<tt>video</tt> === redirecting_number_forward_enabled values === Controls forwarding or discarding of redirecting number (SIP: diversion header) to the outgoing call leg. Values for this parameter are "0", "1", "false" or "true. *0/false: Redirecting number (and original called number) is not forwarded to outgoing call leg *1/true: Redirecting number (and original called number) is forwarded to outgoing call leg The value for this parameter at the input of the routing script depends on the "Forward redirecting number" parameter in the "Advanced" section of the Gateway configuration page of the Web Portal. The script may change this value to override the Gateway configuration. Note: To "insert" a new redirecting number value on the outgoing leg, redirecting_number_forward_enabled must also be set to true. === MLPP Precedence values === mlpp_look_for_busy: *<tt>allowed</tt> *<tt>path_reserved</tt> *<tt>not_allowed</tt> mlpp_precedence_level: *<tt>flash_override</tt> *<tt>flash</tt> *<tt>immediate</tt> *<tt>priority</tt> *<tt>routine</tt> mlpp_network_identity: 3 digits value from 0 to 999 mlpp_service_domain: 24 bits value from 0 to 16777215 === ISUB subaddress information values === called_isub_type: calling_isub_type: *<tt>nsap</tt> *<tt>nsap_ia5</tt> *<tt>nsap_bcd</tt> *<tt>user</tt> called_isub: calling_isub: Digits for the subaddress information. === Network Identification Plan === network_identification_plan: *<tt>Unknown</tt> (value 0) *<tt>cic</tt> (3 digits carrier identification code plus circuit code, value 1, SS7 or ISDN) *<tt>user</tt> (User, value 2, ISDN only) *<tt>cic4</tt> (4 digits carrier identification code plus circuit code, value 2, SS7 only) *<tt>dnic</tt> (public Data Network ID, value 3, SS7 only) *<tt>mnic</tt> (public land mobile network, value 6, SS7 only)

Routing Script Tutorial: Script Parameters Definition - Revision history

Allyntree at 14:38, 24 May 2024

Allyntree at 15:19, 3 April 2024