IVR & Digit: * fail in V2

[Club de badminton Phoenix de Saint-Hubert]

Hi,

 I use many IVR with Responses and I use also the Digits: * 

I did a lot of testing.

Results:

- None of the IVR shows in V2.

-  "loading IVR" pop up screen without ending.

- Same results on new device without using backups. 

- The keyboard don't let you use the * or # in V2 for Digits.  The keyboard give option of 0 to 9 comma and dot.

- If there is only one Responses configured in IVR with Digit * in V1 then none of them will show in V2. 

Partial fix without digit * :

FROM V1:

 In IVR, if I replace ALL the Digits * by a number (0-9).  Then all my  IVRs will appear in V2.

If I put  back a digit * in ONE of them in V1 they will all disappear again in V2.

I hope you can fix that issue.

Martin

[Steve Punter]

Thanks for letting me know about this. A fix in the form of Build 3.0.3 has been uploaded to Google Play and should appear in the next hour or so.

[Steve Punter]

Unfortunately there is a bit of a gotcha with this recent issue. It turns out that the API does not allow the upload of an IVR with a # or * symbol as the response character. Even when I send back exactly the same data as I am getting from the server when the symbols are set up using the web portal, I get sent to an error which is wholly inappropriate for the problem. It’s giving me an error message related to creating a virtual DID, which strongly suggests there is a bug at their end that needs to be looked into.

I have posted a trouble ticket explaining the problem, and hopefully they will fix this shortly, though the speed at which they have been fixing issues of late has been rather dismal. For the time being the app will now successfully load an account with an IVR containing # or * symbols, but if you attempt to edit any of these IVRs and try to save them with a # or * still found in one or more of the responses, a message will pop up explaining why you can’t do this.

If you absolutely need a # or * in an IVR response, then for the time being you will have to edit it using the web portal. With any luck they will fix the API in short order and my app will be able to accommodate these symbols. 

[Club de badminton Phoenix de Saint-Hubert]

How come it's still working in V1. It does accept a new IVR with the * key.  Don't they use the same API. 

--
You received this message because you are subscribed to the Google Groups "VoIP.ms Console Support Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voip-ms-conso...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/voip-ms-console/8f5f6dbd-c135-4bb1-b005-20fb4cd548a4n%40googlegroups.com.

[Steve Punter]

It doesn't work in V1. I reinstalled V1 on my phone and tried to create an IVR with a response containing a # and *. I got the same error back from the VoIP.ms server.

[Club de badminton Phoenix de Saint-Hubert]

All my founding that I posted  was done by modifying on V1.  Without even logging once to the VoIP.ms portal.

Now, I did a new IVR with another Voip.ms account on V1. This time I check on Voip ms portal and it's on the portal. It's working and tested.

The phone I use for the test is clean and never had the lates version of your app.

When I wrote V1 in my posting . It meant using version 2.0.181 built date: 31-dec-2025 for the creation or modifications with * symbol.  It's an old Huawei P30 Android 10. Not even able to get the new version of your app from the store. Iqt's to old.  But still good for testing.

To view this discussion visit https://groups.google.com/d/msgid/voip-ms-console/25870106-3b1d-4cc4-b170-4de7ef84b392n%40googlegroups.com.

[Steve Punter]

I have gone ahead and posted 3.0.3 with the fix for LOADING IVRs, but I'll look more deeply into V1 being able to create IVRs with # and * responses. Can you give me a detailed description of how you created one of these IVRs using V1 so I can do exactly the same thing. Thanks in advance.