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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No Answer Recall Timer

Status
Not open for further replies.

ulforv

Technical User
Apr 13, 2010
77
SE
Hi.

I have a pbx with different user types in. when they transfer a call some of these users would like to have a longer time for ext to answer a call before it returns to the transfering unit.

the only place i can change this timer is on the COS for the trunks and I use COS, No Answer Recall Timer for this. but if i change here i affects all user types in my pbx. is there any other way so that i can custom make this for every user type.

hopefully someone understands my question.

Regards UO
 
forgott to tell.

system is mitel 3300MXe and sw release is 4.1. UR 1

//UO
 
Set COS.

The single biggest problem with communications is the illusion that it has taken place.
 
Hi, i have done that changes on the sets COS and also on every COS included in the call, for ex for huntgroups and so on. but the only COS that made any differece was on the COS for the trunk.

is this correct, I think it would have been the natural cos to change for the sets but for me that did not work, or should it?

Regards U
 
It normally should be the set COS because you are defining how long after the set transfered the call that it will re-ring the device that transferred it i.e the set. The trunks did not transfer the call so I would think there COS would not be the COS value that would matter. There was a COS option that was something like use the COS of the held party ( the trunk ). So if that is on that might explaing why the Trunk COS seems to be controlling the call. Thats my thoughts anyway.

The single biggest problem with communications is the illusion that it has taken place.
 
Hi, this text is found in a traning documentation for the 3300.

"If an Attendant Console or other station originally transferred a trunk call to the target set, and if the final alternative fails to answer, the call returns to the Attendant Console or station that made the transfer.
Before returning to the console or station, the call rings at the last alternative for the duration of the No Answer Recall Timer (NART). The NART is in the incoming trunk’s COS. Its default is 17 seconds, and only applies to incoming trunk calls."

-> LoopyLou

I have read and search for that COS option you talked about but no result. And the text i put in above, why is it design like this. would be much better if the sets COS was in charge of this timmer...

any idées for a work around?

Regards UO


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top