asterisk users - May 2022 - [External] Geolocation/E911

We have a customer who wants to perform both directions.

For inbound calls, they have indicated their switch will provide
Geolocation/E911 information using two different ways.  Sounds like it depends
on the equipment before the SIP proxy.
It will either be in SIP headers (which we retrieve through PJSIP_HEADER in the
dial plan).  Trivial for us to do this approach.
Second approacy is their SIP proxy will append information to the body with mime
delimiters (indicating content type of pidf+xml).

They want us to retrieve this information (via Asterisk) and store it into their
database.  When a 911 agent answers the call, they retrieve the data from the
database and use it as needed for assisting the first responders.

If Asterisk can’t do this and isn’t planned to be able to support this, we’re
looking to make Kamailio able to process the INVITE in front of Asterisk.  Idea
being Kamailio could communicate the information our customer requires and we
store it in the database.  When Agent answers the call, use the Call-ID provided
by Asterisk to match it with the Kamailio INVITE data’s Call-ID.


We are still trying to gather details on how the customer wants the outbound
calls to work.

Dan

From: asterisk-users <asterisk-users-bounces at lists.digium.com> On
Behalf Of Sebastian Nielsen
Sent: Monday, May 23, 2022 3:19 PM
To: 'Mailing List' <asterisk-users at lists.digium.com>
Subject: Re: [External] [asterisk-users] Geolocation/E911

What are you talking about exactly?

What I have understand, E911 geo information is sent “out of band” when 911 is
called.

So the question is, is you operating a 911 call centre – then you should have
this information at hand already how to access this information.

Or are it the opposite, you want to send geocoded information about SIP handset
location to a E911 service when 911 is called? (that you want to embed in the
outgoing body when 911 is called)?

I think gaining access to these types of E911 API’s requires you being a SIP
operator – and if you are a SIP operator with a number plan already, you should
already have access to these types of API from the beginning and how to use
them.

Från: asterisk-users-bounces at
lists.digium.com<mailto:asterisk-users-bounces at lists.digium.com>
<asterisk-users-bounces at lists.digium.com<mailto:asterisk-users-bounces
at lists.digium.com>> För Dan Cropp
Skickat: den 23 maj 2022 22:01
Till: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users
at lists.digium.com<mailto:asterisk-users at lists.digium.com>>
Ämne: [asterisk-users] Geolocation/E911

Out of curiosity, is there any documentation on what is planned for the
Geolocation/E911?

Is the plan for Asterisk to expose the SIP body and leave it to dial plan, ARI,
AMI to process the data?
For example, mime pidf+xml section?

Or is there a different approach being worked on (or planned to be worked on)?

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20220523/04645ab0/attachment.html>

On Mon, May 23, 2022 at 5:52 PM Dan Cropp <dan at amtelco.com> wrote:
> We have a customer who wants to perform both directions.
>
>
>
> For inbound calls, they have indicated their switch will provide
> Geolocation/E911 information using two different ways.  Sounds like it
> depends on the equipment before the SIP proxy.
>
> It will either be in SIP headers (which we retrieve through PJSIP_HEADER
> in the dial plan).  Trivial for us to do this approach.
>
> Second approacy is their SIP proxy will append information to the body
> with mime delimiters (indicating content type of pidf+xml).
>
>
>
> They want us to retrieve this information (via Asterisk) and store it into
> their database.  When a 911 agent answers the call, they retrieve the data
> from the database and use it as needed for assisting the first responders.
>
>
>
> If Asterisk can’t do this and isn’t planned to be able to support this,
> we’re looking to make Kamailio able to process the INVITE in front of
> Asterisk.  Idea being Kamailio could communicate the information our
> customer requires and we store it in the database.  When Agent answers the
> call, use the Call-ID provided by Asterisk to match it with the Kamailio
> INVITE data’s Call-ID.
>
>
>
>
>
> We are still trying to gather details on how the customer wants the
> outbound calls to work.
>
Both directions will be supported according to the specification and
standard. The information will be accessible from the dialplan using a
dialplan function, but not the pidf+xml itself. If they're doing something
outside of the standard, then it likely wouldn't work. The code is not
written for 911 PSAPs/handlers specifically, it's written for receiving the
information from an endpoint, and for sending it out.

-- 
Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20220523/0db20781/attachment.html>