Hi
There must be some solution about this...there can be no bug in release 11.0.1 for abcf call release or attendant call release issue ...because there was no issue in previous releases i think only some system parameter will be managed..
Hi
As i know the "Attendant call release" feature added from release 11.2 so i think you must upgrade your system and it cost a lot of money .sadi_seemi wrote: ↑26 Dec 2019 02:01Dear..
Timer 260-2990......we set for timed release call...if any extension access trunk group directly ...call release work...from abcf...
but if attendant transfer outgoing call on abcf node extension call not released after set timer 260-2990.....
Our system release 11.0.1. Any idea brother...
Advance thanks..
fery_s wrote: ↑28 Dec 2019 01:07Dear fery_s.sadi_seemi wrote: ↑26 Dec 2019 02:01As i know the "Attendant call release" feature added from release 11.2 so i think you must upgrade your system and it cost a lot of money .fery_s wrote: ↑17 Dec 2019 01:30 as of release 11.2 time call release also apply for incoming call.
Timer no. 260 is used for public trunk and ABC-F call release
Timer no. 312 is used for QSIG call release
[/quote
Dear..
Timer 260-2990......we set for timed release call...if any extension access trunk group directly ...call release work...from abcf...
but if attendant transfer outgoing call on abcf node extension call not released after set timer 260-2990.....
Our system release 11.0.1. Any idea brother...
Advance thanks..
Attendant call release works ok ...when attendant through out going call to local same node extension...call release timer works ok ..call will release after timer set in timer 260...
The issue is if attendant through out gong call on abcf node extension call will not release after set timer in timer 260... It will be extension call release issue ....not attendant call release ..