" /> PBX Avaya ECS (G3) configuration for OCS - Genesys CTI User Forum

Author Topic: PBX Avaya ECS (G3) configuration for OCS  (Read 4698 times)

Andy

  • Guest
PBX Avaya ECS (G3) configuration for OCS
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Please, send me an example of PBX Avaya ECS (G3) configuration for Genesys Outbound Contact. I'm not going yo use predictive dialing no CPD use. I' like to start outbound campaigns in progressive mode.
Please, send me info how to configure PBX objects and setup related objects in Genesys system.

gauthier

  • Guest
PBX Avaya ECS (G3) configuration for OCS
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Even if you are just doing Progressive dialing, you need to use Call Process Detection(CPD). However the AVAYA swith have this functionality integrated through Call Classifier cards.
    As for the configuration what you have to do is configure on the switch a VDN that sends the call to a vector, that does a Route to 1st Skill.
    Program a Hunt group where your agents are going to log into.
    assign the skill linked to your hunt group to your agents.
    In Configuration Manager Create your VDN as a Routing Point and your hunt group as an ACD Queue.
    Create an Agent Group and in the origination DNs set your RP and ACD Q. Check the Genesys OCS documentation to know in which you have to add them.

    Andy

    • Guest
    PBX Avaya ECS (G3) configuration for OCS
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • I've not found any informatin in the Genesys documentation that CPD is mandatory for Outbound. Is there any other campaign mode in Outbound (other that progressive) that does not need CPD ?

    Offline Gururaj S

    • Newbie
    • *
    • Posts: 13
    • Karma: 0
    Re: PBX Avaya ECS (G3) configuration for OCS
    « Reply #3 on: December 15, 2008, 07:28:04 AM »
  • Best Answer
  • We have configured predictive dialing with Genesys Outbound

    suite and Avaya pbx which has call classifier.



    But when we run the campaign we get A_NO_CLASSIFIER

    error. I have attached a sample log for the scenario.

    We would be thankful if you can have a look and suggest any change.


    Thanks in advance!