OXO - more than 8 digits, NMT

[lbanias]

I have to configure the public numbering plan with more than 8 digits received from ISDN public network provider (10 digits - 02xxxxxxxx and 03xxxxxxxx) and I am nor sure how the DDI Number Modification Table translates the number. Strange thing, the technical documentation or the OXO training docs does not explain this. I wonder, when the call come in with 10 digits, where it is analyzed first in the public numbering plan (does not know more than 8 digits) or in the DDI Number Modification Table (more likely, but there is a limitation of only 16 entries). And , I'm not sure how is composed the CLI for an outgoing call, it reads again the DDI NMT ? So, the question is how can be configured DDi numbers with more than 10 digits? Or, should I choose an OXE for that ?

[lbanias]

No one had this problem before? I know that usually you get DDI numbers with the last 3 or 4 digit fron the complete number, but there are sometimes situations when the provider gives you the whole number.

[giovanni.attolini]

Have you tried include number prefix on Numbering -> Installation Numbers -> Installation Number field?
If you receive 1122223333 from public network, include in this field 112222, so you can work with 3333 on Numbering -> Numbering Plans -> Plubic Numbering Plan.

[lbanias]

The second digit is the first different digit from all the 10 digit received: I have 02 11112222 and 03 11112222 in from the provider, so if I enter 0 at installation number I cannot create the rest of the 9 ddi numbers in the public numbering plan. I cannot have 2 installation numbers, as well I cannot route twice 2222 as ddi.

[haroun]

a diffrent question : why such as numbering plan range , 8 digits are much enough are you second opeartor! .
from 0200000000 to 0299999999 do you know how many number have :10.000.000(10 million) possibilities how much have you payed for this range!?
if you you're operator, or you would keep the 8digits did i will suggeste to have OXE .

[lbanias]

02xxxxxxxx are ported fron one provider to another provider and this provider is forced to keep the number unchanged. Imagine this number being a public number of a well known company that does not want to change it for the sake of customer comfort but it only changes the provider.

[haroun]

hum operator class, so you have to use oxe witch offers more feature on isdn
i remenber i have got a carrier ask for sending whole installation +sup or installation +did (not only did) ,
so with entity or npd management you can got what you want even use of personal number ( test it with a non legal number and has worked)

[tot3nkopf]

You could declare one of the providers as private trunk and the other public: private installation number and public installation number available (depends on the use of accounting)
You can also use and play with alternative CLIP/COLP (user level, trunk level/system level and the priorities between them.
You could also use as you stated the DDI modification table as stated by Giovanni.

Regards,
Bogdan

[Pledd74]

I am not sure if you have solved this case?
But you can also use ARS to solve this incoming routing of number series more then 8 digits.

I have done this today with luck. I have one range with 8 digits from Singapore, and one range with 10 digits from USA.
My problem is to solve the outgoing CLIP, when internal telephones uses the USA range.

[Krusty65]

This can be done using the DDI Number modification table in the OxO, but I have to admit that the documentation really does not explain it very well

For this I have used the following numbers (I hope that this fits with the original intent of the question)

Range 1 0288881100-1199
Range 2 0388881100-1199

In the installation number leave it with just the defaults.

Create 2 entries in the DDI Number Modification Table
Index 1 External DDI number 02888811 Internal DDI number 888811
Index 2 External DDI number 03888811 Internal DDI number 777711

Then do your numbering plan as you see fit.

I have uploaded a pdf with screen shots that makes it easier to see.

OxO-DDI-NMT.pdf

K.