Hi Aivis,
h323-redirect-number works more like [RasSrv::RewriteE164] and it takes step just before routing/outbound gw rewrite is made, so, with h323-redirect-number, gateway capacity limits apply as well as per-gw outbound rewrite rules. It overrides only inbound global/per-gw rewrite rules.
----- Original Message ----- From: "Aivis Olsteins" <aivis@xxxxxxxxxxxxxxxx>
Sent: Wednesday, November 10, 2004 5:14 PM
I suspected that.
So this also means that if "h323-redirect-number" is present in access-accept, the number will be sent out as specified by radius and any outgoing [RasSrv::GWRewriteE164] rules will be ignored, correct?
regards, Aivis
Zygmuntowicz Michal wrote:I guess that if your system redirects the call to a specific IP
- it knows what it is doing. Therefore, nothing more (like matching
prefix, other gateways) is checked. The call is simply and unconditionally
redirected to this given IP.
----- Original Message ----- From: "Aivis Olsteins" <aivis@xxxxxxxxxxxxxxxx>
Sent: Wednesday, November 10, 2004 4:57 PM
Has anybody tried how radius based routing works in 2.2 when you define more than one GW per destiantion with limited capacity and different priorities?
Suppose GW1 has higher priority than GW2, but it is already filled up. Now radius server sends "h323-redirect-ip-address=<GW1>". Will call be routed to GW1 regardless of fact that it's capacity is full or will it respect Capacity setting and route to GW2?
Any thoughts?
Regards, Aivis
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
