Geographic Sources
Geographic Sources
N2FE requires the configuration to identify the source of data that a caller location node may user for their lookup value. That is to say, the caller location node requires knowledge of whether it should compare it’s geographic location table to the calling party number, or some other value (e.g. an input accepted from the user - such as a postcode).
The list of available geographic lookup sources must be whitelisted in N2FE and this is done in the “geographic_sources” configuration field in n2fe.xml.
Where the caller location node uses a lookup based on a postcode or other piece of information input from the user, the system will validate that this input from the user has been retrieved. However to do this it must know which lookups require such user input.
The list of Geography Sets which require a user input are configured in the “user_input_geography_sets” configuration field in n2fe.xml.
User Input Geography Sets
Geography sets that follow user input can be configured within the main N2FE
configuration file /etc/jarvis/n2fe.xml
. Within the habitat
configuration
XML element the following JSON fragment can be altered as required.
"user_input_geography_sets": ["Postcodes"],
When the caller location node is configured to use a geography set whose prefix matches one of the prefixes listed in the “user_input_geography_sets” configuration list, it will validate that a user input node exists prior to the caller location node.
Further, the lookup value used in by the caller location node will be the one used in the user input.
Geographic Sources
When mapping between the lookup value (either from a user input source, or from another source, such as the calling party number) and a geography set, the caller location node needs to know what valid lookup sources exist.
These sources must be configured in the configuration file
/etc/jarvis/n2fe.xml
. Within the habitat
configuration
XML element the following JSON fragment can be altered as required.
"geographic_sources": [
{
"source_profile_block": "18"
, "source_profile_tag": "327684"
, "source_profile_type": "NSTRING"
, "buffer_name": "system.network_calling_party"
}
],
The user interface users the simple name “system.network_calling_party”, and this name is translated in to a backend value used by NCC.
Sometimes historical OCNCC control plans user invalid or incorrect source profiles. Using the “mapping” configuration these can be silently corrected if necessary.
Name | Description |
---|---|
source_profile_block |
[Required] The source profile block associated with
the current geography set that will be matched against. |
source_profile_tag |
[Required] The source profile tag associated with the
current geography set that will be matched against. |
source_profile_type |
[Required] The source profile type associated with the
current geography set that will be matched against. |
source_mapping_profile_block |
If specified, on successful source matching the source profile block will be updated to reflect this value. This is often used to correct invalid source configurations within the geographic routing node. |
source_mapping_profile_tag |
If specified, on successful source matching the source profile tag will be updated to reflect this value. This is often used to correct invalid source configurations within the geographic routing node. |
source_mapping_profile_type |
If specified, on successful source matching the source profile type will be updated to reflect this value. This is often used to correct invalid source configurations within the geographic routing node. |
buffer_name |
[Required] The buffer name that will be assigned to the
geographic routing if the source matches the source of the geography
set. |