Routing Strategy with Collect Digits

Voice & Telephony
1

Hi Everyone,
I use an Alcatel-OXE with Genesys 8.1 , i try to create a strategy wich collect digits , but it’s not working.
When the call arrives to the Collect Digits block, cut the call and does not continues with the flow, i have this in the properties:

MAX_DIGITS : 8
START_TIMEOUT: 2
DIGIT_TIMEOUT: 5
TOTAL_TIMEOUT:10

Is there some configuration into URS for accept Collect Digits?

In URS logs i see this:

_B_I_00770221d744f005 [14:28] treatment===========>TREATMENT_REQUEST
15:28:03.033_A_I_00770221d744f005 [0E:0c] ----------->TMESSAGE
15:28:03.033_I_I_00770221d744f005 [09:04] <<<<<<<<<<<<suspend interp(WAIT_PLAY_TREATMENT), func:TreatmentCollectDigits timers:00000
received from 65200(TServerOxe)srvdatafono:13000(fd=) message EventTreatmentApplied
	AttributeNetworkCallID	28e023519a020100
	AttributeCallState	0
	AttributeCallType	1
	AttributePropagatedCallType	1
	AttributeConnID	00770221d744f005
	AttributeCallUUID	'42T92K4H312JR8M4DF78SM8D4S00000Q'
	AttributeDNIS	'29891'
	AttributeThisDN	'29891'
	AttributeThisDNRole	2
	AttributeThisQueue	'29891'
	AttributeCallID	666
	AttributeThisTrunk	269960
	AttributeTreatmentType	6 (TreatmentCollectDigits)
	AttributeReferenceID	27
	AttributeExtensions	[109] 00 04 01 00..
		'GCTI_SUPERVISED_TRANSFER'	0
		'GCTI_GLOB_CID'	bin: 28 e0 23 51.. (len=8)
		'BusinessCall'	1
		'GCTI_BUSINESS_CALL'	1
	AttributeTreatmentParms	[21] 00 01 01 00..
		'MAX_DIGITS'	8
	AttributeTimeinSecs	1361305683 (15:28:03)
	AttributeTimeinuSecs	38000
	AttributeEventSequenceNumber	00000000000000e6
15:28:03.038_T_I_00770221d744f005 [14:0c] EventTreatmentApplied is received for ts TServerOxe[Voice_Switch] (this dn=29891)
    _B_I_00770221d744f005 [14:21] treatment applied===========>TREATMENT_APPLIED
15:28:03.038_M_I_00770221d744f005 [10:1f] pulse for one call
received from 65200(TServerOxe)srvdatafono:13000(fd=) message EventAbandoned

Can anyone help me? ???

2

¬¬
Review configurations from other customers…or in your LAB…
Sonso

3

:-\ ..I export/import configurations from another customers where it works fine, and the strategy is the same.
But idk why the T-Server finished the call … T-Server listen RequestApplyTreatment send EventTreatmentApplied and inmediatly EventAbandoned.
Well … if anyone have an idea what could happening only post it ;D , i try to solve this issue by myself anyway.

Thanks

4

Configs have nothing to do.
Check well the Prompt tab properties. Drops usually happens when using a prompt/collect and the VG doesn’t exist or lack of resources.
Verify RP config (type=2)
Nothing else

5

The problem is solved ;D
In the readme of this PBX release, I can see there more than 5 issue on DTMF detection, we upgrade the PBX for J2.501 → J2.50.1.19.a and start to work fine.

Thanks for everything.

6

El pepe…jaja