'Originator DN' for Outbound configuration

[Andrzej Belda]

I have set 'Origination DN' parameter (as DN of skill Hunt Group defined on PBX) for agent group. I've also set 'Origination DN' for the agent group in the campaign definition as DN of VDN defined on PBX. I've defined the VDN in the Genesys CME as Routing Point with 'switch specific type' = 2.
Then I run the outbound campaign. In the result I've received an error 'Invalid request: originator is not monitored' (for DN of the Hunt Group) in the log and none of telephones listed in the campaign list have started ringing.
The skill Hunt Group is defined in the Genesys CME as Queue with 'switch specific type' = 3

What could cause the 'Invalid request: originator is not monitored' error?
How to configure properly VDN and Hunt Group object for Outbound on PBX and in the CME ?

[gauthier]

Hi,
There are a few modifications that you could try. 1st of all from your message I see you are using a G3. For the G3 you VDN configured as a RP should have a 'switch specific type = 1' and your ACD Queue DN(Hunt Group) should have a switch 'specific type = 2'. Second when you setup your Origination DNs check the documentation because there is an order in which you have to set them up.

[Ramesh Pitchumani]

Hi Andrzej:

If you want the VDN in G3 to function as a Route Point, then you create the VDN in CME as follows: Type "Routing Point", Switchspecific type = 1. (Default setting)

If you want the VDN in G3 to function as an ACD Queue for reporting purposes as in CCPulse or in CCAnalyzer, then you create the VDN in CME as follows: Type "ACD Queue", Switchspecific type = 2.

While creating huntgroup extensions in CME, Create them as of type "ACD Queue" with switchspecific type = 1.

Basically if the VDN has the adjunct oute step and the waitstep, it can be created as a "Route Point" and Genesys can monitor it. But if you do not have these TWO steps in the VDN, but would still like to get data on that VDN, then you have to create it as an "ACD Queue" of switchspecific type = 2.

Thank you,
Ramesh.