All,

I have a case open since April or May of 2020.

Apparently, if you would like to route your calls using Call Handling, it does not work for t-mobile.

Example:

Call Handling 1: Zoom Application

Call Handling 2: T-Mobile

Call Handling 3: VoIP Phone

If someone calls my direct number (Zoom), it will ring Max 15 seconds then it will (or should) ring my t-mobile number. If I don't pick it up then it will ring my voip phone. That's how should it works.

Well...it does NOT work. After the Zoom app max ring time, it just skips Call Handling 2 and goes directly to Call Handling 3. It does not matter where I put my t-mobile in order using the Call Handling  feature - it just skips the t-mobile phone.

For months I've been going back and fourth with Zoom support and finally convinced the Zoom tech support to find co-workers who has t-mobile phones and use the Call Handling feature. He did and confirmed that there is an issue with t-mobile phone numbers. He had escalated the ticket # to the Telephony DevOps Team and we should hear back from them. Well...it has been 6 months already no update. Even though I've been having this problem since my company start using Zoom phone back in April of 2020.

Hopefully this post will catch someone's attention (Zoom) and push for this to be resolve.

In this page that explains Shared line groups the following 2 seemingly contradictory statements appear.  Can you confirm whether a user can be a member of more than 1 shared line group/call delegation ?

• Members are added to the shared line group by your Zoom Phone admin. Each member can only belong to one shared line group.
• Note: Each member can belong to multiple call delegation setups or shared line groups.

Thanks,

Simon

We went to rollout Zoom Phone to our first location today, was in the final testing and found that when we put a person on hold, put the handset back on the receiver the call would be disconnected.  This was tested during our initial testing, several versions ago and the call was not disconnected.

A call comes in and is answered by picking up the handset.  The call is put on hold by pressing the physical hold button on the phone or by pressing hold on the screen.  After this the handset is returned to the receiver and the call is immediately disconnected.

Another thing we noticed was when multiple calls come in.  A first call is put on hold, the handset is still off the hook, and a second call comes in.  After putting the second call on hold, when the handset is returned to the receiver, only the second call is disconnected.  The first call remained on hold without issue.

We are running a Yealink VP59 in Zoom Phone Appliance mode.  Version 5.9.3 (653)

Anyone else have this problem?  Maybe there is some setting that we missed?

Is there anyway to have the emergency services alerts follow the locations inside of the sites instead of the site, since locations are nomadic and are picked up by defining subnets or switch information?

Our issue is we have a lot of nomadic users that travel between states/cities and if they are assigned to a site for a location and go to another location out of state in a different building we want those email alerts to go to the front desk of the building they are in, not what is statically assigned to the site they are in, so we can comply with the new e911 regulations.