Axis Perimeter Defender Perimeter Defender Bridge to Genetec 5.3 & 5.4

AXISPerimeterDefenderwithGenetecVMS

UserManual

AXISPerimeterDefenderwithGenetecVMS

TableofContents

Introduction...............................................3

VMSIntegration............................................4

InstallationHost................................................4

Prerequisites...................................................4

Licensing......................................................5

Installation....................................................5

Conguration..................................................5

OperatingtheSecurityDesk.......................................10

2

AXISPerimeterDefenderwithGenetecVMS

Introduction

Introduction

TheIntegrationPackallowsquickandseamlessintegrationbetweenAXISPerimeterDefenderandGenetecSecurityCenter.Alarms
triggeredbyAXISPerimeterDefenderareautomaticallyconvertedtoSecurityCenterCustomEvents,that,inturn,cantriggera
widesetofactionsandleveragethefullpoweroftheSecurityCentersystem.Atthesametime,thelivemetadatageneratedby
AXISPerimeterDefenderaresenttoSecurityCenterforlivedisplayandrecording.Therefore,themetadataarealsoavailable
whenplayingtherecordedvideosequencesinplaybackmode.

3

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

VMSIntegration

InstallationHost

TheintegrationbetweenAXISPerimeterDefenderandSecurityCenterisbasedontwosoftwaremodulesrunningontheSecurity
Centerserver(oranotherserverconnectedbyLANtoboththeAxiscamerasrunningAXISPerimeterDefenderandtheGenetec
SecurityCenterserver):

•The“AXISPerimeterDefender”runsasaWindowsService.ItfeedstheSecurityCenterServerwiththemetadatacoming
fromAXISPerimeterDefender.TheSecurityCenterServerrecordsthemondiskandmakesthemavailabletotheSecurity
Deskforliveandplaybackdisplay.

•The“MetadataBridgeCongurationTool”isagraphicaltoolthatallowstheusertoconguretheMetadataBridgeandto
providethecredentialsandnetworkaddressesoftheAXISPerimeterDefenderserver,ifthereareany.

Prerequisites

Globalprerequisites

InordertooperateasuccessfulintegrationbetweenAXISPerimeterDefenderandGenetecSecurityCenter,thefollowingsolution
modulesmustbeavailable:

•Aworking,correctlylicensedandconguredSecurityCenterServer(atleast5.3SR4CU1or5.4SR3)

•SomeAxiscamerasrunningAXISPerimeterDefender.TheAxiscamerasmustbeconnectedtoandconguredwithin
SecurityCenter.

Note

AXISPerimeterDefenderdoesnotneedtobefullycongured(i.e.calibratedandeventdened)toconguretheAXIS
PerimeterDefenderGenetecSecurityCenterIntegrationPack.Nevertheless,aslongasanot-yet-congureditdoesnotsend
alarmsnormetadata,youwillnotbeabletoreceivethemintheSecurityCenter.

•Atleastone“GSC-1SDK-Axis-PerimeterDefend”SDKconnectionlicensemustbeavailablewithintheSecurityCenter(see
dedicatedsection“Licensing”formoredetails)

•YoumustbeabletoinstalltheGenetecSDKcorrespondingtoyourSecurityCenterversiononthehostwhereyouplan
toinstalltheAXISPerimeterDefenderGenetecSecurityCenterIntegrationPack(seededicatedsection“Installation
host”forfurtherdetails)

SoftwarePrerequisites

Theintegrationpackhasthefollowingprerequisites:

•Microsoft.net4.0mustbeavailableonthePCwheretheintegrationpackisinstalled.Ifitisnotavailable,itwillbe
automaticallyinstalledbytheIntegrationpackinstaller.

•AtleastGenetecSecurityCenter5.3SR4CU1or5.4SR3

•AXISPerimeterDefender1.0.0oralaterversion

•TheGenetecSecurityCenterSDKRedistributablecorrespondingtotheinstalledSecurityCenterversionmustbeinstalled
ontheserverwheretheAXISPerimeterDefenderGenetecSecurityCenterIntegrationPackisinstalled.Toobtainthe
SecurityCenterRedistributableSDK,contactyourGenetecrepresentative.

•SDKconnectionlicense(seefollowingsectionfordetails).

4

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

Licensing

EveryrunninginstanceoftheAXISPerimeterDefenderMetadataBridgeneedsan“SDKconnectionlicense”fromSecurityCenterin
ordertobeabletoconnecttoit.TheSDKlicenseisnamed“GSC-1SDK-Axis-PerimeterDefend”andisdisplayedintheCerticatestab
oftheAboutmenuoftheCongTool.Thefollowingpicturedisplaysasystemwith10oftheselicensesinstalled:

