sundance-communications.com/forum Forums TDM Business Telephone Systems Inter-Tel Telephones & Systems program key - macro or dial string?

Hi, I want to program a button on IP set 8622 to automatically dial the following:
359
(extension)
(password)#
355
(extension)

I tried to set it as a speed dial but the speed dial entry terminates on the #.

Is this possible?

19 manual entry key presses might be too much for some of our users to handle.

Try building it under personal speed dial in on line monitor. Use a capital P for pauses, that should fix the problem. I have this programmed for a customer and it works If you need I can access the database and see exactly where I put the pauses to get it to work. I remember taking about 3 tries at it to get it to work every time. I think it is something like 395P(phantom ext)P (password#)P 355 P(HG I'm sending calls to)
Let me know If I need to look it up. E-mail address and phone number are in my profile
Randy

Thanks Randy! That worked. The value field for a station's speed dials seems to be limited to 15 characters so with no pauses and 4 digit extensions I can get right up to the remote forward command, meaning the user has to enter the last 4 digits - the forward destination.

After trying it though that works perfectly for us because I can now use one button plus the forward destination to forward calls to anywhere the user needs. That really works great.

Thanks again!

For anyone else trying to make sense of this, here is what I am doing:

DID > STAR (day hours) > CRA > PHANTOM > HUNT GROUP

Instead of going CRA to HUNT GROUP directly, we are trying to use a phantom to control forwarding.

The specific application is this. If agents in the hunt group need to leave early, they can forward (via the phantom) calls to another phantom which is call forwarded to an on-call mobile phone.

The volume of calls is very low so this works fine.

Why not use night mode you might ask? We already use night mode for another functionality so this is kind of like having two night modes in a sense.

With several phantoms forwarded to several mobile phones and with several other hunt groups available we have a lot of flexibility here.

I use DND for this function as well, with the DID pointed directly to a keyset. I create two forward points for Call Routing Table only.

The first forward point is DND forward to the phantom.

The second forward point is immediate forward to the hunt group (or an auto attendant).

When the keyset is put into DND, DID calls forward to the phantom. Otherwise, DID calls route to the hunt group or auto attendant.

The keyset functions normally for all other calls, except DID. Since most receptionists don't have a "private" DID number, this works well.

I have sites where offices have different business hours, but share a PRI. Using a "steering extension" is an easy work-around for night mode.

Hey that's a great trick. Thanks! If I had thought of that beforehand, I might have done it that way.

dhostetter
Glad it worked out, you were trying to do exactly what we did for a customer. The DND deal also works great have it as well as other forwards built depending on status of the phone and where the call came from.
Randy