ExceptionError on trying to delete extension or exporting extensions via Bulk Handler

General Help
,
#1

This is on Asterisk 13 and FreePBX 13.

There are two errors I have started facing, likely after upgrading to Voicemail 13.0.59.3 (I am not sure and it may just be coincidence that there is an aliases related fix in 13.0.59.2. Not sure if it broke some compatibility)

The behaviour gets exposed when after upgrade to Voicemail 13.0.59.3, I try to do one of the following:

1) After importing extensions, and then try to export the extensions csv file via Bulk Handler. I get a Whoops\Exception “Cannot unset string offsets” (picture enclosed) in voicemail.class.php. On closer look I find that in voicemail.conf, under general settings, this new line is getting added post the upgrade “aliasescontext=pbxaliases”, and all extensions being added as “[email protected][email protected]” under a new context [pbxaliases]. If I delete the context and the newly added line “aliasescontext=pbxaliases”, then I am able to successfully export without exception error.

FreePBX-voicemail-exception-1
FreePBX-voicemail-exception-11280×643 133 KB

2) Remove one or more extensions from Extensions page, I get Whoops\Exception undefined variable var (picture enclosed). Unable to work around this one - when I am required to bulk remove say 100 extensions. However, if I edit the extension and then click Delete from the edit page, then it removes the extension without throwing any exception.

FreePBX-voicemail-exception-2
FreePBX-voicemail-exception-21280×277 112 KB

After two days of debugging, I am yet to find the root cause though it does seem to point towards the voicemail module and the handling of aliases. Looked at app_voicemail.c but not very sure how the aliasescontext is being handled and if anything has changed recently.

Here’s what I am trying to do - please review and point if I am doing or expecting something incorrect.

We ship our box with predefined extensions and users 200-299. Some clients want a different numbering scheme, in which case, we export out the extensions csv, then we delete 2XX series, then import back with new numbering scheme. This was working as expected until we recently upgraded about 39 packages, including the Voicemail 13.0.59.3.

Appreciate any help please. Thanks.

Regards,
Rohit

#2

Hi @rohitg76,

It’s known issue. Please watch for this bug (https://issues.freepbx.org/browse/FREEPBX-19924)
to know the fix release.

#3

Hi @mmishra:

Are both the issues reported in my note related? I see mention of bulk handler in the issue #19924 but not the extension removal from extensions module throwing an exception. I suspect both may be related.

Thanks for the prompt acknowledgement.

#4

Mohit @mmishra, can you please advise which version of Voicemail or any other package introduced this issue and reverting back to which version may help avoid it? Thanks.

#5

Hello @rohitg76,

Please try with latest release(Voicemail v13.0.59.5). I hope it will resolve your issue.

Thanks

#6

Hi Mohit @mmishra, applied the 13.0.59.5 package. It resolved the bulk handler issue but did not fix the other exception error that I got when removing the extension from the extension module. Please look into that too. Thank you for the prompt action!

#7

Hi @rohitg76,

Please update the framework to latest release. It will resolve your second issue.

Thanks

#8

Thank you @mmishra, updating to the top of the trunk framework package resolved the other exception too. Thanks for the prompt fixes.

#9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.