TheselicensescanbepurchasedfromGenetec,contactyourGenetecsalesrepresentativeincaseofdoubt,mentioningthatyouwant
topurchaseSDKlicensesnamed“GSC-1SDK-Axis-PerimeterDefend”.

ThenumberofneededlicensesdependsonthenumberofinstalledMetadataBridgesandnotonthenumberofserversorAXIS
camerarunningAXISPerimeterDefender.TheMetadataBridgeCongurationToolalsoneedsanadditionallicenseduringthe
congurationphase,seeLoginCredentialsonpage6forfurtherdetails.

Installation

Theinstallerexecutable(“AXISPerimeterDefenderSecurityCenterIntegrationPackX.Y .Z.W.exe”)installsboththeAXISPerimeter
DefenderMetadataBridgeandtheMetadataBridgeCongurationTool.Theinstallerautomaticallytakescareofallthenecessary
lesandsettingsonthedestinationmachine.Toexecutetheinstaller,theusermustdouble-clickonitandgothroughthefew
installationscreens.Thedefaultvaluesofeacheldsuitthemajorityofthestandardinstallations.

Conguration

Whentheinstallationnishes,theMetadataBridgeCongurationToolstartsandpresentstheinterfaceforthenecessary
congurationstep.Thefollowingscreenshotshowsthetoolinterface:

5

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

LoginCredentials

TheusermustprovidelogincredentialstotheSecurityCenterServer:

•Directoryname/ipistheipaddress(like192.168.1.100)orname(server.domain.com)oftheSecurityCenterserver.Ifthe
MetadataBridgeisinstalledonthesamemachineasSecurityCenter,“127.0.0.1”canbeused.

•PortisthenumberoftheportwhereSecurityCenterlistensforincomingSDKconnection.Whereindoubt,leavethe
defaultvalueof5500.Thecorrectvaluecanbefoundinthe“GenetecServerAdmin”application(installedontheSecurity
CenterServer)andthenlookingatthe“IncomingConnectionPort”line.

•Loginistheloginofauserhavingadministrativerightsonthesystem.IfSecurityCenterisconguredtoacceptWindows
Domainlogins,andyouwanttousethose,prependtheloginnamewiththedomainname,like“DOMAIN\User”.

•Passwordisthepasswordcorrespondingtotheuseryouspecied.

6

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

WestronglyrecommendusingtheTestbuttontobesurethattheprovidedcredentialsworkasexpected.Potentialissues,besidesthe
mostevidentoneslikewrongloginorwrongpassword,are:

•TheSecurityCenterdoesnothavethe“SDKconnectionlicense”GSC-1SDK-Axis-PerimeterDefend,andthustheMetadata
BridgeCongurationToolcan’tconnecttotheSecurityCenterServer.

•TheSecurityCenterserverisnotrunning(stopped)orthenetworkconnection(iftheAXISPerimeterDefenderBridge
isinstalledonanothermachine)isbroken.

•AlltheavailableSDKconnectionlicensesoftypeGSC-1SDK-Axis-PerimeterDefendareinuse(forexample,theMetadata
Bridgeisusingtheuniqueavailablelicense).Seethenextsection“SpecialNotes”.

Important

Iftheconnectioncredentialsaremodied,theAXISPerimeterDefenderMetadataBridgeserviceneedstoberestartedin
ordertousethenewvalues.

Listeningportforalarms

TheMetadataBridgeconguresthedifferentAXISPerimeterDefenderinstancesrunningonAxiscamerasconnectedtotheSecurity
CentersystemsotheywillsendalarmsonagivenportofthePCwheretheMetadatabridgeisinstalled.Thedefaultportis10000.It
doesnotneedtobechangedexceptifthisportisalreadyusedbyadifferentapplication.

Important

Ifthelisteningportismodied,theAXISPerimeterDefenderMetadataBridgeserviceneedstoberestartedinorderto
usethenewvalue.

AttheIntegrationPackinstallation,aruleallowingincomingconnectionstoanylisteningportoftheMetadataBridgeis
automaticallyaddedtotheWindowsFirewall.Nevertheless,therulecanberemovedbyasuccessiveinstallationorblocked
bysomeantivirus.Itisrecommendedtodouble-checktheconnectivityfromtheexternalworldtothechosenlisteningIP
porteachtimethislastischanged.

Note

ThisparameterdoesnotneedtobeconguredormodiedintheOutputssectionofAXISPerimeterDefenderSetupInterface,
astheMetadataBridgedoesitautomatically.

CustomEvents

ThefollowingpartoftheMetadataBridgeCongurationToolinterfaceallowsyoutocongurewhatdefaultactionsshouldbe
triggeredbytheMetadataBridgewhenitreceivesanalarmfromAXISPerimeterDefender:

