After Update to new version 2.4.1-3 voicemail plays busy greeting when the phone is not in use

VitalPBX Community Support General Discussion After Update to new version 2.4.1-3 voicemail plays busy greeting when the phone is not in use

  • Post
    DannyLarsen
    Participant
    none

    After Update to new version 2.4.1-3 voicemail plays busy greeting when the phone is not in use on all extensions. Can you help. Thanks

    — Executing [s@sub-leave-vm:7] Gosub(“SIP/10-0000006b”, “sub-vm,s,1(19@vitalpbx-voicemail,bs)”) in new stack
    — Executing [s@sub-vm:1] NoOp(“SIP/10-0000006b”, “Leave a Voicemail”) in new stack
    — Executing [s@sub-vm:2] VoiceMail(“SIP/10-0000006b”, “19@vitalpbx-voicemail,bs”) in new stack
    — <SIP/10-0000006b> Playing ‘vm-theperson.ulaw’ (language ‘en’)
    > 0x7f4d5c0cac10 — Strict RTP learning complete – Locking on source address 192.168.0.233:50090
    — <SIP/10-0000006b> Playing ‘digits/1.ulaw’ (language ‘en’)
    — <SIP/10-0000006b> Playing ‘digits/9.ulaw’ (language ‘en’)
    — <SIP/10-0000006b> Playing ‘vm-isonphone.ulaw’ (language ‘en’)
    — <SIP/10-0000006b> Playing ‘beep.ulaw’ (language ‘en’)

    0
