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

Modem get's recognized but does not give any number #147

Open
pabloemma opened this issue Mar 13, 2021 · 3 comments
Open

Modem get's recognized but does not give any number #147

pabloemma opened this issue Mar 13, 2021 · 3 comments

Comments

@pabloemma
Copy link

Just installed the system on a Raspberry pi3B with a us robotics 5637 and callattendant recognizes the modem.
When I call, the modem will even blink on the data, and the output in debug just shows
b'RING\r\n'
{RING LED BLINKING}
b'RING\r\n'
{RING LED BLINKING}
I have caller ID on my line and the jack I am using works. I tested it with a real phone.
I attach my output.
I am running python3.7.3
Thanks for any help,
Andi

debug.txt

@marklt1
Copy link

marklt1 commented Mar 27, 2022

Just installed the system on a Raspberry pi3B with a us robotics 5637 and callattendant recognizes the modem. When I call, the modem will even blink on the data, and the output in debug just shows b'RING\r\n' {RING LED BLINKING} b'RING\r\n' {RING LED BLINKING} I have caller ID on my line and the jack I am using works. I tested it with a real phone. I attach my output. I am running python3.7.3 Thanks for any help, Andi

debug.txt

I am seeing the exact same behavior also. My debug text was like yours. The only difference is that I am running on Python 3.9. My Caller ID is passed to the other POTS phones. I never see it in the logs or console and only this:
b'RING\r\n'
{RING LED BLINKING}
b'RING\r\n'
{RING LED BLINKING}
b'RING\r\n'
.
I am using a OBiTALK OBi200. I did the USB modem firmware update listed here but still no luck - https://groups.io/g/callattendant/topic/76934787#282

@pabloemma
Copy link
Author

pabloemma commented Mar 27, 2022 via email

@marklt1
Copy link

marklt1 commented Mar 27, 2022

Thanks for the tip. I was thinking now that it could be a python version issue but now likely a hardware issue based on your experience.

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

No branches or pull requests

2 participants