i3-Interconnect™

Built for the industry’s transition to IP-based emergency communications, i3-Interconnect™ supports direct SIP call delivery into the NG9-1-1 environment. This gives Communications Service Providers (CSPs) and Originating Service Providers (OSPs) a modern path for delivering 9-1-1 traffic while continuing to support providers transitioning from legacy infrastructure.

i3-interconnect

What is i3-Interconnect™?

i3-Interconnect™ is part of the SynergemNET™ suite of Next Generation Core Services, which provides common Points of Interconnect (POIs), giving CSPs and OSPs a streamlined way to connect to Synergem’s NG9-1-1 network, SynergemNET™.

SynergemNET™ consists of a geographically diverse infrastructure providing Border Control Function, Session Border Control, switching and routing capabilities, NENA i3 core services and other services to support NG9-1-1 implementations.

For providers that have not yet completed the transition to SIP, i3-Interconnect™ continues to support legacy TDM and SS7 connectivity through Legacy Network Gateway (LNG) functions. These capabilities provide the interworking necessary to convert legacy traffic for delivery into the NG9-1-1 environment.

This flexible approach allows Synergem to support providers wherever they are in their NG9-1-1 transition, which provides modern SIP-based connectivity while maintaining a practical migration path for networks that still rely on legacy infrastructure.

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).

How i3-Interconnect™ is Deployed

Design, Assign & Test
Signaling
Cutover
i3-interconnect

Design, Assign & Test

During the planning phase, Synergem works with the Originating Service Provider (OSP) to design and validate its connection to the NG9-1-1 environment.

Typical activities include:

  • Reviewing current 9-1-1 connectivity and capacity requirements.
  • Reviewing the proposed end-to-end signaling design.
  • Assigning the appropriate Point of Interconnect (POI).
  • Processing the Letter of Authorization/Customer Facility Assignment (LOA/CFA).
  • Providing host, IP address and cross-connect specifications for SIP connectivity.
  • Identifying any legacy interworking requirements that need to be maintained during migration.
  • Coordinating network activation between the OSP, network delivery teams and Synergem.
i3-interconnect

Signaling

The signaling phase verifies that emergency calls, routing information and location data can move correctly between the OSP and Synergem’s NG9-1-1 environment.

For SIP-based deployments, Synergem and the OSP configure the appropriate network interfaces and conduct end-to-end interoperability testing, including:

  • SIP connectivity and interoperability validation.
  • Host and IP configuration.
  • End-to-end NG9-1-1 test calls.
  • Verification of call routing and signaling.
  • Validation of location information handling.
  • Execution of the approved test strategy and acceptance test plan.

Where legacy connectivity is still required, SS7, TDM, and the necessary interworking can be incorporated into testing.

Successful testing confirms that emergency traffic can be reliably delivered into NG9-1-1 Core Services (NGCS).

i3-interconnect

Cutover

Once testing is successfully completed, Synergem coordinates the migration of live 9-1-1 traffic into the NG9-1-1 environment.

The cutover process includes:

  • Reviewing the final Maintenance Operation Protocol (MOP).
  • Confirming routing, connectivity, redundancy and failover procedures.
  • Executing the approved migration plan on the scheduled cutover date.
  • Monitoring emergency call delivery throughout the transition.
  • Validating connectivity and routing following cutover.

Following cutover, the OSP is connected to Synergem’s NG9-1-1 environment through i3-Interconnect™, providing a foundation for reliable SIP-based emergency communications and continued NG9-1-1 modernization.

Next Generation 9-1-1 Core Services

NG9-1-1 solutions

i3-Route™
NG9-1-1 solutions

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.