Prank calls on TDE600 "night bell".

[TomMonger]

Hello again!

We have a problem with one of our manufacturing plant facilities. They have a TDE600 system. We have an option in their night/weekend auto attendant to hit a key (0) to reach someone on the plant floor. The "0" option dials an IDC group extension, and rings an analog bell in the IDC group (the bell is the only extension in the group). People on the plant floor dial a code on any phone to pick up the IDC call.

Unfortunately, someone keeps calling and apparently using that option to ring the plant bell. Then when someone answers, there’s no one there.
The calls are always unidentified and come in on “line 23” with is the PRI circuit. No caller ID info.
We aren’t sure if it’s just a prankster doing this (always during one particular shift), or a robo call of some sort. I'm leaning towards someone "having fun".

Is there anything we can do short of getting the phone company involved? I've run call logs and there's no caller ID info, so that's a dead end.

Thanks,
-Tom in Scranton, PA USA

 

[Ired1980]

AFAIK, TDE supports CLI-distribution according to caller's phone number prefix.

If you can get CallerID with every normal call and don't get it only with prank call, you can try to use the following:
1) 10-3. Set "CLI Ring for DDI/DID" in Night mode to ON (Enable)
2) 10-3. Set any incorrect/disconnect extension* as "DDI/DID destination" in Night mode
3) 6-1. Fill in System Speed Dial (SSD) table with "CO line access number" + first digit of Caller's phone number.
For example, CO line access = "0", and Caller's phone numbers start with digits from "0" to "9". In that case you should create 10 records in SSD: "00", "01", "02",......, "09".
4) 6-1. Set your night OGM number as "CLI destination" for all this records of System Speed Dial.

If everything done right, any incoming call with Caller ID will match with one of created System Speed Dial records. And such call will be distributed to your OGM with AA according to SSD table.
Otherwise, if call doesn't have Caller ID information it will not match with SSD CLI rules and PBX will distribute such call accirding to DDI/DID table - to incorrect or disconnect destination

* Incorrect/disconnect extension - any valid or invalid extension which cause disconnection of call.
It can be:
- disconnected Digital PT
- unregistered IP-PT / DECT PS
- ICD Group with Queueing Time Table that has "Disconnect" as a first sequence.

You're welcome!
Harry from Izhevsk, Udmurtia, Russia.

 

[TomMonger]

Thank you, Harry!!! I'll try these!

-Tom in Scranton, PA USA