Saturday, January 7, 2012

Integrating A Viking RC-2A Into A ShoreTel System For Unlocking A Door/Gate

I am on a ShoreTel install and I have come across the need to be able to integrate two Viking RC-2A units into the phone system.  They will open the front door (which is locked all the time) by dialing digits on the phone after a call is made from the Viking unit (by pressing the call button on the box).  Also, they will use this to open a gate in the back of the facility for truck drivers and employees.  Same principle as the front door. 

To do this, we need an ShoreGear 30, so that we can make use of trunk lines.  We will tie these lines directly to the Viking unit.  See the topology below.  Also note that Im using ShoreTel 12.1.

In ShoreTel Director, this is real easy to setup.  For the Front Door, you configure ShoreGear 30 port 1 to be a trunk port.  For the Back Gate, I used port 2.  Two trunk ports for two separate Viking RC-2A units.  The Viking units have nothing to do with each other.  Two totally separate purposes.  Below is the first step, to configure the ShoreGear 30 for the proper port settings.

 Next, we configure a Trunk Group for the Front Door (and the Back Gate).  Make sure you put in a destination for the Inbound destination.  When they push the call button the on the call box, the call has to go somewhere.
 Make sure you have destinations that are valid. You dont want it going to an extension that is a mailbox only, or something odd like that.
Thanks to a post in the ShoreTel forums (ShoreTel sponsored, not the one I got banned from), I learned something that may be important.  I read a post from a guy named TonyZ that talked about callerID on a trunk group. What he said makes sense to me, so I followed his advise.  By the way, thank you TonyZ for your help in the forum.  He says the following:  "the Shoretel wants to listen for caller ID on the trunk, so it wont let the doorbox ring through immediately. So you have to disable this in the Shoretel trunk group."  Well, Im happy to follow his advice, and here is what he says about how to do this:
 "At the DIRECTOR login screen, hold shift+ctrl+alt and click the text that says "user id" - it should now say **support entry** in red below the login. Now just log in as normal. "
" Go to the DOORBOX trunk group, and at the very bottom there's a new field that says "custom" - click the EDIT box. In that window, type in ;1L (semicolon, the number one, capital L) - it has to be EXACT. Then save. This will stop the analog trunk group from looking for caller ID and let it ring through right away."
***NOTE***  I did this and I ran into no issues at all that I had to battle, dealing with this in particular.  Again, Thanks TonyZ for your post in the forums.

Make all you physical connections, as shown similarly in the topology above.  This involved 66 blocks, etc, but you get the idea in the above topology.

Now for the Viking RC-2A unit settings.  For my install, this was already integrated with an Avaya system.  So, I figured the settings were correct just the way they were.  Here is a picture of the settings.  If you cant tell for sure, dip switches 1-5 are down, and 6 and 7 are up.  The three potentiometer looking things are actually settings.  All three of mine are on "D".  Yes, that is sunshine in the picture below.  That thing is in an underground box outside.

 Now, here is what happens.  Ill use the back gate as an example.  When someone presses the button on the call box by the gate (before entering), it rings the analog phone.  Once you are on the phone, you can dial in 16 to open the gate (or the front door).  The gate opens and the front door unlocks (separately of course).  Guests are welcome to come in at this point.  You do not have to do anything else.  NOTE THIS*** You will want to know, you can not dial the Viking unit directly, that I am aware of (at this point anyway, TAC is working on this capability in my case).  So, how do you initiate a command to the Viking without someone calling from the call box?  Read the next paragraph.  Why would you want to do this?  Because if an 18 wheeler shows up a the gate, its too tall to reach down to the call box made for the height of cars.  Its useful for the security guard to just pick up the phone and dial the code so as not to inconvenience the truck driver.

When the security guard wants to initiate a command to the viking unit, like opening or closing the gate, they press 807 to access the Viking unit (807 is what they had before on the Avaya).  Once you have dialed in, you get a secondary dial tone.  You then press a code (we did 16) on the dialpad and then press #.  Hang up the phone, and in about 2 seconds, the phone rings and you pick it up and dial the code (16 to open the gate in this case).
Now, something that really got me on this second Viking, where I was trying to get the Back Gate to work.  I had a very hard time getting this going.  When I went to the outside call box and pressed the button, it never rang the phone inside at the security station.  However, I knew it was working, because I could take an IP phone and dial the analog phone, and it would ring just fine.  So, why wouldn't the call box ring the analog phone?  Because I had punched down NOT the analog phone wrong, but the Viking unit.  But, it was on the ShoreGear 30 side where I punched it down.  So, if you look up the amphenol cable's pinout (which I listed in another post on this site), it shows pins 1 and 26 as blue/white, blue.  Pins 2 and 27 are orange/white, orange.  Makes sense to me that we would use these two for ports 1 and 2 on the ShoreGear 30.  However, the ShoreGear 30 does not line up that way.  See below for the pinout to port chart.  For some reason, they use pins 3 and 28 for port 2.  I have no idea why, but this really had me stuck for several hours until TAC pointed that out to me.  Ugh.

 I hope this helps.

NOTE ADDED 4/10/2013*** I ran into another RC-2A that was slightly different.  I posted about that install here.