cancel
Showing results for 
Search instead for 
Did you mean: 

Overlapping PSTN ranges

Former Member
0 Kudos

Hi together,

I have a CCtr-setup with multiple PSTN-Gateways accross Europe where the last 2, 3 or 4 digits of the PSTN ranges will be equal.

1) Is it usefull to specify the PSTN range in E.164 Format? E.g. for the 3 digit PSTN ranges "+4912345000-+4912345999, +414567000-+414567999".

In this case I have to add the new PSTN range value in IA everytime the customer is opening a new location.

2) Setting the whole E.164 range +0000000000000-+9999999999999 in IA.

This setting is prefered in my case from the SAP guys in Finnland (except the leading "+").

But what about the locations that only have a 7 or 8 digits number? Are they covered as well or do I need to specify all possible lengths that the customer might have?

3) Setting "0-9,00-99,000-999,0000-9999" in IA.

This way every PSTN-number is covered.

Outbound calls will be directed to the right PSTN Gateway by "Location Based Routing".

In case 1+2 all internal numbers would be > 13 digits.

How do you setup the PSTN ranges in IA in case of multiple locations?

THANKS!

BR,

Robert

System will be 7.0 SP8

Accepted Solutions (1)

Accepted Solutions (1)

former_member203097
Active Participant
0 Kudos

Hello Robert,

Full E.164 is supported in PSTN range. In case your PSTN range is between 0000000000000-9999999999999, the shorter numbers are not covered. If you set it to 0-9999999999999, you will cover all possible numbers. Note that even leaving the PSTN range field empty would do the same thing.

The purpose of the range(s) is that you can allocate very specific number range(s) in SC to be administered by different administrators. If you have allowed all numbers, the administrators can accidentally use a number which does not fit their real PSTN number range. Typically, the telephone operators will just block calls coming from such number.

Kind Regards,

Tomi

Former Member
0 Kudos

Hi Tomi,

thanks for this explanations. This helps a lot.

Best regards,
Robert

Answers (0)