atcomsystems.ca/forum
I am having a problem finding the correct method for callforwarding an ext. to a cell phone number for example.
I have tried every feature for forwarding in the user guide and i can't seem to get this feature to work.Callforwarding is enabled.
How about your trunk to trunk settings?
& possibly your device interconnection table.

------------------
Bound to cover,
just a little more ground.
I did find out that there must be a callforward access code dialed and also an abbreviated dial access code entered and here is where the external number would be located..I am not sure if this would work anyhow i thought i'd let you know what i have found.
does anyone know the correct command to activate the callforwarding external from the phone itself?
Thanks much...
Hey folks,
I am still looking for the correct procedure to activate external call forwarding from a 4025 superset.
Any help would be appreciated!!
Well, if you have Call Forwarding enabled in your class of service you can do the following to call forward external:

1: Create a system speed dial bin with the number that you want to forward to. Using the superkey select call forwarding always. Program the destination as the speed dial feature access code and the bin number. (For example, if 4 is the feature access code for speed dials and 66 was the bin number you would enter 466). Press save and then make sure that you turn it on. You can check this by going back into the call forward setup. If you see a * behind the destination it is enabled. If not use the softkey to turn it on.

2. This is a better way for the end user.
Program a speed dial key on the set. Program call forwarding as above but when propted to enter destination, press the button that you programmed and it will enter the number for you.

You cannot just enter a any number into the call forwarding for security reasons. This makes it a little harder for the end user to forward their phones where ever using up trunks.

You could also program a call forward always key on the set and toggle the forwarding on and off at your pleasure.

This feature will not work if the system is not programmed correctly. One way to check is the call the extension internally. If it forwards to your external number your programming is good for destination and what your set is allowed to do. If it does not work when you call from the outside, there is a programming issue with trunk to trunk transfer or device interconnect restrictions.

Hope I didn't lose you in my explanation.

Simon
Thank you very much MitelMan..This explanation helped me tremendously.
I will keep you posted on the results..Thank you for your time!!
Mitelman.

I've tried the same thing on my ICP 3300. But i can seem to get it to work. On the 3300 i can only find a personal invoke/store/remove feature access code. Is there a way to configure such a solution with only 1 button to be pressed? So i can configure several external numbers and forward all call to number on the PKM or phone programmed button?

Regards,

Keyracer
Keyracer, on the 3300 it is even simpler to forward to an external number. Use th superkey to select call forward always and enter 9+number as the destination and save and turn on.
Mitelman,

I've figured it out. The problem lies within the web interface. You cannot assign a feature access code and external number via the system administrator option to a button. But you can via the group administrator option.
Thanks folks for the updates to my question.
Now all i have to do is implement this feature and i am god to go.
This system is not very user friendly but hey we have to learn to deal with this unfortunate reality.
Have a happy Holiday!
Hi All,

It looks like I'm in the same boat, as when we program Call Forwarding - External (follow me) we cannot get it to work with outside calls.

We have selected the COS for the trunks and sets as described in the System Admin Tool, I have set the call forward always to an external set (my outside cell to simulate an external device.) Call from within the network work fine. Calls from another network via the IP trunks work fine. But calls coming in from outside do not.

This is a ramp up for a live system. Right now, we have one PRI that we are using, and they are all in one trunk group, using the same trunk service assignment, COS, and descriptor numbers.

My thought is that the problem lies with the handoff from TDM back to TDM, but I can't determine if it is a PRI issue or a ICP programming issue. We can dial in and out over the PRI no problem, CPN substitution works great, everything. Just can't get an external call, dialing an extension in the network that is forwarding calls to another external device to connect.

Any ideas? Thanks.
[QUOTE]Originally posted by rdpayne:
[QB] Hi All,

It looks like I'm in the same boat, as when we program Call Forwarding - External (follow me) we cannot get it to work with outside calls.

We had similar problems with a worker who wanted her phone forwarded to her home. It was also a long distance call for us. I think most of the problems happened outside our system. They seemed to caome back when she was on a call at home. Of couse my answer was to require her to stay at work and not work from home...
Check that your dpns to dpns connection is set to yes in the sta and trunk cos . Also make sure external trunk to external trunk in you sta and trunk cos is set to yes . Also check the cor of the trunks to make sure they are not ars restricted . Post back after checking . It's either a cos problem or a cor problem . Should be a simple fix . When using a PRI the dpns features come into play . Hope this was of some help . smile My Teleworker phone is off our 3300 and I can forward my teleworker number to my home phone via a speed dial key . So I know the feature works .
As mitelman said you must also check the interconect restrictions table and see if isn't an R (restriction) between the interconect number(s) of the two trunk (the incoming trunk and the outgoing trunk). And also check Public Network to Public Network Connection Allowed option enabled in the COS of the trunks and station.
I have ensured that Public Trunk to Public Network Connection and Public Network Access Via DPNSS are both set to yes on the COS for the set and the PRI Trunks.

The one place I was NOT looking was the COS for the Hunt Group that I placed all my Voice Ports into. I programmed my Voice Port Assignments, designating their numbering, Interconnect and Tenant numbers, then once I added the modified COS to the Hunt Group (this case 7300)it worked. The COS was modified for the sets and trunks, and once I checked it was the same for the Hunt Group, it worked just fine. Thanks guys...
© Sundance Business VOIP Telephone Help