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 record.
LNP database‘s attributes:¶
- Unique LNP database’s id.
- Database name. Unique field.
- Driver which will be used. Available options:
- UDP SIP 301/302 redirect thinQ RESR LRN driver In-memory hash
- Database host (will be ignored by In-memory hash driver).
- Database port.
- Maximum time to wait for response from database. Request will fail with appropriate code and reason.
- Thinq username
- Authorization username for thinQ API.
- Thinq token
- Authorization token for thinQ API.
- Csv file
- Path to the file with data to preload (for In-memory hash driver only).