[asterisk-bugs] [JIRA] (ASTERISK-26965) Caller ID set to 'asterisk' during atxfer from bridged queue

[David Wakelin (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Wakelin updated ASTERISK-26965:
-------------------------------------

    Attachment: sip.conf.txt
                queues.conf.txt
                features.conf.txt
                extentions.conf.txt

Conf files to reproduce problem.

> Caller ID set to 'asterisk' during atxfer from bridged queue
> ------------------------------------------------------------
>
>                 Key: ASTERISK-26965
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26965
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue, Features
>    Affects Versions: 14.3.0
>         Environment: Ubuntu 16.04 LTS
> Asterisk 14.3.0 
>            Reporter: David Wakelin
>            Assignee: David Wakelin
>            Severity: Minor
>         Attachments: extentions.conf.txt, features.conf.txt, queues.conf.txt, sip.conf.txt
>
>
> Scenario:
> A customer calls into a queue.
> Agent A's phone rings and can see the caller ID fine.
> Agent A picks up the call.
> Agent A starts an attended transfer to agent B using atxfer in features.conf
> Agent B's phone rings, but the caller ID is set to 'asterisk'. At this point I would expect the caller ID to be set to the phone number of agent A.
> I am using a Websocket based SIP phone, but the same problem occurs when using other SIP devices.
> Settings to recreate the issue:
> sip.conf: https://pastebin.com/LnD7Vepe
> extentions.conf: https://pastebin.com/wyhxBi0J
> queues.conf: https://pastebin.com/TQai9dKD
> features.conf: https://pastebin.com/2WLCZFfp



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