InorderfortheSecurityCentertobeabletoreceiveaCustomEvent,thesetwoconditionsneedstobefullledatthesametime:

•Tobedened

•Tobetriggered

ThetwosettingsontheCustomEventlineallowsyoutocongurebothactions:

•IftheCustomEvents–AutomaticallyTriggercheckboxisticked,andifaGenetecCustomEventcorrespondingtothe
receivedAXISPerimeterDefenderalarmexists,thisoneistriggeredandsenttoSecurityCenter.Untickthisboxifyouare
notinterestedinreceivingaCustomEventwhenAXISPerimeterDefendertriggersanalarm(forexample,becauseSecurity

7

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

CenteralreadyreceivestheAXISPerimeterDefenderalarmsbyanothermean).IfyouwanttoreceiveCustomEventson
AXISPerimeterDefenderalarms,leavethisboxticked.

•IftheAutomaticallydenecheckboxoftheCustomEventssectionisticked,allthenecessaryCustomEventsare
automaticallygeneratedbythetoolsotheycanbetriggeredwhenthecorrespondingAXISPerimeterDefenderalarm
isreceived.Sountickthisboxifyouplantomanuallydene(asubsetof)thenecessaryCustomEvents,andleavethis
boxtickedifyouwantthemtobeautomaticallydened.

ThecompletelistoftheCustomEventsthatwillbecreatedis:

-AxisPerimeterDefenderIntrusionStart

-AxisPerimeterDefenderIntrusionStop

-AxisPerimeterDefenderLoiteringStart

-AxisPerimeterDefenderLoiteringStop

-AxisPerimeterDefenderZone-CrossingStart

-AxisPerimeterDefenderZone-CrossingStop

-AxisPerimeterDefenderConditionalStart

-AxisPerimeterDefenderConditionalStop

Important

IfyouchoosetodenetheCustomEventsmanually,itisimportantthatthenameoftheCustomEventrespectsthe
followingrules:

•Itmustcontainthe“Axis”string.

•Itmustcontainoneofthefollowingstrings:“Intrusion”,“Loitering”,“Zone-crossing”,“Conditional”.

•Itmustcontainoneofthefollowingstrings:“Start”,“Stop”.

(Forthesethreerules,thecomparisonisdoneinacase-insensitivemanner.Moreover,theCustomEventIDnumberis
irrelevant,choosetheoneyouwant)

IfyouonlywantasubsetoftheCustomEvents(forexample,benotiedonlywhenanalarmstartsbutnotwhenitstops)butyoudo
notwanttodenetheCustomEventsmanually,dothefollowing:

•TicktheAutomaticallydenecheckbox.

•OpentheGenetecCongToolandgotoSystemtask,thenGeneralSettingsandEvents.

8

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

•Makesureyouhavethe8CustomEventsdenedhere.

•UnticktheCustomEventsDenemissingonesintheMetadataBridgeCongurationTool.

•DeletefromtheGenetecCongTooltheCustomEventsyoudon’twant,i.e.thefour“Stop”CustomEventsinthisexample.

•MakesuretosavebyclickingonApplyintherightlowercornerofthewindow:

9

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

Note

OncetheCustomEventscongurationnished,arestartoftheSecurityCenterserviceisnecessary.

Bookmarks

IfyouwantabookmarktobeautomaticallygeneratedbytheMetadataBridgeeachtimeitreceivesanAlarmStartfromAXIS
PerimeterDefender,ticktheBookmarksAutomaticallygeneratecheckboxintheMetadataBridgeCongurationTool:

Abookmarkwithlabel“AXISPerimeterDefender{alarm_type}”({alarm_type}being“Intrusion”or“Loitering”or“Zone-crossing”
or“Conditional”)willbecreatedintheassociatedvideostream(i.e.theonecomingfromthecamerawhereAXISPerimeter
Defenderhasgeneratedthealarm).

Metadata

TheMetadataBridgeisabletoautomaticallyretrieveandcongurealltheAXIScamerasrunningAXISPerimeterDefenderby
scanningthelistofcamerasconnectedtotheSecurityCenter.TheMetadataBridgeautomaticallyassociateseveryAXISPerimeter
Defenderalarm/metadatastreamtothecorrespondingGenetecVideoSource(i.e.theAXIScamerawhereAXISPerimeterDefender
runs).Therefore,nomanualcongurationstepsarerequiredforAXISPerimeterDefender.

AXISPerimeterDefendergeneratesmetadatainformationthathelpsthesecurityoperatorunderstandwhatishappeningintheeld
ofviewofthecamera.ThesemetadatacanbesenttoSecurityCenterfordisplayandrecordingthroughtheMetadataBridge.

