Nokia Fastmile 5G gateway 12

[Liptonbrisk]

"Server" parameter with x.y.w.z, and "Port" parameter ppppp – if different than default (514).
Note that ppppp must be in the range 1 - 65535.
Where do I get these parameters? Sorry I don't understand

Login to Obihai ATA. Navigate to System Management-->Device Admin-->Syslog

Server should be the LAN IP of the PC where you're going to run syslog. ex. 192.168.50.55 (you need to find the LAN IP of your PC).
In Windows, press the windows key, type cmd, hit Enter, then type ipconfig, and press Enter; your LAN IP is the IPv4 Address (e.g., 192.168.x.x).
Or go to Settings-> Network & Internet--> Properties (on your active Wi‑Fi/Ethernet)--> look for IPv4 address

Port can be the default, 514.

[domptg]

"Server" parameter with x.y.w.z, and "Port" parameter ppppp – if different than default (514).
Note that ppppp must be in the range 1 - 65535.
Where do I get these parameters? Sorry I don't understand

Login to Obihai ATA. Navigate to System Management-->Device Admin-->Syslog

Server should be the LAN IP of the PC where you're going to run syslog. ex. 192.168.50.55 (you need to find the LAN IP of your PC).
In Windows, press the windows key, type cmd, hit Enter, then type ipconfig, and press Enter; your LAN IP is the IPv4 Address (e.g., 192.168.x.x).
Or go to Settings-> Network & Internet--> Properties (on your active Wi‑Fi/Ethernet)--> look for IPv4 address

Port can be the default, 514.

Okay I did it. What should I do the next to get the logs? Sorry I never done it before.

[Liptonbrisk]

Okay I did it. What should I do the next to get the logs? Sorry I never done it before.

You need to follow the steps written here: viewtopic.php?p=80667#p80667

1) You need the syslogd.exe executable from the Internet Archive (unzip the file to extract syslogd.exe)

2) Enable logging of SIP Messages for the SP that's being used for Freephoneline.
From the OBi ATA's webUI, navigate to the SP1 Service (or SP2, SP3, or SP4 Service) setting that's being used for Freephoneline.
Change the "X_SipDebugOption" parameter to "Log All Messages."

3) From an elevated (admin) command prompt where the syslogd.exe file is located, run "syslogd -nl -s=all" without the quotation marks.

Open the Start Menu: Click the Windows Start button or press the Windows key.
Type "cmd": This will initiate a search for the command prompt application.
Right-click Command Prompt: Locate "Command Prompt" or "Command Prompt (Admin)" in the search results.
You want Command Prompt (Admin).
Otherwise, right-click on it.
Run as administrator: Select "Run as administrator" from the context menu.
Confirm UAC prompt: if prompted by User Account Control (UAC), click "Yes" to allow the application to make changes.

You may not need an elevated command prompt. I can't remember. I always use one by default.

4) Reboot the ATA. Receive an incoming call. After the call ends, exit syslog. You should find a text file with the contents of the log.

The problem is if RTP packets are never received, and if everything is basically being dropped due to CGNAT, I doubt the log file is going to be terribly useful. It's not always easy to analyze what you can't see. "Oh hey, look: you're not receiving stuff you need to receive." I already knew that (unless you are receiving data and the ATA is borderline wrecked). It's possible something useful will be shown. I'm just a little skeptical.

[Liptonbrisk]

It's important to test whether there's voltage running through the phone jacks before plugging your ATA back into a phone jack that potentially has voltage running through it (that's dangerous for ATAs), and the lack of a change doesn't rule out whether the ATA has been damaged in some manner from voltage running through phone jacks. If possible, you might want to bring it to a home that has SIP ALG disabled and isn't using CGNAT to confirm.

One of the biggest time wasters, in my opinion, is troubleshooting damaged hardware. So, if possible, please try to rule that out. Absolutely do not plug in the ATA to existing phone jack wiring until you ensure there is no power going through it.

[Liptonbrisk]

I don't see evidence in your log that X_UsePublicAddressInVia is enabled. Seems weird that your ATA's LAN IP is being used in it. Is X_UsePublicAddressInVia enabled as I requested previously?

Seeing a private/LAN IP (e.g., 192.168.x.x) in the Via header means the ATA did not place its public/WAN IP in Via, which is exactly what X_UsePublicAddressInVia should have done if enabled. Enable it, and keep it enabled. That's in step 6f (in bold) from viewtopic.php?p=82562#p82562

Also I don't see any evidence of an incoming call--just keep-alive packets.

At least one header correctly has your WAN IP in it.

[domptg]

Very sorry I did enable X_UsePublicAddressInVia now. For some reason I did not save it before and was not changed.

[Liptonbrisk]

The log that was sent to me does not capture what happened when rebooting the ATA. There is no registration request. Also no call capture exists. All I see are keep-alive/Notify interactions, presumably ever 20 seconds (because I don't see time stamps).

run "syslogd -nl -s=all" (without the quotation marks)

Reboot/power cycle (off/on) ATA. Wait for successful registration.

Call your FPL number.

Try to answer the call with phone connected on the back, directly to ATA.

When the call ends, stop syslog (exit).

[domptg]

The log that was sent to me does not capture what happened when rebooting the ATA. There is no registration request. Also no call capture exists. All I see are keep-alive/Notify interactions, presumably ever 20 seconds (because I don't see time stamps).

run "syslogd -nl -s=all"

Reboot ATA.

Call your FPL number.

Try to answer the call.

When the call ends, stop syslog (exit).

What do I do wrong?

[Liptonbrisk]

What do I do wrong?

Rather, I did something wrong. I forgot to tell you to ensure syslog Level is set to 7 (debug) in the ATA.

1) Dial ***1. Enter the IP address you hear into a web browser. Login to your ATA's webui. Navigate to System Management-->Device Admin-->Syslog-->Level--> (uncheck the default box). There's a dropdown box. Change Level to 7. Then scroll down and click "submit".

2) Navigate to ITSP Profile (used for Freephoneline) -> SIP -> X_SipDebugOption. Ensure that's set to Log All Messages. Submit/save settings.

3) Enter "syslogd -nl -s=all" (without the quotation marks) at an elevated command prompt.

C:\>syslogd -nl -s=all (for example)


4) Reboot/power cycle (off/on) ATA. Wait for successful registration.

5) Call your FPL number.

6) Try to answer the call with phone connected on the back, directly to ATA's phone port.

7) When the call ends, stop syslog (exit the dos/command window). A syslog text file should be in the folder path where syslogd.exe exists that contains the captured log. That text file is what you need. Alternatively, you can copy and paste the log entry as you did previously.

[Liptonbrisk]

Very sorry I did enable X_UsePublicAddressInVia now. For some reason I did not save it before and was not changed.

Oh, wait. Now do incoming calls work with a phone connected directly to the back of the ATA's phone port (let's avoid house phone jacks for now), after rebooting the ATA?

After rebooting the ATA ensure that X_UsePublicAddressInVia (Navigate to Service Providers-->ITSP Profile used for FreePhoneLine-->SIP) is still enabled for Freephoneline.

[domptg]

Can we go on Quick Assist so you can view my desktop on your PC? Let me know I'll send you PM with the code

[Liptonbrisk]

Sorry, I balk at doing live tech support. I'm not being paid, and I don't work for Fongo. I try to help out when I can on the forums. This is best I can do, and I prefer that others can read here and interact/help (or potentially learn). I have stuff I need to troubleshoot for myself (unrelated to FPL), which I haven't done yet today.

Did I explain something poorly, maybe? Should I provide a clearer explanation about something I stated?
Is there a step that I need to explain in more detail?