Viewing 15 replies - 1 through 15 (of 15 total)
  • Replies
    Up
    0
    Down

    Try regenerating the VitalPBX Configurations

    vitalpbx --dump-conf
    asterisk -rx"core reload"

    Also, make sure your extensions are reachable, and capable to receive calls, we’ve same version in the office without issues.

     

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    I have done both commands and the issue remains, if I do a sip show inuse the phones show not in use, also in testing if the phone is offline ( not registered ) and you call the extension it does go to the unavailable greeting. Its only after the phone has been rung but not answered that it goes to the busy greeting. Calls thru an IVR also go to the busy greeting on no answer. Calls that are specified to go to the Unavailable greeting thru a ring group or que etc do reach the correct greeting.

    0
    Up
    0
    Down

    That’s normal, if you don’t answer the call, must go to voicemail as normal.

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    No, idle phones should not go to the busy greeting

    I was just saying calls that are specified to a voicemail condition thru a ring group do play the unavailable greeting.

    0
    Up
    0
    Down

    May you describe the desired flow,

    So if the extension A calls to extension B, then, the extension B must play unavailable greetings if no answer?

    Actually the unavailable greetings is only played if the extension is disconnected or unreachable, otherwise, it plays the busy message

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    This is the problem: Extension A calls extension B, extension B does not answer but is NOT on the phone, the voicemail prompt plays ” the person at ext XX is on the phone” ( or the recorded Busy greeting}.

    Normal operation of this has always been to play the Unavailable Greeting

    Here is a trace in Ver 2.3.8-1   (playing the unavailable greeting as it should)

    — Executing [s@sub-leave-vm:7] Gosub(“SIP/212-00001ab6”, “sub-vm,s,1(211@vitalpbx-voicemail,us)“) in new stack
    — Executing [s@sub-vm:1] NoOp(“SIP/212-00001ab6”, “Leave a Voicemail”) in new stack
    — Executing [s@sub-vm:2] VoiceMail(“SIP/212-00001ab6”, “211@vitalpbx-voicemail,us“) in new stack
     — <SIP/212-00001ab8> Playing ‘vm-theperson.ulaw’ (language ‘en’)
    > 0x7fba6c05f110 — Strict RTP learning complete – Locking on source address XXXXXXXXXXX:50122
    — <SIP/212-00001ab8> Playing ‘digits/2.ulaw’ (language ‘en’)
    — <SIP/212-00001ab8> Playing ‘digits/1.ulaw’ (language ‘en’)
    — <SIP/212-00001ab8> Playing ‘digits/1.ulaw’ (language ‘en’)
    — <SIP/212-00001ab8> Playing ‘vm-isunavail.ulaw‘ (language ‘en’)
    — <SIP/212-00001ab8> Playing ‘beep.ulaw’ (language ‘en’)

     

    Now a trace of Ver 2.4.1.3 (playing the busy on the phone greeting when the phone is NOT in Use)

    — Executing [s@sub-leave-vm:7] Gosub(“SIP/10-000000bb”, “sub-vm,s,1(12@vitalpbx-voicemail,b)“) in new stack
    — Executing [s@sub-vm:1] NoOp(“SIP/10-000000bb”, “Leave a Voicemail”) in new stack
    — Executing [s@sub-vm:2] VoiceMail(“SIP/10-000000bb”, “12@vitalpbx-voicemail,b“) in new stack
    — <SIP/10-000000bb> Playing ‘vm-theperson.ulaw’ (language ‘en’)
    > 0x7f4d5c03d760 — Strict RTP learning complete – Locking on source address 192.168.0.233:50118
    — <SIP/10-000000bb> Playing ‘digits/1.ulaw’ (language ‘en’)
    — <SIP/10-000000bb> Playing ‘digits/2.ulaw’ (language ‘en’)
    — <SIP/10-000000bb> Playing ‘vm-isonphone.ulaw‘ (language ‘en’)

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    In further testing I see this issue started somewhere between 2.4.0-2 and 2.4.0-5

    0
    jrosetto
    Participant
    Up
    0
    Down

    @dannylarsen

    I seem to be having a similar issue.  Did you every find a resolution to this?

    0
    DannyLarsen
    Participant
    none
    Up
    0
    Down

    Anyone?

    0
    jrosetto
    Participant
    Up
    0
    Down

    Let me explain a little further.  I come from freepbx where the voicemail prompts are busy, unavail, no-msg, and instructions-only.  Usually when a call goes to a phone on freepbx and nobody is on the phone and the extension is available it plays by default “please leave a message for extension 101”.  Is there a way to make VitalPBX function in this same manor?

    0
    Up
    0
    Down

    You can modify the context sub-leave-vm on the file /etc/asterisk/ombutel/extensions__20-baseplan.conf

    You must change this line

     same => n,Set(VM_OPTIONS=${IF($[$["${CALL_STATUS}"="BUSY"]|$["${CALL_STATUS}"="NOANSWER"]]?b:u)})

    Whit this


    same => n,Set(VM_OPTIONS=${IF($["${CALL_STATUS}"="BUSY"]?b:u)})
    0
    jrosetto
    Participant
    Up
    0
    Down

    @ing-joserivera26

    Will this get overwritten when applying changes or upgading to a new version?  If so, is there a way to override it permanently? 

    0
    mo10
    Moderator
    none
    Up
    0
    Down
    Posted by: @jrosetto

    @ing-joserivera26

    Will this get overwritten when applying changes or upgading to a new version?  If so, is there a way to override it permanently? 

    Make a new file called:
    extensions__19-baseplan_change.conf

    and put all of this in:

    [sub-leave-vm]
    exten => s,1,NoOp(Leave Voicemail)
    same => n,Set(VM_OPTIONS=${IF($["${CALL_STATUS}"="BUSY"]?b:u)})
    same => n,Set(VM_OPTIONS=${IF($["${DB(${TENANT}/extensions/${CALL_DESTINATION}/skip_vm_instructions)}"="yes"]?${VM_OPTIONS}s:${VM_OPTIONS})})
    same => n,GotoIf($["${DB(${TENANT}/extensions/${CALL_DESTINATION}/vmenabled)}" = "yes"]?:vm_disabled)
    same => n,Set(MAILBOX=${DB(${TENANT}/extensions/${CALL_DESTINATION}/voicemail)})
    same => n,Answer()
    same => n,Gosub(sub-vm,s,1(${MAILBOX},${VM_OPTIONS}))
    same => n(vm_disabled),Return()

    This way your code will come first and you don’t have to edit anything inside original extensions__20-baseplan.conf

    0
    Up
    0
    Down

    Yes, all changes on file extensions__20-baseplan.conf are overwritten on each update. However, in the next update, the line that I have provided in the previous post will be the default behavior.

    same => n,Set(VM_OPTIONS=${IF($["${CALL_STATUS}"="BUSY"]?b:u)})
    0
    jrosetto
    Participant
    Up
    0
    Down

    @ing-joserivera26

    Just tested this and it is exactly what I was looking for.  Can’t wait for the update.

    Thanks.

    0
Viewing 15 replies - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.