Multi tenant voicemail issue

VitalPBX Community Support Reporting an Issue Multi tenant voicemail issue

  • Post
    Einm
    Participant
    Up
    0
    Down
    Hello,

    There is an issue with the voicemail passwords being reset in a multi tenant system, and after some troubleshooting we found the below,

    When you change your voicemail password by calling the voicemail (not in the GUI) it adds the new password value in the database ({TENANT}/extensions/${CALL_SOURCE}/vm_password) but it does not update the voicemail conf file, now when calling the voicemail again it will accept the new password, but if you apply config form the main tenant or run “vitalpbx dump-conf” it won’t accept the new password anymore, instead it will be reset to the password in the conf file which was never changed, although the database still has the new password, then, if you hang up before changing the password it will reset the password stored in the database to the password from the conf file (Priority 3 in h@sub-direct-voicemail), but if you apply changes from that tenant, or you run “vitalpbx fully-dump-conf” then it will update the password in the conf file to the new password,

    0
Viewing 7 replies - 1 through 7 (of 7 total)
  • Replies
    Up
    0
    Down
    Could you please specify the current version of your VitalPBX installation?
    0
    Einm
    Participant
    Up
    0
    Down
    3.0.8-1
    0
    Up
    0
    Down
    Could you share a call trace?
    0
    Einm
    Participant
    Up
    0
    Down
    It looks like the ODBC is being executed to update the password in the database.

    [2021-05-27 10:49:30] VERBOSE[68687][C-0000b08e] pbx.c: Executing [h@sub-direct-voicemail:3] Set("PJSIP/T23_501-00005ab3", "DB(b83bc4c395c31303/extensions/501/vm_password)=4321") in new stack
    [2021-05-27 10:49:30] VERBOSE[68687][C-0000b08e] pbx.c: Executing [h@sub-direct-voicemail:4] Set("PJSIP/T23_501-00005ab3", "ODBC_VOICEMAIL-PASSWORD(501,b83bc4c395c31303)=4321") in new stack

    We are going to check if the method “ODBC_VOICEMAIL-PASSWORD” is working or not.

    0
    PitzKey
    Participant
    US
    Up
    0
    Down
    Hi Jose,

    I am @einm’s colleague. I will elaborate on this….

    When we setup a new tenant extension, for example Ext 102 with VM password 102, the password is stored in the tenant’s voicemail conf file as well as in the Asterisk Database and once you reload asterisk, it is stored in memory.

    Now, when the new user changes their password to 1234, it gets updated in the asterisk DB and in memory, but NOT in the tenant’s voicemail conf file, in the conf file it is still 102.

    So, if you are on the main tenant and you do a reload which is essentially a vitalpbx dump-conf, it causes asterisk to read the conf file and set the voicemail password in memory to 102.

    Now, when the user calls their voicemail and enters the 1234 password, asterisk says that it wrong… And once the person hangs up, you guys read under the h@sub-direct-voicemail context the VM pass from ${VM_INFO} which takes the VM password from memory and then you store it in the Asterisk DB.

    Let me know if you have any questions

     

    Thank you

     

    0
    Up
    0
    Down
    The command:

    Set("PJSIP/T23_501-00005ab3", "ODBC_VOICEMAIL-PASSWORD(501,b83bc4c395c31303)=4321")

    It stores the password in the database; if you execute the script “vitalpbx –dump-conf” the information must be read from the database and generate the new password in the file.

    As I said before, we will do some tests about this.

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