sundance-communications.com/forum Forums TDM Business Telephone Systems Inter-Tel Telephones & Systems Is there a way to turn on call forwarding remotely?

Working on an InteTel Axxess 5.352 system. Customer wants to forward calls to his cell phone. We've verified that it's working when doing it manually from the phone itself using the fwd key.

Is there a way the customer can call-in to the system to turn it on and off for a specific DID?

Upon further reflection/research, I guess my real question is... how do I program their trunk for DISA? As far as I can tell, there is no access number assigned to the trunk.

You could program a DID for DISA, and use the Remote Programming feature. It's real kludgy, and I would expect the end-user to screw up about 50% of his attempts to use it.

No doubt... but, they want it, nonetheless.

I've assigned a DID to DISA via call routing tables. When I call it all I get is consistent tone... must be missing something.

I need a little direction. From what I can piece together the DISA not only needs a number assigned, but needs to be assigned to a CO Trunk Group. Correct?

They've got 9201 assigned as their "Main T1" with day/night programming assigned to all stations. It contains all the trunks - 7 of them. Then they've got "PP011" with the description "unused CO trunks", but there are no trunks assigned to the group.

Where do I go from here? I don't know where to program the DISA to or how to setup a security code for it.

The constant tone is the DISA dial tone.

The DISA security code is programmed in the trunk group. To the very right side of the screen, at the ring in destination, you can enter the security code.

If you are getting a solid tone, that is correct.



You are correct that the security code for DISA must be set up on the trunk group. The problem is that you would have to assign all 7 channels of their T1 to this trunk group set up for DISA, as every time a DID is called, it does not necessarily come through on the same channel. This would obviously not be a viable solution as you would have effectively aimed all of their incoming lines to DISA. Not only is that a security risk, but now no calls are routing.

Your best option (other than talking them out of this as DND ON alluded to) would be to use an unused loop start line that you could assign to its own trunk group. This would require that they have an LSC card in the system of course.

Other than that, you could use a DID like you mentioned but would not be able to assign a security code.

The rest is just remote call forwarding just like you would do from an internal phone. You can find out how to do that in the manual or possibly on a search within this forum.

Looks like DND ON responded before I could finish my post. Sorry to talk over you.

Thanks. Got the security code in there.

Following these instructions (below - from Stix1) with no luck. At Step 4 I enter 355 + 8 (for outside line) + my cell with area code. Then hang-up. I tested from an outside line and it just rings through to the company voicemail. Tried again, this time hitting # after the feature code... still no luck.

Remote Call Forwarding

The Remote Call Forward Programming feature allows you to forward a station’s calls, either from another station or through DISA. Each station has a password to limit access to this feature. This feature is handy if you need to make changes from a remote node or from your IP phone.

1. If calling from an outside telephone, access the system through a DISA line and enter the Remote Programming feature code (359). Or, from another extension, just enter the Remote Programming feature code (359).

2. Enter the extension to be forwarded.

3. Enter the extension’s password, followed by #. (This password defaults to your extension number, but you can change it.)

4. To turn on Call Forward enter one of the Call Forward feature codes. To turn off Call Forward, enter feature code (355) and then hang up instead of entering a destination.

Call Forward All Calls (355)
Call Forward If Busy (357)
Call Forward If No Answer (356)
Call Forward If no Answer/Busy (358)
5. Enter the forwarding destination.

6. Hang up to complete the programming.

To reiterate what DND ON said, calling in from an outside line to do this programming is extremely unsuccessful. To be honest, I think a 50% success rate is even a little high.

Your best bet would be to practice the remote call forward from an internal phone to the phone that needs to be forwarded. Don't do it through DISA at all. This will give you the proper keystrokes that need to be performed. You will know that you did it right because the phone in question will show "All calls forwarded to 1-123-456-7890" i.e.

Get at least that part correct before trying from the outside.

After attempting the DISA call forwarding, look at the telephone display. It should tell you what’s happening with that station.

Also, check the station flag to make sure that manual PSTN forwarding is allowed.

Thanks for clarifying a lot of this!

So... using DISA securely requires an unused, dedicated channel ...which basically counts it out for this customer.

If I'm understanding all of this correctly... if I leave the DID I assigned to DISA in place and remove the security code from the trunk, then I should still be able to dial-in to DISA and enter 359 to do some remote programming.

Is anything else required?

It seems like I'm in the system, but as soon as I enter the password for the extension I'm trying to change I hear 5 tones, whereas every other time I hear two tones. I take it that 5 tones means something is off... because it seems to go downhill from there.

I'll try on-site as you've suggested.

It doesn't seem viable for the end-user. But, it would be nice to have available for emergency use.

Otherwise... I can access DB Studio remotely via terminal server... is there a way to forward or unforward a DID from there if I had to do it in a pinch?

Since your trunk group is pointed to a Call Routing Table, you do not need to dedicate a channel. POTS lines would be a different story.

You can change forwarding with DB Studio via On-Line Monitor, under Forward Information on the station. Be very careful with OLM, you can do real damage.

I'm not familiar with On-Line Monitor. Is it an add-on to DB Studio? If so, where I can I get it?

I figured out my DISA issue on-site. I had assumed the password for the extensions either matched the v/m password or was the extension itself... and that was not the case at all. I have no idea what they were set to, so I simply changed the passwords. Then everything fell into place.

I also see now that "on-line monitor" is there as an option in DB Studio. I've been using DB Studio for years and never realized that on-line monitor existed. Whaddya know? I'll carefully poke around in there.

Thanks for the help! You guys are great.

My users tend to find doing remote forward is easier when done over a VoIP phone extension. Most of my users that would want remote forward (either to cell or remote VoIP extension) already have a VoIP extension remote where they want it.

But it does eliminate the DISA part.

We're talking about an obsolete Axxess 5.3.

If this was a modern system, you'd use Configuration Assistant and call it a day.