Design the conversation.

Build your call routes on a visual canvas, bring data into the flow and publish changes with a clear fallback.

MUNASIP v1.6.0Reviewed 21 October 2026Upstream reference ↗

A map of the whole call

Drag nodes onto the canvas and connect each exit to the next step. Flows are stored as JSON and executed by the API’s ARI engine. A draft is separate from the published version used by live calls.

Visual IVR designer · MunaSIP interface illustrationAn illustrative interface mockup, not a live phone system or a product screenshot.MunaSIPYOUR PHONE SYSTEMOverviewCall flowsCall recordsQueuesExtensionsReportsSettingsAll systems readyWORKSPACE / ADMINVisual IVR designerSAMPLE DATAMAIN LINE / PUBLISHED FLOWValidated♪Welcome menuHow can we help today?↗SalesPress 1 · ring extension 201⌘Customer lookupPress 2 · GET /customer↗Support queueConnect to the right team1 · Sales2 · Support4 connected steps · every exit has a destinationMunaSIP / A clearer connection.INTERFACE CONCEPT
Animated interface concept. Demo values describe a sample flow.

17 node types, clear exits

NodeUse
StartEntry point, with caller, did and time variables.
Announce / TTSPlay a WAV prompt or speak templated text.
Menu / Get keyCollect DTMF digits; handle timeout and invalid input.
API requestMake an HTTP request and map JSON response values.
If / Set variableBranch on data or update flow variables.
Pause / LanguageWait, optionally with hold music; change prompt language.
Schedule / DirectorySelect by business hours or dial by name.
SubflowRun another flow and return.
Transfer / QueueConnect an extension or destination, or join a queue.
Voicemail / HangupLeave a message or finish the call.

Connect a live API

The API request node supports GET, POST, PUT, PATCH and DELETE, templated URLs/headers/bodies, and response mapping via JSON paths. Authentication can use Bearer, Basic or a custom header. Store credentials in Settings → Secrets instead of the flow JSON.

The default timeout is 3 seconds, up to 10 seconds, with an optional single retry. Timeouts, non-success responses and unparseable data follow the error exit. A flow cannot publish with that exit left unconnected.

API node mapping
# Conceptual mapping inside an API request node
# Response: {"customer": true, "agent": "201"}
$.customer  -> known_customer
$.agent     -> agent
 
# Next: condition -> transfer to the mapped agent
# Error: route to the general support queue
API request node · MunaSIP interface illustrationAn illustrative interface mockup, not a live phone system or a product screenshot.MunaSIPYOUR PHONE SYSTEMOverviewCall flowsCall recordsQueuesExtensionsReportsSettingsAll systems readyWORKSPACE / ADMINAPI request nodeSAMPLE DATARequest configurationBring context into the conversation.Request methodGETEndpointhttps://api.example.com/customerAuthenticationBearer token · configuredTimeout3 seconds · one retryTest requestResponse mapped.A useful answer. A clear next step.200 OK · application/json{ "customer": true, "agent": "201"}Error exit → general support queueMunaSIP / A clearer connection.INTERFACE CONCEPT
Configure the request and test the mapped values in the designer.

Put the right words on the line

Use $name or {{name}} in speech and API templates. Filters format values, including digits, round, amount, province and ascii. Prompts are synthesized sentence by sentence and cached.

EngineLanguage / connectivity
Edge NeuralEnglish and Turkish voices; internet access needed during generation.
EMA LightningOffline Turkish neural speech; weights are baked into the image. Uses the PBX CPU.

Offline English synthesis is not provided. Edge speech sends synthesis requests to an external service. Choose engines and prompt content according to your own privacy requirements.

Test, publish and roll back

  1. Validate missing destinations, unconnected exits, unreachable nodes and cycles, including subflows.
  2. Simulate caller, DID, date/time and keypad inputs. Inspect variables and visited steps. Use mock API JSON or a real test endpoint deliberately.
  3. Publish the reviewed draft. Existing calls finish on the version they started with.
  4. Keep version history for rollback, and export JSON for your own records.

Simulation helps inspect logic. Test real media, timings and provider routes on your PBX before directing business calls to a new flow.

← All guidesSoftphone & portal