Routing DIDs between two MICS

[edoo]

The Goal:
When a user moves locations, they wish to keep their current DID. I wish to re-route their existing DID to an extension on another site.


Current Setup:
• Telco sending 3 Digits
• DN Length 3
• DID Block 616-2400 to 2419
• Destination Codes 9(pri), 5(other site)
• Routes Rte000(poolA) Rte001(pri-B other site) Rte002(pri-A)



Attempted Solutions: (that doesn't work)

1) Program a target line and make the prime set the desired ext. However, the system will not accept a leading digit that is a destination code. In this case 5.

2) Create a route that sends it to the desired set on the other system. Create a destination code of the received digits using the route that was just created. When a call comes in, the digits are recognized by the destination code and routed correctly. This method works but not for the DIDs in this range. The Destination codes conflict with valid DN's.

I have thought about asking the carrier to send 4 digits instead of three. However, I don't think that will help because the digits received will start with a 2. It seems like a 2 would conflict with current extensions.

Got any suggestions or advice?


Thanks for taking the time to read this post!


Current hardware
• MICS 6.0
• MCDN 4.0
• PRI
• T1 (p2p to other site)
• 6 Port Expansion
• NAM rel4

 

[senk1s]

i think you are better off upgrading to a BCM with IP Phones for 'floating users' ...
with just a data network between the 2 offices

 

[edoo]

Yes a BCM would be very nice to have. Unfortunately it's out of the budget.

 

[jerryreeve]

what are your valid dn's at each station?
for a Coordinated dial plan you have to have a unique start digit for each node, (the lead digits on each mics has to be different than all other MICS lead digits)

I pulled the following from the 6.1 book for UDP

Calls routed over private networks using UDP require a
private DN length, since each node requires an identification
code in the dialing string, which makes the DN length different
than for a public-routed call.
If you are networked using UDP:
• you indicate a private DN length, which is the number of
digits required to access sets in the system (System
Programming/Dialing Plan/Private network)
• each system has a unique location code (System
Programming/Dialing Plan/Private network)
• you indicate that you are using a UDP dialing plan
(System Programming/Dialing Plan/Private
network)
• you set up private access codes (Access codes/Private
access codes)
• a telephone in another node is accessed using the access
codes, the location code, and the telephone DN.
Any programming for routing and access codes should be
carefully planned using the tables supplied with the
Programming Record. The settings for routing and destination
codes are fully explained in Services on page 371.
Note: Network access codes must not conflict with access
codes used for other purposes.



----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

Mind like a Steel trap - Once used forever clamped shut.

 

[jerryreeve]

Bad post previously, I was going to clean up the quotes.

mainly you may have to go to the book and look over the networking portion carefully to see what you can get it to do for you. this portion of the book has some pretty good examples of network setups.

you may not be able to moove a customer DN from location to location.

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

Mind like a Steel trap - Once used forever clamped shut.

 

[senk1s]

when networking it is good to keep the numbering plan uniform (PBX1 2xxx, PBX2 3xxx and so on) ...esp if you are routing DIDs over the network

or else you need to have an access code to go from site1 to site2 and another to go from site1 to site3 and so on
then you play with the digit manipulation, to insert the access code and dial.

ivent done the latter one in norstar and think it is not doable, becuase of the way dest codes are setup

 

[edoo]

JerryReeve,

It looks like we are using a Coordinated Dialing Plan
System 1 has unique lead digit of 2
System 2 has unique lead digit of 5
System 1 has Destination Code of 5 absorbs 0 and uses Route001 over PRI-B

The routing of internal call works great. Dialing any ext5xx will reach the respective ext on the other site.

As for the DN's
System 1 has DN's 221 to 232 but I think the system reserved to dn476 due to the 6 port expansion card.

I don't think I want to move their DN from one location to another. As you had noted, I think this would be impossible due to the unique lead digit.

However would it be possible to route their current DID to a different dn? ie. route 616-2419 to dn 530 instead of 230?

Trying to route this DID to System2 is stumbling block.