Asterisk cron job or daemon on the free trial cloud installation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • angeloio
    Junior Member
    • May 2026
    • 3

    #1

    Asterisk cron job or daemon on the free trial cloud installation

    Greetings to everyone.

    I am the CTO of an IT company and I just created a free EspoCRM cloud instance to test some of the paid extensions for some prospective clients of ours. The extension we are most interested in testing is the VoIP extension combined with an Asterisk Integration. However it seems that Asterisk requires a cron job or daemon running on the EspoCRM server itself (php command.php voip Asterisk) to poll AMI events. As we do not have ssh access to the cloud server can someone please answer me if this cron job is already setup for us or how to start it?

    I thank you in advance

    Kind Regards
    Ioannis
  • victor
    Active Community Member
    • Aug 2022
    • 1194

    #2
    On Espo Cloud, cron is configured for trial and paid plans. You can start testing.

    Comment

    • angeloio
      Junior Member
      • May 2026
      • 3

      #3
      Thank you so much for the immediate reply.

      Comment

      • angeloio
        Junior Member
        • May 2026
        • 3

        #4
        Hello again,

        As previously said I'm evaluating the VoIP Integration extension with Asterisk on my cloud-hosted EspoCRM demo instance. The AMI connection is established and working (Test Connection succeeds, and I can confirm the persistent connection via "asterisk -rx manager show connected" on the Asterisk side). However, I'm encountering four issues.

        Environment:
        - EspoCRM: cloud demo instance (trial plan with cron for Asterisk confirmed by your support)
        - Asterisk: 22 (FreePBX 17 on Debian 12, hosted on Hetzner VPS)
        - Connector: VoIP · Asterisk AMI, connection test successful
        - Two PJSIP extensions configured: 100 and 101
        - Two EspoCRM users, each mapped to one extension via VoIP Settings
        - Admin user mapped to extension 101
        - Softphones: MicroSIP (ext 100) and Zoiper (ext 101), both registered

        Issue 1 – Incoming calls are not recorded and no popup is displayed
        When extension 100 calls extension 101 (the Admin user's extension - and the admin is logged in), the call connects successfully in Asterisk, but EspoCRM does not create a Call record and no popup notification appears for the Admin user. This happens consistently.

        Expected behavior: An incoming call popup should appear for the Admin user when their extension (101) receives a call, and a Call record should be created.

        Issue 2 – Outgoing call popup appears late (after answer, not on ring)
        When the Admin user (extension 101) calls extension 100 from Zoiper, the popup in EspoCRM DOES appear but only few seconds after the call is answered by the other party. It does not appear during the ringing phase.

        Expected behavior: The popup should appear as soon as the outgoing call starts ringing at the remote end, not after the call is answered. The Asterisk AMI does emit DialBegin and Ringing events that could be used for this.

        Issue 3 – Call record does not associate the called party's EspoCRM user
        The Call record created for an outgoing call (e.g., "Outgoing Call: admin to 100") correctly assigns the Admin as the originating user but does not include the second EspoCRM user (mapped to extension 100) as an attendee. (see attached image)

        Issue 4 – Call popup save button times out
        When the outgoing call popup appears, I fill in the details (only the note section) and click "Save". The save operation hangs for several seconds and then times out without completing. The Call record IS ultimately created (likely via the "Automatically save a call" setting), but the manual save from the popup window fails consistently. This happens both during an active call and after hanging up. (see attached images)

        Diagnostic information:
        - AMI connection is persistent (confirmed via "manager show connected")
        - AMI user has full read/write permissions: system, call, log, verbose, command, agent, user, dtmf, originate, cdr
        - Dialout Channel: PJSIP/###
        - Dial Context: from-internal
        - Automatically save a call: Yes
        - Display call notifications: enabled for both users

        Could you please advise on whether these are known limitations, configuration issues on my side, or bugs? I'm particularly interested in Issues 1, 2 and 4, as incoming call popups and the ability to associate calls with CRM records via the popup are essential for the demo we are creating for our client.

        Thank you for your help.

        Best regards,
        Ioannis
        Attached Files

        Comment

        Working...