" /> AMD Detection - Genesys CTI User Forum

Author Topic: AMD Detection  (Read 3146 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
AMD Detection
« on: November 26, 2012, 06:59:38 PM »
Advertisement
Hello,

We are using ocs 8.1.1 and want to test the answer machine detection false positive/negative rates.
ocs allows us to use two new configuration options pa-amd-false-positive-rate and pa-amd-test-percentage.
If I set the percentage value to 100, all answer machine detects should route into the agent to verify call result detected by dialler.
However it doesnt because am-detected option in SIP is set to drop.
If I change this to connect, all answer machine detected results are routed to agent no matter what value I use in pa-amd-test-percentage.

Anyone had any experience of this, or what settings should be used?
Using SIP 8.1
MCP 8.1.2
OCS 8.1.1

Thanks.

Offline Flávio

  • Newbie
  • *
  • Posts: 32
  • Karma: 0
Re: AMD Detection
« Reply #1 on: November 26, 2012, 10:33:58 PM »
Hi,

i do not have much experience but i think i can help a little  ;D.

As far as i understand you must connect your calls because if you not (as you said) you will drop everything.

Check that:

The only possibility to continue processing other records from the same chain after a record with call result AM is connected to the VTD is to use Next In Chain or Next In Chain After Treatment for AM result. This feature is available from 7.6.101.11:
=>
Outbound Contact Server (OCS) now supports the application of the Apply to Record actions of Next-In-Chain and Next-In-Chain-After to the Answering Machine call result, whenever the Apply to Call action of Transfer or Connect is also configured for this call result. When the Answering Machine Detected call result is detected, the call is transferred to the specified destination and the next record in the chain is dialed.
To configure this type of treatment, combine the Apply To Call and Apply To Record actions in one Treatment object:
Configure these items as follows:
From the Apply to Call drop-down list, select Transfer or Connect.
Verify that the Apply to Record action is set to No Treatment.
In the Destination DN drop-down list, select the destination DN.
From the Apply to Record drop-down list, select Next-In-Chain or Next-In-Chain-After.
In the Number in sequence text box, specify a value of 1.
Previously, OCS only supported the Apply to Record actions of Update all records in chain and No Treatment, whenever Transfer or Connect was also configured for the Answering Machine Detected call result.
<=
In addition, it would be recommended to set the OCS parameter record_save_intermediate_result to true.

That is something i got from 7.6 version but i think can be of some help to use the same idea.

if does not work please let me know so i can research a little more.

cheers,

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: AMD Detection
« Reply #2 on: November 26, 2012, 11:11:02 PM »
Please check if outbound calls have special kvpair "GSW_CALL_RESULT_FEEDBACK = 1"?

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: AMD Detection
« Reply #3 on: November 27, 2012, 03:36:18 PM »
[quote author=bublepaw link=topic=7522.msg32249#msg32249 date=1353971462]
Please check if outbound calls have special kvpair "GSW_CALL_RESULT_FEEDBACK = 1"?
[/quote]

Yes it does
we also receive the periodic statistic reports under 12-50145 and 12-50146 log messages in ocs.
The issue is we cant apply the percent of nominated Answer Machines call results to agents.

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: AMD Detection
« Reply #4 on: November 28, 2012, 09:21:49 PM »
Just one more question even when You set pa-amd-test-percentage to let say 10 - each call has GSW_CALL_RESULT = 1? Or some don't have but they are still routed to agent?