Possible to use the SIP/Voip from voice on FTTH with Freepbx or something similar?

@varkey - Yes I did the same. I was not sure about the default ONT IP range so used a Linux laptop and changed the the ip address using ifconfig for every 192.168.1.x.. to 192.168.254.x range and then ping. But no luck

Could be 192.168.0.x too?

Tried that as well. So my theory is the ONT is in bridge mode so no ip configured. That is why I am not able to access. it. Else vendor may be configured a nonstandard ip or subnet.

Yeah they appears to have changed the IP address or its something else. Even in bridge mode the device will have an IP address and if an IP address from the same subnet is assigned it works. I have my ONT configured in bridge mode and I can access the UI cause I have it setup with the correct IP address.

I'm using a raspberry pi running siproxd at a location where I have FTTH connection. Also I run wireguard VPN client on the pi which connects to my server on the cloud. I use my phones Android dialer apps sip feature to connect to siproxd via VPN. My inboud interface is wg0 (VPN interface) and my outbound interface is VoIP vlan forwarded to pi from FTTH ONT.

Calls get connected and I hear the voice from the other side. But my voice is not going through. I called a toll free no. and I cannot respond to IVR.

I have tried using almost every possible tool available on Linux to pinpoint the issue.

Firewall is disabled. UDP ports are open. One thing I noticed was UDP packets from BSNLs VoIP server arrive to my phone. But UDP packets from my phone reach siproxd but they are not going through the VoIP vlan on the pi.

I have also tried every possible configuration option on siproxd conf file. Even ran it on debugging mode and didn't notice anything strange.

What can I do solve this one way voice issue?

I solved the issue. Siproxd was sending UDP packets via the WAN default gateway (INTERNET). Previously I had a static route to BSNLs VoIP network. I removed the default route to the Internet and made the VoIP gateway as the default gateway.

Also, I could make the VPN work by adding a specific/static route to my VPN server. But I can't reach whole of the internet from my pi. I may have to create two separate routing tables. Happy that VoIP works. Latency is pretty bad. Nothing can be done about it. I'm on a different carrier on my phone.

Thanks for the update @goodyet, I had it working with a static route to the VOIP network. I wonder why it takes the default route 🤔Perhaps you need to enable NAT for that interface?

I had got it working with a similar setup (I use ZeroTier for remote connectivity, VPN is over kill, might be useful for you too) and never had route issue. Although I made some firewall change later which broke the VOIP stuff, haven't had the time to get that fixed yet.

NAT isn't required because BSNLs VoIP servers are on private ip's. I read somewhere that VoIP servers/proxies tend to ignore static routes and use default gateways. I'm yet to get siproxd work on static route. I'll continue to find a way out of this.

Well, if BSNL's VoIP server sees traffic from an internal private IP address how is it going to send the return traffic back to you? It wouldn't know how to send it back cause yours would be from an unroutable IP address or atleast BSNL wouldn't be aware of the route.

So you definitely need NAT, and any traffic going to the VoIP server needs to use the 10.x.x.x IP address allotted to you as the source.

I definitely got it working with a static route so it's something in your configuration.

@varkey after setting up SIP/VOIP do we need to use the same BSNL wifi to make/receive calls? or we can receive anywhere using any internet in a different city/place?

@ChrisM You need to use the same BSNL connection, if you need to use it from a different location, you'd need some mechanism to access your home network from elsewhere (VPN, ZeroTier etc)

Hello All,

I have got a new BSNL FTTH connection and that has been installed and activated, Voice and Data works perfectly fine using Syrotech ONU (Wi-Fi, POT, 2 LAN). Now what I am trying to configure or rather trying to use my Grandstream GXP1625 IP Phone directly instead of the traditional analog phone. I have tried few configuration as mentioned earlier in the thread but no go. Can someone please summarize the entire settings on how to get the BSNL Voice work on a grandstream phone directly.
TIA

Regards,
Abhijit

@abhi5130 To summarise

1. Setup VoIP wan profile in bridge mode and bind it to a different ethernet port.
2. You'd need to configure your VoIP phone WAN interface with the VoIP IP address details (you'd need to do this prior to connecting the cable from the ONT or would need to use the UI within the phone to configure), similarly pre-configure the SIP details too.
3. Connect the cable from the ONT.

In this config you wouldn't be able to access the config user interface though.

Thanks for your reply @varkey was expecting from you.

As I have read thru the entire thread here, I have tried all the steps mentioned above but no go. I am outside right now, I will share the screenshot of the device settings onu and ipphone gxp 1625 and Syrotech onu later.

varkey said:

Well, if BSNL's VoIP server sees traffic from an internal private IP address how is it going to send the return traffic back to you? It wouldn't know how to send it back cause yours would be from an unroutable IP address or atleast BSNL wouldn't be aware of the route.

So you definitely need NAT, and any traffic going to the VoIP server needs to use the 10.x.x.x IP address allotted to you as the source.

I definitely got it working with a static route so it's something in your configuration.

Click to expand...

Looks like BSNL made some change recently so now it requires one more static route entry for traffic to 10.191.55.68, so I just added a static route for 10.191.0.0/16 to go through the VOIP interface. (A /16 is too much, but then I thought what if BSNL changes the IP address or something, anyway I don't have anything else on that subnet so it wasn't an issue)

I was noticing intermittent voice drops and did a packet dump, could see that there are many packets coming from 10.191.55.68 through the VOIP interface but none going back, so I added the appropriate routes and things are back to working.