ITEngineer

Let me go through this in a couple of steps. For your receptionist to be getting calls with the name DNIS, that name has to exist somewhere. (If no one is there then these are likely what we call phantom calls.) Most likely in the call routing table (System\Trunk Related\Information\Call Routing Tables). In reality DNIS is something that we see in a T-1 not a PRI. DNIS is dialed number information service which is a series of digits that identifies the number ringing in, not caller ID and the system routes the call based on what number was dialed. You are dealing with DID numbers if you have a PRI, not DNIS. You can assign in the call routing tables any name to a pattern description ringing in, if no caller ID is received the description name will be displayed on the endpoint. At the botton of the call routing table there should be two entries a + and E, in this order. Plus means any DID number received but not in the list of patterns and E means a empty pattern. For your situation to happen as it has been described the description for E would have to be DNIS or simply the call routing table is programmed incorrectly and + and E does not exist at the bottom of the call routing table. If DNIS does not match E the case then is you have been given the incorrect answer. Look at your call routing table and see what pattern has a description of DNIS, and this is the number causing the problem. I normally would assign the E pattern a description of EMPTY so if it rings into the receptionist you know why. You can direct E to a Call routing announcement if this is causing the phantom calls and then if wanted make Timeout hangup and this will drop all calls coming in that do not have a DID number assigned. I would NOT recommend this. As you can see by assigning a ring in destination to E the system does know where to route calls that it receives no pattern for. OK, this is enough on how the name DNIS shows up on the display.

As you can see in a properly programmed call routing table the system knows where to route a call if it matches a pattern, receives a pattern not defined in the call routing table (+) or receives a (E) empty pattern. There is no "Spike" in a PRI this is BS. For more on this when in programming in call routing tables press F1 for help and read the section entitled NOTE:. And lastly if for some reason your service partner did not provide the DB Studio programming application for you, shame on them. Insist that you be provided DB Studio and have access to your system. It is your system and you should have the application. If they resist then based on the info you provided in your questiona and them not wanting to give you access to your own system, find another service partner, again this is my opinion.

My guess is that your PRI or T-1 is receiving errors and that is what is actually generating the potential phantom calls. In programming go to (System\Cabinets\Select the + beside your T-1 or PRI then T-1 diagnostics and then hourly or daily to see if it is generating errors. Most likely BPV or CRC errors. CRC errors could be a sign that the timing is slipping, which is the most likely cause of your problem. Solution is to call the telco and report problems on the circuit. But have your facts straight before you call telco, know how to ID the problem so you know when it is fixed.

__________________
Life is a highway....