ThebridgeautomaticallysubscribestothemetadatageneratedbyAxiscamerarunningAXISPerimeterDefender.Ifthesecamerasare
connectedtoSecurityCenter,itthensendsthemetadatatoSecurityCenterthatdisplaysthemontopofthecorrespondingvideo
streamsandarchivesthemalongsidethevideofootagestobeabletooverlaythemagainwhenplayingbackthevideosequence.

Metadatadonotrequireanyspecialconguration,theMetadataBridgeautomaticallymanagesthenecessaryconguration
automatically.

SpecialNotes

WhenclickingTest,theMetadataBridgeCongurationToolsneedsforashorttimeanSDKconnectionlicenseoftype
“GSC-1SDK-Axis-PerimeterDefend”tobeabletoconnecttotheSecurityCenterService.TheAXISPerimeterDefenderMetadata
Bridgealso,ifrunning,needssuchalicense.SoifbothofthemarerunningandthereisonlyoneSDKconnectionlicense
“GSC-1SDK-Axis-PerimeterDefend”available,theMetadataBridgeCongurationToolwillnotbeabletoconnecttotheSecurity
Centerserverandwillreportanerror,eveniftheprovidedcredentialsarecorrect.Inthiscase,temporarilystopthe“AXISPerimeter
DefenderMetadataBridge”service,runyourtestandthenstartitagain.

OperatingtheSecurityDesk

Metadata

SecurityDeskdisplaysthemetadataasinthefollowingscreenshot:

10

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

1.Theupperrightcorneroftheimagecontainsacoloredspot,thecolordisplaysthealarmstatus:

-Red,ifAXISPerimeterDefenderisrunningandanalarmistriggeringforthecamera(inthescreenshotexample,
anintrusionalarmisgeneratedbyAXISPerimeterDefender).

-Green,ifAXISPerimeterDefenderisrunningandnoalarmistriggeredforthecamera(forexample,foran
intrusionscenario,ifthepersoniswalkingoutsidetheintrusionzone).

11

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

-Grayduringashortperiod(30-60seconds)afterAXISPerimeterDefenderhasbeenstarted.Duringthisphase
AXISPerimeterDefenderisinitializingandcannotgeneratealarms.

2.Arectanglesurroundsthepersonsand/orvehiclesdetectedinthescene.Thecoloroftheboundingboxisredforpersons
andblueforvehicles.

3.Thezonesongroundrelativestothescenario(s)denedonthecameraaredisplayedinblue.Inthisscreenshotthe
intrusionzoneisdisplayed.Inthepreviousscreenshot(theoneinsideSecurityDesk)onecameradisplaysanintrusionzone
andtheotherthetwozonesofaZone-crossingscenario.

4.Theapproximateactortrajectoryisdisplayedinred(foraperson)orblue(foravehicle).

Thesameoverlayisalsoautomaticallydisplayedwhenthecorrespondingrecordedvideosequenceisplayedback.

Bookmarks

SecurityDeskdisplaysbookmarksinthebottomtime-lineofeachtile(seetheorangelabelspointedbythearrowinthefollowing
image:eachoneofthemisabookmark):

Bookmarkscanbeusedtondthecorrespondingvideosequencesbyusingthe“Bookmarks”Task:

12

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

CustomEvents

CustomEventsinSecurityCentercanbeusedtotrigger,inturn,awidesetofpossibleactions.

IfyouwanttomonitorCustomEventsinSecurityCenter,youneedtocongurethecorrespondingcamerasas“monitoredentities”in
SecurityCenter.Proceedthisway:

1.IntheSecurityDesk,clickontheMonitoringtab.

2.ClickMonitoredEntitiesonthelowermenubar.

3.SelectthecamerayouwanttoreceiveCustomEventsfrom.

4.ClickAdd.

5.ThecamerasareaddedtotheMonitoredEntities:

13

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

6.NowdragdowntheupperpanelhandletodisplaytheCustomEventslistintheMonitoringtaskofSecurityDesk.

7.TheCustomEventsforthemonitoredcameraswillappearintheupperpanel:

14

AXISPerimeterDefenderwithGenetecVMS

VMSIntegration

Ifacameraismonitored,assoonasaCustomEventattachedtothatcameraisreceived,SecurityDeskwillautomaticallydisplay
thecameraintherstfreetileoftheMonitoringTask.Itispossibletocongurethemonitoredentitytobedisplayedalwaysin
thesametile:

15

UserManualVer.M1.5
AXISPerimeterDefenderwithGenetecVMS
©AxisCommunicationsAB,2016

Date:April2016

PartNo.1587513