Re: RewriteCLI Understanding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Order of entries is unrelevant. CLI rules have priority
over DNO rules. I am not sure, but this should be stated
in the manual (priorities for rule types).

----- Original Message ----- From: "Edson" <4lists@xxxxxxxxx>
Sent: Friday, May 12, 2006 7:06 PM


Hi, I have this config:

[RewriteCLI]
 RemoveH323Id=0
 %r1% in:aaa.bbb.cc.d=cli:91*=1578
 %r2% in:aaa.bbb.cc.d=dno:any=157800

Why all CDRs register caller-id as 157800, if GK recieves caller-id as 91xx
(9101,9102,etc)? Why is GK not using the first rule if the %r1% matches?
Should I revert the order of the rules? I understand that it would stop on
the first match... Or maybe it's because on first rule I use 'cli' and on
second 'dno'?

Edson.

P.S.: This "stop on first match" also didn't work on Rassrv::RewriteE164
rules. I use MySQL and have to reverse order from less significant to more
significant so that matches works correctly.



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________________

Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux