Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add possibility to specify address range when binding with SMSC #131

Merged
merged 1 commit into from
Jan 23, 2024

Conversation

Hurtsich
Copy link
Contributor

We're using the lib to connect to SMSC but there was no way to setup the address range parameter within the connector.
We saw that the bindRequest struct was responsible for it and we took the freedom to improve the way we instantiate the connector.
With this pull request you can see that on the Receiver and Transceiver, we can now modify the connector without breaking the public interface of the lib. Which can now be used to add the addressRange option.

@goten4
Copy link
Collaborator

goten4 commented Jan 11, 2024

lgtm

@laduchesneau
Copy link
Collaborator

My two cents, the Functional Option should also be added to Transmitter bind, address_range (addr_ton, addr_npi) are allowed in the bind_transmitter body.

@goten4
Copy link
Collaborator

goten4 commented Jan 11, 2024

@laduchesneau : Even if it's technically possible to provide address_range in a transmitter bind, it is not expected according to the specification :

The address_range parameter is used in the bind_receiver and bind_transceiver command to specify a set of SME addresses serviced by the ESME client.

Copy link
Owner

@linxGnu linxGnu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you for contributing.

@linxGnu linxGnu merged commit f949840 into linxGnu:master Jan 23, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants