Component: Outbound Contact Server
Besides a record can set to campaign callback by agent (GAD, or custom softphone), it is also possible to configure directly from OCM.
Following is the step to hack it
- Set column record_type = Campaign CallBack. In export mode, or SQL*Plus, the value is 6
- Set column dial_sched_time to desire callback time with local timezone. This is EPOCH time in SQL*Plus, which is number of second since 1970-01-01 + timezone
- Set record_status = Ready. In export mode, or SQL*Plus the value is 1
Testing procedure:
- Login to GAD and change status to Ready
- Launch OCM. The callback record's record_status will always be Ready until it passed the time
- Wait for extra 1.5 - 2 minutes, and record_status will change to "Retrieved"
- Agent should get the callback record after retrieve a couple regular record
Other factors to consider:
- timezone is different, and needs to adjust the dial_sched_time to match local time
- daily_from and daily_till time is not within current time, so OCS won't pick up the record
- agent not login to GAD, but physical phone. Needs to use GAD or custom softphone
- configured wrong date in dial_sched_time. Used OCM to verify
In case troubleshooting is required, search OCS server log using following keywords
- Campaign name
- Calling list name
- @RecType = 6
- Buffer Size Coefficient Optimal value is set too high. Configure it lower
- RequestMakeCall
- 'Record_Type' 6
- Place name of the test agent
- EventUserEvent(PreviewRecordRequest)
- CallPreview[]::RequestMakeCall {
- message RequestDistributeUserEvent
- SQL: sp123423182267 @CampID = '123' (check log to determine the actual store procedure number, and cfg_campaign for the CampID)
Please use following PayPal donate if my post helped
1 comment:
Great Article, very useful here at...
Heating and Cooling Toronto
Heating and Cooling Bradford
Post a Comment