Howdy,

I've got two nodes.

Node A: has 200 DID's that begin with the 206 area code. They also have an extension 206. The entry for SPNet in the DID table is 2**.

Node B gets Invalid Extension on the display when they try to dial extension 206.

Since the PRI's use the DID table and SPNet also uses the DID table, and there's only the one DID system-wide table, what's a poor boy to do?

I made a phantom extension at node A with extension 236 that forwards to 206 and they can get it there but I can't think I'm the only person out there who's experienced a conflict between extension numbers and DID digits with SPNet in the DID table.

Are you using LCR? There should not be an issue. For SPNET you use a MGI channel/trunk, and when you call out you use the PRI/analog trunk.

I am using LCR but the issue seems to be in the incoming side at Node A.

The DID table has:
2065551212
2**

If the user in the other node dials extension 206 into this node, there is a split second then it comes up with INVALID EXTENSION on the screen. That tells me that the incoming DID table on Node A doesn't like it. All other 20x extensions work, just 206.

This is the only issue with SPNET calls routing in via the DID table.

Couple of things you can do

Can you get the carrier to not send the area code?
renumber that extension from 206
renumber the whole of node a

Thanks Nameless, that's what I thought.

That'd make it hard with a very large network and a vast array of DID's to make that all jive.

However, I've just got one nurse and we can renumber her bleeping extension.

Kind of weak. They really should use a table number for DID routing. One table for SPNet by Node and multiple tables for PRI groups...

Thanks!

Yeah, I wish there was a separate SPNET table to the DID table, I have come across your issue a couple of times, I try to make voip 4 digit extensions/groups

Just a thought, but in theory seems logical.

You could configure your modify digit table to append a 1 after you dial 206.

Node A would recieve 2061 in the DDI table to which you send these digits to the extension of 206.

You may have to create the same rule from 201-209

T.C.s recommendation is a good one, but I think it'd still get rejected because it's still conflicting.

I'd say go simpler. Somewhere in your NLCR you've likely got 20 being converted to 00120 with a length of 3 and a max of 6 or some similar.

I'd say bump it up to length 3 max 7 and have 20 modify to 001320. Then in node A you'd have to have 3201 ~ 3209 manually route to 201 ~ 209, but it'd absolutely circumvent the issue.

Alternately, since you've only got two nodes, eat up a few more NLCRs: call out 201 through 209 specifically, then you just need to modify 206 itself.

Either way is a little confusing if you come back to look at it in 6 months, but in my opinion the latter is easier to recall later.

Good thoughts guys!

If I make an extension on Node A that is 236 and do a FWD ALL to 206, it works great if the person in Node B dials 236 instead.

Using that logic, I could make an entry in the Modify Table in Node B when dialing 206 that will strip 2 and add 36. Then the user in Node B will dial 206, then Node B will change it to 236 and send it to Node A and Node A will forward that call to 206.

It works so fast you can't notice it.

I'll put in a change request with Samsung (also known as the great black hole) to have multiple DID tables.

Thanks fellas!

it would be much easier to insert a digit at Node B and delete 1 digit at Node A.
Node B use Lcr to send say 001 3 206, Node A strips out the 001 and is left with 3206, delete 1 digit in DID entry and is left with 206.

The only (minor) issue with modifying the digits is that BLF won't work

If you are using LCR for both nodes then they should be using a dial code like 9 or 8 to access it. This would not interfere with your extensions if you setup the NLCR correctly. I had the same situation and it works without a hitch. When node b dials 206 directly it should go to ext 206 of node a and when they dial 206 using lcr to dial out it should work just fine without conflict.

what if you put a wild card XYZ with 206 respectively enabled and point it to SPNet and then 206X pointing to the DID
X would enable 0123456789*#
Y would enable 0 only and
Z enable 6 only. I will have to test it when back @ office