Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Announced transfers

Status
Not open for further replies.

ltxn

Technical User
Nov 23, 2007
81
BE
I tried to search but didn't find much.

Some of our clients want the following:
A cascade for incoming calls first to the receptionist and then to the backup.
The cascade should work on the main number and everyone's ddi.
All phones have 2 appearances with reserve last CA ticked, except the receptionist who has 3, so she can take two lines at the same time.

Attempt 1:
For the receptionist I use a huntgroup and overflow for the backup.
For the colleagues I want to use the User/Forwarding/Forward On No Answer to the receptionist huntgroup.
To make sure the forwarding doesn't disappear with a *00, I change that shortcode.
Problem: When someone calls the main number and asks to be transfered internally after the no answer time the call comes back to the receptionist...

Attempt 2:
The main ddi still arrives at the receptionist huntgroup.
Every colleague has the receptionist huntgroup set as User/Telephony/Supervisor Settings/Coverage Group.
Problem: Only one level of the cascade will work, overflowing or forwarding to other destinations isn't possible.

Attempt 3:
For external incoming calls huntgroups are programmed.
Problem: A lot of the functionality is lost. No more personal VM boxes, the user has to chose between either forwarding or a second line.

Attempt 4:
Again make for every user a huntgroup, the huntgroups will have the old internal number and the users will have a new number. Then couple the ICRs with the users.
Problem: The phones will show a different number then the number that has to be dialed.

I haven't actually used the fourth attempt, the third I have, but I don't like to use it, because it is too complicated for something as simple as a transfer.

Out of the IPO Manager help files:[tt]Transferring Calls
The following are some of the methods usable to transfer calls.
· Supervised Transfer
This is a transfer where the user waits for the transfer destination to answer and talks to that party before completing the transfer, this is referred to as a consultation call. They then either complete the transfer or drop the call and return to the held for transfer call.
· Pre-IP Office 4.0
The initial consultation stage is presented as an internal call with internal call details and ringing.
· IP Office 4.0+
The call details, display, ringing and forwarding applied are appropriate to the type of call being transferred. [/tt]

Is there any other way I can make this work?
Otherwise Mr. Avaya can you change the behaviour of the transfer or make it an option. Or add a no answer destination for the ICRs. Or let the coverage groups overflow.

Thanks for reading :)
 
No I don't.
Sales tell me that it is quite expensive for most costumers, the license and hardware (pc or server).
 
btw, sales too afraid to sell VM Pro?

Its a good revenue stream!!

they can sell them

PC / Server to run it on
the OS
Licences.
Install time
and maintenance.

= nice money
 
I don't doubt they try to sell it, but if it comes down to sell an IPO without VMPro or a competitor selling one or another platform, there is no choice.
 
The best and easy way to solve the problem would be if it was possible to set a fallback extension in ICR if the call is not answered...
 
You can't really do that as it would cause confusion with many people what with forward on busy/ no answer and Incoming call route doing it too, which setting does it follow etc :)

ACSS (SME)
APSS (SME)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top