Fongo Community Forums

Credits to Val, thank you for your help.

The attached PDF will help you set up your SPA122 device from scratch. It is a known working configuration so if you are having troubles with your SPA122 reset back to defaults and follow this guide.

--

Edit by LiptonBrisk: 1.Navigate to Voice-->SIP tab-->SIP Timer Values (sec)-->Reg Retry Intvl should be 120 seconds
https://support.freephoneline.ca/hc/en- ... redentials

2. (Do what Mango wrote below.)
In your SPA122 ATA, navigate to Voice-->SIP tab-->NAT Support Parameters, and make sure that the following settings are enabled:

a)Handle VIA received-->yes
b)Handle VIA rport-->yes
c)Substitute VIA Addr-->yes

3. In your SPA122 ATA, navigate to Voice-->Line 1 (or whatever Line you're using for FPL)-->SIP settings, and change SIP Port to a random number between 30000 and 60000. Do this for security reasons (to help avoid SIP Scanners/hackers). Also, this step may help to temporarily address a corrupted NAT association that's developed between a router and ATA (if you're having registration issues, try selecting a new random port number in this range, and then reboot the ATA. If that works, you were dealing with a corrupted/stale NAT association in your router).

4. In your ATA, navigate to Voice-->Line (whichever you use for FPL)-->Supplementary Service Subscription-->Block CID Serv:
a) change to no
b) Click "submit"
Do this to avoid 15 minute call drops.







By the way, these are the known methods for accessing the ATA:


Method A: LAN Access (Recommended First-Time Setup)

Prerequisite: USB-to-Ethernet adapter if laptop lacks Ethernet port

1. Connect an Ethernet cable from the computer to the yellow ETHERNET port on the SPA122.

2. Ensure the computer is set to obtain an IP address automatically (DHCP).

3. Open a web browser and navigate to http://192.168.15.1.

4. Log in with default credentials. Username is admin, and Password is admin (case-sensitive).

5. If the page doesn't load, manually set the computer's IP to 192.168.15.2 with subnet 255.255.255.0, then revert to automatic after configuration.

6. Change the default admin password (Navigate to Administration tab> Management > User List). This step is mandatory before Remote Management will function.

7. Navigate to Administration --> Management --> Web Access Management.

8. In Web Access Management, set
i) Admin Access to Enabled
ii) Web Utility Access to HTTP or HTTPS (HTTPS is more secure)
iii) Remote Management to Enabled
iv) Remote Management Port: Enter desired port (default 80)


9. Click "Submit" to save all settings.




Method B: WAN Access via IVR (After Method A Completed)

Please note this critical requirement: the default admin password must be changed via Method A before IVR code 7932# will function; otherwise, it returns "invalid option".

1. Connect an analog phone to "Phone 1" (grey port).

2. Press **** (four stars) to enter the IVR menu.

3. Dial 7932# followed by 1 to enable WAN access to the admin web server.

4. Dial **** (four stars) again to re-enter the IVR menu.

5. Dial 110# to hear the IP address announced.

6. Enter the IP address you heard into a web browser (include port if changed from default 80, ex. https://203.0.115.50:80).

7. Log in with the new admin credentials set in Method A.

8. Select Advanced view in the upper right for full configuration options.


IVR codes (after dialing ****)

110# -- Reads WAN (Internet port) IP address | Used for remote access after 7932# is enabled

210# Reads LAN (yellow Ethernet port) IP address | SPA122 only; default is 192.168.15.1

7932# Toggle WAN web access (1=enable, 0=disable)
Only works after changing default admin password


https://www.cisco.com/c/en/us/support/d ... pa122.html

Emulator is located at https://highspeed.tips/files/emulators/ ... ement.html.

To prevent one-way or no audio with the new FPL switches, set the following from within Voice >> SIP:

Handle VIA received: yes
Handle VIA rport: yes
Substitute VIA Addr: yes

Hi,

This is what finally helped me.

Thanks a lot. I'll post my whole story later but after trouble shooting for days and even convincing rogers to disable SIP ALG on my router, this is what actually solved my one way audio problem where the other person could hear me but I couldn't hear them. Also I wasn't able to connect to certain phone numbers after I dialed. This has also been resolved.

Hello,

I have recently switched from BELL DSL to Tecksavvy CABLE and can't get my CISCO ATA to work. I'm wondering whether my Linksys WRT1900ACS router isn't letting traffic through? I've configured the ATA122 using the parameters shared here and am at a loss. Not sure who to ask for help or where to go. Any ideas would be welcomed!! Thanks.

saunders000 wrote:Hello,
and can't get my CISCO ATA to work. .

Can you be a little more specific please? What isn't working?
Registration?

1) What does the registration status in the ATA indicate?

