- Joined
- Sep 17, 2021
- Messages
- 89
- Reaction score
- 109
I would like to propose an improvement to the Microsoft 365 integration regarding contact and user synchronization.
Currently, the synchronization with the phone directory and users appears to be key-sensitive. Since Microsoft 365 often provides contact data containing spaces or special characters — including extension and mobile number fields — this can occasionally lead to matching and routing issues within the PBX.
It would be very helpful to introduce an automatic normalization process during synchronization. For example, the system could automatically remove spaces, brackets, hyphens, and other special characters from phone numbers before storing or processing them.
At the moment, when the M365 sync imports numbers in formats such as +1 (1234) 12345 or +1 1234-12345, the PBX may fail to correctly match or assign these numbers. A normalization step that consistently converts all numbers into a unified format (e.g., +1123412345) — regardless of how they are stored in the tenant — would significantly improve reliability.
Additionally, incorrectly formatted mobile numbers can cause problems when mobile phone signaling is enabled, potentially resulting in failed or dropped calls. Automatic number normalization could help prevent these issues.
Currently, the synchronization with the phone directory and users appears to be key-sensitive. Since Microsoft 365 often provides contact data containing spaces or special characters — including extension and mobile number fields — this can occasionally lead to matching and routing issues within the PBX.
It would be very helpful to introduce an automatic normalization process during synchronization. For example, the system could automatically remove spaces, brackets, hyphens, and other special characters from phone numbers before storing or processing them.
At the moment, when the M365 sync imports numbers in formats such as +1 (1234) 12345 or +1 1234-12345, the PBX may fail to correctly match or assign these numbers. A normalization step that consistently converts all numbers into a unified format (e.g., +1123412345) — regardless of how they are stored in the tenant — would significantly improve reliability.
Additionally, incorrectly formatted mobile numbers can cause problems when mobile phone signaling is enabled, potentially resulting in failed or dropped calls. Automatic number normalization could help prevent these issues.
Upvote
13
