Quantcast
Channel: Mitel MiContact Center Knowledge Base
Viewing all 959 articles
Browse latest View live

PBX programming related error messages for CCC softphone

$
0
0

Common CCC softphone error codes related to PBX programming

 

Problem

When attempting to start the softphone, you get the following error

Error type: eCommsError

Error code: -1

Operation:  RealtimeCallControlClient - WaitOnPendingWorkItem

Detailed message: System.TimeoutException: Softphone proxy server did not respond after 30 seconds

 

If you look at the Mitai proxy server logs on the server, you find the following error

eError: …              MiTAIEngine - SetExtnMonCallback:       Failed to monitor device - DN:[xxxx] ReturnCode:[SXERR_PRIVILEGE_VIOLATION] Hmon:[…]

Cause

The Mitai proxy server fails to set the monitor on the requested extension because it is associated to a class of service on the PBX that has it’s “HCI/CTI/TAPI call control allowed” and “HCI/CTI/TAPI monitor allowed” set to false

Resolution

Either modify the class of service for the associated extension so that the “HCI/CTI/TAPI call control allowed” and “HCI/CTI/TAPI monitor allowed” are set to true, or create a brand new class of service with the mentioned properties set to true.

--------------------

Problem

When attempting to start the softphone, you get the following error

Error type: eMitaiError

Error code: 1245

Operation:  GetForwardFeatureInfo

 

If you look at the CCC log, you will find the following error

eError: …              SoftphoneConfig::populateForwardingInfo:        Operation failed - MessageTag:[3] ReturnCode:[SXERR_FEATURE_NOT_ALLOWED]

Cause

The Mitai proxy server fails to set the monitor on the requested extension because the prime line for that extension is a part of a multicall group that is linked to other extension as well.  This causes the mitai monitor to be set on the group DN, instead of the requested extension.  Then, when trying to get the forwarding info for that extension, Mitai fails because it tries to get forwarding information from the group, which is not possible.

Resolution

Change the prime line of that extension to be a single line.  If the multicall group have to remain, simply create it as a secondary line appearance on the extension.

--------------------

Problem

After the CCC softphone is started, when attempting to use the ACD actions menu to log in as an ACD agent, you get the following error

Failed to login using the specified ACD agent, some of the possible reasons include are

                - The specified agent ID is used somewhere else

                - There is already an ACD agent logged in to this phone

                - This phone is not enabled for ACD login

 

If you look at the CCC logs, you will find the following error

eError: …              MiniPhoneView::mnuSubACDLogin_Click:            Operation failed - MessageTag:[5] ReturnCode:[SXERR_PRIVILEGE_VIOLATION]

Cause

The mitai proxy server fails to login the extension with the specified agent because the extension itself is not enabled for ACD

Resolution

Make sure the “ACD enabled” feature on the associated extension is turned on (NOTE: "ACD enabled" is not required when used with a hot desking agent)


HOWTO - Disable realtime summarization of Lifecycle Data but keep it available for historical reporting

$
0
0
Article ID:  - Last Review: December 1, 2015

ISSUE

Busy sites (sites meeting a “Large” configuration as defined in the System Engineering Guide) can experience memory resource exhaustion on the Enterprise Server due to a large amount of call data remaining in memory for use in LifeCycle reporting. The lifecycle engine by default will hold 2.25 hours’ worth of data in memory before flushing it to disk during real-time summarization.

Life cycle real-time summarization can be disabled which will prevent a current-day lifecycle reports from being run, but the vast majority of use-cases for LifeCycle reporting involve the need to run these reports against historical (ie, yesterday and farther back in time) data, and by following the steps outlined in this article, you can enable LifeCycle for historical reporting only.

RESOLUTION

Disable LifeCycle Reporting via YourSite Explorer

    • LaunchYourSite Explorer
    • Access the Enterprise | General Tab
    • Remove the check mark from the box "Enable Life Cycle Reports"
    • Click the save icon.

