Genesys Cloud - Main

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

Kent,

I suspect that this is more of a "heads up, this might happen" than a "if you want to set it up, you can make it do this".

I know PureConnect used to run through the Dial Plan multiple times, and many of the original documentation team came over from that product. It could be that either they were stuck in old habits, or that the product did that (or maybe still does, in some cases) which prompted that comment.

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

Thanks Paul. I suspect you're probably right on this but would be handy to standardize all non E.164 dialed numbers to E.164 and pass them through again because I don't see how the Match Type of "E.164 Number List" is useful if the user can just dial the number as 10-Digit and bypass the E.164 Number Plan Entry. Or maybe there needs to be a Match Type of "10-Digit Number List" or something?  IDK, I have a few other ideas as to how to address this as well lol

I do appreciate your response!

Kent,

I suspect that this is more of a "heads up, this might happen" than a "if you want to set it up, you can make it do this".

I know PureConnect used to run through the Dial Plan multiple times, and many of the original documentation team came over from that product. It could be that either they were stuck in old habits, or that the product did that (or maybe still does, in some cases) which prompted that comment.

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

You are welcome.

Another approach (which may be hugely unpopular) if this is a serious problem, is to use a RegEx entry to block all non-E.164 numbers and mandate everyone dials using E.164?

That would be crazy drastic, though! I like Vaun's idea...

Thanks Paul. I suspect you're probably right on this but would be handy to standardize all non E.164 dialed numbers to E.164 and pass them through again because I don't see how the Match Type of "E.164 Number List" is useful if the user can just dial the number as 10-Digit and bypass the E.164 Number Plan Entry. Or maybe there needs to be a Match Type of "10-Digit Number List" or something?  IDK, I have a few other ideas as to how to address this as well lol

I do appreciate your response!

Kent,

I suspect that this is more of a "heads up, this might happen" than a "if you want to set it up, you can make it do this".

I know PureConnect used to run through the Dial Plan multiple times, and many of the original documentation team came over from that product. It could be that either they were stuck in old habits, or that the product did that (or maybe still does, in some cases) which prompted that comment.

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

Agreed, that would be drastic but would resolve the issue :)

I also agree that I like Vaun's idea and I have actually already created the Number Range/Call Flow and it actually works better than using the Number Plan as I can play the caller a custom message as to why the call didn't proceed.

The only thing I don't like is that I have to create a separate number range for each number as they are not in sequential order (different numbers all together).  Also I think this will impact inbound calls from these numbers too which really isn't the objective, just wanted to block outbound calls.

You are welcome.

Another approach (which may be hugely unpopular) if this is a serious problem, is to use a RegEx entry to block all non-E.164 numbers and mandate everyone dials using E.164?

That would be crazy drastic, though! I like Vaun's idea...

Thanks Paul. I suspect you're probably right on this but would be handy to standardize all non E.164 dialed numbers to E.164 and pass them through again because I don't see how the Match Type of "E.164 Number List" is useful if the user can just dial the number as 10-Digit and bypass the E.164 Number Plan Entry. Or maybe there needs to be a Match Type of "10-Digit Number List" or something?  IDK, I have a few other ideas as to how to address this as well lol

I do appreciate your response!

Kent,

I suspect that this is more of a "heads up, this might happen" than a "if you want to set it up, you can make it do this".

I know PureConnect used to run through the Dial Plan multiple times, and many of the original documentation team came over from that product. It could be that either they were stuck in old habits, or that the product did that (or maybe still does, in some cases) which prompted that comment.

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

It shouldn't impact calls from those numbers.

Since they are not your numbers, nobody outside your ORG would reach you by dialing them. The call routing uses DNIS not ANI, so calls from those numbers would not be set to the flow.

Agreed, that would be drastic but would resolve the issue :)

I also agree that I like Vaun's idea and I have actually already created the Number Range/Call Flow and it actually works better than using the Number Plan as I can play the caller a custom message as to why the call didn't proceed.

