IP addresses for your firewall
There are two directions, and each has its own addresses: where our requests to you come from, and where your systems connect to us. Every address on this page is reserved for Interconnect-Solutions and stays the same when our services are redeployed. If one ever has to change, we announce it in advance.
Main addresses are in use now, all of them at once. A reserve address is where we switch if the main ones fail, and it may carry no traffic today. Add it in advance, so that the switch needs nothing from you.
Requests from us to you: webhooks
Delivery reports, incoming messages and other notifications that Interconnect-Solutions sends to your notification URL come from these addresses:
| Address | Role |
|---|---|
138.68.127.125 | Main |
Connections from you: SMPP
| Name | Address | Ports | |
|---|---|---|---|
| Plain | smpp.interconnect.solutions | 138.68.127.125 | 3700, 2775 |
| TLS | smpp-tls.interconnect.solutions | 138.68.127.125 | 2995 |
| Reserve | — | 35.204.59.96 | 3700, 2775 |
Point your client at the name, and use the address only in the outgoing rules of your firewall. For TLS the name is mandatory: the certificate is issued for it.
The reserve entry leads to the same SMPP platform, bypassing the main entry point, so the same account binds there with the same login and password. Add it as a second address if your client can switch over by itself when the main one does not answer. It carries plain SMPP only; TLS works through the name.
How to connect, what to put in the bind and what the session understands — see SMPP connection.
For carriers and providers: our connections to you
If Interconnect-Solutions sends traffic through you — binds to your SMSC over SMPP or calls your HTTP API — allow these addresses on your side:
| Connection | Address | Role |
|---|---|---|
| SMPP to your SMSC | 35.204.59.96 | Main |
| SMPP to your SMSC | 138.68.127.125 | Reserve |
| Requests to your HTTP API | 138.68.127.125 | Main |
Each is a single address, not a range.