Just to share some findings on BACD experiment. My BACD is both for the embedded BACD and the external TCL-based BACD (2.1.x.x) running on IOS 12.4(15)T.
I always think BACD is fairly straightforward and well-document. And, I have never come close to question the validity of Cisco's own BACD documentation. Step 27 *param* *second-greeting-time**seconds* Example: Router(config-app-param)# param second-greeting-time 45 (Optional) Defines the time delay before the second greeting is played after a caller joins a Cisco Unified CME B-ACD call queue. The same time period is used for the interval between repeats of the second-greeting message. The second greeting is stored in the audio file named en_bacd_allagentsbusy.au. To record a customized second greeting, see the instructions in the "Welcome Prompt and Other Audio Files" section<http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/bacd/configuration/guide/40bacd.html#wp1012403> . •*seconds*—Time interval before the second-greeting message is played or replayed, in seconds. *The range is from 5 to 120. The default is 60.* So, the document is saying, yes, you can set the value of the timer to between 5 and 120, go ahead!!!! The debug message is telling me different story however. I am speechless. I sort of know that BACD would be a bit flaky, but to tandem that with misleading/incomplete information on the documentation is just too much. I seriously thought it was a bug on the IOS version I used until I dig up a bit further and found that it is not a bug and I am not the only one who has encountered this. R1#call application voice load x-app-b-acd-aa R1# *Mar 1 00:08:43.951: //-1//HIFS:/hifs_ifs_cb: hifs ifs file read succeeded. size=37673, url=flash:/app-b-acd-aa-2.1.2.3.tcl *Mar 1 00:08:43.951: //-1//HIFS:/hifs_free_idata: hifs_free_idata: 0x667DE330 *Mar 1 00:08:43.955: //-1//HIFS:/hifs_hold_idata: hifs_hold_idata: 0x667DE330 R1# *Mar 1 00:08:51.175: //39//TCL :/tcl_PutsObjCmd: TCL AA: -- max-extension-length is set to default value of 5 -- **Mar 1 00:08:51.179: //39//TCL :/tcl_PutsObjCmd: TCL AA: ++ second-greeting-time is set to less than minimum allowed value of 30 ++* **Mar 1 00:08:51.179: //39//TCL :/tcl_PutsObjCmd: TCL AA: ++ Setting second-greeting-time to minimum value of 30 ++* *Mar 1 00:08:51.179: //39//TCL :/tcl_PutsObjCmd: TCL AA: -- Valid mandatory parameter second-greeting-time = 30 -- *Mar 1 00:08:51.183: //39//TCL :/tcl_PutsObjCmd: TCL AA: -- Valid mandatory parameter call-retry-timer = 20 -- *Mar 1 00:08:51.183: //39//TCL :/tcl_PutsObjCmd: TCL AA: -- Valid mandatory parameter max-time-call-retry = 180 -- *Mar 1 00:08:51.183: //39//TCL :/tcl_PutsObjCmd: TCL AA: -- Valid mandatory parameter max-time-vm-retry = 3 -- *Mar 1 00:08:51.183: //39//TCL :/tcl_PutsObjCmd: TCL AA: -- Valid Mandatory parameter number-of-hunt-grps = 1 -- *Mar 1 00:08:51.187: //39//TCL :/tcl_PutsObjCmd: proc init_perCallvars *Mar 1 00:08:51.187: *Mar 1 00:08:51.187: //39//TCL :/tcl_PutsObjCmd: TCL AA: +++ B-ACD-SERVICE not registered, Starting B-ACD-SERVICE +++ *Mar 1 00:08:51.207: %IVR-6-APP_INFO: TCL B-ACD: >>> B-ACD Service Started <<< *Mar 1 00:08:51.211: //39//TCL :/tcl_PutsObjCmd: TCL B-ACD: >>> B-ACD Service Started <<< *Mar 1 00:08:51.211: //39//TCL :/tcl_PutsObjCmd: TCL B-ACD: >>> Handoff String = x-app-b-acd-aa <<< *Mar 1 00:08:51.239: //39//TCL :/tcl_PutsObjCmd: proc init_perCallvars *Mar 1 00:08:51.239: *Mar 1 00:08:51.259: //39//TCL :/tcl_PutsObjCmd: TCL AA: ++ Playing Welcome Prompt and options menu ++ Note: Martin Sloan has sent out detail about another BACD timer's behavior that is also contradict to the documentation in http://www.mail-archive.com/ccie_voice@onlinestudylist.com/msg33344.html Regards, --Somphol.
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com