RAMRAM2019
IS-IT--Management
Hello
How can I find out if a customer or Agent has dropped a call in Mitel?
How can I find out if a customer or Agent has dropped a call in Mitel?
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Where dropped a call? 1
- Thread starter RAMRAM2019
- Start date
- Status
-
1
- #4
Ok lets assume its a MIVB ver 9 or above and that you have SMDR correctly configured
By default, there is no indicator in SMDR to determine which party initiated the disconnect.
When enabled, the optional indicator < or > will appear in the 1st position in the SMDR
to indicate which party initiated the disconnect
< indicates MIVB/PBX side cleared the call
> indicates the far end/outside party cleared the call.
Note: The indicator overrides the long call indicator field (column 1) when enabled.
The indicator works for calls of 5 minutes or less.
The indicator will be ignored by MICC report ( i..e it is compatible)
[highlight #FCE94F] The command does not survive on MIVB reboot[/highlight]
MiVb 9.0 Process:
To enable the SMDR flag:
• Establish a SSH connection to the MSL IP
• Login as root
• Issue the following command: # /sysro/bin/debug-term
• Issue the following command: > smdr_disc on
• Issue a <Ctrl C> to exit the debug terminal
To disable the SMDR flag:
• Repeat as above with: > smdr_disc off
Make the test call and check SMDR
[highlight #FCE94F]>[/highlight] 08/16 02:29P 00:00:07 2002 624700 A X999
In this example, the ">" symbol indicating that the call was disconnected by remote extension 4700 via IP trunks.
If I never did anything I'd never done before , I'd never do anything.....
By default, there is no indicator in SMDR to determine which party initiated the disconnect.
When enabled, the optional indicator < or > will appear in the 1st position in the SMDR
to indicate which party initiated the disconnect
< indicates MIVB/PBX side cleared the call
> indicates the far end/outside party cleared the call.
Note: The indicator overrides the long call indicator field (column 1) when enabled.
The indicator works for calls of 5 minutes or less.
The indicator will be ignored by MICC report ( i..e it is compatible)
[highlight #FCE94F] The command does not survive on MIVB reboot[/highlight]
MiVb 9.0 Process:
To enable the SMDR flag:
• Establish a SSH connection to the MSL IP
• Login as root
• Issue the following command: # /sysro/bin/debug-term
• Issue the following command: > smdr_disc on
• Issue a <Ctrl C> to exit the debug terminal
To disable the SMDR flag:
• Repeat as above with: > smdr_disc off
Make the test call and check SMDR
[highlight #FCE94F]>[/highlight] 08/16 02:29P 00:00:07 2002 624700 A X999
In this example, the ">" symbol indicating that the call was disconnected by remote extension 4700 via IP trunks.
If I never did anything I'd never done before , I'd never do anything.....
- Thread starter
- #5
RAMRAM2019
IS-IT--Management
My software version is MiVB 8.0 and type of controller is 3300 Mxe III
I didn't find ""' indicates MIVB/PBX side cleared the call""
> indicates the far end/outside party cleared the call.
I didn't find ""' indicates MIVB/PBX side cleared the call""
> indicates the far end/outside party cleared the call.
ok for mivb 8 commands are different
Access SX2000 CDE maintenance terminal (telnet on port 23 with default sx2000 login credentials, not ESM's
Type: lldli smdr_disc on
Make the test call and check SMDR
If I never did anything I'd never done before , I'd never do anything.....
Access SX2000 CDE maintenance terminal (telnet on port 23 with default sx2000 login credentials, not ESM's
Type: lldli smdr_disc on
Make the test call and check SMDR
If I never did anything I'd never done before , I'd never do anything.....
It looks like there might be an error in the Rel 8 instructions corrected in highlight below
Access SX2000 CDE maintenance terminal (telnet on port 23 with default sx2000 login credentials, not ESM's
Type: [highlight #FCE94F]lldcli smdr_disc on[/highlight]
Make the test call and check SMDR
Access SX2000 CDE maintenance terminal (telnet on port 23 with default sx2000 login credentials, not ESM's
Type: [highlight #FCE94F]lldcli smdr_disc on[/highlight]
Make the test call and check SMDR
- Status