Hi Emmanuel, you can easily do this with a dynamic routing policy (vqueue or sql) at the front of the chain that simply routes all outside calls to your fallback endpoint and lets all other calls pass on to the other policies, including ENUM. You could also solve this with tech-prefixes. Some authenticators can also do rewriting and that will happen before the routing stage. But I think it would end up a bit more complicated. Regards, Jan Emmanuel BUU wrote: > Hello: > > I need to setup the following > > 1/ If calls comes from my network (identified by a limited set of IP > address), I need to us ENUM to send the call to the correct destination > > 2/ If the call comes outside my network, I need to send the call to one > endpoint in my network. > > To do this, I did not find any other solution but to run two gnuGK. It > seem that there is no way to have a per end point or per source IP > routing policy. > I tried to work this around adding a "technical prefix" for calls > originating from my network but, then the RewriteE164 rules are supposed > to be applied BEFORE the routing policies are selected. So back to square 1. > > Any other solution with the current gnuGK? > > Would a per end point or per IP/subnet routing policy be a useful addition? > > Emmanuel BUU > IVèS > http://www.ives.fr/ -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
