Integrating Viking C-1000B door Controller to open door.

[getzjd]

We have a Viking C-1000B Door entry/paging controller. Right now it is hooked up to a standard analog wireless phone. To unlock the door, we take the phone off hook, dial #1 ** which initiates an unlock for our maglock system.

There is no dial tone when we take the phone off hook, just silence until we press #1 ** then we hear the confirmation beeps.

What I would like to do is try to put this in shoretel as an extension so anyone can unlock the door frmo their desk if they have a visitor at the front door. The visitor will then wait in the lobby for the employee.

Any Ideas?

Here is the instruction manual
http://www.vikingelectronics.com/pro...df/c-1000b.pdf

I tried a few things such as hook analog station directly to it and tried an analog loop start trunk. The instructions said something about a trunk which I tried creating and made the access code 88 just for giggles, but when I dial the #1 shortel system just disconnects.

[gberkemeyer]

You should be able to do the following:

Create a separate trunk group with one analog (probably loop start) trunk
Add an off-system extension to that trunk group
Add a custom Trunk Group dialing rule of ;1G;1I to the trunk group

Then when you dial the off system extension, wait 1 second, and then dial the #1 ** code, it should work.

From the ShoreTel Knowledge base, here is what the custom dialing rule does...

The first three characters tells the system to wait 1 second after going off hook and presume a connection even if dial tone is not heard. The second three characters tells the system not to outpulse the off system extension (e.g. 199) after the trunk is seized.

By the way, this is the same way you hook up a multi-zone paging system or any paging system that connects via a trunk.

Gary

[getzjd]

That is close... I made 2900 as the off system extension, trunk group, analog trunk....

I dial 2900, it connects, but when I dial #1, the shoretel phone goes silent, the c-1000B clicks (which tells me it received the #1 key sequence and is waiting for further instructions, but about 2 seconds later the shoretel phone is disconnected and back to a dial tone. Just seems that the #1 sequence causes the shoretel system to disconnect as the handset goes dead silent after #1 is pressed then is returned to dial tone.



The trunk appears to stay active as I can no longer dial the 2900 extension after this. As soon as I remove the analog line that runs to the C-1000B , the device clicks again which tells me it is back on hook and waiting to answer.


Here are the logs from trunk test:

11:12:18.143: Call State Idle --> Offering
11:12:18.143: Inside-ID Unknown --> 2283
11:12:18.143: Outside-ID Unknown --> 2900 (Unknown)
11:12:19.143: Port Seizing --> Dialing
11:12:19.377: Call State Offering --> Connected
11:12:19.409: Port Dialing --> Established
11:12:22.487: Digit #
11:12:22.940: Digit 1
11:12:26.237: Call State Connected --> Idle


Ideas?

[Palitto Consulting]

You might try setting up a digit translation table for that trunk group and translating 2900 to #1**. ShoreWare Director will not allow you to enter this in the UI, but you might be able to do it through the database. I have tested on 8.1 and it seems to generate correct tones.

[getzjd]

Can you explain how one would go about editing the DB?

However, if you translate 2900 to #1**, how does that go about working? The door controller is setup on a trunk and 2900 is that external extension.. If I just dial 2900 and it immediately translates 2900 to #1**, how would that work?

Some of you guys who know this system inside and out amaze me! I feel like a beginner!

[Palitto Consulting]

A translation table is applied after the trunk is chosen. You dial 2900 and ShoreTel chooses the proper trunk group. Without the translation table, it pulses the digits 2900. With the translation table, it pulses whatever digits you mapped to 2900. This is primarily designed for integrating with other phone systems, but has a multitude of other purposes as well. Consider translating 119 to 911, for example, which allows you to use 911 as a target of an auto-attendant. (We get some strange requests!)

Before 8.1, the database is an Access database and is in the Shoreline Data\Database folder. You can get a copy of Access and go open it up.

After 8.1 it is in MySQL and a little harder to reach. The method I usually prefer is to download a copy of OpenOffice and the MySQL ODBC connector (MySQL :: MySQL Connector/ODBC 5.1). Install the connector and OpenOffice Base. Under Control Panel->Administrative Tools->Data Sources, add a new data source using the MySQL driver, server localhost, username root, password shorewaredba. Open Base and create a new MySQL database file and connect to it via ODBC.

The table you're looking for is digittranslationentries. I recommend you stick a bunch of numbers in the field via ShoreWare Director so that you can locate the correct record. They will be in ReplacementDigits and OriginalDigits for that row will be "2900".

[TonyZ]

Viking Doorbox/Relay integration

