MrRebooting wrote:Hello
1) Busy line
2) Nop, I never called the 911
Okay, I wanted to see whether your FPL account is blocked. I suspect it is not blocked. If you want to ensure it's not, you can try to provision your FPL account on a SIP app, or try the Freephoneline desktop app on a Windows PC:
viewtopic.php?f=4&t=8268.
Light is flashing red
What is the flashing interval?
Red Button flashes every 1 second If Ethernet link is down
Red Button flashes every 2 seconds means DHCP Failed or WAN No Cable
(if DHCP is configured)
Red Button flashes every 4 seconds means ATA fails to register
(if SIP server is configured)
Red Button flashes every 6 seconds means Firmware Upgrading
Red Button flashes briefly means No STUN response
Red light steady means device malfunctions
https://www.voipsupply.com/downloads/dl ... _guide.pdf (page 14)
4) There is a voice giving a kind of code (5 length) with letter and number but not a WAN IP
Dialing *** reaches the interactive voice menu (IVR or interactive voice response).
You're hearing an error code. What is the code?
https://www.voipsupply.com/downloads/dl ... _guide.pdf (page 10)
IVR ERROR REPORT
IVR supports error reporting when the following problems occur. User will hear silence when picking
up the handset. After pressing ***, user will hear one or more error codes listed below. User may hear
one or more error codes depending on errors detected such as E104E103E. Upon hearing error code,
user can press # to get into the IVR main menu.
E101E Ethernet link down
E102E No IP address obtained (DHCP or PPPoE mode)
E103E Device is not registered to SIP server
E104E Provisioning in action
E105E No STUN responses
Does not work since my modem/router is in bridge mode (since my UDM pro is the router) and cannot get an IP (normaly)
All ISP's modems, modem/router combos, gateways, or hubs can provide internet/WAN access to a single device, including an ATA, regardless of whether they're in bridge mode.
What doesn't get an IP normally? Is the ATA not in DHCP mode? Ensure that it is.
Login to ATA via web UI.
Navigate to Basic Settings tab.
Ensure IP address is set to "dynamically assigned via DHCP (default)".
Are you using STUN in the ATA? Don't. Using STUN introduces an additional point of failure. When the STUN server goes down, so does your FPL service.
Ensure you don't have a STUN server listed under Advanced Options in the ATA. Don't enable STUN.
Also, the light remains red and when I cal incoming call, it goes directly to the voicemail.
The ATA is not registered. Registration is a requirement for incoming calls. Lack of registration means incoming calls go to voicemail. Registration is not a requirement for outgoing calls, except to ensure the call continues beyond 15 minutes.
I cannot check the registration since from my computer I cannot access the ATA.
The light on the front of the ATA would be green or not blinking red every 4 seconds if the ATA were registered.
Incoming calls not working also means the ATA isn't registered.
Also, a smartphone or tablet with cellular data access can login at
https://www.freephoneline.ca/showSipSettings to check registration status.
SIP server is voip.freephoneline.ca
Change that to "voip4.freephoneline.ca:6060" without the quotation marks while troubleshooting.
To be honest, the next tests will be to bring my ATA to a friend house and try with their internet.
Sure.
Ethernet link being down (E101E) doesn't make sense if you can log into the ATA via web user interface to check settings. E101E must not be the error code.
Has there been a power outage lately? Or a lightning storm?
If you have access to another power supply/power adapter for the ATA, try it.
Provided the ATA isn't damaged, if all else fails, you can try to perform a factory reset. Then you would have to configure the ATA again.
Configuration guide is located at
viewtopic.php?f=15&t=16334.