We are having an issue where we are getting an error when adding an international number to an existing call. We have a hosted (by an MSP) system. This is the pattern of my testing:
The following result in a 'false' error popup and the international call does not get added:
1) Call an internal number and try to add an international number.
2) Call an external local number and then try to add an international number.
3) Call and international number and try to add another international number.
The following tests worked with no error:
1) Call an international number and then add a local number
2) Call an international number and then add an internal number.
3) Any of the above tests, but instead of conferencing, we make a second call and then merge the two (not optimal).
We opened a ticket with Microsoft and they are saying this is by design and not a bug or misconfiguration. I have been unable to find any references to this limitation or any complaints about it online, so I am not convinced.
Do the first three scenarios work for others who use Teams with 3CX?
The following result in a 'false' error popup and the international call does not get added:
1) Call an internal number and try to add an international number.
2) Call an external local number and then try to add an international number.
3) Call and international number and try to add another international number.
The following tests worked with no error:
1) Call an international number and then add a local number
2) Call an international number and then add an internal number.
3) Any of the above tests, but instead of conferencing, we make a second call and then merge the two (not optimal).
We opened a ticket with Microsoft and they are saying this is by design and not a bug or misconfiguration. I have been unable to find any references to this limitation or any complaints about it online, so I am not convinced.
Do the first three scenarios work for others who use Teams with 3CX?
