# Default Dispatchable Location

**URL:** https://forums.vitalpbx.org/t/default-dispatchable-location/1260
**Category:** Reporting an Issue
**Created:** [April 25, 2022, 7:50pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260 "2022-04-25T19:50:06Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![EINM](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/einm/32/375_2.png) [@EINM](https://forums.vitalpbx.org/u/EINM)
#### Post date: [April 25, 2022, 7:50pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260/1 "2022-04-25T19:50:06Z")

</div>

Hello,

I noticed that when you create an extension or device and leave the dispatchable location on default, and then create a dispatchable location and set it as default, it won’t update the database (${DEV\_TREE}/location), unless you go back to the extension and click update,  
Is it possible to have this changed, that when you save a dispatchable location that is set as default, it should update all devices that are set to use the default location?

Thank you.

---

<div class="post-metadata">

### Author: ![PitzKey](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/pitzkey/32/420_2.png) [@PitzKey](https://forums.vitalpbx.org/u/PitzKey)
#### Post date: [May 4, 2022, 4:01pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260/2 "2022-05-04T16:01:52Z")

</div>

Per @EINM if you run `vitalpbx fully-dump-config` it fixes this issue.

Of course, this is a temporary fix. This needs to be addressed ASAP, because sending incorrect e911 information can sometimes be a difference between life and death. This is aside from the $fine you pay for sending incorrect e911 info.

---

<div class="post-metadata">

### Author: ![PitzKey](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/pitzkey/32/420_2.png) [@PitzKey](https://forums.vitalpbx.org/u/PitzKey)
#### Post date: [June 13, 2022, 12:36pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260/3 "2022-06-13T12:36:46Z")

</div>

Hello,

Is there an update on this issue?

Thanks

---

<div class="post-metadata">

### Author: ![PitzKey](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/pitzkey/32/420_2.png) [@PitzKey](https://forums.vitalpbx.org/u/PitzKey)
#### Post date: [June 27, 2022, 12:51pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260/4 "2022-06-27T12:51:35Z")

</div>

This is a serious issue. Sending incorrect e911 caller ID leads to a heavy fine.

I’d appreciate if we can get an update on this 🙂

Thanks

---

<div class="post-metadata">

### Author: ![TBG](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/tbg/32/1111_2.png) [@TBG](https://forums.vitalpbx.org/u/TBG)
#### Post date: [August 4, 2022, 9:19pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260/5 "2022-08-04T21:19:11Z")

</div>

still an issue?

How does this work as i set e911 at our trunk level?

However this particular time it wasnt set at trunk level but was set in pbx. still got fined!

Thanks

---

<div class="post-metadata">

### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)
#### Post date: [August 4, 2022, 10:53pm UTC](https://forums.vitalpbx.org/t/default-dispatchable-location/1260/6 "2022-08-04T22:53:38Z")

</div>

We addressed this issue in the latest version of VitalPBX 3. Keep in mind that the dispatchable locations are used just when the emergency numbers are defined in the Emergency Numbers module on VitalPBX.