FreePBX
  1. FreePBX
  2. FREEPBX-5245

Emergency Caller ID should be set with device, and not user

    Details

    • Backend Engine:
      All
    • Confirmation:
      Need Feedback

      Description

      FreePBX currently supports an "emergency caller ID feature." This feature allows admins to set a special caller ID for each extension, so that when that user calls a trunk designated as an emergency trunk, the emergency caller ID is sent.

      This is a great feature, but there's one problem: When FreePBX is used in device and user mode, the emergency caller ID is linked to the USER and not the DEVICE.

      This is important because the correct caller ID to send in an emergency should be determined by the location of the device and not by the particular user who is logged into that device.

      For example, suppose that I have two homes. At both homes, I have a phone that is registered as user 200. The phone is at my home in California is device 300 and the phone at my home in New York is device 301. I use device and user mode so that any of my employees/users can dial 200 and reach me, wherever I happen to be, and I can get voicemails from either phone as well.

      If I pick up the phone in New York and dial 911, I want the Emergency Caller ID to be a # that links to my New York location. If I pick up the phone in California and dial 911, I want my Caller ID to be a # that links to my California location. If the emergency caller ID were linked to the device, I could do that.

      As it is now, however, Emergency Caller ID is linked to the user, i.e. user 200. So, everytime I go from one place to another, I have to manually change the emergency caller ID.

      Honestly, I can't think of a reason why you'd ever want emergency caller ID tied to the user instead of the device. When dialing an emergency number, you almost always want the emergency services coming to the location of the device, without regard to the identity of the person using that device.

        Activity

        Hide
        Moshe Brevda added a comment -

        I would recommend that you create two separate users. While there is some merit to your logic, there are design patterns in FreePBX that would make this extremely improbable. Ill wait for a second option though before deciding what to do here...

        Show
        Moshe Brevda added a comment - I would recommend that you create two separate users. While there is some merit to your logic, there are design patterns in FreePBX that would make this extremely improbable. Ill wait for a second option though before deciding what to do here...
        Hide
        Martin Anderson added a comment -

        It is my understanding that the developers spent quite a bit of time setting up device & user mode precisely so that a single user could be logged in to two different devices, and still receive pages, voicemail notifications, etc.

        In my humble opinion, making two separate users defeats one of the fundamental purposes of Device & User Mode.

        Show
        Martin Anderson added a comment - It is my understanding that the developers spent quite a bit of time setting up device & user mode precisely so that a single user could be logged in to two different devices, and still receive pages, voicemail notifications, etc. In my humble opinion, making two separate users defeats one of the fundamental purposes of Device & User Mode.
        Hide
        Philippe Lindheimer added a comment -

        I'm sorry I didn't notice this earlier.

        The Emergency Caller ID IS associated with the device, not the user. It is obtained with the following line in the macro-outbound-callerid:

        exten => s,n(bypass),Set(EMERGENCYCID=${DB(DEVICE/${REALCALLERIDNUM}/emergency_cid)})
        

        The REALCALLERIDNUM is the devices callerid, not the user callerid.

        So your reasoning and logic is 100% correct. I will leave this ticket open to give you a chance to clarify if there is a bug happening somewhere,, and details of the release version and other info for us to have a look. But it should be pulling this info from the DEViCE object which is the specific physical phone that you are calling from.

        Show
        Philippe Lindheimer added a comment - I'm sorry I didn't notice this earlier. The Emergency Caller ID IS associated with the device, not the user. It is obtained with the following line in the macro-outbound-callerid: exten => s,n(bypass),Set(EMERGENCYCID=${DB(DEVICE/${REALCALLERIDNUM}/emergency_cid)}) The REALCALLERIDNUM is the devices callerid, not the user callerid. So your reasoning and logic is 100% correct. I will leave this ticket open to give you a chance to clarify if there is a bug happening somewhere,, and details of the release version and other info for us to have a look. But it should be pulling this info from the DEViCE object which is the specific physical phone that you are calling from.
        Hide
        Martin Anderson added a comment -

        The problem is that the Emergency Caller ID is set on the User page, and not on the Device page in the Web Interface. Otherwise, see my initial report, above for details.

        Show
        Martin Anderson added a comment - The problem is that the Emergency Caller ID is set on the User page, and not on the Device page in the Web Interface. Otherwise, see my initial report, above for details.
        Hide
        Martin Anderson added a comment -

        More specifically, there isn't a bug.

        Rather, I'm making a feature request.

        I'm suggesting that you move the "Emergency Caller ID" field from where it currently appears on the Users configuration pages to the Device configuration page instead.

        Show
        Martin Anderson added a comment - More specifically, there isn't a bug. Rather, I'm making a feature request. I'm suggesting that you move the "Emergency Caller ID" field from where it currently appears on the Users configuration pages to the Device configuration page instead.
        Hide
        Philippe Lindheimer added a comment -

        What version are you looking at?

        When you are in extension mode, then everything is combined so you will see the Emergency CID there. When you are in Device and User mode, then the Emergency CID is associated with the Device page on the current version, and to the best of my knowledge that has been the case since the beginning though I could be mistaken there and thus my request.

        This would be a bug if we had it in the wrong place. Please clarify before I close the ticket to make sure there is not something else I am missing.

        Show
        Philippe Lindheimer added a comment - What version are you looking at? When you are in extension mode, then everything is combined so you will see the Emergency CID there. When you are in Device and User mode, then the Emergency CID is associated with the Device page on the current version, and to the best of my knowledge that has been the case since the beginning though I could be mistaken there and thus my request. This would be a bug if we had it in the wrong place. Please clarify before I close the ticket to make sure there is not something else I am missing.
        Hide
        Martin Anderson added a comment -

        You're right! I just checked on 2.8 and it is as I say it should be already. I'm not sure why I thought otherwise. I must be under a lot of stress...

        Show
        Martin Anderson added a comment - You're right! I just checked on 2.8 and it is as I say it should be already. I'm not sure why I thought otherwise. I must be under a lot of stress...

          People

          • Assignee:
            Philippe Lindheimer
            Reporter:
            Martin Anderson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development