Enable Lifecycle for Summarization

1. Open the GlobalAppSettingsEditor.exe located in [InstallDir]\CCM\Services\ConfigService\.

2. Fill in the following details:

    • Application:  DataService.exe
    • Section Group:  enter prairieFyre.BAL.DataAnalysis.Properties.Settings
    • Name:  enter EnableLifeCycleHistorical
    • Value:  True
    • Description:  Add a note on why this is being changed.  NOTE: You must enter something in this field in order to save.

3. Click Save.  Note that saving these changescan take 30 to 60 seconds.  Wait until you get a confirmation screen toclose the GlobalAppSettingsEditor.

This will override the value for all client and remote machines.

 

Applies to

version 7.1.2.0 and higher

Keywords Lifecycle Life Cycle Historical EnableLifeCycleHistorical Global Application Setting Enterprise memory

ALM0001 - IVR File Synchronization error

$
0
0
Article ID: 51343 - Last Review: October 22, 2015

DESCRIPTION

An alarm 0001 will present itself when the sync of a prompt or workflow fails to be downloaded to any of the remote IVR servers. The alarm will display the name of the prompt or workflow as well as the server that failed to download the file.

SEVERITY

Warning.

IMPACT

Audio files will not be able to play from the remote VWM server resulting in a poor customer experience.

TROUBLESHOOTING STEPS

  1. Open YourSite Explorer and go to the Servers page.  Ensure that the remote IVR server is listed correctly.
  2. Attempt to save the file a second time.
  3. In YourSite Explorer click the Tools tab at the top and then click Re-synchronize clients.  This will attempt to force a download of all files since the last completed synchronization.


APPLIES TO

CCM/VWM/IVR

Keywords: ALM0001

ALM0002 - IVR Missing audio file

$
0
0
Article ID: 51344 - Last Review: December 1, 2015

DESCRIPTION

This alarm is triggered when the VWM Messaging service tries to access a .wav file that is no longer there, is corrupted, is saved in the incorrect format, or cannot be accessed for any reason.

SEVERITY

Minor


IMPACT

Audio files will not be able to play from the VWM server resulting in a poor customer experience.


TROUBLESHOOTING STEPS

Audio files must be saved in [INSTALLATION DIRECTORY]\CCM\IVR\Media\<language>\ where <language> is the specified language for the file (ie. EN-US for English United States).

 

APPLIES TO

CCM/VWM 

Keywords: ALM0002

ALM0003 - IVR Port Out Of Service

$
0
0
Article ID: 51345 - Last Review: December 1, 2015

DESCRIPTION

Ports will go out of service for the following reasons:

  • The port is in use by another application.  In this case will port will keep alternating between in and out of service.
  • MiAUDIO Lost connection to the PBX due to network issue.  In this case you will see that all ports will be out of service.
  • The port is not programmed right on the PBX.
  • During heavy call traffic some of the ports will go out of service, Mitel is currently working on this issue.

SEVERITY

Major/Critical

IMPACT

VWM will not be processing calls if the port is out of service. 



TROUBLESHOOTING STEPS

  1. There is a form on the ESM that shows the IP address of the PC using the port in order to find out where is the application that is hijacking the port.
  2. UAC must be disabled and appropriate firewall exceptions made for MiAUDIO.
  3. Ensure connectivity to the PBX is possible, either by pinging the controller or by reaching the ESM web configuration via it's IP
  4. Ensure the port has been programmed as a 5020IP set, and it's service type within User and Devices is set to Trusted. Also verify the MAC address has been populated accordingly, for example:
    • Port 1221 will have a MAC address of A1:21:00:00:12:21
    • Port 778965 will have a MAC address of A1:21:00:77:89:65:66 


APPLIES TO

CCM/VWM 

Keywords: ALM0003

ALM0004 - IVR Port Out Of Service count

$
0
0
Article ID: 51346 - Last Review: December 1, 2015

