Door Entry Project - Revision history

Summakor: Moved to Previous Projects

2016-12-16T03:28:14Z

Moved to Previous Projects

← Older revision		Revision as of 03:28, 16 December 2016
Line 25:		Line 25:
	Ideally: Video from the panel camera will be split, so it can be digitized by the web video server AND by the surveillance recorder in Brian's office, which is NOT connected to the internet.		Ideally: Video from the panel camera will be split, so it can be digitized by the web video server AND by the surveillance recorder in Brian's office, which is NOT connected to the internet.

	[[Category:~~Ongoing~~ Projects]]		[[Category:Previous Projects]]

ITechGeek: Undo revision 4069 by Yrewevaca (talk)

2010-11-24T06:42:47Z

Undo revision 4069 by Yrewevaca (talk)

← Older revision		Revision as of 06:42, 24 November 2010
Line 1:		Line 1:
	~~----~~
	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
	~~----~~
	~~=[http://ejahibuko.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=~~
	~~----~~
	~~=[http://ejahibuko.co.cc CLICK HERE]=~~
	~~----~~
	~~</div>~~
	Note that, as a point of distinction from the [[Physical Access Control Project]], this project's scope includes the whole [http://www.saintstephensdc.org/ church], its staff and tenants.		Note that, as a point of distinction from the [[Physical Access Control Project]], this project's scope includes the whole [http://www.saintstephensdc.org/ church], its staff and tenants.

Yrewevaca at 06:25, 24 November 2010

2010-11-24T06:25:43Z

← Older revision		Revision as of 06:25, 24 November 2010
Line 1:		Line 1:
			----
			<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
			----
			=[http://ejahibuko.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
			----
			=[http://ejahibuko.co.cc CLICK HERE]=
			----
			</div>
	Note that, as a point of distinction from the [[Physical Access Control Project]], this project's scope includes the whole [http://www.saintstephensdc.org/ church], its staff and tenants.		Note that, as a point of distinction from the [[Physical Access Control Project]], this project's scope includes the whole [http://www.saintstephensdc.org/ church], its staff and tenants.

Myself: /* Current plans */

2008-12-18T22:34:01Z

Current plans

← Older revision		Revision as of 22:34, 18 December 2008
Line 11:		Line 11:
	Requirement: the person doing the unlocking must see the guest before opening the door. So, unlocking by phone is not permissible. Either get video on screen, or just walk downstairs and see 'em through the window.		Requirement: the person doing the unlocking must see the guest before opening the door. So, unlocking by phone is not permissible. Either get video on screen, or just walk downstairs and see 'em through the window.

	Outside: All that's needed is a camera, a keypad, and a place Brian can stick a printed directory page. Two-way audio (speakerphone at the outside panel) would be nice too but isn't a strict requirement.		Outside: All that's needed is a camera, a keypad, and a place Brian can stick a printed directory page. Two-way audio (speakerphone at the outside panel) would be nice too but isn't a strict requirement. The video will be served to the internet over St. Stephen's internet connection.

	When a guest dials a suite number: (which will be a 1 or 2 digit number, probably followed by the star or pound key) ~~Our~~ system should place a call over the PSTN to ring whoever's associated with that space. The suite-number-to-phone-number lookup table will be maintained by Brian.		When a guest dials a suite number: (which will be a 1 or 2 digit number, probably followed by the star or pound key) The system should place a call over the PSTN to ring whoever's associated with that space. The suite-number-to-phone-number lookup table will be maintained by Brian.

	When the phone is answered: It'd be nice to have two-way audio to the panel, so the answerer can talk to the guest and ascertain who they are. BUT UNLOCKING CANNOT BE DONE BY PHONE. See "requirement", above.		When the phone is answered: It'd be nice to have two-way audio to the panel, so the answerer can talk to the guest and ascertain who they are. BUT UNLOCKING CANNOT BE DONE BY PHONE. See "requirement", above.

	To unlock the door: The answerer (or anyone else) can just walk downstairs and open the door, OR pull up video over the web, and after having visually confirmed the guest's identity, the answerer can enter their PIN on the website and unlock the door that way.		To unlock the door: The answerer (or anyone else) can just walk downstairs and open the door, OR pull up video over the web, and after having visually confirmed the guest's identity, the answerer can enter their PIN on the website and unlock the door that way. So the webserver will need a copy of the PIN database, or will need to forward all attempts to some other device to try them.

	Any authorized user can just enter their PIN at the keypad and let themself in, of course. (Yeah, I know that's not a word. Bite me, English language!)		Any authorized user can just enter their PIN at the keypad and let themself in, of course. (Yeah, I know that's not a word. Bite me, English language!)
Line 26:		Line 26:

	[[Category:Ongoing Projects]]		[[Category:Ongoing Projects]]


	~~<b>Diagrams</b>~~
	~~<p>[[Media:Base_Diagram.jpg]]</p>~~
	~~<p>[[Media:Person_with_entry_code.jpg]]</p>~~
	~~<p>[[Media:Person_without_entrycode.jpg]]</p>~~

Myself: added requirements from Tuesday's convo

2008-12-18T20:46:59Z

added requirements from Tuesday's convo

← Older revision		Revision as of 20:46, 18 December 2008
Line 4:		Line 4:

	Discussion is taking place on [http://hacdc.org/mailman/listinfo/reddoor_hacdc.org the red door mailing list].		Discussion is taking place on [http://hacdc.org/mailman/listinfo/reddoor_hacdc.org the red door mailing list].

			= Current plans =

			As per a discussion Nate had with Brian on Tuesday, December 16th, here are the current plans:

			Requirement: the person doing the unlocking must see the guest before opening the door. So, unlocking by phone is not permissible. Either get video on screen, or just walk downstairs and see 'em through the window.

			Outside: All that's needed is a camera, a keypad, and a place Brian can stick a printed directory page. Two-way audio (speakerphone at the outside panel) would be nice too but isn't a strict requirement.

			When a guest dials a suite number: (which will be a 1 or 2 digit number, probably followed by the star or pound key) Our system should place a call over the PSTN to ring whoever's associated with that space. The suite-number-to-phone-number lookup table will be maintained by Brian.

			When the phone is answered: It'd be nice to have two-way audio to the panel, so the answerer can talk to the guest and ascertain who they are. BUT UNLOCKING CANNOT BE DONE BY PHONE. See "requirement", above.

			To unlock the door: The answerer (or anyone else) can just walk downstairs and open the door, OR pull up video over the web, and after having visually confirmed the guest's identity, the answerer can enter their PIN on the website and unlock the door that way.

			Any authorized user can just enter their PIN at the keypad and let themself in, of course. (Yeah, I know that's not a word. Bite me, English language!)

			Caveat: The answerer could just tell their PIN to the guest over the phone, couldn't they? To prevent this, and enforce the face-view requirement, perhaps the keypad could refuse to accept PINs for a while after dialing a suite number.

			Ideally: Video from the panel camera will be split, so it can be digitized by the web video server AND by the surveillance recorder in Brian's office, which is NOT connected to the internet.

	[[Category:Ongoing Projects]]		[[Category:Ongoing Projects]]

Katie at 13:36, 7 December 2008

2008-12-07T13:36:01Z

← Older revision		Revision as of 13:36, 7 December 2008
Line 1:		Line 1:
			Note that, as a point of distinction from the [[Physical Access Control Project]], this project's scope includes the whole [http://www.saintstephensdc.org/ church], its staff and tenants.

	There was a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.		There was a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.

Katie at 13:29, 7 December 2008

2008-12-07T13:29:46Z

← Older revision		Revision as of 13:29, 7 December 2008
Line 1:		Line 1:
	There was a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.		There was a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.

			Discussion is taking place on [http://hacdc.org/mailman/listinfo/reddoor_hacdc.org the red door mailing list].

	[[Category:Ongoing Projects]]		[[Category:Ongoing Projects]]

Katie at 22:22, 6 December 2008

2008-12-06T22:22:59Z

← Older revision		Revision as of 22:22, 6 December 2008
Line 1:		Line 1:
	There ~~will be~~ a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.		There was a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.

	[[Category:Ongoing Projects]]		[[Category:Ongoing Projects]]

Hasufin at 21:24, 6 December 2008

2008-12-06T21:24:06Z

← Older revision		Revision as of 21:24, 6 December 2008
Line 2:		Line 2:

	[[Category:Ongoing Projects]]		[[Category:Ongoing Projects]]


			<b>Diagrams</b>
			<p>[[Media:Base_Diagram.jpg]]</p>
			<p>[[Media:Person_with_entry_code.jpg]]</p>
			<p>[[Media:Person_without_entrycode.jpg]]</p>

Katie: New page: There will be a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end. Category:Ongoing Projects

2008-12-05T14:39:15Z

New page: There will be a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end. Category:Ongoing Projects

New page

There will be a meeting in the space at 1pm on Saturday, 6 December 2008 to start prototyping the Asterisk back-end.

[[Category:Ongoing Projects]]