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

Changes to support alternative configuration settings #7

Closed
wants to merge 1 commit into from

Conversation

reyrodrigues
Copy link
Contributor

Additional check to parse out what comes out of the ModemNumber element.

If the modem is properly set up, the value is :;
If the modem is not properly set up, the value is then and no colon;
If the modem is a single port modem, this is either empty, or it has the SIM phone number;

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 98.29% when pulling fe4aed3 on reyrodrigues:modem_number into 097e288 on caktus:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 98.29% when pulling fe4aed3 on reyrodrigues:modem_number into 097e288 on caktus:master.

# RR: This gets a little more complicated than that. If the modem is not set up correctly,
# this field will be only the index of the number. The possible values are:
# <ModemNumber>[Index]:[Configured Phone Number]</ModemNumber> -- for multi-port and configured
# <ModemNumber>[Configured Phone Number]</ModemNumber> -- for single port and configured
Copy link
Contributor

Choose a reason for hiding this comment

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

So this part is unfortunately not quite right. Single Port Modems only put their modemnumber in there, no phone number. The only valid ModemNumber sent by our 1-port modem is: <ModemNumber>1</ModemNumber>.

Given that, I don't think there's a good way of differentiating a properly configured single-port modem from an improperly-configured multiport modem, aside from adding a setting to the configuration (yuck...)

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.

None yet

3 participants