Import O365 users mobile # sanitizing

Status
Not open for further replies.

rogerfar

SOHO User
Joined
Feb 17, 2021
Messages
4
Reaction score
0
We use the Office365 sync and every night it imports / syncs users, it also syncs the Mobile field.

Issue is that the numbers aren't standard, some are 587-123-4567, some are +1 5791234567, so it's mixing spaces, dashes, plusses.

We have mobile phone fallback for all extensions and E164 processing enabled, but it fails when the user doesn't have a properly formatted number in the mobile field, the errors we're seeing are:

05/30/2023 9:56:42 AM - [CM303006]: There's no outbound rule for external number '+1 4031234567' defined
05/30/2023 9:56:42 AM - [Flow] Target endpoint for +1 4031234567 can not be built!
05/30/2023 9:56:42 AM - Call to T:Extn:101@[Dev:sip:[email protected]:5483;rinstance=88d0664b24e1b025] from L:307.1[Line:10001<<5878904770] failed, cause: Cause: 486 Busy Here/INVITE from 127.0.0.1:5483
05/30/2023 9:56:42 AM - [CM503003]: Call(C:307): Call to <sip:[email protected]:0> has failed; Cause: 486 Busy Here/INVITE from 127.0.0.1:5483
05/30/2023 9:56:42 AM - [Flow] Target endpoint for +1 4031234567 can not be built!

When I fix the number manually without the space, it's fine.

How do we santize the incoming numbers?

2nd problem, which I think is a much bigger bug, those extensions are set to do multi Ring my mobile simultaneously, but it won't ring the extension either, it will simply disconnect the call. To clarify, when I dial the extension 101 directly, or disable Ring my mobile simultaneously for that extension, it does work.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,832
Messages
589,284
Members
164,662
Latest member
DejanMDS