Ticket #5374 (closed Bugs: fixed)

Opened 2 years ago

Last modified 1 year ago

Attended transfer resulting in 'device' for CNAM

Reported by: kiemosan Assigned to: p_lindheimer
Priority: minor Milestone: 2.10
Component: Core - Users/Devices Version: 2.9-branch
Keywords: Cc:
Confirmation: Need Feedback Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description (Last modified by p_lindheimer)

Setting 'device' in sip_additinoal.conf has always been correct. This appears to be a bug related to deriving the proper CNAM during attended transfer. I would request a summary with repro steps be put in the ticket along with a reference for further details to the forum post as it otherwise makes it quite time consuming to sort through the forum posts trying to determine exactly what the failure scenario is. Thanks in advance.

Original description:

When an extension is edited the CallerID reference is set to 'device'.

See forum discussion here on the issue.

http://www.freepbx.org/forum/freepbx/installation/internal-name-not-showing-on-attended-transfer#comment-41852

Change History

09/23/11 12:14:07 changed by mickecarlsson

That is the correct behavior. callerid= in sip_additional.conf is set to device <extension number>

The bug is however in macro-user-callerid that does not set the callerid name from astdb.

10/04/11 10:53:31 changed by p_lindheimer

  • summary changed from 'device' set as CallerID when extension edited. to Attended transfer resulting in 'device' for CNAM.
  • description changed.
  • milestone changed from Cut Line to 2.10.

will have a look, it would help to provide a short and subsequent summary of repro step and exactly where the wrong behavior manifests itself and on what phone. Include how the attended transfer is initiated (e.g. *2 or button on phone). This will facilitate a developer getting to something like this much quicker if they see a bulleted list while reading the ticket and can immediately try it, vs. digging through the forum post trying to determine how to repro it and where the bug is. Thanks!

10/04/11 11:13:43 changed by p_lindheimer

  • confirmation changed from Unreviewed to Need Feedback.

OK did the following, it was done on 2.10-latest which I don't think has any changes but it's always possible. I may not have read the thread carefully enough but now I need clarification with details to know how to repro and where to look for the issue:

  1. 700 calls 702, and sees proper CONNECTEDLINE CID of 702 upon answer as does 702 see proper CID for 700
  2. 702 does a button initiated attended transfer to 701
  3. 701 sees the proper full CID of 702 as does 702 see the proper CONNECTEDLINE CID of 701
  4. 702 finished the transfer and thus hangs up
  5. 700 now sees the proper CID info of 701 and 701 sees the proper CID info of 700

in all cases, CID includes proper CNAM and CID info. In all cases, sip_additional.conf is properly written with "device" for the CNAM of all three.

So more info is needed in this ticket so we can further identify the reported issue.

10/04/11 12:16:12 changed by tonyclewis

I just tried doing the same thing and I do not get the bug either. I am using an aastra phone and using the aastra built in attended transfer. I am also using extension mode not device and user.

02/02/12 16:59:28 changed by Spart

I'm getting this issue in FreePBX 2.8.1.4 and Asterisk 1.8 (included in PBX in a Flash.)

It happens when using the *2 feature code transfer, NOT when using the buttons on our phones, which are Polycoms with mostly default configuration.

The buttons on the phones do the transfers differently and the caller ID name shows up as expected.

02/16/12 19:21:30 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

(In [13454]) fixes #5374 if I understand the bug correctly, which results in the wrong CID displayed to the recipient of the attended transfer, all the other CIDs looked proper and still are with this change