Intel variant

someone do factory reset the GPON ONU SFP and cause TM MIB (management information base) get erased, thus OLT denied authenticated at stuck at O7 State
had to re-import MIB from D-LINK ONR to GPON ONU SFP




This MIB what I got from D-LINK ONR should respect TM OLT.

if OLT OMCI said VLAN400 should stay inside ONU, GPON ONU SFP also follow and wont bridge VLAN400

apparently Scammer use ODI to force bridge VLAN400, many customer don't use VoIP and Scammer simply rent it,
as owner of VoIP account got huge sum and give it away the VoIP Credential, this very reasons TM don't tell your VoIP password
unless you persuade the on-site  technician.

I think TM need detect one IP login multiple VoIP, but this will hurt legitimate as-well.

I had no idea how to prevent it, I hope my Maxis VoIP wont cause of that

no risk at the moment, just use legally 😅

I just don't want this GPON ONU SFP become bad stuff that disturb TM network

Today I had test GPON ONU SFP (non-Realtek) with TM and check if OMCI and MIB is acceptable,
well, it is, abide all TM OLT playbook, no issue using it for 1/2Gbps customers.

plus, it respect OLT bandwidth management (GEM), so, no speed hacking that violate TM Terms and Condition




to check OLT is allow bridging VLAN 400 (VoIP) and it's works.

any update I will update here

not available on the market 😅
take from somewhere else Deployment, I can provide it with manual.

Guys, have any of you successfully set the PPPoE MTU to 1500? At most I can get 1488 on my Unifi.

Today, I made the switch from Maxis fiber to Unifi Ultra 2Gbps. This upgrade allows me to thoroughly test, troubleshoot, and engage in reverse engineering of PON Firmware to optimize throughput.

Then I can experimenting Unifi VoIP

I have successfully made voip call works on Android phone using the built-in SIP client. Router is Mikrotik.

High level Steps:
1. Add a VLAN. I use name "voip", tag it to ID 400.
2. Attach DHCP client to VLAN "voip". Don't use peer DNS, NTP or default route.
3. Once the DHCP client successfully get an address, check the Status and get it's default gateway address.
4. Add a static route with Dst Address 10.225.0.0/16, and put the default gateway address you copied above. Immediate Gateway should show something like this: 10.40.255.254%voip
5.Add a NAT rule. Chain=srcnat. Out Interface=voip. Action=masquerade
6. Add another NAT rule. Chain=dstnat. In Interface=voip. Action=dst-nat. To Addresses=<IP address of your phone>

Step 6 is necessary for RTP packet to reach you. For Cisco IOS, use the following instead:
ip nat service allow-sip-even-rtp-ports

Obviously for Mikrotik you can only use 1 phone. Cisco allow you to use multiple phone with one router configuration.

Android phone overview:
1. I use the Phone app
2. Go to Settings
3. Calling accounts
4. SIP accounts

I set "Send keep-alive" to "Always send"
After that just enable "Receive incoming calls"

Go to "All calling accounts" and enable the voip account.

It seems like you have at least 2 separate issues.
First one is DHCP. Instead of using Torch, you need to use Packet Sniffer to see how packets traverse your network.
Sniff at the ONU port to see if things are working. Then sniff again at your bridged eth port.

The second issue is a common one. TM will change the Outbound Proxy of the VoIP once in a while. For me it has happened twice. Put back the TM ONU and verify VoIP is working. Then login the ONU and get the new Outbound Proxy. Configure the static route and your FreePBX accordingly.
[Firmware Feature Request]
Maybe a method to list configuration for VoIP?