-
Notifications
You must be signed in to change notification settings - Fork 303
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
Can it work when the 3G connection is active? #18
Comments
If I first make the connection, and then start the python script, all is fine. |
Thanks for the report! I'm glad you found a workaround, but this is indeed a valid bug (and one which I have been able to replicate), so I am reopening this until I have submitted a fix. |
The issue is that the sakis3g script modifies the "extended incoming call indication" setting of the modem (AT+CRC). Since python-gsmmodem sets this during connect(), it does not expect an external program to modify it - this is also why it works if you start python-gsmmodem after sakis3G. The patch above allows python-gsmmodem to detect this change, so it should work fine either way for you now. Please re-open the ticket if the issue is not resolved for you. |
Works like a charm here. Thanks! |
add decoding for enc_list response
So all works well when there's no 3G connection. But when there is I have an issue running the incoming_call_demo.py script. When I dial the number it is ringing and with every ring an error message logs to the screen:
Manufacturer: huawei
Model: K3715
Revision: 11.104.05.00.00
Furthermore, I'm using the sakis3G script to connect.
The text was updated successfully, but these errors were encountered: