OneX Agent v2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • winstonleong
    Aspiring Member
    • Feb 2011
    • 1

    OneX Agent v2

    Station login is working fine... 17387
    ACD login 31518 works too... using Other Phone mode to HOME Office.
    We get the confirmation tone.
    But right after that, it sends out DTMF tone 0.
    It then rings the Operator...
    How do I fix this?

    This only happend for REMOTE users.
    Here locally using the same information above... there is no issue.
    Last edited by winstonleong; 01-19-2012, 06:39 PM.
  • davis124
    Brainiac
    • Oct 2011
    • 50

    #2
    I know this is vauge but if memory serves me correctly it has something to do with how the Aux Codes are setup in One-X Agent causing it to dial the 0 you see. That's about all I can remember about that right now...

    Maybe my mind will clear up later to remember the whole thing!

    James
    James E. Davis
    10 years at Lucent/Avaya as a System Application Specialist
    4 years at Avaya as a TIER III Engineer
    Now working for UNMC as a System Admin/VoIP Engineer

    Comment

    • schaladoue
      Aspiring Member
      .
      • Oct 2010
      • 1

      #3
      Originally posted by winstonleong View Post
      Station login is working fine... 17387
      ACD login 31518 works too... using Other Phone mode to HOME Office.
      We get the confirmation tone.
      But right after that, it sends out DTMF tone 0.
      It then rings the Operator...
      How do I fix this?

      This only happend for REMOTE users.
      Here locally using the same information above... there is no issue.
      You would check the default AUX code in OneX configuration, the default should be some of your aux code is already configured in pbx.

      Comment

      • areminsky
        Aspiring Member
        • Apr 2012
        • 1

        #4
        Default should be Zero

        When setting up a new user, the Reason Code for "default" is "10". Then I added reasons 1 thru 9. So now I have a "1" followed by a zero.

        Had to change "default" to "0". Now I have Reason Codes 0 thru 9 and it doesn't call the operator.

        thanks for the help!

        Alexis

        PS: I added one-X Agent on 11 machines - all in-house (not remote users). Only 2 dialed the operator and had to be changed. The other 9 didn't have any trouble with this and are still working with Reason Codes 1 thru 10!
        Last edited by areminsky; 04-19-2012, 10:43 AM.

        Comment

        • simmersgeorge
          Aspiring Member
          • Jan 2015
          • 1

          #5
          Default Reason Codes

          Check the default reason code guide being used and make sure it is not using the guide for the newly created reason code 10. This is located in the AuxReasonCode.xml in the profile. This will cause the agent to then go off hook and dial 0 after ACD Login.

          Comment

          Loading