[Home]

Summary:ASTERISK-22829: AMI Atxfer not working with alphanumeric extensions
Reporter:Alberto Rinaudo (Syco)Labels:
Date Opened:2013-11-06 10:28:49.000-0600Date Closed:2013-11-06 10:38:18.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/ManagerInterface
Versions:SVN 11.6.0 Frequency of
Occurrence		Constant
Related
Issues:
is duplicated byASTERISK-26440 ami: AMI atxfer not accepting alpha numerics
Environment:CentOS 6.4 64bitAttachments:
Description:The ami command Atxfer relies on the general atxfer confured in features.conf.
in manager.c lines 3897/3904 there's the piece where it queues the digits as dtmf in the channel:
{code:title=manager.c|borderStyle=solid}
for (feature_code = atxfer_feature->exten; feature_code && *feature_code; ++feature_code) {
struct ast_frame f = { AST_FRAME_DTMF, .subclass.integer = *feature_code };
ast_queue_frame(chan, &f);
}

for (feature_code = (char *)exten; feature_code && *feature_code; ++feature_code) {
struct ast_frame f = { AST_FRAME_DTMF, .subclass.integer = *feature_code };
ast_queue_frame(chan, &f);
}
{code}

So when you call
{code:title=AMI command|borderStyle=solid}
Action: Atxfer
Channel: Agent/7001
Context: atxfer
Exten: a7002
Priority: 1
{code}
in a telnet console, 'a' is filtered away from Exten resulting in a wrong transfer to '7002' and not 'a7002'.
Comments:By: Matt Jordan (mjordan) 2013-11-06 10:37:28.276-0600

This is a limitation of the Attended Transfer AMI action. It does not, at this time, support transfers to alphabetic extensions. It is essentially an AMI variant of the existing Attended Transfer DTMF transfer.

This is not a bug, but is a limitation based on the design of the feature. If someone wanted to improve the feature by not using the DTMF attended transfer code as the implementation that'd be great, but that would be an improvement to the overall AMI action.
By: Matt Jordan (mjordan) 2013-11-06 10:38:18.561-0600

I'm closing this out for now as "Not a Bug", as this is how this AMI action was designed to work. If you'd like to provide a patch that modifies the internal implementation to use a different mechanism for performing the transfer, we'd be happy to reopen the issue as an improvement.
By: Alberto Rinaudo (Syco) 2013-11-06 11:46:44.519-0600

http://pastebin.com/8hX9y7ZR

From the top of my head I can just change the validation mask for atxfer, now it always accept chars.
From a standard phone is basically useless.
From AMI works as expected.
From a softphone (using my querty keyboard) I honestly didn't tried.
Do you think there are drawback I didn't consider?