h323-redirect-numbers works exactly like the RasSrv::RewriteE164 sections does - the rewrite happens just right after RasSrv::RewriteE164 and authentication is performed. Two exceptions to the auth-based rewrite: 1) it removes other destination aliases from the list of destination aliases, 2) the redirect-number is stored inside a call record, so it is enough to perform redirection only during the ARQ phase. The Setup message will be rewritten automatically. On Fri, 2004-09-03 at 17:17, Rafael J. Risco G.V wrote: > hello > I was testing these new attributes last week, all the outgoing calls > are redirected but when you talk about "inbound rewrite" it means that > it is possible to forward inbound calls to the "h323-redirect-number" > too? > > I am using freeradius, user file contains authentication and security > information for each user like this: > > agent04 Auth-Type := Local, User-Password == "callcenter" > Cisco-AVPair = > "h323-ivr-out=terminal-alias:agent04,6600020,6603000;", > Framed-IP-Address = "10.0.0.236", > Reply-Message = "Hello, %u", > h323-return-code="0", > h323-credit-time = "h323-credit-time=86400", > h323-redirect-number = "6604001" > > thanks > Rafael ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