DESCRIPTION

This alarm will be triggered when the number of ports that go out of service exceeds 33% of the number of licensed ports.

SEVERITY

Variable

IMPACT

VWM will not be processing calls if the port is out of service.

TROUBLESHOOTING STEPS

Please follow the following steps for troubleshooting ports out of service;

  1. There is a form on the ESM that shows the IP address of the PC using the port in order to find out where is the application that is hijacking the port.
  2. Check to see if UAC is turned on or a firewall is blocking MiAUDIO from connecting to the PBX, also make sure you can Ping the PBX.
  • You could also make sure that the NetworkAdapter IP address programmed in the YSE can ping the PBX. [ Launch YSE -> go to Visual Workflow manager -> click Extension page -> click on the port, the networkAdapter will be the field named MiTAI/MiAudio Local Binding IP Address].
  • Make sure the port is programmed as a '5020 IP', its Service Type is 'User and Device' and its MAC Address start with 'A1:21:XX:XX:XX:XX' where XX XX XX XX is the DN of the port.
  •    i.e: port 1221 its MAC Address will be A1:21:00:00:12:21
            port 1109 its MAC Address will be A1:21:00:00:11:09
            port 778965 its MAC Address will be A1:21:00:77:89::65
            port 99887766 its MAC Address will be A1:21:99:88:77:66

    NOTE: Depending on which port is out of service, the IVRInbound, IVROutbound or Upiq service may be restarted to recover the system.



    APPLIES TO

    CCM/VWM 

    Keywords: ALM0004

    ALM0015 - IVR Bad Audio File

    $
    0
    0
    Article ID: 51357 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm is triggered when the VWM Messaging service tries to access a .wav file and is unsuccessful.  It can also be caused by a .wav file attempting to play after the audio channel has closed, such as when a caller hangs up before completing a menu and the system attempts to play the 'no input' audio file after.

    SEVERITY

    Minor

    IMPACT

    Audio files will not be able to play from the VWM server resulting in a poor customer experience.

    TROUBLESHOOTING STEPS

    The wave files must be in the proper codec format: CCITT, uLaw, 8khz, 8bit, mono.



    APPLIES TO

    VWM 

    Keywords: ALM0015

    ALM0016 - IVR Insufficient Outbound Ports

    $
    0
    0
    Article ID: 51358 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm is triggered when the outbound services tries to get an available outbound port to execute a workflow and they all are busy for a minute.

    SEVERITY

    Minor

    IMPACT

    Not having enough call back ports to handle the volume will increase the time it takes a customer to get a call back.

    TROUBLESHOOTING STEPS

    This issue can be resolved by reallocating ports, purchasing additional ports, or by adjusting when customers are offered callbacks. 



    APPLIES TO

    VWM/CCM 6.0.X.X


    NOTE: This event code will no longer be used in version 7.0


    Keywords: ALM0016

    ALM0017 - IVR Port in DND

    $
    0
    0
    Article ID: 51359 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm is triggered when the VWM port goes into DND and the system is not able to remove it.


    SEVERITY

    Major


    IMPACT

    When ports are in DND, VWM is unable to process calls.


    TROUBLESHOOTING STEPS

    Typically this indicates a problem in COS. Only RAD ports should have the ability to be set DND.  Please correct the COS settings according to our Golden Rules.

    • RAD Ports should be set to DND: True.
    • All other IVR ports should be set to DND: False

     

    APPLIES TO

    VWM/CCM 

    Keywords: ALM0017

    ALM0018 - IVR Port Not Answering

    $
    0
    0
    Article ID: 51360 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm will be triggered if the VWM delivers a call to a port, but the port does not answer it within a timeout period of 4 rings. 

    SEVERITY

    Major


    IMPACT

    This port will not be processing calls until the problem is corrected.


    TROUBLESHOOTING STEPS

    • This is often an indication that the MiTAI monitor is not set, or has been lost.  The reason the severity is a warning is because the auditor code is aware of this and will continously attemp to reset the MiTAI monitor, if this is the case.
    • Make sure that the MiTAI Proxy service is up and running.
    • Look at the MiTAIProxy Logs and check that ICP connection is opened to the corresponding PBX. [No SXERR_PBX_NOT_OEPN OR SXERR_SERVER_UNAVAILABLE]. 


    APPLIES TO

    VWM/CCM 

    Keywords: ALM0018

    ALM0019 - IVR UPIQ Port Deprived

    $
    0
    0
    Article ID: 51361 - Last Review: December 1, 2015

    DESCRIPTION

    The UPIQ service tried to access a UPIQ port from the configured port group but there were none available.

    SEVERITY

    Minor

    IMPACT

    Customers have not been played a message with the configured UPIQ message.

    TROUBLESHOOTING STEPS

    If this occurs often, more UPIQ ports may be required to meet the needs of the callers in queue.  Alternatively, you can assess which Queues are utilizing UPIQ and decrease that, or decrease the number of Positions in the UPIQ configuration that are being reported on. 



    APPLIES TO

    VWM/CCM 

    Keywords: ALM0019

    ALM0020 - IVR Phone Audio Error

    $
    0
    0
    Article ID: 51362 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm is triggered when VWM fails to initialize miAudio.

    SEVERITY

    Major

    IMPACT

    MiAudio will not function.

    TROUBLESHOOTING STEPS

    This is caused when we fail to initialize MiAudio.  This should rarely happen and signifies that something is not working properly. If it does, please create a support package and contact prairieFyre Support.

    APPLIES TO

    VWM/CCM 

    Keywords: ALM0020

    ALM0039 - IVR Calls Forwarded

    $
    0
    0
    Article ID: 51383 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm indicates that calls are being forwarded and not hitting the VWM ports.

    SEVERITY

    Variable

    IMPACT

    The calls are being forwarded and not getting to the VWM ports. They will not reach the callflow.

    TROUBLESHOOTING STEPS

    The Class of Service mapped to that Media Server has call forwarding on. In order to resolve the issue, please disable the Call forwarding option of the Class of Service that you are using for the affected ports.



    APPLIES TO

    CCM 

    Keywords: ALM0039

    ALM0042 - IVR Ports over licensed

    $
    0
    0
    Article ID: 51384 - Last Review: December 1, 2015

    DESCRIPTION

    Alarm notification that the user has created more VWM ports than they're licensed for.

    SEVERITY

    Critical

    IMPACT

    High if the customer assigns ports to a live callflow but the ports are not licensed and cannot answer the calls.

    TROUBLESHOOTING STEPS

    Ensure all ports that are assigned to call flows are licensed and that the site is not over licensed on VWM ports. 



    APPLIES TO

    CCM 

    Keywords: ALM0042

    ALM0045 - IVR Missing Callflow Activity

    $
    0
    0
    Article ID: 51430 - Last Review: December 1, 2015

    DESCRIPTION

    When the Ivr Engine tries to evaluate a YourSite Explorer Device such as a Queue, Extension, or Variable and it can not be found.

    SEVERITY

    Critical

    IMPACT

    If a caller reaches the part of the callflow that is referencing the missing device, the action will not be successful.


    TROUBLESHOOTING STEPS

    Check YourSite Explorer to ensure that the device has not been deleted.

    To fix this issue there are 2 possible solution remove the device from the callflow or add the device and modify the activity to select the new added device.

    APPLIES TO

    CCM/IVR 6.0

    Keywords: ALM0045  

    ALM0101 - IVR Insufficient outbound ports

    $
    0
    0
    Article ID: 51630 - Last Review: December 1, 2015

    DESCRIPTION

    This alarm indicates that all configured outbound ports are in use. 



    SEVERITY

    High 



    IMPACT

    The system is unable to process any more outbound calls. 



    TROUBLESHOOTING STEPS

    Possible reasons for running out of ports:

    1. There are more outbound calls queued than you have outbound ports to handle.  In this case, assigning more ports is the best solution.
    2. The call flow does not have a hang up or transfer activity at the end, and ports will stay in an established state indefinately.
    3. Ports are stuck in an established or in-use state.  Look at the device port and make sure the port is idle and that the inUse flag has been set to false.



    APPLIES TO

    CCM / VWM 6.0.1 and 6.0.1.1 only.

    Keywords:
    VWM insufficient outbound ports ALM0101

    VWM0001 - IVR Callback Make Call failed

    $
    0
    0
    Article ID: 51315 - Last Review: December 1, 2015

    DESCRIPTION

    This issue occurs when the callback services fails to successfully submit a callback to the queue.

    SEVERITY

    Error

    IMPACT

    All callbacks that follow this plan will fail.

    TROUBLESHOOTING STEPS

    This issue is typically a result of invalid configuration in the YSE. Verify that the Path Dialable Number that the service is dial is correct.  To do this:

    1. Launch YourSite Explorer.
    2. Go to the Incoming callfow that the callback request is being executed on.
    3. Check the Destination field on the Callback Request Activity to verify that the Destination field is correct.  It should match the Dailable of the Path as configured in the Mitel 3300. 


    APPLIES TO

    VWM

    Keywords: VWM0001

    VWM0002 - IVR Callback Calling Customer Invalid Phone Number

    $
    0
    0
    Article ID: 51316 - Last Review: December 1, 2015

    DESCRIPTION

    An Agent that was offered a callback request from the IvrOutbound Engine tried to connect to the customer and was not able to do so.

    SEVERITY

    Error

    IMPACT

    A customer who is expecting a callback will not recieve one.

    TROUBLESHOOTING STEPS

    This issue is usually due to what the customer entered for their phone number. There are a couple of things to check for:

    1. Phone Number containing an Area Code
    2. Phone Number not containing the long distance digit, for example in North America its 1, this should NOT be in the callers phone number


    If these are both correct, then this issue can be caused by the PBX not being configured to properly identify long distance, or international calls and appending a leading digit. 



    APPLIES TO

    VWM 

    Keywords: VWM0002

    VWM0020 - IVR Node is missing

    $
    0
    0
    Article ID: 51627 - Last Review: December 1, 2015

    DESCRIPTION

    The VWM Node is not appearing in the SQL configuration. 



    SEVERITY

    Major 



    IMPACT

    VWM records can not be filed.  VWM will not function properly. 



    TROUBLESHOOTING STEPS

    1. Re-run the CCM Configuration Wizard.
    2. Open SQL Management Studio.
    3. Open the CCMData database.
    4. Verify that the tblEnterpriseConfig_Node table is populated with a node entry for VWM.



    APPLIES TO

    CCM / VWM 6.0 SP1 

    Keywords: VWM0020 VWM Node missing SQL

    ALM0113 - MiTAI performed a hotrestart

    $
    0
    0
    Article ID: 51676 - Last Review: October 16th, 2012

    DESCRIPTION

    The MiTAIClient dll will reload if a certain threshold is reached for MiTAI errors.

    SEVERITY

    High 



    IMPACT

    MiTAI commands cannot execute and no MiTAI events are received.

    The following services and applications will not function:

    • IVR Routing ports will not process calls
    • Contact Center Softphone and Contact Center PhoneSet Manager will work partially if using soft phone but will not function if using a hard desk extension
    • Collector will not be able to carry out Interactive Contact Center commands

     



    TROUBLESHOOTING STEPS

    Change the threshold level at which MiTAI errors cause the service to reload the MiTAIClient dll.

    APPLIES TO

    CCM 6.0.2 

    Keywords: ALM0113 MiTAI hotrestart restart

    Viewing all 959 articles
    Browse latest View live