Manage database catalogues and procedures
Separate descriptive catalogues, telephone geography and database maintenance so that a naming change never becomes an accidental data operation.
Choose the correct area
Open Administration → Database and procedures. The areas cover queues, agents, lines, number normalization, telephone geography, report procedures, scheduled database events and restoration of standard definitions. Identify whether you need to change a description, interpret a telephone number or maintain SQL objects before proceeding.
Work on catalogues first
Use the queue, agent and line catalogues to review the identifiers used by reports. Number normalization and geographic prefixes are separate settings: a readable label does not fix an unrecognized telephone prefix.
Review a sample number
Check the source format and normalization rules before changing a prefix. Geographic entries associate telephone prefixes with country, area, city and available coordinates.
Inspect maintenance previews
Review selected objects and the proposed operation before restoring standard SQL definitions. Distinguish editing a procedure from running it, and inspect event enablement separately.
Find the seven tabs and the restore preview
The database page has seven tabs. The standard SQL restore preview is an additional workflow opened from the relevant toolbar, not an eighth tab. Use the following eight areas to choose a precise task before changing data or definitions.
| Area | Task and boundary |
|---|---|
| Queues | Search identifiers and descriptions used by reports; refresh the queue inventory from PBX when needed. |
| Agents | Review agent identifiers and descriptions in the catalog. A catalog entry is distinct from a user login account. |
| Trunks | Identify outgoing lines and their descriptions; use the PBX trunk inventory refresh before investigating an unknown line in a report. |
| Number normalization | Define how numbers without an explicit international prefix are interpreted and preview a representative number. |
| Telephone geography | Review prefix, country, area or city classification and available coordinates. Preview catalog imports before applying them. |
| Report procedures | Inspect the SQL definitions and available actions. Running a procedure is an operation on report processing, not just refreshing this page. |
| Database events | Review database-scheduled work and its enabled state. The database event scheduler is distinct from operating-system cron jobs. |
| Standard restore preview | Review proposed restoration of shipped procedures and events, select the intended objects and review the confirmation. It does not recover historical call rows. |
Test the number format before applying it
Load the current normalization settings, then review the default country code, international 00 prefix, national/international/preserve interpretation, leading-zero option and short-number limit. The carrier’s actual numbering convention determines the appropriate choice: the first digits alone do not establish a country.
Preview representative examples
Try a domestic number, an explicit international number and a short internal number. Compare the proposed value with the actual number supplied by the carrier before saving.
Distinguish report normalization from PBX routing
The separate incoming-context tool previews an Asterisk context and inserts only the managed Obelisk block. Assigning that context to trunks and applying FreePBX configuration are separate manual steps. Review its effect on every incoming call on those trunks, including CallerID, before activating it.
Verify the intended result
Reopen the catalogue entry and a report containing the affected identifier. For geography, check that the same number resolves as expected and that the browser can load map tiles. For SQL maintenance, use Installation diagnostics to check required objects, grants and scheduler state.
Distinguish restoration from backup
Restoring procedure definitions is not a database data restore. The truncate_cons procedure clears derived report tables; it is not a routine refresh button. Investigate an empty report before executing destructive SQL. A complete recovery also needs the appropriate SQL backup, separate from the configuration archive.
Keep cron and SQL definitions under support control
Cron jobs and SQL events serve different parts of processing. Do not edit the shipped schedules, worker commands, stored procedures or SQL event definitions unless Obelisk support gives you a specific instruction. Editing, running and restoring a procedure have different effects: none is a generic way to refresh a page.
Use the controls, understand what changes
Choose the catalog tab before searching or editing. Queues, agents and trunks identify report resources; normalization and geography control number interpretation. Restore preview concerns standard SQL definitions, not a restore of historical call data.
Complete product screenshots
Illustrative data. Open the screenshot to enlarge it and match the controls to the instructions in this chapter.
Open complete screenshot
Read the workspace section by section
Match the numbers and panels below to the complete workspace. These screenshots use illustrative data; the procedures above explain how to work with your own installation.
Agents
Inspect the agent identifiers collected for reporting. A clear catalogue helps you interpret agent groupings and recognise the people behind call activity.
Lines and trunks
Associate outgoing channels with recognisable descriptions. Use those names when comparing traffic by line in the outbound report.
Geographic catalogue
Review telephone prefixes, country, area, city and coordinates used by the report maps. The catalogue describes telephone geography, not the live position of the customer.
Report procedures
Inspect the SQL procedures that process source data for reporting. Review each operation before execution, especially procedures that empty report tables.
Scheduled database events
Check the scheduled database jobs, their status and last execution. Distinguish these SQL events from the application tasks configured on the server.
SQL restore preview
Inspect the standard procedures and events to restore, select the objects and review the changes before confirmation. This view restores definitions; it is separate from a configuration backup.