i3-Interconnect™

i3-Interconnect™ is a nationally available next gen core service that provides a managed network for Communications Service Providers (CSPs) to easily and affordably connect their legacy 9-1-1 traffic to a NENA NG9-1-1 network. This service aggregates traffic from CSPs, prepares and delivers it into an NG9-1-1 system. Inbound traffic can be delivered in TDM format or in SIP format, while outbound traffic will be in SIP format adhering to NENA i3 specifications.

i3-interconnect

i3-Interconnect™

i3-Interconnect™ is offered via the SynergemNET™ suite of next gen core services. SynergemNET™ consists of a geo-diverse group of primary data centers that provide the Border Control Function, Session Border Control, switch and routing facilities, NENA i3 core services and ancillary services to support a full implementation of an NG9-1-1 system.

i3-Interconnect™ specifically provides Legacy Network Gateway (LNG) functions, including Protocol Interworking (PIF), Location Interworking (LIF), and NG9-1-1 specific (NIF) functions, ensuring that your emergency communications are seamless, reliable, and fully compliant with industry standards.

Next Gen Core Services will Eliminate the Need for New Interconnect Agreements
  • New interconnect agreements, that are often difficult to negotiate, are not necessary with a subscription to the next gen core service, i3-Interconnect™. OSPs need only modify the number of voice channels on existing trunks to connect to i3- Interconnect™. This accommodates any increased 9-1-1 call traffic associated with call delivery to additional networks. In addition to voice connectivity, existing SOI/MPC/VPC connectivity between the OSP and i3-Interconnect™ will be utilized facilitating location data provisioning to other NG9-1-1 networks.
  • i3-Interconnect™ provides common Points of Interconnect (POIs) for carrier connections. CSPs deliver 9-1-1 calls to the POI with the desired destination specified, and ANI or pANI in the ‘from’ field. The service will accept either TDM, SS7 or SIP traffic. For all TDM traffic, the calls are processed through a Protocol Internetworking Function (PIF) where they are converted to Session Initiation Protocol (SIP).

Steps for Deploying i3-Interconnect™

Design, Assign & Test
Signaling
Cutover
i3-interconnect

Design, Assign & Test

  • Originating Service Provider (OSP) completes inventory of all current 9-1-1 connectivity and capacity requirements with each PSAP.
  • Our team reviews proposed end-to-end signaling design.
  • OSP requests LOA/CFA (Letter of Authority/ Customer Facility Assignment); our team assigns 9-1-1 an appropriate Point of Interconnect (POI) location.
  • Synergem provides cross-connect information when the OSP connects to i3-Interconnect™ via Session Initiation Protocol (SIP).
  • OSP circuit activation is completed by the Network Delivery Team with the OSP and Synergem team coordinating trunk activation.
i3-interconnect

Signaling

  • The Integrated Services Digital Network User Part (ISUP) is used to establish wired connections between exchanges.  The OSP submits SS7 ISUP orders to enable (possible 3rd Party) specific exchange connectivity.
  • For SIP implementations, Synergem will share Host and IP address specifications with current OSP and coordinate the interoperability testing.
  • OSP and Synergem coordinate end-to-end test calls to the NG9-1-1 network and when successful, provisioning is completed to i3-Interconnect™.
  • OSP and Synergem ensure proper routing is in place on the voice and signaling switches to deliver calls to i3-Interconnect™ and to NGCS.
  • OSP and Synergem coordinate and execute the tests defined in the test strategy/acceptance test plan document.
i3-interconnect

Cutover

  • Final Maintenance Operation Protocol (MOP) review is completed.
  • Synergem coordinates the cutover plan and prepares for cutover on the appropriate cut date.
  • Synergem executes cutover.

Next Generation 9-1-1 Core Services

psap-next-gen-solutions

i3-Route™
next-gen-solutions-migration

i3-Log™
X

Standard Reports

The table below lists the LogEvents which are supported by the logging service.

CallProcess
StartCall/EndCall
StartRecCall/EndRecCall
TransferCall
Route
StartMedia/EndMedia
StartRecMedia/EndRecMedia
RecordingFail
Message
AdditionalAgency
MergeIncident
UnMergeIncident
LinkIncident
UnLinkIncident
ClearIncident
ReopenIncident
LoSTquery
LoSTresponse
CallSignalingMessage
SiprecMetadata
ALILocationQuery
ALILocationResponse
MalformedMessage
SplitIncident
EIDD
DiscrepancyReport
ElementStateChange
ServiceStateChange
AdditionalDataQuery
AdditionalDataResponse
LocationQuery
LocationResponse
CallStateChange
GatewayCallEvent
Hookflash
LegacyDigits
AgentStateChnge
QueueStateChange
SecurityPostureStateChange
KeepAliveFailure
X

Logging of all Functional Elements

Each functional element will provide LogEvents as the call traverses the system. This provides the operator with a powerful oversight tool, ensuring they have current and historical data at their fingertips. The primary functional elements are shown below.

Requirement
Description
Call Tracing
Trace a call throughout all the hops within the network.
Event Details
Reviewing the events within a call.
Timing
Review log timing throughout a call.
Exporting
Exporting the LogEvents for external review.
Functional Element Usage
LogEvents usage by Functional Element.
Routing
Review routing decisions for the calls.
Alias Configuration
Configuring the system enabling URI to match readable names.