Indicators lights not working ATA HT812

[LPAT]

is it normal that the indicator lights are not on but everything is working fine and I am with freephoneline ATA HT812

[Liptonbrisk]

Take a look at page 20 of the admin guide: http://www.grandstream.com/sites/defaul ... _guide.pdf.

If incoming calls work fine, submit a ticket to Grandstream requesting advice: https://helpdesk.grandstream.com/.

[LPAT]

yes everything works well even incoming calls the only lights that come on is power and LAN led

[Liptonbrisk]

Incoming calls means your ATA is registered.

That situation doesn’t seem normal to me. Unplug your ATA for 30 seconds. Then plug it back in.
If the problem persists, contact Grandstream.

[LPAT]

Here I unplug and plug in again and it is always the power and LAN lights that remain on

[Liptonbrisk]

I would contact Grandstream.

[LPAT]

I will still contact them and second question is that a freephoneline telephone number can be changed ?

[Liptonbrisk]

Please visit https://support.freephoneline.ca/hc/en- ... are-moving

[LPAT]

RING FREQUENCY 20Hz or 25Hz please ?

[Liptonbrisk]

RING FREQUENCY 20Hz or 25Hz please ?

20Hz is more often used in Canada and the U.S. Europe is more likely to use 25Hz.
https://www.zytrax.com/tech/telephony/ring_patterns.htm

[LPAT]

dial plan for *67 ( send anonymus ) please ?

[Liptonbrisk]

dial plan for *67 ( send anonymus ) please ?

Freephoneline does not officially support *67. So using a dialplan for *67 is pointless.

You shouldn't need a dialplan for *67 if "Enable Call Features" is enabled in the ATA under the "Profile" tab that you're using.
"CID Per call" feature also has to be enabled.
Click http://forum.fongo.com/download/file.ph ... ew&id=2095
You would just dial *67 along with the phone number.
Refer to #2 below.


I don't have a Grandstream to test, but in theory, you would remove anything that could possibly match *67 (*xx for example) from your dial plan so that the ATA processes the star code instead of sending the star code to the provider (Freephoneline). *67 still won't work properly when calling Fongo Mobile numbers, even if the star code is processed by the ATA. The receiving provider has to comply with the anonymous flag that's sent in the SIP header. Some providers recognize the anonymous flag and comply. Others don't. Refer to #2 below.


It's better to have *67 supported at the provider level (the provider blocks outgoing Caller ID information completely), which Freephoneline doesn't do. Refer to #1 below.


There's two possible ways *67 (block outgoing Caller ID) works:

1)You can send *67 through the service provider, who then either accepts the code or doesn't do anything. Freephoneline, by default, doesn't do anything. At least that was the case before server migration: http://forum.fongo.com/viewtopic.php?f=15&t=19702 (I'm just posting that link to show there was a server migration). There have been a few exceptions made for certain individuals, but it's rare.

Unless an FPL account supports *67, using a dial plan for it is pointless.


2) You can have *67 processed by your ATA, which sends an anonymous call flag in the SIP header along the path to the receiving carrier that, in turn, has to recognize and agree to not show Caller ID (CID). Blocking outbound calls to Telus Mobility numbers, for example, works when *67 is processed by the ATA. That is, no caller ID is displayed. When *67 (with Disable CID per call setting is enabled) is parsed by an ATA or IP Phone, my Freephoneline number constantly appears when calling Fongo Mobile numbers. But my outgoing Freephoneline number is blocked when calling regular Telus mobile numbers, for example. Telus Mobility acknowledges the anonymous flag and complies. Fongo Mobile doesn't.



For Cisco ATAs, for some reason, after FPL's server migration earlier this year, users have reported 15 minute call drops and also fast busy when block Block CID Setting is enabled. So using *67 can cause problems with some ATAs and Freephoneline.