I literally did this exact integration about 3 weeks ago for a customer using a very similar relay (the C-2000A) and a Viking E-20B (a simple push-button talkback doorbox). There are a couple "nuances" that are easily misinterpreted if you just try to follow the literature. I had noticed there wasn't really any posts on the forums with a solid recommendation of how to integrate a doorbox, and meant to post my steps hoping it would help someone later on. I was also able to avoid having to do any weird translation tables/funky programming as well. Most likely because it was a simple ring-in scenario that was requested.

Long story short - here's how it had to work for us.

First step - shoretel programming:

On the shoretel, create a new hunt group and label it "Doorbox Ring-in". Add whatever phones you want to ring when someone hits the doorbox button - I also recommend you make it "simultaneous".

Next, create a Trunk Group (Analog Loop Start) and label it DOORBOX. Set the inbound destination to the hunt group you just made.

Second step - Physical wiring

First and foremost, for the record, be sure to GROUND the relay!

Next, on the viking relay - wire from the "LINE OUT TO PHONES" port to the ANALOG TRUNK PORT on the Shoretel. (this is the part that threw us, because the way it's labeled in the viking literature, and even in a ShoreTel KB post, makes you think you need to use an analog station extension! But, the viking relay is actually generating dialtone out on this port when accessed, so you have to treat it as a loop start line. I actually confirmed this with Viking Tech support! - very misleading!)

Wire the remaining zones as needed for your doobox setup. In my example, we only had 1 front doorbox, so we wired the pair feeding the Viking Doorbox E-20B to the DOORBOX 1 input, then the maglock pair went to DOOBOX 1 STRIKE. This part you may need to mess with a little if you don't know if your maglock is in a "normally open" or "normally closed" position by default. The GROUND goes to the center pin of the three pins, but the other wire of your pair you may have to try at the left pin first, then the right if it doesn't work.


At this point, you should be able to go off hook on your doorbox (press the call button), and it should ring through to the shoretel hunt group. And, as long as the Viking relay programming hasn't been changed from its default config, once a user answers the phone and establishes the talk-path, pressing ** will release the lock.


Third Step - advanced tailoring because I'm anal about ring-ins

Inherently, 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. But, to do this, you must enter through **support** mode. Be warned, this enables some advanced settings in director that nobody should really mess with unless instructed by shoretel, but hey, who really pays attention to that??

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.

Also, keep in mind that the viking relay itself has various timers that can be programmed via its own settings - for example, you'll almost always have to increase the doorstrike activation time because for some reason viking likes to set it to 0.5 seconds by default. I normally set it to 3 or 4 seconds thereabouts depending on the options that the relay allows. On the newer viking relays, like the C-2000A which I used for the above install, you may also wantto disable the "caller ID passthrough" on the relay, because inherently it will want to pass caller ID to the system.

I hope this info will help someone at some future point - because doorbox integration is always a pain in the A$$!

[getzjd]

That's great information. Thank you for taking the time to reply. I will see if i can get ours working based on this information. The only difference is that we will not be using the door box, just a phone on a desk in a breezeway from which they will dial the extension of the person they are here to see.

Thanks again!

[TonyZ]

Shouldn't be a problem - just wire the lobby phone your using the same way as I had described wiring the doorbox I used (since they're both just an analog device) and operationally it should be exactly the same! Good luck!

[getzjd]

Well the lobby phone is a standard shoretel phone IP115. Has a rindgown to a auto attendant menu and such.

I was just looking for a way for someone to unlock the door from their desk and let their visitor in to sit in the lobby until the employee comes to greet them.

[luap]

funny tangent

I find it funny that jgetz - a senior member - is amazed by the comprehensive knowledge of TonyZ - a junior member

Little things make me chuckle

Tony, I work with Jay so I'm razzing him a bit :_tongue:, but thanks for a great post.

[bhaikalis]

Did you get this working? According to the KB13440, only the C-2000 is compatible not the 1000

[sreinert]

TonyZ post was correct and worked perfect with my two Viking E30 Call Boxes, especially the "Third Step" info...Thank you! We moved from a 3Com NBX where these were connected to analog line cards to a ShoreTel 12.3 and I connected these on a SG90.

[ctrl_alt_del3t3]

Do you guys know if this will work for the W-3000 viking system? I created a user and assigned them a port. Then i gave them delayed ring down of zero and an extension to forward to. When i press the button i does not call...

If i hookup a reg phone to the port it automatically calls to the forwarded extension desired.

[bkuhn]

Do you guys know if this will work for the W-3000 viking system? I created a user and assigned them a port. Then i gave them delayed ring down of zero and an extension to forward to. When i press the button i does not call...

If i hookup a reg phone to the port it automatically calls to the forwarded extension desired.

Is the W-3000 expecting an FXO or an FXS port?