App assigns wrong voicemail to a DID

[Andrew Webber]

I looked back and didn't see this discussed, sorry if it's already there.

I have several DIDs and for each I've created a Voicemail (just the default "the person at extension [DID #] ..."). There may be a better way to manage this, but that's a separate discussion. Each DID has the corresponding voicemail set as "Voicemail associated with DID" in the voip.ms website.

If I open a DID in the app and make any change to it,  the voicemail assigned (4th field, under POP) also changes. It appears to be changing to the last voicemail in the list, not sure if that's coincidence. Phoning the number confirms that incorrect voicemail is associated (the automated message reads the number, and if I leave a message the email says so too).

Once that's happened, the only way to make it right is through the website (very painful on my phone, not so bad on notebook), because changing the voicemail field seems to constitute a change, resulting in the same wrong voicemail being associated.

That was longer than I intended, I'll stop now but I'm happy to provide more details privately, and happy to troubleshoot.

[Andrew Webber]

Last week I had to edit a DID using the app (have been doing my best to avoid that) and it still changes the assigned vmail to last one on the list instead of the assigned one. Had to go into website to assign the correct vmail.

[jftess...@gmail.com]

I have the same problem.

8 DIDs and 7 voicemails.

Everytime I change any voicemail for any DID, it's always save with the wrong VM.

If I applied [None] as VM, it save ok.

[Andrew Webber]

Thanks for confirming it's not just me. :) Does it always apply the last VM on the list? Mine seems to. My DIDs are pretty low-volume, so I've usually got time to login to the website, check what the app did, and fix if necessary. But if it were higher-volume I'd probably create a new generic vmail and force it to be last on list, something like "thank you for calling, please leave a message and someone will reply as soon as possible" so that at least it doesn't fail-save to "the person at extension [wrong DID]..."

[jftess...@gmail.com]

Hello,

For your info, the problem still exist with version 1.0.149 pro.

Thank you for this great app.

Jf Tessier

[Andrew Webber]

FWIW, it's working for me now on 1.0.149 - Pro, build date 15-Mar-2022. 

Thanks.

[Jf Tessier]

Hello,

Sorry for the delays.

I've got no problem when I use a 10 digits VM within the VOIP website.

Validate with VOIP if 10 digits is possible

Step 0 - Version Check (1.0.149 - Pro)

Step 1 - Start With None

Step 2 - Test with 9 nine

Step 3 - Validation for 9 nine

Step 4 - Change to 10

Step 5 - Saving confirmation

Step 6 - Result is another VM

Hope it help

[Jf Tessier]

Version 1.0.151 - Pro work perfectly. Thanks a lot.