Lag in button presses AFTER a call is in progress

Hi All,

[SEE UPDATE AT BOTTOM]

We are a school with Zoom VOIP phone service and a mix of Polycom VVX 311 and VVX 411 phones.  In one of our buildings, we perform intercom paging by calling into an Algo 8301 IP Paging Adapter which is paired to a Bogen PCM2000 zone paging system.  When the algo receives our call, it plays a chime to let us know it has answered.  We then need to press some buttons on our phone to signal to the PCM2000 which zone we would like to talk to.  For example, the button press we use most often is *01 to page to just our internal building speakers.

Our issue is that the button presses are very laggy when we do them from the Polycoms.  The tones don't come out right away and often come out in a burst all at once.  It doesn't matter how fast or slow we dial the sequence.  There's always an unpredictable timing to the tones coming out.  Because of that, we frequently need to try multiple times before the Bogen PCM2000 gets the signal and initiates the intercom page.

Two very important things to note about this situation: (1) we don't have this issue when calling into the Algo from the Zoom smartphone app, and (2) in another building of ours where we have the Algo but not the Bogen, we don't have this issue.

Based on the above, it's my assumption that the issue lies with how the Algo or the Polycom talks to the Bogen.  I know this is a long stretch, but I'm hoping someone might have a generic suggestion to resolve this like "Switch your DTMF detection type to X instead of Y."  Please let me know any ideas you might have.  Thank you!

[UPDATE] I think I've pinpointed exactly what's going on.  When we press the * key on our phones, a tiny menu appears suggesting symbols (similar to the old T9 style typing).  The suggestions in the menu are "* + , ; p".  No other key on the phone suggests options to you like that, including the # key.  It only happens on the * key.  Does anyone know how to tell the Polycoms not to do that when you press the * key?  I think that would solve our issue entirely.