Hi experts,

We used to have a number plan to transform particular numbers via designated trunks:

Site Number Plan:

• Match Expression: (tel:)(7)(\+)(.*)
• Normalized Number Expression: $3$4

Put sending fax to address "7+12049840418" It would successfully transform the call from tel:7+12049840418 to tel:+12049840418

However user faced issue to send fax recently and we found it returned failed because matched number plan not found. And the DNIS showed up is tel:+7+12049840418

We are not sure if anything changed behind the scene. So we updated the expression to (tel:)(\+7)(\+)(.*) too but it's still not matching. We opened a case and customer care said no "+" should be inserted inbetween the numbers and DNIS should be E164 format.

We adjusted the expression to below and it works too:

• Input: 77712132942943
• Match Expression: (777)(.*)
• Normalized Number Expression: +$2
• Normalized Calling Address is tel:+12132942943 as we expected. 

So input for none E164 is working fine before regular expression kicks in, but maybe "+" is not allowed now in between the number?

To my understand, we can allow any digital input format in the interface as long as the interface doesn't reject, and we have the chance to convert it to correct E164 format after site/trunk transforming via normalized number expression. Is that correct understanding or something has changed? 

Thanks for any insight if anyone face the same issue recently.

Dylan

#Telephony

------------------------------
Dylan Jiang
Lightspeed Commerce Inc.
------------------------------

Hi Dylan,

I am not sure what is asked here. :-) There has been nothing in the release notes about this topic for a long time (at least, I'm unaware of it :-) ) . 

As for Match Expression for 2 examples with/without leading "+" followed by 7 and number in E164, can you try this  (tel:)(\+7|\b7)(\+)(.*) 

------------------------------
Tatjana Knezevic

www.startelecom.cloud

https://www.linkedin.com/company/star-telecom-www-startelecom-ca-/
------------------------------

Original Message:
Sent: 06-26-2024 21:57
From: Dylan Jiang
Subject: Site Number Plan Transform

Hi experts,

We used to have a number plan to transform particular numbers via designated trunks:

Site Number Plan:

• Match Expression: (tel:)(7)(\+)(.*)
• Normalized Number Expression: $3$4

Put sending fax to address "7+12049840418" It would successfully transform the call from tel:7+12049840418 to tel:+12049840418

However user faced issue to send fax recently and we found it returned failed because matched number plan not found. And the DNIS showed up is tel:+7+12049840418

We are not sure if anything changed behind the scene. So we updated the expression to (tel:)(\+7)(\+)(.*) too but it's still not matching. We opened a case and customer care said no "+" should be inserted inbetween the numbers and DNIS should be E164 format.

We adjusted the expression to below and it works too:

• Input: 77712132942943
• Match Expression: (777)(.*)
• Normalized Number Expression: +$2
• Normalized Calling Address is tel:+12132942943 as we expected. 

So input for none E164 is working fine before regular expression kicks in, but maybe "+" is not allowed now in between the number?

To my understand, we can allow any digital input format in the interface as long as the interface doesn't reject, and we have the chance to convert it to correct E164 format after site/trunk transforming via normalized number expression. Is that correct understanding or something has changed? 

Thanks for any insight if anyone face the same issue recently.

Dylan

#Telephony

------------------------------
Dylan Jiang
Lightspeed Commerce Inc.
------------------------------