[asterisk-bugs] [JIRA] (ASTERISK-23862) DTMF atxfer doesn't set CallerID for the recall calls to the transferrer.

[Rusty Newton (JIRA)]

Rusty Newton created ASTERISK-23862:
---------------------------------------

             Summary: DTMF atxfer doesn't set CallerID for the recall calls to the transferrer.
                 Key: ASTERISK-23862
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23862
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Features
    Affects Versions: 12.3.0
            Reporter: Richard Mudgett


A calls B, B does a DTMF blonde atxfer to C.

If neither B nor C answers then the recall calls to B have issues with Caller ID.  If B is a PJSIP endpoint, the Caller ID displays as a UUID.

The basic bridge sub-class needs to save the following information before the initial attempt to call party C: the accountcode of party B, the party A (COLP) identification, and party B (CLID) identification information for the possible recall calls.

For B recall:
After calling {{ast_dial_prerun()}}, use {{ast_dial_get_channel()}} to get the created channel and set COLP (party A), CLID (party B), and accountcode on it.  Setting the CLID is needed to ensure that if party B is reconnected to party A again party A will get the original party B identification instead of possibly nothing.  Should also copy the channel variables from the original B channel.  Then call {{ast_dial_run()}}.

For C recall:
After calling {{ast_request()}}, set COLP (party A) and possibly accountcode on the new channel before calling {{ast_call()}}.  Setting the COLP before {{ast_call()}} is needed to ensure that the party A identification is available before the Local;2 channel actually dials party C.  Some phones do not update the display if the party identification information changes once the call is started.



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