Hi Peter, yes, sharing the IP lists between FS and OpenSIPS may be a workable solution - you can share via DB (slower) or via memcached (faster) - memcached is available only in 1.6 release.
Regards, Bogdan Peter P GMX wrote: > I now implemented a solution in Freeswitch. I created a whitelist based > on defined external gateways and IPs of registered UAs. > Now only whitelisted IPs are routed inside Freeswitch. > > I am looking forward to seeing the memcached implementation in the next > OpenSIPS release. That way I can share the whitelisted IPs quickly with > OpenSIPS and may block Invites in OpenSIPS based on a whitelist in > memcached. This is less CPU intensive. > > Best regards > Peter > > > Raúl Alexis Betancor Santana schrieb: > >> Bogdan-Andrei Iancu escribió: >> >> >>> So, in such a case, a real working solution will be to have opensips to >>> spoof the source IP of the outbound request? but this may really break >>> the transaction.... Only if the spoofing is done with skipping the VIA >>> insertion. >>> >>> Regards, >>> Bogdan >>> >>> >>> >> Spoofing IP's is the worst solution, you could not asure that packages >> will arrive at the gw ... imagine there are firewalls between ... and >> lot of more problems. >> >> From my POV, if he need to go throught the proxy ... better to >> translate the acl validations to the proxy. >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users