top of page
Myra logo-01.psd.psd.png

⚙️ MYRA Telephony – Technical Implementation Guide

  • Writer: David Botros
    David Botros
  • Sep 5, 2025
  • 3 min read

This guide is for IT administrators and telephony providers responsible for configuring the clinic’s phone system to integrate with MYRA.

Important: The clinic’s public phone number does not change. Patients will continue to dial the same number published on Google Maps, websites, and business cards. MYRA will process inbound calls and, when required, transfer them back to reception.


🔑 Prerequisites


Before deployment, the clinic must confirm the following:


General Requirements

  • Main clinic number remains active and unchanged.

  • Reception staff must have a dedicated line or DID that MYRA uses when transferring calls back to reception.

    • This Reception DID must be provided to MYRA Support.


PSTN (Landline)

  • Carrier supports unconditional forwarding (all calls).

  • Carrier supports conditional forwarding (busy / no answer).

  • Access to feature codes or a web portal to configure forwarding.


VoIP / SIP

  • Inbound routing rules can forward calls to MYRA’s SIP URI.

  • MYRA Support will provide the unique SIP URI for your clinic.


🔧 Deployment Methods

There are two general methods for integrating MYRA into your telephony environment:

  1. Dial to SIP URI: Forward inbound calls to MYRA via SIP routing.

  2. PSTN Call Forwarding: Forward calls from your public number to MYRA via carrier call forwarding.

VoIP / SIP Integration


Below are general vendor-agnostic instructions. Please consult your PBX or carrier documentation for platform-specific steps.


Dial to SIP URI

  1. Create a SIP Route

    • Obtain the unique MYRA SIP URI from MYRA Support.

    • Provide MYRA Support with the Reception DID (not the public clinic number).

    • In your PBX/carrier portal, create a new SIP route with destination set to the MYRA SIP URI (e.g. sip:clinic@myra.example.com:5060).

    • Assign this route to the Public DID (inbound) or to an IVR option, depending on the deployment method chosen.

  2. Call Flow

    • Patient dials the clinic’s main number (Public DID).

    • PBX/carrier routes the call via SIP URI to MYRA.

    • MYRA answers the call and either:

      • Handles the self-service interaction, or

      • Transfers the caller back to the Reception DID using an outbound route.



Deployment Call Flows

1. All Calls → MYRA

Use Case: Clinic wants MYRA to answer all inbound calls.

  • PSTN

    • Program unconditional forwarding from the clinic’s public number → MYRA’s number.

    • Repeat for each line if multiple PSTN circuits (e.g., hunt group).

  • Dial to SIP URI

    • Create inbound routing rule: all calls to Public DID → MYRA SIP URI


2. Busy / No Answer → MYRA

Use Case: Reception answers calls during business hours and MYRA covers overflow.

  • PSTN

    • Configure conditional forwarding: if busy or unanswered, forward → MYRA.

    • Set ring timeout (e.g., 4–6 rings).

  • VoIP

    • Inbound rule rings reception first.

    • If unanswered/busy, forward the call → MYRA SIP URI.


3. IVR Menu (VoIP Only)

Use Case: Patients choose MYRA or reception.

  • Add MYRA as an IVR option (e.g., “Press 1 for MYRA, Press 0 for Reception”).

  • Route the IVR option → MYRA SIP URI.

  • Configure an outbound route for MYRA → Reception DID.



🔄 Transfers from MYRA Back to Reception

  • PSTN: MYRA places a normal outbound call to the Reception DID and bridges the patient.

  • VoIP: MYRA initiates a SIP REFER to transfer the call directly to the Reception DID or hunt group.

    • If SIP REFER is not supported, the transfer will fall back to a normal outbound call to the Reception DID.


✨ This setup ensures MYRA can be deployed seamlessly into any clinic telephony environment (PSTN or VoIP), while keeping the clinic’s public number unchanged and allowing reliable transfers back to reception.


 
 
bottom of page