Open/Close Door Relay at Specific time using VMPro

[sceaton]

Hello!

I want to open the DOOR1 relay at 5pm every day.

My idea was to set a VMPro Alarm to ring a dummy extension at 5pm daily. Forward that extension to *40 to open the relay.

Dialing the *40 shortcode directly opens the relay as expected. Dialing the extension, however, rings busy and doesn't open the relay.

Any ideas on how I can accomplish this? Maybe something less convoluted?

Thanks!

~shawn

 

[DaIPOTek]

What version is the IPO? What does a monitor trace show?

 

[joe2938]

Why not just dial the short code as you stated that works

 

[sceaton]

IPO 9.1.5.145

SYS SC: *40 3  sc=type=RelayOff code=*40, num=1 callinfop->sending_complete=1 secondary_dialtone=
SCtype=RelayOff code=*40, num=1: Not permitted from Forward

So according to Monitor, it's not possible to modify relays from a forward.

Can I use a short code instead of an extension directly in VMPro Alarm module?

(I'm upgrading from embedded and still programming, so I don't yet have VMPro live yet to test)

 

[derfloh]

Isn't there a door relay action in VMPro? Never used it before to be honest...

 

[sceaton]

There is, but it only pulses the relay on for 5 seconds, then off. Can't specify to turn relay on/off with that module.

 

[derfloh]

OK, I see... But you can dial a short code from VMPro in any case.

 

[mforrence]

The user will be much happier if you simply get an Altronix timer/relay module for this task. They work, they work every day. No one can screw it up!

 

[budbyrd]

From my testing of the Alarm, it doesn't like to target dummy users, it wants to ring a phone and play a message. 9.1 fails targeting every time for me. I would be looking at an alternative solution.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[Gunnaro]

Alarms on phantom users stopped being reliable on R9.0 and higher (as did a lot of other things too).

Kind regards

Gunnar
_______
B.U.B.F

 

[Greybeard191]

9.1.5 Avaya turned off the ability to forward to a host of SC's.

Read tech tip 286
IP Office Technical Tip
Tip Number: 286
Release Date: 08 April 2016
Region: GLOBAL
Forwarding Calls to Feature Short Codes
It has come to Avaya’s attention that customers have been attempting to forward calls to Feature Short Codes. This may cause issues with the operation of IP Office. With the release of 9.1.5, Avaya have implemented restrictions to limit the Short Code features that forwarding will process. A forward to a non-permitted feature will fail and be processed as if there was no forward.
From the analysis of scenarios, it appears that simpler methods of configuration can be used. For example, in one scenario an incoming call route was configured with a User as a destination, the User was forwarded to a Short Code (*99*123#) which was a “ConferenceMeetMe” Feature Short Code. This can achieved more simply by configuring the Short Code in the ICR Destination, remembering to put the # in quotes, as # is a special character for matching X characters in the Incoming Number field:
As another example, to route a call to a Voice Mail Pro Call Flow, the Incoming Call Route destination can be configured as follows with the name of the Call Flow start point:
COMPAS ID 197926 Issue 2 Page 2 of 2
The following Short Code features can be used in conjunction with call forwarding:
 Auto Attendant
 Call Queue
 Dial
 Dial 64K
 Dial 56K
 Dial V110
 Dial V120
 Dial Video
 Dial 3K1
 Dial CW
 Dial Extension
 Dial Physical Extension by ID
 Dial Physical Extension by Number
 Display Message
 Fax Call
 Priority Call
 Speed Dial
 Voicemail Collect