AlanS Posted May 19, 2022 Report Share Posted May 19, 2022 I enabled this on the trunk and have locations set. I called 933 for testing and ran a pcap, but no PIDF headers were sent. Was this because they only send with 911? Quote Link to comment Share on other sites More sharing options...
AlanS Posted May 19, 2022 Author Report Share Posted May 19, 2022 I only found out about this, because we got smacked with an unregistered 911 fee today. Even with this enabled and the location filled out. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 22, 2022 Report Share Posted May 22, 2022 Well the big question is if your service provider supports PIDF-LO. Most don't. Before investing time into this you should double check if it would make any difference. Most of the fines are not because of missing location information, they are because users are using caller-ID that don't belong to them (the location is already associated with the number). Some people think it's funny when it is clearly not. Quote Link to comment Share on other sites More sharing options...
AlanS Posted May 22, 2022 Author Report Share Posted May 22, 2022 Voip Innovations 100% supports PIDF-LO https://voipinnovations.atlassian.net/wiki/spaces/VIW/pages/1986330625/E911+Dynamic+Location+Routing Quote Link to comment Share on other sites More sharing options...
AlanS Posted May 22, 2022 Author Report Share Posted May 22, 2022 We ran a PCAP, and there was no location information sent during the invite. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 23, 2022 Report Share Posted May 23, 2022 The main problem is that the location needs to be verified first. We do that with Bandwidth in a way that they generate the URL for the location, which the PBX stores along with the location information. In the case of an emergency call, it then includes the URL in the Geolocation header. There were previous versions of the PBX that included the PIDF document in the INVITE, but that had to be scrapped because of the prior validation and location precision (what is the point of providing location information if the user is actually somewhere else). I would not be surprised if VoIP Innovations will go the same route because the way it looks to me right now, the SIP client can send anything — which might cause additional trouble with the emergency response centers. IMHO I would go for the static registration of the address, if your users are actually using the PBX always from the same location. If your users are using the app for calling 911 there is a much easier solution. The Vodia Apps can redirect emergency calls to the native dialer which sends the GPS location to the response center anyway. Quote Link to comment Share on other sites More sharing options...
AlanS Posted May 23, 2022 Author Report Share Posted May 23, 2022 VI does the same thing with locations. They have to be verified. If they are not, then PDIF is ignored. To confirm, PDIF in the invite is now scrapped? I need to know, so I can spend an afternoon updating all accounts with their e911 address in VI. Quote Link to comment Share on other sites More sharing options...
AlanS Posted June 23, 2022 Author Report Share Posted June 23, 2022 If there is a way to bring back PIDF into the sip headers, that would be awesome. 90% of my customers simply do not care about apps. All they care for is a dial tone with an IVR lol. They all use physical phones. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.