Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Everybody needs free billing for Quintum

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #28951
    Kaizerr
    Guest

    I am one of them So I want to open a topic on configuring freeradius with quintum a400 and ask a questions about it here.
    So let`s begin may be some Guru`s will go down to us to give an answers.
    Q1.I installed Fedoracore3 with bundled freeradius and make radtest command to see how radius functions it works good I can see how it can get authorization request from radtest utility it looks and works as it should.But when I configure my quintum for prepaid ivr and radius, and then issue “tspdump udp” to see what rad_requests it will send, I see no authorization requests when I make a call on pstntg1 on wich I configured ivr I see only tftp requests to my fileserverip that provide voice prompts and ivr asks me a calling card number but after I submit that number it does not send authorization requests to radius but sends tftp request to get failed.wav from tftp fileserver.And then it sends only accaunt_request packet So what should I configure on my quintum for it to send an authorization requests to radius server or may be my quintums version do not allow to do it?
    Q2.In what form should I write to or add user in radius`s user file may be some example of users file would explain all my qustions about this file
    Q3.To save all troubles and worries may be it would be easyer to post all generic configurations files for quintum users of analog series to save them time or this is so high a secret that no one radius admin would reveal it in any sircumstances

    #28952
    Matt
    Guest

    You need to check out the documentation quintum provides if you want to dive into using freeradius.

    http://www.quintum.com/support/xplatform/ivr_acct/Billing_Authentication_Handbook.chm

    That said,
    You aren’t going to see any radius information on prepaid ivrtype until you actually enter the information, after the IVR plays.

    If you are getting failed tftp requests… do you have the tftp server with the proper languages files setup?

    #28953
    Noname
    Guest

    onfig radius# user
    config radius user# print

    host p 64.xxx.xxx.xxx
    authenticationport p 1812
    accountingport p 1813

    host s 0.0.0.0
    authenticationport s 1812
    accountingport s 1813

    retry = 3
    timeout = 5
    accountingtype = 2
    sharedsecret xxxxxxxxxx
    config radius user#

    You will need the Quintum sending the radius user information to the place where the billing is at.

    Post your e-mail or write to Mike3799@yahoo.com. I will like to get in touch with you.

    Best regards.

    #28954
    kaizerr
    Guest

    YEess I have found an answer for my Q1 and Q2 and I will explain now what was it. first of all I edited my users file incorrectly
    I should edit it like this:'”210987654321 Auth-Type := Accept
    Quintum-h323-return-code = “h323-return-code=0”,
    Quintum-h323-credit-amount = “h323-credit-amount=124”,
    Quintum-h323-credit-time = “h323-credit-time=10” “to show here that my card number is 12 digits long as it is configured in my quintums pstntg 1 ivr related part. As I complained earlier that I am not seeing any access-request packet that was because I typed not 12 digit access code and my quintum even doesn`t send it to radius.
    Now I can see it :rad_recv: Access-Request packet from host 192.168.1.3:24579, id=241, length=152
    NAS-IP-Address = 192.168.1.3
    User-Name = “210987654321”
    User-Password = “210987654321”
    NAS-Port-Type = Async
    Quintum-h323-conf-id = “h323-conf-id=34323035 37326531 62360033 65390000”
    Quintum-AVPair = “h323-ivr-out=ACCESSCODE:”
    Processing the authorize section of radiusd.conf
    modcall: entering group authorize for request 40
    modcall[authorize]: module “preprocess” returns ok for request 40
    modcall[authorize]: module “chap” returns noop for request 40
    modcall[authorize]: module “mschap” returns noop for request 40
    rlm_realm: No ‘@’ in User-Name = “210987654321”, looking up realm NULL
    rlm_realm: No such realm “NULL”
    modcall[authorize]: module “suffix” returns noop for request 40
    rlm_eap: No EAP-Message, not doing EAP
    modcall[authorize]: module “eap” returns noop for request 40
    users: Matched 210987654321 at 153
    modcall[authorize]: module “files” returns ok for request 40
    modcall: group authorize returns ok for request 40
    rad_check_password: Found Auth-Type Accept
    rad_check_password: Auth-Type = Accept, accepting the user
    Sending Access-Accept of id 241 to 192.168.1.3:24579
    Quintum-h323-return-code = “h323-return-code=0”
    Quintum-h323-credit-amount = “h323-credit-amount=124”
    Quintum-h323-credit-time = “h323-credit-time=10”
    Finished request 40
    Going to the next request
    — Walking the entire request list —
    Waking up in 6 seconds…
    — Walking the entire request list —
    Cleaning up request 40 ID 241 with timestamp 42052c3c
    Nothing to do. Sleeping until we see a request.
    rad_recv: Accounting-Request packet from host 192.168.1.3:24579, id=242, length=566
    NAS-IP-Address = 192.168.1.3
    Quintum-NAS-Port = “0 0/2/3”
    NAS-Port-Type = Async
    User-Name = “210987654321”
    Called-Station-Id = “”
    Calling-Station-Id = “”
    Acct-Status-Type = Stop
    Acct-Delay-Time = 0
    Acct-Input-Octets = 0
    Acct-Output-Octets = 0
    Acct-Session-Id = “2020202000000079”
    Acct-Session-Time = 18
    Acct-Input-Packets = 0
    Acct-Output-Packets = 0
    Service-Type = 0
    Quintum-h323-conf-id = “h323-conf-id=34323035 37326531 62360033 65390000”
    Quintum-AVPair = “h323-incoming-conf-id=34323035 37326531 62360033 65390000”
    Quintum-h323-gw-id = “h323-gw-id=”
    Quintum-h323-call-origin = “h323-call-origin=answer”
    Quintum-h323-call-type = “h323-call-type=Telephony”
    Quintum-h323-setup-time = “h323-setup-time=01:29:05.340 UTC Sun Feb 6 2005”
    Quintum-h323-connect-time = “h323-connect-time=01:29:05.600 UTC Sun Feb 6 2005”
    Quintum-h323-disconnect-time = “h323-disconnect-time=01:29:23.570 UTC Sun Feb 6 2005”
    Quintum-h323-disconnect-cause = “h323-disconnect-cause=29”
    Quintum-h323-voice-quality = “h323-voice-quality=0”
    Processing the preacct section of radiusd.conf
    modcall: entering group preacct for request 41
    modcall[preacct]: module “preprocess” returns noop for request 41
    rlm_acct_unique: WARNING: Attribute NAS-Port was not found in request, unique ID MAY be inconsistent
    rlm_acct_unique: Hashing ‘,Client-IP-Address = 192.168.1.3,NAS-IP-Address = 192.168.1.3,Acct-Session-Id = “2020202000000079”,User-Name = “210987654321”‘
    rlm_acct_unique: Acct-Unique-Session-ID = “206a051e3218719e”.
    modcall[preacct]: module “acct_unique” returns ok for request 41
    rlm_realm: No ‘@’ in User-Name = “210987654321”, looking up realm NULL
    rlm_realm: No such realm “NULL”
    modcall[preacct]: module “suffix” returns noop for request 41
    modcall[preacct]: module “files” returns noop for request 41
    modcall: group preacct returns ok for request 41
    Processing the accounting section of radiusd.conf
    modcall: entering group accounting for request 41
    radius_xlat: ‘/var/log/radius/radacct/192.168.1.3/detail-20050206’
    rlm_detail: /var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /var/log/radius/radacct/192.168.1.3/detail-20050206
    modcall[accounting]: module “detail” returns ok for request 41
    modcall[accounting]: module “unix” returns noop for request 41
    radius_xlat: ‘/var/log/radius/radutmp’
    radius_xlat: ‘210987654321’
    rlm_radutmp: No NAS-Port seen. Cannot do anything.
    rlm_radumtp: WARNING: checkrad will probably not work!
    modcall[accounting]: module “radutmp” returns noop for request 41
    modcall: group accounting returns ok for request 41
    Sending Accounting-Response of id 242 to 192.168.1.3:24579
    Finished request 41
    Going to the next request
    — Walking the entire request list —
    Waking up in 6 seconds…
    — Walking the entire request list —
    Cleaning up request 41 ID 242 with timestamp 42052c44
    Nothing to do. Sleeping until we see a request.
    Now I think I should find the way to send in Access-response some attributes to get me in my quintum because it as it is shown here accepts it but then hungs up the line I do not know why right now If some of you can read this given output and gave me some clue what is happeninng I would appreciate much

    #28955
    Kaizerr
    Guest

    Matt
    Thank you I have got that document earlier but I am a new to this so it takes some time to get used to this staff
    Noname
    I think you are from Huston You are the first man ever helped me to get to work my quintum a year ago
    I did that part that you are saying about but I was not able to see access-request cause I typed 3 digit password configured in users file of radius but should type 12 digit as I myself configured in quintum. Now I see it but there is more questions: Q4. what is Quintum-AVPair = “h323-ivr-out=ACCESSCODE:” attribute and what it does?
    Q5 May be in this part:Sending Access-Accept of id 241 to 192.168.1.3:24579
    Quintum-h323-return-code = “h323-return-code=0”
    Quintum-h323-credit-amount = “h323-credit-amount=124”
    Quintum-h323-credit-time = “h323-credit-time=10” I should add some attribute to make IVR play what it should and if so how can I do it ? Cause after that radius says that it finished request it means that I should hear an IVR prompting with minutes left or to dial the destination number or something else dont now yet.
    Q6. Acct-Session-Time = 18 why it logs this time in accounting-request part of it though I was not able to proseed whith call

    Regards to everybody who make free software really free by explaining how it works

    #28956
    Noname
    Guest

    Hello Kaiser.

    Yeaph, it is me.

    If you wanted to compare the log from the Quintum talking to a free radius versus the log of quintum talking to a working billing system, write to my e-mail.

    Best regards.

    And by the way, you could adjust the number of digits that the Quintum needs before it sends them out to the radius server.

    I use ten digits on my billing.

    #28957
    kaizerr
    Guest

    No It appears that I was totally wrong, what I have done to this point is right direction.
    I mean today February 6th I was desperate and tryed to call several times without not configuring anything because I do not now what to configure.
    But after a little thought I changed amount of money in users file to less than 100$ and the seconds value to some multiple times of the money value I made it 100/0.30=333min*60~19849seconds like this:
    210987654321 Auth-Type := Accept
    Quintum-h323-return-code = “h323-return-code=0”,
    Quintum-h323-credit-amount = “h323-credit-amount=99.25”,
    Quintum-h323-credit-time = “h323-credit-time=19849”
    and tryed to call again and what you think it got through and I was able to make call several times because I configured ** value in pstntg 1 group and after I hang up my phone it write the call detail in /var/log/radius/radacct/193.168.1.3/detail-20050206 file so now I can use some simple programs to get it to a printer or something.
    The most exiting thing was that ivr read the amount from users file and spoke to me as I never thought it would and with all details.So I think that my freeradius works and logs the information I need to the place I want.
    But now there it is
    Q7. I want to know how this amount of money in users file will get subtracted by the amount of a last call multiplayed by the destination rates. This side of work should do some external programm named billing I think. And here goes all this MySQL and DB related staff. Any thoughts about some free billing platforms to connect to freeradius.
    Now its time to dig for any free billing solutions.
    I will post again with explanation of all the quirks and tricks I-a user that never write any programms in any languages exept “Hello, World” ones-have met while trying to use freeradius in
    some near future
    Best regards to all of you who will benefit from my postings

    #28958
    Matt
    Guest

    I’m definately not from houston.

    I suggest reading the free radius book from o’reilly. I wouldn’t start off with trying to do any kind of accounting with free radius. To get anywhere with a prepaid type scenario you will almost definately need some programming ability.
    Buried somewhere in the documentation that comes with freeradius they recommend using a PostgreSQL database for accounting.

    #28959
    Teodor Georgiev
    Guest

    correct, PostgreSQL is recommended for VoIP-VSA-H323 accounting, than Mysql. That fact however does not stop a lot of billing software packages (like DataTechLabs, Alepo RBS and etc) to use Mysql for VoIP billing.

    The below link is also a great help for those who have Radius experience and the intention to start working on H323 auth/acc software.

    http://www.cisco.com/warp/public/cc/so/cuso/sp/sms/acct/caaaf_cg.htm

    #28960
    kaizerr
    Guest

    I have figured out how to use Postgresql for H323 accounting but there appears to be a question again
    It is hidden in the preprocess module of freeradius which makes cisco_vsa_hack_something I do not now how to change it a little for it to make quintum_vsa_hack_something in preprocess.c file before recompiling it.
    Q8 Will it work without doing such a hack because alltheway it logs accounting info in such a weird fasion but it works with plain text and I do not know would it work with h323_postgresql.sql with such a way or I must do quintum hack.
    Or somebody would share their expirience with such a behavior of quintum`s?

    Everybody very welcomed to participate in this discussion

Viewing 10 posts - 1 through 10 (of 10 total)
  • The forum ‘Voice over IP’ is closed to new topics and replies.