" /> Feature NotSupported ISERVER72/IVR - Genesys CTI User Forum

Author Topic: Feature NotSupported ISERVER72/IVR  (Read 3670 times)

docherp

  • Guest
Feature NotSupported ISERVER72/IVR
« on: September 28, 2006, 01:59:29 PM »
Advertisement
Call is released with this message. I have this working well on a local model, then attempted on remote system but fails. All looks identical, all s/w identical.

Offline Adam G.

  • Hero Member
  • *****
  • Posts: 552
  • Karma: 12
  • Still Gorgeous.......
Re: Feature NotSupported ISERVER72/IVR
« Reply #1 on: September 28, 2006, 02:13:33 PM »
Can you tell us which IVR you are using, which PBX and if it's TDM or IP?

Regards,

Pavel

Marked as best answer by on Today at 11:27:25 PM

docherp

  • Guest
Re: Feature NotSupported ISERVER72/IVR
« Reply #2 on: September 28, 2006, 03:54:03 PM »
  • Undo Best Answer
  • S/W =IVR_SERVER, ISERVER, PREMISE TSERVER7.2, on IVR MPS5000 (Nortel, previously Periphonics) using a SunFireV210/Solaris10. DMS100 - Nortel Switch - IP. Configured a driver "peri_1" in CME with ports 1-31. This can be caused by typo's but looks fine. Suggestion by Genesys we should use Port 0, but working model starts on Port 1.

    docherp

    • Guest
    Re: Feature NotSupported ISERVER72/IVR
    « Reply #3 on: September 29, 2006, 08:25:53 AM »
    Configured as Virtual Switch fir IVR In-front

    docherp

    • Guest
    Re: Feature NotSupported ISERVER72/IVR
    « Reply #4 on: October 12, 2006, 09:08:41 AM »
    Problem solved, basically a complete a mismatch/alignment of lines configured in CME with ACD Positions being incorrect, you must start at 1 and not zero. Configured 16 to start with (1-16) after finding that we were supplied with incorrect ACD Positions. Restarted tappman on MPS IVR, the the mps driver and set all configs set start at 1.