Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: VinceWhirlwind on December 18, 2017, 11:36:57 PM
-
Is there some kind of a trace I can run during one of these calls that will give me some clues as to why it is going on hold?
-
Is there some kind of a trace I can run during one of these calls that will give me some clues as to why it is going on hold?
ccs trace continuous
But this probably won't tell you very much, but it might tell support... Many years ago I remember a doc that told how to read those codes, but I am talking like release 6 or 7 (not MCD, the old releases) and I haven't seen one since.
Common culprits are the phone itself and MiCollab Client, otherwise I haven't really heard of this occurring.
-
I need to run a CCS trace out of hours and try to capture a deliberate "hold" event to see what it looks like.
I was running one yesterday during a call but there was nothing in the trace that had any reference to the extension involved. (Trace started after the call was setup).
MiCollab is being used to dial, and it's an EHDU, so not entirely sure how that will show up in the trace.....again need to run it out of hours to see what an EHDU looks like in the trace.
I suspect the phone as well - it must be sending mid-call features.
-
headset in use?
-
Yes, but it's a headset on an EHDU (mobile phone) device.
I've put her on a new CoS that has mid-call features disabled to see if that stops it.
-
There was/is a bug I think where if you are moving between cell towers the caller can be put on hold.
Disabling midcall features should stop it.