[VOPRadius] Field Alert Bulletin

[Charles Shaffer]

Title: Message

Hello Sylvain,

 

    Thanks for the update. We currently use Platypus and SQL 2K. The current scripts on Boardtowns site pertaining to the integration of Platypus and VOPRadius already have the field type set to integer for both analog and digital access. Here is the section that pertains to the creation of the acct_attributes table.

 

create table acct_attributes(
  Acct_ID                    integer identity  NOT NULL,
  Account_Type               varchar(20)       NOT NULL,
  timestamp                  timestamp         NOT NULL,
  ServiceType                varchar(128)      NULL,
  SessionLimit               integer           NULL,
  IdleLimit                  integer           NULL,
  StaticIP                   varchar(16)       NULL,
  IPNetmask                  varchar(16)       NULL,
  FramedRoute                varchar(128)      NULL,
  FilterID                   varchar(128)      NULL,
  AnalogAccess               integer           NULL,
  DigitalAccess              integer           NULL,
  PortLimit                  integer           NULL,
  SpeedLimit                 integer           NULL,
  ExpiryDate                 datetime          NULL,
  profiles                   varchar(25)       NULL
)

 

Is this the location your email refers to?

 

Thanks again for keeping us in the loop.

 

Respectfully,

 

Charles

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Sylvain Savignac
Sent: Wednesday, September 08, 2004 1:47 PM
To: [EMAIL PROTECTED]
Subject: [VOPRadius] Field Alert Bulletin

Hello all,

 

 

Due to the increased number of customers, we have had recently to deal with new SQL database types.

Eventhough SQL is a standard, there are some particularities to every vendor (MS SQL, MySQL, etc...)

 

The Vircom specific attributes Analog-Access and Digital-Access have caused us some problems.

 

The latter were defined at first as Binary. MS SQL returns 0 or -1, where MySQL returns the ASCII

code 0x30 and 0x31. And other SQL vendors have other behaviors...

 

Binary as record type not being "universal" enough, we have to switch to Integer record type.

 

Depending of your SQL database, the latter attributes may work properly independently of their record type.

However  it is HIGHLY RECOMMENDED when upgrading to version 4.0.228 to modify the record type

of the Analog-Access and Digital-Access attributes to Integer in your SQL database.

 

A zero value means FALSE.

A non-zero value means TRUE (1,2, and above) (This accommodates some databases like Platybus for example)

NULL data is allowed meaning "don't care".

 

The readme.txt file will be updated to let the customer know at the end of the software installation to

preferably modify the record type of the Analog-Access and Digital-Access attributes to Integer.

 

This change to accommodate more SQL database types has caused some of you critical down situations.

 

I personnaly apologise to the few of you to whom it caused inconvenients.

 

 

Sylvain Savignac, P. Eng.

 

Development Lead

RADIUS Development Unit

Vircom Inc.

 

2055, Peel St, suite 200

Montr�al (Qu�bec) Canada H3A 1V4

www.vircom.com