Forwarding Twice

[rtetryyt]

I am wondering. Why can't i forward extension 3425 to 3136 and then forward 3136 to 3948. Theoretically if I call 3425 shouldn't the call make it all the way to 3948? I have a G3si. Thanks TJ

 

[Mitch672]

because a definity will NOT do double coverage. period.

mitch


AVAYA Certified Specialist

 

[dazling]

HI Avaya have specisl green field customers options that you can purchase and there is one for call fowarding to more than one destination.please speak to you business partner it is not expense
Hope this helps

 

[4merAvaya]

You can do coverage instead of forwarding. Create a coverage path for station 3425 with the first coverage point 3136. Make the 2nd point of coverage 3948.

Kevin

 

[hollye4488]

I have two legacy G3si's. Location A does not have vectoring enabled, so I've forwarded calls to a VDN at Location B for menuing and to capture VDN statistics.

Callers who select options 1,2,3 from the menu are then routed back through vectors (using route to xxxx) to Location A. This works great.

The problem I've run into is with the groups at Option 1 and Option 3:

Option 1 folks want the flexibility to have calls roll after 4 rings to a voicemail announcement, AND to be able to override this and route calls to an after-hours standard announcement on their switch on the fly… They are accustomed to forwarding their group number to Announcment xxxx at lunch and when they're not available.

Now that the main number is forwarded to Location B for processing, the second forward doesn't work as established in the posts above. I'd like for them to be able to toggle between two coverage paths, but haven't figured out how to do that yet. I'm using time of day routing in the vector at Location B right now as a temporary band-aid, but it doesn't give them the flexibility they want.

Option 3 folks don't want to ever answer their number at the desk. Instead, they want to alternate which cell phone calls route to. Now that forwarding doesn't work, I set them up with a fancy coverage path which routes calls to one coverage remote number or the other depending on whether or not Send Calls is active. Again, this works great when I call their number directly, but for some reason it ONLY routes calls to one cell, and not the other, even when Send Calls is active which is supposed the override the other one (as it does when I call directly).

Hopefully I've articulated in a way that will make sense to someone… I'm happy to provide more details if there's anyone out there willing to help.

Mich672 states above that Definity will not do "double coverage", but I don't see why I can't toggle between coverage paths somehow since one of them is working.

Still hoping...

holly

 

[Plumber123]

A neat trick that I've used was to create agents and skill sets. Have the group member login and out and write a vector to accommodate the desired route for either condition.


to prevent it is better than to have it to cure ..

 

[hollye4488]

That would be really cool - thanks for the idea. Unfortunately the switch at that location doesn't support vectoring.

This morning I was able to get the cov paths at Option 3 to work by forwarding the main number from Location A to Location B through the external cloud rather than across our point-to-point T1.

This successfully disguised the fact that it was a forwarded call. Unfortunately the signal was so degraded when calling in from outside, voice quality was significantly impacted, and the tones weren't coming through well enough to be recognized by the tone detector, so we had to revert back.

My next step is to try giving them a "toggle" between cov path 1 and cov path 2 by programming 2 feature buttons with the appropriate FAC and corresponding digit(s).

Wish me luck...

 

[SF0751]

I've done that - I program the buttons on the soft buttons for the 6408 set, and I prefix the digit string with ~s to supress the digit readout.

Susan
"When the gods wish to punish us, they answer our prayers." - Oscar Wilde, An Ideal husband, 1893

 

[hollye4488]

Thanks everyone - I've gotten it to work using the FAC.

(Note: The phone controlling cov path 1 vs cov path 2 has to have a COS with console permissions. ~s#7xxxx1 activates cov path 1, and ~s#7xxxx2 activates cov path 2 where xxxx = the extension being changed.)

Unfortunately while the person's cell associated with cov path 2 does receive the call as expected, the quality of service is really poor. I now think the issue though is with his cellular service provider, as the Blackberry on cov path 1 works great consistently. But that's a whole separate issue.