Outbound callerid setting as [STRICT] rule

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

 



Hi,

Trying to find a way for outbound callerid setting like below.

If client A from 192.168.10.60 is sending 10 digit callerid then we want to forward it as it is .But if he sends callerid other than 10 digits (below/above)
then callerid will be rewritten to default [12643020000-12643029999] as RANDOM basis.


[RewriteCLI]
out:192.168.10.60=any pi=allow cli:..........*=..........       # [10 digit specific]
out:any=any any=12643020000-12643029999                # [Default Rule]

But it is not working .


From  http://www.gnugk.org/gnugk-manual-6.html#ss6.8    I found..
"After a match for caller's/caller's IP is found, no more rules are checked, even if no prefix/number is matched inside the set of rules for these IPs."
That means it is working per manual or guideline as [LOOSE] rule .


But I believe most of the users will agree to set callerid as [STRICT] rule. If a rule does not match strictly (including ip/prefix/number) then
we should set the [DEFAULT] rule .



Can anyone sheds some lights on this issue .


Thanks in advance.

Best Regards,

//Tusar\\

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________________

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/

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

  Powered by Linux