Updating voicemail via *97 calls ends with busy signal

Reporting an Issue
1
  • When updating voicemail via *97 and someone reaches the updated voicemail they hear a busy signal instead of the custom recording.
  • I see the 3 .wav files in the voicemail folder with the correct asterisk permissions.
  • in the logs, I see Trunk Hangup
  • When deleting the ext folder under voicemail and rebooting the PBX all is good
  • I tried twice and the same thing happened
  • I’m running Asterisk 18.10.0 VitalPBX 3.1.7-1

Anyone can try this on their PBX running the same version and reply here if they have the same issue.

Thank you.

2

A call trace could help!

When you say “Updating Voicemail,” do you mean setting up the Voicemail for the first time?

3

Setting up the Voicemail for the first time.

See call trace

 -- PJSIP/5333-000000ab connected line has changed. Saving it until answer for PJSIP/PBX-trunk-000000a9
    -- PJSIP/5333-000000aa connected line has changed. Saving it until answer for PJSIP/PBX-trunk-000000a9
    -- PJSIP/5333-000000aa is ringing
    -- PJSIP/5333-000000ab is ringing
  == Spawn extension (sub-local-dialing, 5333, 50) exited non-zero on 'PJSIP/PBX-trunk-000000a9'
    -- Executing [h@sub-local-dialing:1] NoOp("PJSIP/PBX-trunk-000000a9", "Finishing the call") in new stack
    -- Executing [h@sub-local-dialing:2] Gosub("PJSIP/PBX-trunk-000000a9", "sub-udpate-virtual-dev-state,s,1(5333,NOT_INUSE)") in new stack
    -- Executing [s@sub-udpate-virtual-dev-state:1] NoOp("PJSIP/PBX-trunk-000000a9", "Update Virtual Devices State") in new stack
    -- Executing [s@sub-udpate-virtual-dev-state:2] Set("PJSIP/PBX-trunk-000000a9", "EXT_NUM=5333") in new stack
    -- Executing [s@sub-udpate-virtual-dev-state:3] Set("PJSIP/PBX-trunk-000000a9", "NEW_STATUS=NOT_INUSE") in new stack
    -- Executing [s@sub-udpate-virtual-dev-state:4] Set("PJSIP/PBX-trunk-000000a9", "EXTENSION_ID=15") in new stack
       > Found no rows [SELECT `device_id` FROM ombu_devices WHERE extension_id='15' and technology='virtual' and tenant_id=(SELECT tenant_id from ombu_tenants WHERE path='58deec75c59ab8e3')]
    -- Executing [s@sub-udpate-virtual-dev-state:5] Set("PJSIP/PBX-trunk-000000a9", "ODBC_ID=") in new stack
    -- Executing [s@sub-udpate-virtual-dev-state:6] GotoIf("PJSIP/PBX-trunk-000000a9", "1?no_rows") in new stack
    -- Goto (sub-udpate-virtual-dev-state,s,14)
    -- Executing [s@sub-udpate-virtual-dev-state:14] Return("PJSIP/PBX-trunk-000000a9", "") in new stack
    -- Executing [h@sub-local-dialing:3] GosubIf("PJSIP/PBX-trunk-000000a9", "0?dynamic-routing-connected,s,1(CANCEL,XXXXXXXXXX)") in new stack
    -- Executing [h@sub-local-dialing:4] GotoIf("PJSIP/PBX-trunk-000000a9", "0?call_ended") in new stack
    -- Executing [h@sub-local-dialing:5] GosubIf("PJSIP/PBX-trunk-000000a9", "0?wake-up-no-answered,s,1") in new stack
    -- Executing [h@sub-local-dialing:6] Gosub("PJSIP/PBX-trunk-000000a9", "sub-call-completion-check,s,1") in new stack
    -- Executing [s@sub-call-completion-check:1] NoOp("PJSIP/PBX-trunk-000000a9", "FEATURE: CALL COMPLETION CHECK") in new stack
    -- Executing [s@sub-call-completion-check:2] Set("PJSIP/PBX-trunk-000000a9", "CC_MODE=none") in new stack
    -- Executing [s@sub-call-completion-check:3] Set("PJSIP/PBX-trunk-000000a9", "CC_MODE=none") in new stack
    -- Executing [s@sub-call-completion-check:4] Set("PJSIP/PBX-trunk-000000a9", "CC_MODE=none") in new stack
    -- Executing [s@sub-call-completion-check:5] GotoIf("PJSIP/PBX-trunk-000000a9", "1?end") in new stack
    -- Goto (sub-call-completion-check,s,17)
    -- Executing [s@sub-call-completion-check:17] Return("PJSIP/PBX-trunk-000000a9", "") in new stack
    -- Executing [h@sub-local-dialing:7] NoOp("PJSIP/PBX-trunk-000000a9", "Call ended") in new stack
    -- Executing [h@sub-local-dialing:8] Gosub("PJSIP/PBX-trunk-000000a9", "notify-call-hangup,s,1") in new stack
    -- Executing [s@notify-call-hangup:1] Verbose("PJSIP/EPBX-trunk-000000a9", "0, Extension Hangup") in new stack
 Extension Hangup
    -- Executing [s@notify-call-hangup:2] GotoIf("PJSIP/PBX-trunk-000000a9", "0?:incoming") in new stack
    -- Goto (notify-call-hangup,s,5)
    -- Executing [s@notify-call-hangup:5] Verbose("PJSIP/PBX-trunk-000000a9", "0, Extension Hangup - Incoming Call") in new stack
 Extension Hangup - Incoming Call
    -- Executing [s@notify-call-hangup:6] UserEvent("PJSIP/PBX-trunk-000000a9", ""EXTENSIONS_SUMMARY","Data: INCOMING,XXXXXXXXXX,,IN"") in new stack
    -- Executing [s@notify-call-hangup:7] Return("PJSIP/PBX-trunk-000000a9", "") in new stack
    -- Executing [h@sub-local-dialing:9] Hangup("PJSIP/PBX-trunk-000000a9", "") in new stack
  == Spawn extension (sub-local-dialing, h, 9) exited non-zero on 'PJSIP/PBX-trunk-000000a9'
4

This is a partial call trace. Please grab a full call trace and post it via pastebin.com

5

I tried setting up the voicemail on another VitalPBX system and I don’t have this issue.

What is the recommended way to repair VitalPBX?

6

We have no idea what’s wrong. Please share a full call trace via pastebin

7

Check the FAQ section here. For example:

1 Like
8

@techisnumberone

did this really help you fix the issue?

9

I clicked Solution by mistake.

It’s bizarre as I can’t reproduce the issue now.
I could reproduce the issue from the Vitalpbx mobile app on one PBX (I thought I figured it out), but now I can’t generate the problem.
I guess ill reply if it happens again.

Thanks all for your help