[asterisk-bugs] [JIRA] (ASTERISK-27918) Transfer in U&D mode

[George Joseph (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243831#comment-243831 ] 

George Joseph commented on ASTERISK-27918:
------------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'pjsip set logger on' if the issue involves chan_pjsip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> Transfer in U&D mode
> --------------------
>
>                 Key: ASTERISK-27918
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27918
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 13.18.5
>         Environment: asterisk - 13.18.5 
> freepbx - 14.0.1.36
> FreepbxDistro
>            Reporter: Maxim Trofimov
>
> Good afternoon.
> When transferring a call, the communication channel with the first user called is not completed and as a result the system does not treat this call as a transfer (there is no event in the queue_log ATTENDEDTRANSFER only COMPLITECALLER and it is created when the call with the user to whom the transfer was terminated ends). Transfer is made through *2 or ##. User&Device mode.
> I'm calling from number 6118 (external trunk for PBX) to the queue number 4777 the operator registered on the device 4920 at number 4987 (TEST) picks up the phone and transfers (* 2) to number 4988 talks and hangs up, call transfer number 6118 communicates with 4988 and ends the conversation. However, in the queues of the queue, this transfer is not processed as a transfer. Logs reflect that the conversation was between 6118 and 4987 and the duration of the conversation is equal to the total duration from when the 4987 accepted the call before the end of the conversation with 4988
> 1520274014 | 1520274013.270913 | 4777 | NONE | DID | 4777 1520274014 | 1520274013.270913 | 4777 | NONE | ENTERQUEUE || 6118 | 1 1520274021 | 1520274013.270913 | 4777 | TEST | CONNECT | 7 | 1520274014.270914 | 6 1520274061 | 720274013.270913 | 4777 | TEST | COMPLETEAGENT | 7 | 40 | 1
> LogFile - http://pastebin.freepbx.org/view/0a163b01



--
This message was sent by Atlassian JIRA
(v6.2#6252)