Linksys WRT1900ACS

a) Ensure whatever modem/router combo you're using with Teksavvy is in bridge mode.

b) And try disabling SIP ALG
Click https://www.phonepower.com/mediawiki/im ... 00AC09.png

c) Then reboot modem-->router (wait for it to be fully up and transmitting data)-->ATA in that order.
That's always the proper device reboot order.

2) Are you getting 1-way audio issues? Visit viewtopic.php?f=8&t=20532

Great user guide trying to repurpose my YAK VOIP CISCO SPA122 for freephoneline.ca. It seems YAK has the device locked configured for their own SIP settings. I'm able to login as admin and change the SIP settings according to the directions provided for the freephoneline.ca setup, but the device has none-the-less been per-customized by YAK which means it's probably useless. Anyone else familiar with this issue? I actually have 3-ATA's including this one, and all of them are locked by the VOIP service provider so I can't use any of them. Probably end up buying a new ATA that's unlocked. My freephoneline.ca works great in microSIP but would be great if there was someway to repurpose my YAK CISCO SPA122 but somewhat doubtful unless some has any suggestions.

TerryC wrote: 12/09/2025 the device has none-the-less been per-customized by YAK which means it's probably useless

The only other relevant thread I've come across here is located at viewtopic.php?t=19210. Someone speculated that "Restricted Access Domains" may only block Line 1, leaving Line 2 available for any provider if you have admin access. However, that has not been confirmed (I'd be surprised if that's true), and the original user discussing YAK hardware chose to buy a new ATA rather than test anyway.

Locked SPA122s typically push a custom configuration that sets the provider's SIP server, hides certain fields, and re‑applies those settings on every factory reset or power cycle via a provisioning URL. YAK uses the "Restricted Access Domains" parameter, which is hardcoded to yak.ca, yakdigital.ca, yakdigitalphone.ca, etc. and cannot be edited even with admin login. This makes the device refuse to register with other SIP servers (voip.freephoneline.ca, for example), regardless of what you configure in Line 1 settings.

If you have admin login access, you can try to verify in the System tab whether "Restricted Access Domains" is empty and editable. If YAK has populated this or it is greyed out, Freephoneline won't work. In the Provisioning section, you can try clearing the "Profile Rule" and any resync URLs/intervals, then save and reboot. If that field is locked or keeps repopulating with a YAK URL, the ATA is being forced to re‑download Yak's configuration at startup. You can try the IVR code ****7932# (1=enable, 0=disable) to enable WAN access, but the default admin password must be changed for that to work anyway.

You can also try factory resetting the ATA while WAN is disconnected (no internet access for the ATA) and clearing profile rules (by logging into LAN). I'm not sure that will help if custom firmware was used. However, if you can flash to official firmware afterwards, that may help: https://www.cisco.com/c/en/us/support/d ... pa122.html. Basically, the idea is to block access to the internet for the ATA, and then perform a factory reset. Afterwards, log into the ATA and remove any profile rules/configuration urls that may still be present. Finally, attempt to flash or update the ATA to using official firmware: https://software.cisco.com/download/hom ... .4.1%20SR5. However if that doesn't work, the ATA may be using custom firmware that prevents removal of provisioning links and profile rules.

For some, fully unlocking a SPA122 appears to require connecting to the internal serial console, interrupting the bootloader, and manipulating flash partitions in its Linux environment to remove vendor customization files by deleting or renaming `custom.dat` and `flat_profile.xml` in the `/ca_data` partition. This works but requires opening the case, soldering/clipping to the J2 UART header, and issuing low‑level commands that can brick the device if done incorrectly. Here's an example: https://www.insentricity.com/a.cl/277/u ... y-provider. You may find that's not worth the effort.

I typically do not support locked ATAs; I find supporting them tends to be a waste of time (especially if custom firmware was used).

Hello Liptonbrisk,

Thank you for your thorough and knowledgeable technical assessment which is greatly appreciated in consideration of the time and effort it takes to read forum questions and respond accordingly. I ended up buying a new Grandstream ATA. The cost is reasonable, device highly recommended and should have it configured and working by this weekend. Might, for fun, try some of the suggestions you've offered to repurpose the YAK ATA and if it works, give it to someone else to enjoy freephoneline.ca services. Thanks again.

Terry

You’re welcome. Good luck!