The SMPP network interconnect solution
Messaging businesses may have requirements to be able to route messages between networks using SMPP. As such they need a solution which meets a range of specialised requirements, including the need to act as an SMPP server, make SMPP client connections to a range of networks and their SMSCs, route messages from one network to another according to conditional logic and apply filtering checks in order to remain compliant with message content rules which “downstream” networks might impose. The Selenium SMPP Router solution meets all these requirements and more and comprises Selenium SMPP Access and Selenium SMPP Router running as a single service with a configuration designed to meet these requirements.
Download our Selenium SMPP Router overview presentation here
|“Upstream” networks may connect to the Selenium SMPP Router and submit messages to it using SMPP. In this instance, the Selenium SMPP Router solution is acting as an SMPP server to those upstream SMPP clients.
|The Selenium SMPP Router may connect to many “downstream” SMSCs and act as an SMPP client, submitting messages to those SMSCs using SMPP.
|Accounts can be created for all upstream networks so that their SMPP sessions can be authenticated and billing records (“CDRs”) attributed to the right network for subsequent billing.
|Selenium SMPP Router is able to produce billing records, often referred to as CDRs (Call Data Records) at various points in the message processing lifecycle. These records contain data which has been selected to support typical billing and support scenarios.
|MT messages submitted by upstream networks must to be routed to an appropriate SMSC in a downstream network. It is possible to define routing rules which revolve around the country code (the first so many digits) of the address to which a message is sent.
|Delivery Receipt Routing
|Delivery receipts received from the downstream networks must be routed to an appropriate upstream network. The routing decisions relating to delivery receipts is largely automatic and made with reference to details of the original MT message to which the delivery receipt relates.
|You may need to block messages which contain inappropriate content in order that you comply with the rules imposed by your “downstream” mobile network operators. Selenium SMPP Router allows you to define message filtering rules which are applied to MT messages submitted by upstream networks. In the event that a message matches a rule, it is “held” in a database queue and this queue can be managed via the Selenium FM user interface. Managing the queue involves inspection of the messages it contains and deciding to either let the message through to the downstream mobile network or to block it permanently.
|Selenium SMPP Router is able to monitor message senders for suspcious patterns of behaviour such as the submission of large numbers of messages from the same source address to the same destination address. Such behaviour may be indicative of “spam”. The Selenium FM user interface provides you with the ability to specify rules which Selenium SMPP Router will evaluate and enforce at run-time as it tracks message submission frequency from different senders to different destinations. Messages blocked due to “frequency violations” are also placed in the Selenium FM held messages queue and may be subject to similar management actions as for messages blocked by the message filtering sub-system.
|Delivery receipt content mapping
|If your Selenium SMPP Router instance is connected to multiple downstream networks over SMPP, it may be the case that these different networks produce their delivery receipts according to differing content standards, for example with different error codes or descriptions. Via the Selenium CP user interface, users of Selenium SMPP Router may specify rules which allow the standardisation of delivery receipt content to take place at run-time.
|Operational Monitoring and Management
|Selenium SMPP Router includes a user interface called Selenium CP. “CP” provides up to date statistical information about messages handled by the system and at a glance depiction of the “health” of each key system component such as each of the connections to SMSCs. It also provides importent information such as graphs which depict the “latency” of each SMSC connection so that performance issues can be analysed and informed discussions with SMSC oeprators can take place supported by concrete, unarguable data about connection performance. The status of various components may also be changed via CP. For example, connections may be taken off line or brought back on line at the click of a mouse. Finally, the system may be configured to send alerts by email in response to the occurrence of system issues.
|The most important system configuration details may be updated via Selenium CP without the need to restart the Selenium SMPP Router server. A special “configuration service” in Selenium SMPP Router handles all configuration change requests issued via Selenium CP one at a time to ensure that such changes are handled in a steady, measured way, which should not be allowed to disrupt the flow of messages.
|User interface: Selenium CP
|Selenium CP (Control Panel) is a web based user interface which allows operators of Selenium SMPP Router to monitor and manage their Selenium SMPP Router server and to make configuration changes of various sorts.
|User interface: Selenium FM
|Selenium FM (Filtering Manager) is a web based user interface which allows operators of Selenium SMPP Router to maintain message filter and frequency tracking rules and to manage messages blocked by these rules and placed in the “held messages” queue.
Prices are available on application to Selenium Software. Note that Selenium SMPP Router may be purchased with full source code and developer training if required.