- Campaign v7 documentation
- Latest updates
- Release Notes
- Get started
- Start with Adobe Campaign
- Privacy
- Profile management
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- Connectors
- Create and send messages
- Get started with messages
- Key steps when creating a delivery
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Track messages
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Marketing Resource Management
- Distributed marketing
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Get started with workflows
- Execute a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitor workflows
- Advanced management
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Deploy Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Appendices
- Monitoring guide
- Developers guide
- Technotes
- Campaign Control Panel
Migrate unsupported SMS connector to the Extended Generic SMPP connector
As of release 20.2, legacy connectors are deprecated. This document will help you migrate connectors that are still running on the old system to the recommended SMPP connector.
This migration is not mandatory but recommended by Adobe and will ensure you are running on the latest supported version of the software.
About SMS connectors
The following connectors are deprecated as of release 20.2:
- Generic SMPP (SMPP version 3.4 supporting binary mode)
- Sybase365 (SAP SMS 365)
- CLX Communications
- Tele2
- O2
- iOS
Deprecated capabilities are still available and supported, but they will not be further enhanced. We recommend using the Extended generic SMPP connector.
For more information on deprecated and removed features, refer to this page.
Old SMS connectors are using the Java SMS connector that overloads the web process. Migrating to the new Extended Generic SMPP connector will move this load to the MTA which can support it.
Migrating to the Extended Generic SMPP connector
Even if you can transpose the parameters, configuring the Extended Generic SMPP connector requires you to talk with your provider who will give you the information needed to fill in the rest of the parameters. For more on this, refer to this page.
First, you will need to create a new Extended Generic SMPP external account and then you might be able to transpose some of the parameters. You can find the detailed steps in this page.
You now need to fill in the parameters from the Mobile tab of your newly created Extended Generic SMPP external account depending on your previous connector.
From the Generic connector
When choosing the Generic connector, you should have a custom JavaScript connector which will adapt to each situation.
If you know that this connector is already using the SMPP protocol then you can migrate to the Extended Generic SMPP connector. If not, check with your provider if they support the SMPP protocol and set up a new connector with the help of a consultant.
From your Generic connector, you can transpose to your newly created Extended SMPP account:
In the Connection Settings tab:
- Account
- Password
- Server
- Port
From the Generic SMPP connector
From your Generic SMPP connector, you can transpose to your newly created Extended SMPP account:
In the Connection Settings tab:
- Account
- Password
- Server
- Port
- System Type
In the SMPP Channel Settings tab:
- Source number
- Source NPI
- Destination NPI
- Source TON
- Destination TON
In the Mapping of Encoding tab:
- Outbound SMS coding
In the SMSC specificities tab:
- Coding when sending corresponds to ID Format in MT acknowledgement
- Coding when receiving corresponds to ID Format in the SR
From the Sybase365 connector
From your Sybase365 connector, you can transpose to your newly created Extended SMPP account:
In the Connection Settings tab:
- Account
- Password
- Server
- Port
- System Type
From CLX connector
From your CLX connector, you can transpose to your newly created Extended SMPP account:
In the Connection Settings tab:
- Account
- Password
- Server
- Port
- System Type
In the SMPP Channel Settings tab:
- Source number
In the SMSC specificities tab:
- Coding when sending corresponds to ID Format in MT acknowledgement
- Coding when receiving corresponds to ID Format in the SR
From the Tele2 connector
From your Tele2 connector, you can transpose to your newly created Extended SMPP account:
In the Connection Settings tab:
- Account
- Password
- Server
- Port
- System Type
In the SMPP Channel Settings tab:
- Source number
- Source NPI
- Destination NPI
- Source TON
In the Mapping of Encoding tab:
- Outbound SMS coding
From the O2 connector
From your O2 connector, you can transpose to your newly created Extended SMPP account:
In the Connection Settings tab:
- Account
- Password
- Server
- Port
- System Type
In the SMPP Channel Settings tab:
- Source number
- Source NPI
- Destination NPI
- Source TON
- Destination TON
Business.Adobe.com resources
Resources
Adobe Account
