This is in no way a FreePBX issue. Troubleshooting your LAN routing set up is not something that’s going to really happen here. Specially with three subnets and not a single clue as to how your have your network topology or logic.
If I were you, I would first connect the ISP phone modem directly to eth1 on FreePBX. Then you need to configure an IP on the same subnet of the modem, either static or dynamic, if the modem is providing a DHCP. Lastly you need to set a static route so the communication to your phone ISP always goes through eth1.
That’s why I said I might have messed up the names. I just meant that I would connect freepnx to the isp modem directly, without going through the switch. Anyway, the important part is the rest of the post: IP address and static routes.
I have setup on my notebook IP: 192.168.47.148 subnet 255.255.255.0 gateway 192.168.47.1 and I have tried to ping the HOST IP: 192.168.15.70 and I got replay from it.
@arielgrin
Yes it was directly then I have changed it but nothing I have just turned back from modem to eth0 directly but still don’t have any result about it.
If you are using a static IP it must be in the sane subnet as the modem. But then again, your provider should have explained you how to connect your equipment to theirs.
You have yet to confirm how the Mikrotik is setup. Just putting those IPs on your laptop is not enough. The router needs to know what to route for these subnets to “talk”
You are using multiple subnets and “trunking” them from the Mikrotik to the switch. So you need VLANs.
You have an unmanaged switch. So it can’t support VLANs. That is a huge problem.
This is just the tip of the iceberg. This is 100% a network setup issue. You have multiple things to fix before even worrying about the PBX. Until you fix those things, the PBX is going to not work in this setup.
type=peer&user ← You can only have one type, Peer, User or Friend. Can’t have two.
nat=no ← Your provider is not behin NAT
insecure=port,invite (very is depreciated and hasn’t been used since 1.8 almost)
alloweguest=no ← yes let’s anyone in.
allow=ulaw&alaw (g.711 is an invalid choice)
None of the above in the Incoming section is needed the Outgoing is used first and that’s all you need. However, both of these groups of settings is missing an important part of accepting calls, the context to send them to. Add this to the outgoing after you make your changes: