Fanvil Access Control Question

Status
Not open for further replies.

Michael Gamache

Premier Customer
Joined
Aug 14, 2017
Messages
11
Reaction score
0
I am going to be deploying About 16 Fanvil X6 Phones at a LAB location we are implementing.
Normally I am use Yealink T41p-s prhones, but we want to use phones to provide access to facility via doorphone.

I have successfully tested the Fanvil phones (for pricepoint vs Yealink codec-enabled phones), with Fanvil door phone, and for most part, working exactly as it should.

We will have the doorphone setup to dial a ring group instead of individual phone, so anyone inside can unlock door during business hours. We will actually have two doorphones at different entrances. X6's will be setup with Custom BLF to unlock appropriate door.

My only issue at the moment is that when you press the "Door Open" BLF, the phone displays the unlock "code" for that phone. That means that if there is someone looking over when user opens door, they can see the unlock code. They can then use that to open door directly, no? Is there a way to "mask" the entry in the provisioning file?

Anyonw with experience wiht this kind of setup , any insight would be appreciated.
 
It's not a matter of masking it in the provisioning file. The provisioning file is not what people are seeing. You are doing a custom BLF that is sending DTMF which is exactly the same as if someone answered the door phone and dialed the code manually, it will show up on the screen.
 
I completely understand that, I was wondering if there was a way to mask the DTMF entry.
 
I mean you could always make your unlock code something stupidly long so no one would have time to make note since you're using BLF. you could always include * and # too..
 
  • Like
Reactions: Evolute IT
Great idea!! thx
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,937
Messages
589,831
Members
164,818
Latest member
Guriqbal Singh