�

Signalware Enabled Solution Software Advancing Communications®

SIP to TCAP Gateway

The SS7 network hosts extensive real-time databases that are used for intelligent call routing, security controls, mobility,
user status, local number portability (LNP), and Intelligent Network (IN) applications such as prepaid, virtual private
network, and single number service. Traditionally these databases are only accessible using TCAP messages exchanged
between trusted network elements within the carrier’s domain. The only exception to this is 3rd party service providers
who offer wholesale SS7 transport networks and centralized databases such as a nationwide CNAM or LNP. Wholesale
services are offered based on a prearranged service agreement and are generally billed on a per transaction basis. This
allows a CLEC or VoIP service provider to lease their SS7 network and gain access to database services via SS7.
Next generation networks that are deployed using SIP need a simple way to access SS7 databases in order to offer
comparable services to the incumbent fixed and wireless network operators. For example, a VoIP inter-exchange
carrier needs to access an LNP database so it can route the call to the proper local carrier. Incoming calls from
a PSTN switch to the VoIP network will deliver Caller ID information in the SS7 ISUP messages, but a query to
a nationwide CNAM database will be needed to find the caller’s name. The system architecture shown in Figure 1
illustrates a SIP-TCAP signaling gateway or border element as a bridge between the PSTN and next generation network.

���� ���
����
��� ����
����
��� �����
��������
����
���
������������
��������
��� ���� ��� ���
��� �� ����� ���� �������
���� �������
���� ���

*
7
4

0
1

8
5

#
2

9
6
3

��� �����
�������
��� ������ Figure 1
1 2
4 3
5 6
7 8 9
* 0 #

800 Number Application

This SIP to TCAP gateway application allows SIP ������������
��������

entities to access the 800 number database hosted in �� ���

���
®

a traditional SS7 network. This could be a nationwide

hosted database or an SCP in a specific carrier’s ���� ����� �������� ���� ��������
network. Service requests originate from a SIP proxy
server, softswitch/call agent, or any SIP user agent within
������
the VoIP network domain with proper authorization. ���� �����
Figure 2 illustrates the call flow. The SIP client ������ ����� ������
initiates a request to the TCAP gateway using a
standard SIP INVITE that includes the 800 number �������������
��� ������� ����������� ������
in the SIP destination address or URI as follows:
���
<sip:+18000123456@service.gateway.com;user=phone>

Figure 2

The SIP request and subsequent call flow are identical to a query to a SIP redirect or location server. The SIP
INVITE is sent to the signaling gateway that initiates a TCAP query over the SS7 network. The SCP returns the
actual destination number in the TCAP return response. The SG then sends a 3XX SIP response indicating that
the destination has changed to the destination number contained in the contact header. This allows the requesting
SIP server to create a second INVITE to route the call to the appropriate network gateway for delivery to the
PSTN. Similar call flows can be created for other number translation services such as LNP, VPN, and other short
dialing codes for directory or information services. Caller Name can also be implemented by a query to the CNAM
database with a 3XX response that adds the caller’s name to the destination URI returned in the SIP contact header.

SIP to TCAP Gateway

 Signalware-Enabled Solution SIP to TCAP Gateway Solution

Future Challenges
The services described in this solution are relatively simple call redirect or location requests with straightforward mappings from SIP
to TCAP. More complex dialogs, such as interworking IN triggers with SIP services, require more thought and possible extensions
to the SIP headers. In addition, IN services often require user interaction such as playing audio announcements, collecting DTMF
digits, or requesting speech input that require the initiating or subsequent actions, such as routing to a call center agent. Standards
work is needed to define interesting application level call flows for important services so there is interoperability between equipment
manufacturers. This should be done within the spirit of using SIP as an application level protocol and not as a transport protocol
for TCAP or other SS7 protocols. Ulticom recommends the use of SIGTRAN (M3UA, SUA) to transport SS7/TCAP over IP.

In summary, SIP offers a simple protocol for easy access to SS7 databases creating value for next generation carriers offering VoIP
services. Signalware provides an ideal development environment for offering SIP to TCAP gateway solutions in an open, standards
based solution that is optimized for carrier-grade reliability. Ulticom’s professional services organization can provide consulting services
as well as custom software development to reduce time to market for Signalware enabled solutions such as SS7 to SIP gateways.

Signalware-based Signaling Gateway

Signalware offers an integrated development platform for

���������� ��������
offering SIP to TCAP gateway functionality. Signalware SIP ��������
and SS7 protocols can be combined as shown in the software ������� �����������
architecture in Figure 3 to offer a gateway application on ������������
������� ��������
open Solaris or Linux based server platforms. Signalware
TM TM

����������� ������� ���������� ����

provides a high availability cluster environment that supports
�

automatic failover and recovery in the event of a failure at �������� ����

the either the UNIX process level or computer element (CE)
���������� ���
���� ���
level. OAM&P is provided using MML, GUI, or SNMP remote �����
���������� ���� �������
management interfaces. Standard Signalware APIs support
event logging, measurements collection, alarm notification, ������ � ��������� ��
�����������
and platform management functions. The gateway application
contains all the logic to map SIP message requests to the Figure 3
proper TCAP dialog in order to query the SS7 network. ��� ���

About Signalware
Ulticom’s Signalware service-enabling software lowers costs and accelerates the development and deployment of carrier-grade services. Signalware
provides the critical signaling foundation within communications networks that enables vital network services such as global roaming, voice and
text messaging, prepaid wireless and E911. Incorporating SS7, SIGTRAN, and SIP protocols, Signalware offers an unparalleled combination of
scalability, global interoperability, fault tolerance, carrier-grade reliability and standards-based APIs, on a variety of open computing platforms.

About Ulticom

Trusted Name
Reliability is only proven over time. Founded in 1974, Ulticom Getting Started
provides the telecommunications industry with signaling software
Visit www.ulticom.com or contact Ulticom sales:
that enables revenue-generating services in Mobility, Location,
Payment, Switching and Messaging. Ulticom’s carrier-grade Americas Europe, Middle East, Africa
Signalware product family utilizes SS7, SIGTRAN, and SIP and 1.888.295.6664 +33.497.234.567
exceeds 2000 deployments by more than 300 service providers (North America only) eurosales@ulticom.com
in over 100 countries. Ulticom is TL 9000 certified with offices +1.856.787.2760 Asia
throughout the United States, Europe, and Asia. Ulticom is also a sales@ulticom.com +65.6232.2324
member or participant in key standards bodies such as the Parlay asiasales@ulticom.com
Group, IETF, TIA, and 3GPP.
�

Software Advancing Communications®

© 2004 Ulticom, Inc. All rights reserved. Information is summary in nature and subject to change. Ulticom,
Signalware, and Software Advancing Communications are trademarks or registered trademarks of Ulticom, Inc.
All other copyrights are the property of their respective owners. Printed in USA. SIPTCAP0604