Hello Rustam -
On Thu, 20 Apr 2000, Rustam Povarov wrote:
> On Thu, 20 Apr 2000, Hugh Irvine wrote:
>
> > On Wed, 19 Apr 2000, Rustam Povarov wrote:
> > > Could you, please, advise what type of billing do you use for VoIP
> > > with Radiator and Cisco. We have Intel server platform and Linux or
> > > FreeBSD. Thank you.
> > >
> >
> > There is an item in the FAQ here:
> >
> > http://www.open.com.au/radiator/faq.html#72
> >
> > and there is some Cisco documentation in a seperate message.
> >
> > I recently helped another customer with this and apparently the Cisco does some
> > odd things - like sending an initial accounting request *before* sending the
> > access request. To handle this my suggestion was to use a custom session
> > database to keep track of the accounting requests and then match the access
> > requests later. All of this using an SQL database of course.
>
> It is looks like I made my previous question wrong. I did not mean
> the procedures of cooperation between the billing and Radiator. The
> right question is "what _exactly_ ready billing systems (names of
> products and names of manufactors") regulary use ITSP's with Radius".
> We are in a process of desiding what exactly billing system we will
> use and just need the advises which will help you understand right
> would it be better to make our personal billing or buy ready system,
> and if buy - what exactly.
>
I personally don't know what billing systems support VoIP - but I suspect the
answer may be "none"! If anyone else on the list has better information, please
share it as I am sure there are many other customers who are interested.
thanks
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
