REQ-201 One ESME in Many Clusters #25
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sters. The ESME removal to be implemented.
# Conflicts: # .gitignore # core/bootstrap/pom.xml # core/oam/clismpp/pom.xml # core/pom.xml # core/smpp-extensions/pom.xml # core/smpp-extensions/src/main/java/org/restcomm/smpp/EsmeManagement.java # management/ui-management/pom.xml # pom.xml
|
Related with: RestComm/smscgateway#240 |
|
Hello, do you have any design document for your introducing functionality. I am not sure as for now that suggested new functionlity fits to a clustering model we are going to reach in SMSC GW. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
here is a proposal of changes that need to be done in the SMPP Extension module (used by SMSCGW) in order to enable a placement of 1 ESME in many (more than 1) clusters/NetworkIds.
Apart the changes in this module, little adaptation in the SMSCGW Core is required as well. The link to the corresponding PR (in SMSCGW) will be provided here later.
This solution was tested with simulators with cases covering DLR (in deliverSM).
Please review and let me know your opinion on this approach.
Regards,
adam