...
There are a few different ways to pre-validate addresses that are going to be sent for dynamic location routing:
Registering the Address on a Phone number - Registering a phone number to an address will automatically validate the address and have it available to send using PIDF-LO
validate911 API Call - Our validate911 API call allows you to validate address information. If the address is successfully validated it will be available to send using PIDF-LO. There is a “Custom Validation URL” listed on your Address Validation page.
Sample: https://backoffice.voipinnovations.com/restapi/XXXXXXXXXXXXX/e911validate?address=123 Test St&city=Testville&state=NY&zipCode=15555
Simply replace the “XXXXXXXXXXXXX” with the unique string from your Custom Validation URL.
Back Office E911->Address Validation. Whenever reviewing your validated addresses on this page, a form is available to validate additional addresses.
...
Call Flow
In order to update the address being used for routing 911 calls, VI will need to receive the address as a PIDF-LO object within the SIP INVITE. SIP Messages sent this way must contain a GeoLocation header with CID reference to the message body containing PIDF-LO. Any SIP Messages also must include a GeoLocation-Routing header containing the word “yes”, which indicates that the call should be routed using the information supplied. Any calls received with a GeoLocation-Routing header containing “no”, or without a GeoLocation-Routing header, will be routed based off the address used whenever provisioning the phone number originally, regardless of what is populated in the GeoLocation header.
...
A priority exists whenever determining the callback number for an emergency call and whenever linking it with a registered number. The preference order is:
P-Asserted-ID
P-Preferred-ID
Remote-Party-ID
From
VI suggests sending callback numbers in E.164 format.
...