CallPilot AA Transfer Callback Timer

[Jason24]

Is it possible to disable the Transfer Callback Timer instead of setting it to a max of 12 on a MICS 6.1?
I have a CallPilot with AA configured and I'm trying to prevent the the message "The operator is not available. Exiting the system. Good Bye" from being played when the transfer timeout is reached (I assume this is what is causing this.)

Thanks in advance for the help!

Jason

 

[allworxguy]

The recall timer is absolute and can't be diasabled. It can be bypassed by using a Hunt Group

"Exiting the System" can be stopped by setting "Return to AA" = Y. Then on recall the caller will hear the AA prompt instead of being disconnected.

Or you can give your receptionist a mailbox.


Marv

http://www.telemarv.ca

 

[Jason24]

The recall timer is absolute and can't be diasabled. It can be bypassed by using a Hunt Group

"Exiting the System" can be stopped by setting "Return to AA" = Y. Then on recall the caller will hear the AA prompt instead of being disconnected.

Or you can give your receptionist a mailbox.

I am currently using a hunt group (707) which has all of the appropriate end user extensions added and configured to broadcast, but the timer still seems to be relevant.

I tried enabling "Return to AA," but this seemed to disable the operator function entirely. With this feature enabled and you press "0" you immediately get the response that "The Operator is not available" and it returns to the AA greeting.

I currently have all voice mail disabled and I really don't want to enable it unless I absolutely need to.

 

[allworxguy]

With this feature enabled and you press "0" you immediately get the response that "The Operator is not available" and it returns to the AA greeting.

That because you have no operator set in ATDT or "operator available = N" in F982.

am currently using a hunt group (707) which has all of the appropriate end user extensions added and configured to broadcast, but the timer still seems to be relevant.

Hunt Groups must set up correctly in order to bypass recall timers.

1. Any lines being transfered into a hunt group can not appear on the phones assigned to the hunt group.

2. Any lines being transfered into a hunt group must be assigned to the hunt group.

3. Adjust your hunt group queue timer and overflow settings.

In your case assign the ATDT = 707. If you set HG 707 to overflow to 707 it will ring forever provided you follow the above steps



Marv ccna

http://www.telemarv.ca

 

[Jason24]

With this feature enabled and you press "0" you immediately get the response that "The Operator is not available" and it returns to the AA greeting.

That because you have no operator set in ATDT or "operator available = N" in F982.

am currently using a hunt group (707) which has all of the appropriate end user extensions added and configured to broadcast, but the timer still seems to be relevant.

Hunt Groups must set up correctly in order to bypass recall timers.

1. Any lines being transfered into a hunt group can not appear on the phones assigned to the hunt group.

2. Any lines being transfered into a hunt group must be assigned to the hunt group.

3. Adjust your hunt group queue timer and overflow settings.

In your case assign the ATDT = 707. If you set HG 707 to overflow to 707 it will ring forever provided you follow the above steps

With your assistance I was able to correct "The operator is not available. Exiting the system. Good Bye" issue and now after 12 rings the call returns to the AA. – THANK YOU

Still working on the infinite ring situation though, I believe I made all the changes suggested, but I still eventually get "The Operator is not available" message and a return to AA. I will double check and make sure I didn’t miss removing a line from an extension, but is there anything else I should look for / modify.



Jason