Sx-200 Fraud Scam-Hotel-Motel

[lvtech]

I know this probably is not a new scam, it seems they keep rehashing old scams counting on staff turnover in hotels. Sadly, this seems to work.
I have a Mitel SX-200 that is set up to send unanswered calls to the attendant console to a menu mailbox, which offers a couple of press off's for sales, etc.
Apparently, I believe it must be an inherent feature that if you dial a guest room extension at this point, the system will transfer you to the guest room.
The problem is that for the past couple of weeks, very late at night, someone calls the property, gets the menu, rings a room, wakes up a guest pretending to be the night auditor who has somehow "lost" the guests billing information. Guest is groggy, and pissed at being woke up, gives the info, and before the sun rises, their credit cards are maxed out.
Question is....can this dialing feature be blocked from a menu mailbox.
I have already disabled Auto Attendant transfer to any extension in the Voice Mail options, but it still works. I did not see anything else that looked relevant. Anyone have any thoughts?

Thanks

 

[kwbMitel]

You can block digits starting with X

Typically, the rooms start with 7

And, no, this is not new. I typically do not enable AA on hotel's and get the customer to sign a release if they insist.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[pandabear1]

deny by tenant

 

[kwbMitel]

Pandabear - If you deny by tenant will the VM still be able to activate lamps?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[pandabear1]

good question kwbMitel, I will have to try it, i will post results.

 

[pandabear1]

works great and mw lights work also, 200ICP release 5.0.2.11

 

[kwbMitel]

OK, I'm sold, Tenant restriction would be very secure.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[lvtech]

I agree, the tenant restriction would be an ideal application. I am trying to get this sorted out, and have a snag or two.
I made the voice mail ports tenant 1. I made all sets, admin, guest, and consoles tenant 2. Using form 5, I was able to prevent callers in the auto attendant from reaching guest rooms. However, when I changed the tenant number on the trunks from 1 to 2, I lost my auto attendant greeting. I assume this is due to the fact I have a restriction between tenant 1 (voice mail), and tenant 2 (stations). Any thoughts out there as how to get around this?
Many Thanks

 

[pandabear1]

I would imagine you still want the auto attendant/voicemail to access admin sets but maybe not. Example, rooms are say tenant 1, voicemail ports are tenant 5, then restrict in form 5, tenant 5 from accessing tenant 1 but tenant 1 can access tenant 5 as you want them to get to the vmail to access messages.

 

[kwbMitel]

What I would design

Trunks / Admin - Tenant 1 - Can connect to Tenant 2,3
Rooms - Tenant 2 - Can connect to Tenants 1,3
Voicemail - Tenant 3 - Can connect to Tenant 1 (Not 2)

This allows your AA to function normally for Admin

**********************************************
What's most important is that you realise ... There is no spoon.

 

[pandabear1]

I use tenanting to restrict 800 numbers for say reservations from being transferred to rooms, just another use of tenanting.