Hello. We are using (MCD 4.1 SP2 - SW load: 10.1.2.13)We have external hot desking users that have been having issues with Mid-Call features (invoking them inadvertently i.e. placing calls on hold..handing off etc.). I changed the system options form to utilize Feature Access Codes and set them in the FAC form. Everything is working well with the exception of invoking the features i.e. Hold, Hold Retrieve, Handoff etc. I have FAC's for each feature and have all users with the appropriate COS. I am not able to invoke these features. Any suggestions as to what I might be missing? When we were using Mid-Call features we were able to put callers on hold, handoff etc. Thank you!!
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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Mitel-EHDU Assistance Feature Access Codes vs Mid-Call Features
- Thread starter acskmk
- Start date
What kind of trunking and what would the typical FAC codes you would be trying to use in place of the single digits? Do you also have UCA?
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
- Thread starter
- #4
kwbmitel: Yes. I read through all the help files. I appear to have everything correct as far as I can see but am unable to invoke the feature codes I set from our smart phones. LoopyLou: PRI trunks, Call Hold I set to *7, Retrieve to *1 essentially, *1 through *7 and I reviewed all feature codes so as not to conflict with others, checked timers, entered # to end search to ensure it wasn't waiting for another digit. The Mid-Call features worked just fine except that our users kept putting people on hold and if a particular pitch in their voice sent a tone it would put the caller on hold so we decided to move away from Mid-Call. Hope that helps. Thanks
- Thread starter
- #5
- Thread starter
- #6
New information. I just double checked the # entry following the handoff feature we have *3 and then #. it works as well as the transfer function. The issue now seems to be the call hold function and conference function. When placing a call on hold using mid-call features, we were getting our system moh. it doesn't appear to be working to put a caller on hold or conference. I'll double check the FAC's
Since you are on a cell then you are sending the FAC for the call hold down it. Wondering if you checked the COS of the trunks for the ability to conference etc? I know stupid question sorry.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
- Thread starter
- #8
Thank you LoopyLou. I did check trunk COS early on. All was as it should be. I found that the FAC for the Hold mid call feature was indeed a digit confliction. I corrected that and it is working fine now. I was also trying to utilize a FAC for hold retrieve but that was not the correct method of procedure. I didn't realize the way to take a call off of hold was to repeat the FAC used to invoke the feature..one in the same. I have also instructed our users to consistently use # to signal the end of the feature so that the system does not wait for additional digits. Thanks
- Status
Similar threads
- Locked
- Question