The only thing I don't like is that I have to create a separate number range for each number as they are not in sequential order (different numbers all together).  Also I think this will impact inbound calls from these numbers too which really isn't the objective, just wanted to block outbound calls.

You are welcome.

Another approach (which may be hugely unpopular) if this is a serious problem, is to use a RegEx entry to block all non-E.164 numbers and mandate everyone dials using E.164?

That would be crazy drastic, though! I like Vaun's idea...

Thanks Paul. I suspect you're probably right on this but would be handy to standardize all non E.164 dialed numbers to E.164 and pass them through again because I don't see how the Match Type of "E.164 Number List" is useful if the user can just dial the number as 10-Digit and bypass the E.164 Number Plan Entry. Or maybe there needs to be a Match Type of "10-Digit Number List" or something?  IDK, I have a few other ideas as to how to address this as well lol

I do appreciate your response!

Kent,

I suspect that this is more of a "heads up, this might happen" than a "if you want to set it up, you can make it do this".

I know PureConnect used to run through the Dial Plan multiple times, and many of the original documentation team came over from that product. It could be that either they were stuck in old habits, or that the product did that (or maybe still does, in some cases) which prompted that comment.

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent

Ah, yes, you're right, that makes perfect sense.  Have a great weekend and thanks for the clarification on inbound calls associated to that Call Route.

It shouldn't impact calls from those numbers.

Since they are not your numbers, nobody outside your ORG would reach you by dialing them. The call routing uses DNIS not ANI, so calls from those numbers would not be set to the flow.

Agreed, that would be drastic but would resolve the issue :)

I also agree that I like Vaun's idea and I have actually already created the Number Range/Call Flow and it actually works better than using the Number Plan as I can play the caller a custom message as to why the call didn't proceed.

The only thing I don't like is that I have to create a separate number range for each number as they are not in sequential order (different numbers all together).  Also I think this will impact inbound calls from these numbers too which really isn't the objective, just wanted to block outbound calls.

You are welcome.

Another approach (which may be hugely unpopular) if this is a serious problem, is to use a RegEx entry to block all non-E.164 numbers and mandate everyone dials using E.164?

That would be crazy drastic, though! I like Vaun's idea...

Thanks Paul. I suspect you're probably right on this but would be handy to standardize all non E.164 dialed numbers to E.164 and pass them through again because I don't see how the Match Type of "E.164 Number List" is useful if the user can just dial the number as 10-Digit and bypass the E.164 Number Plan Entry. Or maybe there needs to be a Match Type of "10-Digit Number List" or something?  IDK, I have a few other ideas as to how to address this as well lol

I do appreciate your response!

Kent,

I suspect that this is more of a "heads up, this might happen" than a "if you want to set it up, you can make it do this".

I know PureConnect used to run through the Dial Plan multiple times, and many of the original documentation team came over from that product. It could be that either they were stuck in old habits, or that the product did that (or maybe still does, in some cases) which prompted that comment.

Thanks Vaun, that's a good idea and I had considered some type of action like this and then when researching, I came across this documentation on the Resource Center but couldn't figure out how to make it work :) Thank you for the suggestion!

"Numbers can be run through number plan and normalized multiple times"

Another way I've done this is by way of call routing/flows.  Add the #s you don't want people to call into a DID range in Cloud, assign them to a call routing configuration which includes an Architect Flow that just rejects/disconnects the call.  That way you also have an additional way to report on these calls.

Hi I am new to Genesys Cloud and I'm setting up the number plan. I have a list of phone numbers that need to be blocked from being called outbound. I have created a new number plan entry called "Blocked Number" using Match Type "E.164 List", Classification as "Restricted" and then I placed a couple E.164 formatted numbers in the list.  This works if you Dial the number as E.164 but if you dial the number as 10-digits, it obviously doesn't meet the match condition and the call is allowed to go through. 

Is there a way to standardize all outbound calls to E.164 and then pass them back through the number plan for reprocessing?

Thanks,

Kent