Genesys Cloud - Main

Hi Everyone,

We have a BYOC trunk configured as . On incoming calls, the customer is sending the DNIS in the Request-Line as follows:

INVITE sip:+TQ55005P1N11234567890@TG100-EQS.byoc.usw2.pure.cloud SIP/2.0
In Sites > Number Plan, I've configured the following:

Match Expression (Regex): \+TQ55005P1N11234567890

Normalized Number Expression: +11111155001

However, on incoming calls to this DNIS, the platform is responding with a 404 (Not Found), and the caller hears the message "the party is not answering."

Could you please help confirm why the regex match isn't triggering as expected? Is there any adjustment needed in the regex pattern or normalization configuration to properly match this DNIS format?

#PlatformAdministration
#Routing(ACD/IVR)
#SystemAdministration

------------------------------
Karthik Ageer
------------------------------

What are you seeing in the simulate call as the expression you mention yields normalised address of: 

sip:+11111155001@TG100-EQS.byoc.usw2.pure.cloud

Is that what you expected ?

Not much of a regex person but if you looking for the number you can try something like

^([^@\:]TQ55005P1N11234567890@)([^@ ]+)?$

for tel:+11111155001

Simulate call is your friend here.

Hi Everyone,

We have a BYOC trunk configured as . On incoming calls, the customer is sending the DNIS in the Request-Line as follows:

INVITE sip:+TQ55005P1N11234567890@TG100-EQS.byoc.usw2.pure.cloud SIP/2.0
In Sites > Number Plan, I've configured the following:

Match Expression (Regex): \+TQ55005P1N11234567890

Normalized Number Expression: +11111155001

However, on incoming calls to this DNIS, the platform is responding with a 404 (Not Found), and the caller hears the message "the party is not answering."

Could you please help confirm why the regex match isn't triggering as expected? Is there any adjustment needed in the regex pattern or normalization configuration to properly match this DNIS format?