New pages
From Kolmisoft Wiki
Jump to navigationJump to search
- 18:52, 3 June 2026 MOR API v2 tariff rates (hist | edit) [5,480 bytes] Admin (talk | contribs) (Created page with "Returns the complete rate table for a tariff — retail destination groups with time-banded prices, optional custom rates, or wholesale/provider flat rate rows. Not prefix rate lookup — that is MOR API v2 rates (<code>GET /rates</code>). Parity with legacy MOR API tariff rates get (<code>tariff_rates_get</code> / <code>get_tariff</code>). Retail behaviour matches the end-user GUI '''Rates''' screen (<code>/tariffs/user_rates</code>). Wholesale/provider behavio...")
- 18:16, 3 June 2026 MOR API v2 rates (hist | edit) [4,241 bytes] Admin (talk | contribs) (Created page with "Look up call rates for a destination prefix. Default behaviour matches the MOR GUI '''STATS → Search''' screen (field label '''Enter Number to get Rate''') and legacy MOR API rate get when <code>by_full_dst=0</code> is used on the legacy API. Returns one or more rate rows for the authenticated user, or — for '''admin''', '''reseller''', and '''accountant''' callers — for another user named in <code>username</code>. Simple portal users omit <code>username</code...")
- 18:05, 3 June 2026 MOR API v2 balance (hist | edit) [2,836 bytes] Admin (talk | contribs) (Created page with "Returns the prepaid balance of the user identified by the Bearer JWT (self-service only). The response uses the same balance conversion rules as legacy MOR API user balance get for the authenticated user — not for looking up other users by username or device. All endpoints require a valid Bearer token, user type '''admin''', '''reseller''', or '''user''', and <code>v2_balance_show</code> (Read) on the user's API permission group (sect...")
- 17:39, 3 June 2026 MOR API v2 me (hist | edit) [2,634 bytes] Admin (talk | contribs) (Created page with "<br><br> = Account profile (<code>/me</code>) = Returns or updates the profile of the user identified by the Bearer JWT (self-service only — not for editing other users). <br><br> ==== Authentication and permissions ==== * '''Bearer JWT''' (same as other MOR API v2 methods). * All user types may call when permitted. * Each call requires '''v2_me_show''' (GET) or '''v2_me_update''' (PATCH) on the user's API permission group. <br><br> = Endpoints = Base path: <c...")
- 06:12, 3 June 2026 MOR API v2 automatic cdr exports (hist | edit) [5,726 bytes] Admin (talk | contribs) (Created page with "Configure scheduled CDR delivery tasks through MOR API v2. Behavior matches '''SETTINGS → CDR → Export → Automatic''' in the GUI (see Automatic CDR Export for field meanings). Choose a <code>template_id</code> from cdr_export_templates or the GUI. The API '''creates and updates''' export tasks and returns scheduling metadata (for example, <code>next_run_at</code>). It does '''not''' run an export immediately — the syst...")
- 06:11, 3 June 2026 MOR API v2 cdr export templates (hist | edit) [2,322 bytes] Admin (talk | contribs) (Created page with "List and show CDR Export Templates through MOR API v2. Behavior matches '''SETTINGS → CDR → Export → Templates''' in the GUI (see CDR Export Templates for column meanings). Templates cannot be created or edited through this API — use the GUI for create/edit. All endpoints require a valid Bearer token, '''admin''' user type, and <code>v2_cdr_export_templates_index</code> or <code>v2_cdr_export_templates_show</code> on the user’s MOR API Permission...")
- 05:27, 3 June 2026 MOR API v2 whitelisted ips (hist | edit) [3,488 bytes] Admin (talk | contribs) (Created page with "Manage GUI whitelist rows (not IP-authenticated device rows from <code>mor_ipauth_whitelist.txt</code>) via MOR API v2. Behaviour matches '''Security → Monitorings → Whitelisted IPs''' in the GUI: the same validation rules apply (single IP, CIDR, or range; up to about 125 addresses per range). Changes take up to about one minute to apply on servers. All endpoints require a valid Bearer token, accountant '''monitorings_manage''' (read for list, write for create/u...")
- 18:15, 2 June 2026 MOR API v2 blocked ips (hist | edit) [4,667 bytes] Admin (talk | contribs) (Created page with "These endpoints manage rows on '''MOR - Blocked IPs''' (block, list, show, unblock). They complement the read-only diagnostic '''GET /api/v2/ip_access/status''' (check whether an arbitrary IP is blocked or whitelisted). Changes apply on the server within about one minute (same iptables pipeline as the GUI). <br><br> ==== Authentication and permissions ==== * '''Bearer JWT''' (same as other MOR API v2 methods). * User must be '''admin''' or '''accountant''' with...")
- 13:29, 2 June 2026 MOR API v2 user assign provider (hist | edit) [5,636 bytes] Admin (talk | contribs) (Created page with "Assign or unassign an unassigned provider trunk to a simple user so the provider can place calls using that user's balance — the same workflow as Configure Provider which can make calls in the GUI. <br><br> == GUI equivalent == '''Who may use the API:''' Admin, Accountant (with the rights below), or Reseller when provider management is allowed for that reseller. Simple users cannot assign providers....")
- 11:42, 2 June 2026 MOR API v2 ring groups (hist | edit) [2,347 bytes] Admin (talk | contribs) (Created page with "== Ring Groups == List ring groups with member device extensions and caller IDs (MOR API v2). === Authentication === Bearer JWT — same as other MOR API v2 endpoints. Obtain a token via <code>POST /api/v2/authentication/login</code>. === Endpoint === <code>GET /api/v2/ring_groups</code> === Authorization === * Admin — allowed when PBX addon is active. * Accountant — requires <code>manage_ring_groups</code> (read) and API method <code>v2_ring_groups_index<...")
- 05:15, 2 June 2026 CLI Groups - CLI Prefixes (hist | edit) [9,532 bytes] Admin (talk | contribs) (Created page with "A '''CLI Group''' is a list of '''CLI prefixes''' (numeric caller-ID prefixes) attached to a wholesale '''tariff''' rate. Together with the destination prefix, it allows the switch to apply different prices to the same called destination depending on who is calling. In the MOR GUI, the same data appears as '''CLI Group''' on rate lists and import analysis, and as '''CLI Prefixes''' when you edit a single rate. <br><br> == Description == '''What is a CLI G...")
- 16:03, 31 May 2026 MOR API IP access (hist | edit) [2,437 bytes] Admin (talk | contribs) (Created page with "== IP access status (API v2) == Read-only check whether an IPv4 address appears in MOR Monitorings block/whitelist lists. === Authentication === * MOR API v2 JWT (`Authorization: Bearer …`) — obtain token via <code>POST /billing/api/v2/authentication/login</code>. * Accountant users need '''Monitorings → Manage''' read permission (<code>monitorings_manage</code>). * API permission group must grant '''Check IP blacklist/whitelist status''' (<code>v2_ip_access...")
- 11:25, 27 May 2026 MOR API v2 DIDs (hist | edit) [7,694 bytes] Admin (talk | contribs) (Created page with "List DIDs via MOR API v2. <br><br> == Documentation == Full MOR REST API documentation is available at <code>/billing/api/v2/api-docs/</code>. <br><br> == Description == The DIDs API retrieves the list of DIDs visible to the authenticated '''admin''' or '''accountant''' user. Responses are JSON. The same data scope and VoiceAI integration fields as legacy dids_get apply. Authentication follows Usage on the parent page (JW...")
- 11:20, 27 May 2026 MOR API Permission Groups (hist | edit) [6,840 bytes] Admin (talk | contribs) (Created page with "''Fine-grained allow lists for hash-protected MOR API methods. Assign a group to integration users so they can call only the API actions you permit.'' <br><br> == Overview == '''What are API permission groups?'''<br> An API permission group is a named template of per-method API rights. Each hash-protected API method (for example <code>dids_get</code>, <code>users_get</code>, <code>did_create</code>) can be set to '''Disabled''', '''Read''', or '''Write''' inside th...")
- 15:56, 5 March 2026 Re-INVITE UDP fragmentation (hist | edit) [2,984 bytes] Admin (talk | contribs) (Created page with "'''Problem'''<br> The client sends SIP re-INVITEs over UDP that exceed the standard MTU (e.g. 1529 bytes > 1500 bytes). The re-INVITE is fragmented at the IP layer. On your side, re-INVITEs do not appear in traces; the client receives no response, and the call ends. Initial INVITE is within MTU and works; only the larger re-INVITE is affected. <br> '''Root cause'''<br> Fragmented UDP packets are dropped by your NAT/firewall (or possibly by the server interface). Only...")
