<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Emergency Services Release Notes 2026 in Inteliquent Customer Portal</title>
    <link>https://community.sinch.com/t5/Inteliquent-Customer-Portal/Emergency-Services-Release-Notes-2026/ta-p/19348</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;SUBSCRIPTIONS:&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;EM&gt;&lt;SPAN&gt;If you want to subscribe to updates for Emergency Services, click the&amp;nbsp;&lt;STRONG&gt;Options&lt;/STRONG&gt;&amp;nbsp;menu button in the right-hand-corner of this article and select&amp;nbsp;&lt;STRONG&gt;Subscribe&lt;/STRONG&gt;. You will then receive email notifications when this article is updated with new release notes.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Check in here to see information about new releases from Emergency Services.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;4/30/2026 – PSAP Outage Notification Service Update&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Ticket Timing Update: Sinch has increased the automated ticket closure timeframe due to inactivity on a PSAP Outage Notification request/ticket from 24 hours to 30 days. Previously, if a PSAP Outage Notification ticket was opened and 24 hours passed without the Customer submitting an update to the ticket, the ticket would close automatically due to inactivity. In some scenarios, there are extended outages/issues and a material update every 24 hours is not practical, resulting in Customer opened PSAP Outage Notification tickets being closed for inactivity. When a Customer ticket is closed, the Customer has to open a new ticket should they want to notify PSAPs after those 24 hours have passed. The window of allowed inactivity has been increased from 24 hours to 30 days so that Customer’s have a longer timeframe to submit updates and generate follow-up notifications to PSAPs if/when needed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;3/31/2026 – Next Generation (NG911) i3 related enhancements&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Location by Reference (egress to the PSAP / NG911 system):&amp;nbsp; HTTP Enabled Location Delivery (HELD) is a protocol for delivering caller location information in an NG911 i3 format using a Location by Reference methodology.&amp;nbsp; Sinch has added support for transmitting location data to NG911 i3 capable Public Safety Answering Points (PSAPs) using a Location by Reference method (i.e., HELD request and response), in addition to currently supported Location by Value method in the SIP invite (i.e., PIDF-LO embedded in the SIP invite).&amp;nbsp; While all NG911 systems should support both Location by Reference and Location by Value methods for transmitting caller location data in an NG911 i3 format, some may only support one or the other initially. &amp;nbsp;Sinch supporting both methods will accelerate further NG911 i3 adoption as PSAPs become ready.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additional Data (ADR):&amp;nbsp; ADR is a set of standardized information that provides PSAPs with supplemental details about the caller, the location, or the call itself (i.e., info about the service provider, device the call was placed on, building floor plans, etc…) to improve emergency response.&amp;nbsp; Sinch will begin including, where supported, ADR data blocks along with location data when sending calls to i3 capable NG911 systems supporting ADR.&amp;nbsp; More specifically, Sinch will include a Provider Information data block populated with Sinch service provider data, as well as Service Information data block populated with industry standard values for VoIP use cases.&amp;nbsp; Sinch will additionally transparently pass-through any customer provided and properly formatted ADR data blocks without modification.&amp;nbsp; &lt;STRONG&gt;&lt;U&gt;Note&lt;/U&gt;&lt;/STRONG&gt;: ADR support among NG911 systems is currently minimal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Location Validation Function (LVF):&amp;nbsp; the LVF is an important element of a NG911 system that validates civic location information against the authoritative GIS database information, designed to improve location accuracy and is required to achieve NG911 i3 standards compliance.&amp;nbsp; In markets where the 911 Authority provides an LVF that Sinch has integrated with, Sinch will start providing feedback to customers during address validation if the address submitted to address validation passes the 911 Authority LVF validation.&amp;nbsp; &lt;STRONG&gt;&lt;U&gt;Note&lt;/U&gt;&lt;/STRONG&gt;:&amp;nbsp; currently the availability of an LVF is limited to only Massachusetts, but that will expand as additional 911 Authority’s support full NG911 i3 and make LVFs available to service providers for address verification.&amp;nbsp; If the address passes the 911 Authority’s LVF as valid, then the customer will receive an address validation note of “LVF Validation” returned in the Validation Message parameter in the Portal and the validationMsg parameter in the /addressValidate API response (see example from the Portal immediately below).&lt;/P&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="Picture2.png" style="width: 624px;"&gt;&lt;img src="https://community.sinch.com/t5/image/serverpage/image-id/7188iC8D68C88458BEE2E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Picture2.png" alt="Picture2.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;</description>
    <pubDate>Thu, 30 Apr 2026 14:00:00 GMT</pubDate>
    <dc:creator>Shahzad_Ismail</dc:creator>
    <dc:date>2026-04-30T14:00:00Z</dc:date>
    <item>
      <title>Emergency Services Release Notes 2026</title>
      <link>https://community.sinch.com/t5/Inteliquent-Customer-Portal/Emergency-Services-Release-Notes-2026/ta-p/19348</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;SUBSCRIPTIONS:&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;EM&gt;&lt;SPAN&gt;If you want to subscribe to updates for Emergency Services, click the&amp;nbsp;&lt;STRONG&gt;Options&lt;/STRONG&gt;&amp;nbsp;menu button in the right-hand-corner of this article and select&amp;nbsp;&lt;STRONG&gt;Subscribe&lt;/STRONG&gt;. You will then receive email notifications when this article is updated with new release notes.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Check in here to see information about new releases from Emergency Services.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;4/30/2026 – PSAP Outage Notification Service Update&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Ticket Timing Update: Sinch has increased the automated ticket closure timeframe due to inactivity on a PSAP Outage Notification request/ticket from 24 hours to 30 days. Previously, if a PSAP Outage Notification ticket was opened and 24 hours passed without the Customer submitting an update to the ticket, the ticket would close automatically due to inactivity. In some scenarios, there are extended outages/issues and a material update every 24 hours is not practical, resulting in Customer opened PSAP Outage Notification tickets being closed for inactivity. When a Customer ticket is closed, the Customer has to open a new ticket should they want to notify PSAPs after those 24 hours have passed. The window of allowed inactivity has been increased from 24 hours to 30 days so that Customer’s have a longer timeframe to submit updates and generate follow-up notifications to PSAPs if/when needed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;3/31/2026 – Next Generation (NG911) i3 related enhancements&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Location by Reference (egress to the PSAP / NG911 system):&amp;nbsp; HTTP Enabled Location Delivery (HELD) is a protocol for delivering caller location information in an NG911 i3 format using a Location by Reference methodology.&amp;nbsp; Sinch has added support for transmitting location data to NG911 i3 capable Public Safety Answering Points (PSAPs) using a Location by Reference method (i.e., HELD request and response), in addition to currently supported Location by Value method in the SIP invite (i.e., PIDF-LO embedded in the SIP invite).&amp;nbsp; While all NG911 systems should support both Location by Reference and Location by Value methods for transmitting caller location data in an NG911 i3 format, some may only support one or the other initially. &amp;nbsp;Sinch supporting both methods will accelerate further NG911 i3 adoption as PSAPs become ready.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additional Data (ADR):&amp;nbsp; ADR is a set of standardized information that provides PSAPs with supplemental details about the caller, the location, or the call itself (i.e., info about the service provider, device the call was placed on, building floor plans, etc…) to improve emergency response.&amp;nbsp; Sinch will begin including, where supported, ADR data blocks along with location data when sending calls to i3 capable NG911 systems supporting ADR.&amp;nbsp; More specifically, Sinch will include a Provider Information data block populated with Sinch service provider data, as well as Service Information data block populated with industry standard values for VoIP use cases.&amp;nbsp; Sinch will additionally transparently pass-through any customer provided and properly formatted ADR data blocks without modification.&amp;nbsp; &lt;STRONG&gt;&lt;U&gt;Note&lt;/U&gt;&lt;/STRONG&gt;: ADR support among NG911 systems is currently minimal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Location Validation Function (LVF):&amp;nbsp; the LVF is an important element of a NG911 system that validates civic location information against the authoritative GIS database information, designed to improve location accuracy and is required to achieve NG911 i3 standards compliance.&amp;nbsp; In markets where the 911 Authority provides an LVF that Sinch has integrated with, Sinch will start providing feedback to customers during address validation if the address submitted to address validation passes the 911 Authority LVF validation.&amp;nbsp; &lt;STRONG&gt;&lt;U&gt;Note&lt;/U&gt;&lt;/STRONG&gt;:&amp;nbsp; currently the availability of an LVF is limited to only Massachusetts, but that will expand as additional 911 Authority’s support full NG911 i3 and make LVFs available to service providers for address verification.&amp;nbsp; If the address passes the 911 Authority’s LVF as valid, then the customer will receive an address validation note of “LVF Validation” returned in the Validation Message parameter in the Portal and the validationMsg parameter in the /addressValidate API response (see example from the Portal immediately below).&lt;/P&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="Picture2.png" style="width: 624px;"&gt;&lt;img src="https://community.sinch.com/t5/image/serverpage/image-id/7188iC8D68C88458BEE2E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Picture2.png" alt="Picture2.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 30 Apr 2026 14:00:00 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Inteliquent-Customer-Portal/Emergency-Services-Release-Notes-2026/ta-p/19348</guid>
      <dc:creator>Shahzad_Ismail</dc:creator>
      <dc:date>2026-04-30T14:00:00Z</dc:date>
    </item>
  </channel>
</rss>

