- Joined
- Nov 30, 2023
- Messages
- 2
- Reaction score
- 0
We support multiple local hotels with 3cx. The local 911 dispatch is now requiring that they send the room number on any 911 calls. We want to use 3cx's e911 geolocation feature to send that extra info. The docs say it is available on the Generic SIP Trunk templates, which it is. But the problem we are running into is that no matter what we put into the Options> e911 Geolocation > Geolocation URI / ID field, 3cx always prepends "https://emergency.bandwidth.com/locations/5006155/" to the data.

My SIP provider is just expecting the location guid, not a full URL. But I have tried putting full URLs in as well, and they still get the emergency.bandwidth.com portion prepended to them.
I even tried building a Voxtelesys trunk following their guide, and the Voxtelesys URL gets the bandwidth.com URL prepended.

Has anyone gotten e911 geolocation to work with anything other than bandwidth.com? If so, how are you getting it to not prepend the bandwith URL?

My SIP provider is just expecting the location guid, not a full URL. But I have tried putting full URLs in as well, and they still get the emergency.bandwidth.com portion prepended to them.
I even tried building a Voxtelesys trunk following their guide, and the Voxtelesys URL gets the bandwidth.com URL prepended.

Has anyone gotten e911 geolocation to work with anything other than bandwidth.com? If so, how are you getting it to not prepend the bandwith URL?