ABC-F over IP Network with duplicated numbers

[freedom]

I'm working on an ABC-F over IP network with two nodes.
In both nodes I have som extensions with the same number.
I didn't activate the broadcast to make sure no users will be unreachable.

I would like to use an open routing prefix to call from one node to another, but if I create the prefix I get an error: ‘OBJECT -1: Number: Invalid trunk group number’
I know for sure that the trunkgroup number is correct.

The hybrid link is working, the ip-trunks are configured and I have created the VPN overflow (manual created remote prefix because broadcast is off).

Even if I manaually create a network number for a user that only exsists in node 1, I'm not able to call it from node 2.

Now I have two questions:
* Does anyone know if it is possible to have an ABC network with overlapping internal numbers?
* Does anyone know if I should be able to use the open routing prefix within an ABC network? Or do I need an ABC-trunk between different subnetworks for that?

Node 1 is an OXE with release 8.0.1
Node 2 is on OXE with release 9.0

[knightr1der]

Even though you have not activated Broadcast, you should still have some elements audited like trunk groups and entities.

Otherwise, I see no reason why you cannot have same extension numbers in each node, but how will you call a number on the other node if the same number exists for a real user on your local node?

[freedom]

For calling from node 1 to node 2, I want to use a prefix e.g. 18000 to dial from node 2 to ext 8000 in node 1, and 28000 to call from node 1 to ext 8000 in node 2.
I tried to create an open routing prefix, but as mentioned befor, I receive an error if I fill in te IP-trunk number.

[vad]

Create this extension with numbers 1800 and 2800. In one network forbiden to use the same number (use ABC-F TG).

But if you need this - f.e. we have two users 800 (N1 and N2, netw=0). We solve problem with SD.
Create Speed dial 2800 (Node 2) with call number 800.
Create Network number 2800 (Node 1) network=0, node=2.

[freedom]

VAD, thank you for the speeddial solution.
Because we don't have a 2MB direct trunk between the two sites, it's not possible to use een ABC Trunk group connection.
Also the new feature, ABC trunk group over IP, that is available in release 9 will not work, because node 1 is in release 8.0.1.
And I would need a new license for this.

I will give the speed dial option a try.

Because I wasn't able to call an extension that only existed in one node, I'm not sure the network configuration is ok.
I created a network number by hand, but still received an error (please hang up) on an IPTouch when I tried to call this number.
With suproutage the link is ok (option 2), but saturated.
Normally, when you check the Hybrid (H) link, this should be available. But in this case it's also saturated.

Is it possible that I need to reboot/restart a board, service, whole system??
Anyone an idea?

[knightr1der]

@VAD, I didn't think it was speed dial he needed - more like "local short dial" prefix where on;

Node1 18=8
Node2 28=8

[tot3nkopf]

@VAD, I didn't think it was speed dial he needed - more like "local short dial" prefix where on;

Node1 18=8
Node2 28=8

That will only help the users in one node to dial 800 instead of 1800 or 2800 so he will still need to delete and recreate the users in the 2 nodes in order not to overlapp.

@Vad: with speed dial solution I don't think it is possible to retain all ABC-F2 features in the network (for instance callback) ---> non overlapping (at least) user dial plan in netwok still needed. Did you test this solution?

[vad]

Not. From my point of view - this case must be forbiden.
Many problem - broadcast forbiden, user must guess what number must be dialed 800, 1800, 2800?

When customer ask about such case - I say - only separated network and calls through prefix. No supervision, no boss-secretar an so on. After this explanation - usually customer say - OK, one number will be 888 instead of 800 and case solved.

Sometimes problem can be solved in different way - I do not know what in this case REAL problem - customer want to have USER on both nodes with the SAME number (f.e. 800), or customer want to DIAL the SAME number and reach different destination (like dial 0 - same number - and reach different operator - depends of node, entity, time...).

[tot3nkopf]

Not. From my point of view - this case must be forbiden.
Many problem - broadcast forbiden, user must guess what number must be dialed 800, 1800, 2800?

When customer ask about such case - I say - only separated network and calls through prefix. No supervision, no boss-secretar an so on. After this explanation - usually customer say - OK, one number will be 888 instead of 800 and case solved.

Sometimes problem can be solved in different way - I do not know what in this case REAL problem - customer want to have USER on both nodes with the SAME number (f.e. 800), or customer want to DIAL the SAME number and reach different destination (like dial 0 - same number - and reach different operator - depends of node, entity, time...).

I totally agree with you.

[freedom]

I agree on the arguments Vad gave.
I also adviced the customer to change their global numberingplan is such a way that we have unique extension numbers at all sites.
Next Tuesday there is a meeting with the customer to see how we will proceed.

Thanks for all suggestions! I will keep you informed.