If people are walking around the facility while making VoIP calls then you will should always have roaming. As they move further from the original access point they will eventually switch to a new access point - this is perfectly normal and is how wireless should work.
As @cmr states, in NAT mode with Meraki DHCP as you currently have, the access point is changing the source IP address of the wireless device from whatever it is on the wireless network to the IP address of the access point. In this mode when you roam this NAT changes since you're using a different access point with a different IP address. This will potentially cause a gap in the audio.
Using bridge mode the client keeps its IP address (which is issued by a DHCP server somewhere else on your network) and uses well known protocols to transition from one access point to the other, ensuring this is a fast transition and that you don't get any packet loss - so maintaining the packet flow and giving a much better experience to the user.
Like @RupertDot11 states, I'd also be concerned about the height of the access points. At 15m you'd really want to make sure that your wireless site survey was done to take this into account. At 15m, you're losing around 60dB on your signal between the AP and the floor, and if your APs are set for Auto Power management then they may be 'seeing' each other better than the clients and so winding their power back (do you know the maximum power of the radios in the client devices?). This doesn't mean it can't work, you just need to make sure that the RF side has been engineered correctly.
I see you're also using the 2.4GHz spectrum too. This is often a noisy and over utilized spectrum, but I recognize this may be a limitation of the clients - the 5GHz may be better. You may find there is significant background noise that it causing problems. Again this is a RF engineering issue and you may need to get someone out on site to measure this with the correct tools.