Overview
You have an international SMS partner whose SMSC you would like to bind to an SMPP connection you have created for another P2P partner. The route is an AO (SMS traffic originated by an application) for our application, and the path is assumed to be AOMT.
Solution
For this, the new SMSC should act as an application and needs to be defined as such in NewNet's SMSC. Please follow the steps below:
- Create a Service Class via MGR GUI -> Environment -> Service Class -> Add New
- Fill in with an appropriate name
- Select an apt "Allowed Traffic" (for just AO, select AO only)
- Select "Outside Only" Session Model
- Select the appropriate "Charged Party" from drop-down
- Save and enable the New Service Class
- Create a Group in MGR GUI -> SMS Applications -> Groups -> Add New
- Fill in with an appropriate name
- Save and enable the New Group
- Create a Category in MGR GUI -> SMS Applications -> Categories -> Add New
- Fill in with an appropriate name
- Save and enable the New Category
- Create an Outside Listener in MGR GUI -> Environment -> Outside Listeners -> Add New
- Fill in an appropriate Name
- Mention the External SMSC Application Port where it needs to bind to our SMSC against "TCP Port"
- Fill in the Maximum Sessions both parties agree to have simultaneously open
- Fill in the other details as needed
- Save and enable the Outside Listener
- Create the SMPP Application via MGR GUI -> SMS Applications -> Applications -> Add New
- Fill in with the details highlighted in green
- choose the newly created Category, Group
- Discuss other parameters with SMSC-IR and fill in here as required (like Password, Service ID, System Type, Short Code, etc.)
- Save and Enable the App
- Create a new AO Rule in MGR GUI -> Routing -> Routing Rules -> AOR -> Add New
- Fill in with appropriate Name and Priority
- Select the Application created in the previous steps as Condition of Origin
- Select the Action "Route to MS Fallback to Storage"
- Select appropriate "AMS Queue" and also "Log Profile"
- Save and enable the rule
Note: Since it is the external SMSC that is binding to your SMSC as an SMPP application, there is no need to input IP and Port. It is your IP:Port which the external SMSC would bind to, as an SMPP application. The port to which the external SMSC Application would bind would be set as an Outside listener, which is already encompassed in the steps above.
For more information, please refer to the Hub, the Routing and SMS Application sections of the MGR Operating Manual, and also to the RTR Operator Manuals which can be found at the NewNet Download Center.