AS a Silver partner we cannot request changes.
I also realize this may be more a of a north American request, but it it is 100% a user friendly request!!
So I am posting this here to see a) if there is a fix or b) if someone can request for us!
Scenario:
Client has/had 365 sync enabled.
Client uses central email signature tool (like exclaimer) that pulls information from active directory including cellular number.
numbers in are often delimited by spaces, dashes or dots. eg 555-321-9876, 555.321.9876, 555 321 9876 looks nice and is easy to read- for sake of clarity and as this field is pulled for the email signature is formatted for humans. I will call this "human formatted"( vs just formatted as e164 is technically the RIGHT format!!! )
3cx however does not route calls to mobile devices unless it has is 100% numbers in that field eg mobile number needs to be 5553219876.
Dialing an extension directly has has call forward to mobile enabled and a "human formatted number" results in a voice message saying "could not route call" Cool. issue is the CALL log reports the call as "unanswered".
Where this becomes an issue, is if that extension(s) is in a queue and have "ring my mobile " or have forwarding to mobile enabled, the caller does not get the "could not route call "message and the call log reports the call as unanswered.
I'd like to propose 2 things:
1. Have an option to format mobile numbers on the user interface /phone book in the format that humans like, but keep the stored number in format that 3cx will dial/sms (e164)
OR
Have 3cx perform a regex on the mobile number to remove errant characters to ensure it is e164 formatted
2. Update the call log to state "could not route" vs Not Answered
I also realize this may be more a of a north American request, but it it is 100% a user friendly request!!
So I am posting this here to see a) if there is a fix or b) if someone can request for us!
Scenario:
Client has/had 365 sync enabled.
Client uses central email signature tool (like exclaimer) that pulls information from active directory including cellular number.
numbers in are often delimited by spaces, dashes or dots. eg 555-321-9876, 555.321.9876, 555 321 9876 looks nice and is easy to read- for sake of clarity and as this field is pulled for the email signature is formatted for humans. I will call this "human formatted"( vs just formatted as e164 is technically the RIGHT format!!! )
3cx however does not route calls to mobile devices unless it has is 100% numbers in that field eg mobile number needs to be 5553219876.
Dialing an extension directly has has call forward to mobile enabled and a "human formatted number" results in a voice message saying "could not route call" Cool. issue is the CALL log reports the call as "unanswered".
Where this becomes an issue, is if that extension(s) is in a queue and have "ring my mobile " or have forwarding to mobile enabled, the caller does not get the "could not route call "message and the call log reports the call as unanswered.
I'd like to propose 2 things:
1. Have an option to format mobile numbers on the user interface /phone book in the format that humans like, but keep the stored number in format that 3cx will dial/sms (e164)
OR
Have 3cx perform a regex on the mobile number to remove errant characters to ensure it is e164 formatted
2. Update the call log to state "could not route" vs Not Answered
