SMSC

The SMSC (Short Message Service Center) connector provides Netmera clients with the capability to establish a direct, low-level connection to an SMS gateway using the industry-standard SMPP (Short Message Peer-to-Peer) protocol. This integration is designed for high-volume, low-latency SMS delivery scenarios, often involving direct integration with mobile network operators.

Overview

Attribute	Details
Connector Name	SMSC
Category	SMS Providers / SMS Gateway
Primary Function	Direct, high-volume SMS delivery via SMPP Protocol.
Data Flow	Outbound (Netmera > SMSC)
Connection Type	SMPP Protocol 3.4 (Direct Persistent TCP Connection)
Priority Ranking	Rank 5 (after Message Center, Mobildev, FigenSoft, and Infobip)

The SMSC connector is highly technical, utilizing specialized components (SimpleSmscClient.java) to manage persistent TCP connections required by the SMPP standard.

Use Cases and Benefits

1. High-Volume SMS Sending: This connector is specifically utilized for use cases requiring exceptional throughput and reliability, leveraging the efficiency of the direct SMPP connection over standard REST APIs.

2. Direct Operator Integration: It supports Direct Operator Integration, allowing Netmera to connect directly to an operator's infrastructure for reduced latency and optimal delivery rates.

3. High Availability (HA) and Load Distribution: The configuration supports defining multiple server configurations, allowing the system to distribute the load and ensure high availability through redundancy across different SMSC hosts.

4. Low-Latency Delivery: By using the persistent TCP connection defined in the SMPP 3.4 protocol, messages can often be processed faster than traditional HTTP gateway integrations.

Data Flow

The flow is defined as strictly Outbound.

Flow Direction	Data Transferred	Mechanism
Outbound (Netmera > SMSC)	SMS Payload, Sender ID, System ID	The dedicated adapter sends the SMS request directly over the established Persistent TCP Connection using the SMPP protocol commands (e.g., submit_sm).

The SMS message request is initiated in Netmera and processed by the SMS service, which routes the request to the SMSC adapter if no higher-priority connector is active.

Configuration Reference

The SMSC connector uses a Multi-item Form structure, requiring a list of server configurations and a list of approved headers, reflecting its complex, multi-host nature.

Parameter	Type	Description
smsServerConfigList	List of Objects	List of SMPP server details. Each object requires: Host, Port, System ID, Password, and System Type.
smsHeaderList	List of Strings	List of approved SMS Sender IDs (headers) authorized for use with the configured SMSC hosts.

The configuration also requires specifying the Heart Beat (configurable enquire_link frequency) to maintain the persistent connection, although this specific parameter field is not explicitly listed among the required fields.

Setup Instructions

Setting up the SMSC integration is highly technical and requires coordinating network and protocol details with the SMSC provider.

1. Prerequisites: Obtain the following SMPP connection details from your SMSC provider: server Host and Port, API System ID, Password, System Type, and the list of approved Sender IDs.

2. Configure in Netmera: Navigate to the Connectors panel and select the SMSC connector.

3. Add Server Configurations: Input the required Host, Port, System ID, Password, and System Type for each SMSC server you wish to connect to (for HA/Load Distribution).

4. Add SMS Headers: Input the list of approved Sender IDs/Headers into the smsHeaderList.

5. Save Configuration: Save the complex multi-item configuration.

Usage Notes & Considerations

1. Low Priority Ranking: SMSC is ranked at Rank 5 in the overall SMS connector priority list. If higher-priority connectors (Message Center, Mobildev, FigenSoft, Infobip) are active and configured, all SMS traffic will be routed through them first, unless they fail.

2. SMPP Protocol Specificity: Requires deep technical understanding and accurate configuration of protocol parameters (e.g., System ID and System Type) to ensure a successful Persistent TCP connection (Binding) can be established.

3. Real-Time Monitoring Dependency: While the integration includes features for real-time status monitoring and automatic/manual reconnection, the high-performance nature of the direct TCP link means connection stability must be continuously monitored using features available in the Netmera UI (e.g., on the /connector/config/smsc page).

4. No Inbound Data Mentioned: The documented data flow is exclusively Outbound, implying it is strictly used for sending messages, not for receiving delivery receipts or MO messages back to Netmera via the standard connector framework, which usually requires a separate mechanism or dedicated configuration not detailed here.