LNP databases
see https://en.wikipedia.org/wiki/Local_number_portability
Yeti supports interaction with LNP databases by SIP and HTTP REST protocols. We welcome requests to implement additional protocols or LNP database specific formats.
LNP databases are used for specify characteristics of the LNP service, that will be used by Yeti if it is configured in the Routing Plan LNP rules
Attributes
- Id
- Unique identifier.
- Name
- Database name. Unique field.
- Cache TTL
- Response cache ttl
ThinQ configuration
- Host
- Database host (will be ignored by In-memory hash driver).
- Plain Http
- When enabled, thinQ driver will use plan HTTP connection instead of HTTPS
- Port
- Database port
- Token
- ThinQ authetication token
- Username
- ThinQ authetication username
SIP 301/302 Redirect
- Format
Defines where LRN information located in SIP Response.
- Contact URI username
LRN Located in Contact header username, example
Contact: <sip:LRN@example.com>- Contact URI username rn parameter
LRN Located in Contact header username
rnparatemeter, exampleContact: <sip:123456789;rn=LRN@example.com>
- Host
Host where to send SIP INVITE request
- Port
Port where to send SIP INVITE request
- Timeout
Request timeout in milliseconds
CSV configuration
- Csv file path
- Path to the file with data to preload (for In-memory hash driver only).
Alkazar REST API
Host Port Key Timeout
Coure ANQ REST API
Base url
Username Password Country Code Operators map Timeout