Ticket #3120 (closed Feature Requests: wontfix)

Opened 3 years ago

Last modified 3 years ago

the display name

Reported by: dwagner Assigned to: p_lindheimer
Priority: trivial Milestone: 2.5
Component: Core - Users/Devices Version: 2.4-branch
Keywords: callerid device Cc: 1.0
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version:

Description

the displayname (callerid) is not set if you save a sip user. after the sip user has changed the following is saved in the asterisk config file:

callerid = device <123>

in the file modules/core/functions.inc.php you find a request to the description field. this field is not found in the form. the field is called "name"

Change History

08/28/08 09:38:46 changed by p_lindheimer

  • priority changed from major to trivial.
  • confirmation changed from Unreviewed to Confirmed.
  • type changed from Bugs to Feature Requests.

Technically that is correct. The description is used in Device and User mode for a device description. The fact that device mode sets a description but user mode does not can probably be debated. (Either both should set it to device, or we should consider putting the display name in the case of extension mode - although having device there can be of significant help detecting corrupted astdb issues).

The actual display name is always derived from the AstDB DEVICE object, and thus the only important part of the callerid is the number.

So I'll discuss with some of the developers whether we should:

  • make them all: device <num>
  • make them all: name <num>
  • make them all : <num>

08/29/08 13:21:32 changed by p_lindheimer

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

after some dev discussion, the decision is as follows. If you are in extension mode we will leave it as is, meaning it will be set to device. Since extension mode should always have a fixed user connected to a device, this makes no difference and the advantages of seeing 'device' in your caller id when things break (like astdb corruption) is very beneficial.

For device and user mode, it will continue to use the device description. The reason for this is that it is possible to make adhoc devices that may have no person logged into them, in which case the CID is the device cid which becomes the description. For example, you may have a device called (Hotdesk 101) in which case you would get a meaningful CID if someone called from that device without logging in. As soon as they log in, the CID will be their user CID.

That is the reasoning for doing this. Further comments are welcome and will be reviewed but for now closing this as wontfix for the specified reasons.

09/01/08 05:21:35 changed by dwagner

the problem is, that i upgraded from freepbx 1.2 to the latest version. in the old version the name was set correctly. in the new one it does not. is there an error in the upgrade program? why wasn't it set in the astdb during the upgrade process?

09/01/08 05:24:40 changed by dwagner

how can i correct it in the astdb?

09/01/08 09:20:31 changed by p_lindheimer

it is correct, if you are making calls and getting 'device' as your CNAM then you have something else broken/corrupted on your system. macro-user-callerid puts the correct CNAM in.

09/02/08 01:07:54 changed by dwagner

please help me a little bit. i don't know what the device, user and extension mode is and how to set it. please tell me which database key to set the right cidname. is it the AMPUSER/EXT/cidname ?

thanks a lot

09/04/08 04:28:56 changed by dwagner

Please help me, I'm waiting for an answer. I've to setup a customer machine. thanks

09/04/08 08:37:50 changed by p_lindheimer

dwagner, this is not a forum, please use the forums for help