Check the NAT table and run a sniffer in the router and you will see that the router is routing the package via the second ISP but it's still applying the old NAT rule (for the first ISP) instead of the correct NAT rule. Try to re-register the SIP client in the SIP server and you will see that no SIP message returns and the re-register fails Change the distance of the default routes so the second ISP will be the active route (smaller distance) ![]() Set up a SIP client (in the internal network) to register in an external SIP server and do the register Create proper default routes (static routes) for each ISP (the first ISP with the smaller distance) Plug a router to two different ISPs (each one giving you a different real IP) and to an internal network Note: We have tested some real Mikrotiks (mibspe) and run some simulations in GNS3 with routerosx86 Mikrotik virtual machines (chr). If we clean the NAT table or even reboot the router, everything is gonna be ok again.Ħ.38(mibspe),6.38.5(chr),6.39.3(mibspe),6.41(chr) Because of this, the SIP register messages cannot reach the SIP server and the SIP connection drops. When changing the default route from one ISP provider to the another one (manually, or because the ISP link goes down), the Mikrotik applies the wrong NAT rule. ![]() In our setup we have two ISP providers, a SIP client with a private IP, and we're using NATs (a different NAT for each ISP provider) with SIG ALG translation, aka SIP nat helper. SIP client cannot re-register in the SIP server after switching ISP (different NAT).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |