12,579
edits
Category:VoIP Faults: Difference between revisions
m
→Using an ATA but the phone doesn't actually ring, but it still works
mNo edit summary |
|||
|
If you have an older phone plugged in to a VoIP-to-Analogue ATA, and if calls work, but the phone doesn't actually ring, then you may be needing a RG11-to-BT adapter that includes a ring capacitor, such as https://www.broadbandbuyer.com/products/2370-esscable-rjp-bts/
== Ghost calls ==
If you receive phantom calls, perhaps from a CLI (eg just 4 digits) that is odd looking, and when you answer, there's no one then these are probably from portscans of your network and not actually from the A&A VoIP servers - they won't appear on the Call Log records.
These scans result in your phone ringing with a strange caller ID, but when you answer, there's no one there because it's not a real call.
* To stop them, look for a setting in your phone such as "Direct IP calls" or 'Accept SIP Trust Server Only' eg, [VoIP_Phones_-_Yealink_DECT#Other_optional_settings Yealink Phones] have this option.
* Also review your [[VoIP Security|Firewall]], and check you're only allowing VoIP traffic from the A&A servers.
| |||