I've got the idea - it's good. But isn't your patch breaking tariff matching for default tariffs (with no group/selector)? ----- Original Message ----- From: "Kompnet" <kompnet@xxxxxxxxx> To: <openh323gk-users@xxxxxxxxxxxxxxxxxxxxx>; "Zygmuntowicz Michal" <m.zygmuntowicz@xxxxxxx> Sent: Tuesday, August 31, 2004 1:51 PM Subject: Changes in match_tariff function (sqlbill) > Hi, Michal. > I've changed you match_tariff function a little. > If it's needed to apply this schema: > the 1-st user must can place calls whit prefix 1234# with common price, > for the 2-nd user tariffs must be different for different destinations, > but he use 1234# prefix too, > and we use your variance of match_tariff, we need to write all destinations > for both users: > user1 1234#1 price1 > user2 1234#1 price2 > user1 1234#2 price1 > user2 1234#2 price3 > user1 1234#3 price1 > user2 1234#3 price4 > ... > In my variance we can to write destinations separately for each user: > user1 1234# price1 > user2 1234#1 price2 > user2 1234#2 price3 > user2 1234#2 price4 > ..... > -- > Best regards, > Igor Prokhorov ------------------------------------------------------- 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/
