Cover DID #?

[gregarican]

My company has two sites connected via a point to point T1 using tandem networking. The HQ site funnels incoming PRI calls across the T1 to the remote site. The HQ site operator has received 4-5 calls per day that were meant for the remote site operator. I read the incoming DID number and forward the calls to the remote site operator if they come in with the right three digits. In this case, ending with 633. I forward these calls to extension 610 on the Non-Local UDP.

These rogue calls come in reading "Cover DID #" on the HQ site operator's MLX-28D display. Checking the error logs I don't see any drops on the T1. And I don't have any coverage setup for the operator at either site. The calls would typically ring and ring until eventually picked up or until the caller bails out.

Any ideas where to start looking? Could it be telco didn't hand off the proper DID through some glitch? The only other thing I could think of if the remote site operator accidentally hit the Night Service button on their phone. But these calls that are bouncing are in the middle of the day when that's rather unlikely...

 

[Telecomboy]

Cover DID#? is displayed when the Legend doesn't recognize the digits being sent (they don't match anything in the switch to route the number to).

 

[rmelan47]

When you see "Cover DID #?" on colsole it is an indication that a DID or DNIS number is not in the system dial plan.

You can send DID or DNIS number not in dial plan go to voice mail, by changing " Unassigned Extension " from operator ext. # to your VM calling group (770).

 

[gregarican]

Thanks for the responses folks. I guess sending these calls to the HQ operator is fine since they will get a live voice, and they can then manually transfer the caller to the remote site operator. I figured the DID coming in must have been botched somehow. Will perhaps look to open a ticket with telco regarding this (although this probably won't do much).

Thanks again!

 

[gregarican]

Now we are getting calls for the remote site that come up with the caller's orignating ID, not the "COVER DID #" on the main site's operator display.

We have verified that the caller has dialed the remote site's telephone number, which the main site's PBX strips off just the last three digits (633 in this case) and should send the call to the remote site operator (610 in this case).

Checking the telephone programming the 610 extension just has one primary cover phone, which is extension 611. Why are these calls bouncing back to the main site's 110 operator extension?

There are four line buttons on the 610 operator phone. If all of these lines are in use would the calls then bounce back? Just trying to figure out why this would happen. Nothing in programming that I manually set would have 610 calls cover to 110...