Having to restart messaging for failed transfers

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • pfoulk
    Aspiring Member
    • Apr 2015
    • 2

    Having to restart messaging for failed transfers

    Here is my problem: The Avaya CMM 6.0 messaging system is setup to route calls to various options. When a user dials in to the main attendant, they select a function that is supposed to transfer to a telephone extension. The system says "Transfer cannot be completed at this time" and promptly hangs up the caller.

    In order to "fix" the issue, we have to stop messaging and start messaging, which then the system functions properly for a period of a few days. Any suggestions?
  • mathew
    Hot Shot
    .
    • Aug 2010
    • 16

    #2
    Hi

    The possible reason for the transfer failure could be the unavailability of voice mail channels to complete the transfer and it may happen if you have stuck or hung Audix ports.When you do a stop and start all the ports getting free and it starts working again.

    Make sure you have the latest patches available for CM and CMM, make sure your configuration is correct.

    Also you can think of upgrading your systems to the latest release (6.3).

    Jeas Mathew | Office: +1 720 444 1508|E-mail: [email protected]

    Comment

    • pfoulk
      Aspiring Member
      • Apr 2015
      • 2

      #3
      Hi Mathew, Thanks for the reply. How can I see if the voicemail channels or Audix ports are hung? And do you know of another way to "fix" the issue other than stopping and restarting messaging/

      Comment

      • mathew
        Hot Shot
        .
        • Aug 2010
        • 16

        #4
        Hi,

        You can use the voice channel monitor option under server information menu on the messaging webpage. Also you can busy release the voice ports from the voice equipments diagnostics menu. Also you can busy release the signalling and trunk groups from CM. If you have some issues with the voice ports on the CMM you will find an alarm/warning in the messaging.

        Comment

        • jattwo
          Aspiring Member
          • Apr 2014
          • 2

          #5
          I would also inspect the maintenance log for any unusual errors. That could help point to a root cause.

          Comment

          • yadav29
            Brainiac
            • Jan 2013
            • 55

            #6
            please contact your System Administrator for further assistance.
            Rao

            Comment

            Loading