sundance-communications.com/forum Forums TDM Business Telephone Systems NEC Telephones & Systems 2000IPS tracing a DID

Greetings - I have an issue with a 2000IPS with regard to setting up a new DID. We have a block of 100 DIDs coming in on our PRI. In the past to setup a new DID, Ive been able to go into 7601 and 7602, enter the conversion block number, then the extension and it's worked. In this particular case, the extension the DID will go to is at a remote site with its own 2000IPS. 3-digit dial works fine between locations, and I've located several DIDs within the same block going to extensions at the same location. Here's the tricky part. Because this didn't work, I started digging around at how the others are configured. In looking at 7601 and 7602 data for the conversion block numbers in use for these other remote extensions, the data in every case is NONE. I generally try to figure these things out on my own/with the manual, but this one has me stumped pretty bad. Anyone have information on how else the DIDs might be setup, or where else I might start looking for a few clues? Things I know are:
The DIDs all come in on a PRI at location A
Location A extensions with DIDs have proper data listed in 7601/2.
Calls coming in at Location A with DIDs pointing to extensions at location B work, with no correlating data in 7601/2

Thanks to anyone that might lead me down the right path.

In an IPS, if the DID number has a direct match to a number programmed in forms 10, 11, or 14, it will ring at that phone regardless of 76 yy=01/02 with second data NONE.

7601/7602 override this direct match. The system looks at 76, then at 20, in determining where to put the call.

See if 200>xxx>a126, and if so, see if 8a4005>xxx>8003.

Thanks a ton for the reply.

200>9 does come back as a126.

8a4005>xxx>1005 not 8003.

I've been through CM10 and didn't find anything I could match to either the working DID or the working extension (dumped a station listup). Getting into virtual lines (CM11/14) to do this sort of thing is beyond my level of understanding.

do your extensions begin with 9? If not you could be following the wrong track!

Also A126 may not necessarily go to 8A4005! first you need to check that your extension range is actually going to A126 and it may be more complicated than normal. For example lets say we have a DID range of 200 to 299 and you want to send a block of ten numbers to the remote site (assuming your DIDs match your extension numbers) lets send extns 220 to 229 to the remote site, you could have CMD 200 entries like these...

200 de 20 de 803
200 de 21 de 803
200 de 22 de A126
200 de 23 de 803
200 de 24 de 803
200 de 25 de 803
200 de 26 de 803
200 de 27 de 803
200 de 28 de 803
200 de 29 de 803

Then in Cmd 8A4XXX you would send the 20X on through such entries as 1XXX

However if you want to send ad-hoc numbers to the remote site you would have a CMD 200 entry like

200 de 2 de A126 then in Cmd 8A4XXX you would have an entry of 8003 for extensions that are staying in the original system and for extns going to the remote system you would have an entry that sends the number on through the LCR like 1XXX

You also need to check that A126 actually does point to 4005 as I said earlier by checking cmd 8AA000 de 3 as the default I believe is 4004

Finally it is I believe also possible to do this yet another way by using Cmd 76XX where the DIDs are converted to have an access code in front of them! For example 220 needs to go to the remote system, you convert it to, for example 8220 and then in Cmd 200 send 8 to lcr using say A126, this will get 220 to LCR and at the same time strip the 8 back off! You then just handle the 220n number through the lcr in the normal way!

Thanks for the clarification. So here's what I found once I started looking for the right thing. Bit more info - Location A - all extensions are 3xx, Location B, they're all 2xx. So if I look at CM200>2 DATA = 720, which tells me I need to add a digit to get the correct information (just validating that I understand what's happening). So, if I'm more granular, all of the CM200>2X (20, 21, 22, etc)entries, DATA = A129. I believe this is done because each remote location is in a different geographical area within the state (entire state on 1 area code), so they can route calls to Location B using the internal routing of the phone system by prefix (again, validating that I understand what's going on).

So with that out of the way, 8AA000>3 came back as 4007, and yes 4004 should be the default IF A126 were in CM200>2X, but I believe this relates to the internal local call routing by prefix. Looking at 8A4007>2X gave me a route pattern 0120 for all of them.

Now I start to have some success - CM8A4007>(known-routing DID) DATA = 0120 which matches my route for extensions at Location B. On the right path! So I made the change to the DID I'm trying to use in this case, changing CM8A4007>6302(DID I'm trying to assign):8004 (all unassigned or local DIDs are set to 8004) to CM8A4007>6302:0120. This should get the DID routed into the right place.

Now I move onto the Location B IPS. To make sure I'm looking at the right stuff, I verify that my working routed DID exists in CM7601/2 and sure enough, my DID ConvBlockNumber is in there and pointed to the extension it's supposed to. Thinking I've got this nailed, I put in my CM7601/2 to match my DID and extension AND..... no dice.

I feel like I'm inches away here...

If you follow Cmd 8A0120 through the LCR you will get to command 8A5XXX where digit addition and deletion can take place. I'm guessing something is being done there because you say 8004 is used which implies 4 digit numbers but you are saying 2XX which implies 3 digit numbers!

Also, on switch B, look at see if see if 8a4005>3xx>8003. This will make the switch look for a local phone (programs 10, 11, or 14) with the DN 3xx

If 8a4005>2xx>8003, then there's a local phone with DN 2xx, etc.

And R4+Z is correct, 8003 means 3-digit, 8004 means 4-digit.

I suspect that we should be following 63XX and 62XX through the LCR rather than the numbers used as examples. It's always awkward trying to deal with issues like these because the OP doesn't want to give away too much info that could give unscrupulous people an inroad (which is understandable)!

It also needs to be borne in mind that routing can be happening at both locations, so this number could be bouncing back and forth between the two systems

Thank you for the additional follow-up. I was taken off task and will be back working on this today. Again thank you for your help. I will follow up with my findings/level of success.

I tried to answer/respond to each of your responses to the best of my ability.


I went through 8A5120 and 8A5020 (120 is my route and 20 is my trunk. Wasn't positive so I looked at both) and all of the digit delete items were set to 1 (no delete) or NONE.


Looking at 8A4005>3xx/2xx I get 1005 back for both on switch B. I tried digging a little deeper into the tenant pattern stuff, but got lost - this is at a level I just don't know enough about.



I'm not too worried about giving away internal extensions etc... not like I've enumerated where my secret lair is =). I wasn't sure how to interpret looking into 62xx/63xx in LCR. For the sake of clarity, 63xx is my DID block (I assume you probably gleaned this from an earlier post). What I was unable to find in going through LCR was a sign that the first digit was stripped off in either of the two areacode patterns in use (5 and 7 incase you're curious - not sure that makes any difference). All show no digits removed.

Is there anyplace I might have overlooked that would cause the 4-digit DID to be used to route the call rather than the 3-digit conversion block number?