Re: Setting h323id based on IP(s) ?

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

 



That's why I thought it would fit well. CapacityControl/RADIUS modules
already distinguish between H.323 ID and Calling-Station-Id allowing them
to have different values.

----- Original Message ----- 
From: "Tusar" <tusarbd@xxxxxxxxx>
Sent: Tuesday, April 15, 2008 8:38 PM
Subject: Re:  Setting h323id based on IP(s) ?


> And for [CapacityControl] -- h323id is already implemented .
>
> [ip:CALLER_IP|h323id:CALLER_H323ID|cli:CALLER_NUMBER]=[CALLED NUMBER REGEX
> PATTERN] MAX_CAPACITY
>
> Best Regards,
> //Tusar\\
>
> On Tue, Apr 15, 2008 at 8:09 PM, Zygmuntowicz Michal 
> <m.zygmuntowicz@xxxxxxx>
> wrote:
>
>> Another solution would be to bill customers by IPs, not CLI.
>> Anyway, h323id: extension to the RewriteCLI should be quite
>> straightforward to implement and should not affect existing stuff.
>> It could even be more correct/flexible to associate accounts with H.323
>> IDs,
>> not party A/party B numbers.
>>
>> ----- Original Message -----
>> From: "Jan Willamowius" <jan@xxxxxxxxxxxxxx>
>> Sent: Tuesday, April 15, 2008 3:54 PM
>>
>>
>> > since all you are trying to do is authenticate by IP, why don't you
>> > use [FileIPAuth] ? Then there is no need to mangle the CLI.
>> >
>> > I think your idea stretches the idea of "rewriting the CLI" even
>> > further than we already do. Since we already have quite a number of
>> > Rewrite sections that work on the destination number/alias, we could
>> > also add something like "[RewriteSource]".
>> >
>> > Regards,
>> > Jan
>> >
>> >
>> > Tusar wrote:
>> >> Hi,
>> >>
>> >> I am currently managing my wholesale customer using CLI rewriting .
>> Like
>> >> any
>> >> call from [192.168.20.5/192.168.20.6]
>> >> is set to CLI=1234567890 and getting auth and accounting on
>> [1234567890]
>> >> and
>> >> it is running superb . But problem
>> >> is original CLI from my customer are rewritten and can not relay the
>> >> original CLI to telco .
>> >>
>> >> [RewriteCLI]
>> >> in:192.168.20.5=any=1234567890
>> >> in:192.168.20.6=any=1234567890
>> >>
>> >> [CapacityControl]
>> >> cli:1234567890=^1214 30
>> >>
>> >> Just a thought , All calls from specific IP(s) will be written as
>> h323id
>> >> where as original CLI will be
>> >> intact, so that we can relay the original CLI to telco and auth/acc
>> will
>> >> be
>> >> set based on h323id .
>> >>
>> >> [RewriteCLI]
>> >> in:192.168.20.5=any=h323id:1234567890
>> >> in:192.168.20.6=any=h323id:1234567890
>> >>
>> >> [CapacityControl]
>> >> h323id:1234567890=^1214 30
>> >>
>> >> Do you have any plan to implement like this feature or is there any
>> >> option
>> >> already here which I am missing ?
>> >>
>> >>
>> >> Best Regards,
>> >>
>> >> //Tusar\\
>> >
>> >
>> > --
>> > Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________________

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