this post was submitted on 27 Oct 2023
1 points (100.0% liked)
VoIP
1 readers
1 users here now
Rules
-
Be civil. Disagreements of varying intensities will happen, but particularly vitriolic attacks will be pruned from the discussion.
-
Do not promote or advertise for any business, service or product unless responding to a specific request for recommendations. This includes recommending a user change providers when they have not indicated they are interested in doing so.
-
Do not send private messages to users, or invite users to send you a private message, for the purpose of promoting or advertising a business, service or product.
-
Do not invite, encourage, or seek help with engaging in unethical or fraudulent activity relating to VoIP, such as call spoofing, robocalling and autodialers, or fraudulent STIR/SHAKEN attestation.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Been a while since I played with my HT813 but I think the ring patterns are more for the FXS port ("how the phone should ring") than the FXO port ("the pattern incoming calls ring witih")
I did something similar to you, getting a hardwired condo enterphone to ring through to my PBX then through to my cell. I think it was a call forwarding setting on the FXO port and the call went through straight away. There's maybe a setting for caller ID on the FXO port too - this is usually sent between the first and second bursts of ringing, so you might want to turn that off to get a quicker notification of an inbound call.
Maybe post a screenshot of all the FXO settings?
I had more time today and I believe I determined the issue.
I have an Xlink BTTN which I had in storage. I used it for a number of years till I decided to go full digital.
I basically called into the HT813 and it answered on every ring pattern regardless of the C=xxxx stuff. I have since restored that to the c=2000/4000;
I decided to connect it from the RJ11 coming from the panel to the RJ11 of the BTTN and then the output of the BTTN's RJ11 to the FXO of the HT813. Went downstairs, dialed my apartment and it picked up after the first ring pattern, I heard dialing and 2 seconds later my cellphone rang.
That's when it dawned on me. The Xlink BTTN might be reproducing that ring and the gateway sees proper signals and answers it.
Where as the panel downstairs may not be producing enough voltage. Then again technically speaking makes sense. I am on the opposite end of the building away from that panel. With the wire distance. It might have alot of loss that the HT813 is not seeing sufficient ringing.
I'm now in the market for a REN or Ring Voltage booster or something that can provide a clean signal the HT813 would recognize. I think it would solve my issue.
Hmm.. lower voltage isn't the worst theory out there.. but at the same time I'd be surprised.. those ATA devices have always had super wide tolerances on the FXO port. What you could do maybe is spin up a syslog server on your PC and get the ATA to log to it for a bit. Go buzz in from downstairs and see if it spits out data on the ringing.
Your theory on the Xlink re-generating the ring tone? Yeah, could be - I'm not familiar with those devices but if you're going wall outlet --> xlink --> FXO port on the ATA and it's working? welllll... kind of suggests that's what's going on.. but I'm honestly surprised that wall --> FXO doesn't work the same way.
With it connected wall --> FXO, when you buzz in from downstairs, does it just ring and ring and ring? Or do you hear something else?
With the Xlink BTTN being put into the middle of this, I go dial downstairs, it picks up on the first ring. And I have picked random times to test it. Zero issues
With the FXO connected directly to the wall and downstairs when I dial. It will ring and ring and ring and nothing ever picks up. It eventually times out and just cancells.
I have an older 2500 phone with bell Ringers. Seems to ring strong but that's only listening to the audio from my phone as I hit record and go dial downstairs.
I'll do a syslog tomorrow.