Call Routing Getting Hung up on TOD Step in Vector

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • cgearhart1
    Member
    • Jul 2013
    • 6

    Call Routing Getting Hung up on TOD Step in Vector

    We are currently on CM 3.1.4 and have the basic call center. New VDN / Vectors have been programmed for a few groups and the calls are getting up on on the TOD step in the vector and are sending them to after hours calls. I can't figure this out because all of our other vectors are built the same way with TOD steps and they work just fine.

    Here is the trace I did on that vector (150) and the results:

    11:38:48 0 0 ENTERING TRACE cid 6577
    11:38:48 150 1 vdn e6148 bsr appl 0 strategy 1st-found override y
    11:38:48 150 1 wait-time
    11:38:50 150 2 goto
    11:38:50 150 3 goto
    11:38:50 150 3 time-of-day(4,11:38)+VDNTZO(00:00)+DSR(00:00)=4,11:38
    11:38:50 150 19 goto
    11:38:50 150 19 TRACE COMPLETE cid 6577

    Does anyone have any ideas? Any help would be appreciated.

    Christi Gearhart
  • tripathi1
    Hot Shot
    .
    • Jun 2014
    • 10

    #2
    Call Routing Getting Hung up on TOD Step in Vector

    Hi Christi,

    I would suggest you to open a service request with Avaya to investigate further on this issue.

    We might have to enable MST traces to investigate further on this.
    Hope this helps

    Regards,

    Anuj Tripathi

    Comment

    • richa164
      Guru
      • Oct 2013
      • 131

      #3
      It could well be a simple matter of corruption in the vector have you tried removing the logic and simply re-creating followed by a reset sys 4???

      Comment

      Loading