* This is the VOP Radius mailing list *
Here is what I used to fix the issue with RODOPI and Vircom. Maybe Vircom
Support can help me out on this one? We changed the where PlanID = P.PlanID
to where PlanID = O.PlanID, it worked like a champ. This is after we
rebuilt the PlansSuspendState table.
Is this an issue with VIRCOM or RODOPI?
select @ObjectID = O.ObjectID,
@PlanID = O.PlanID,
@PlanInfoID = P.PlanInfoID,
@TemplateLoginID = I.TemplateLoginID
from ObjectValues as V
inner join Objects as O on O.ObjectID = V.ObjectID AND (O.DetailID = 1 OR
O.DetailID >= 1000) -- Dialin account OR Possible prepaid dialin ???
inner join Plans as P on P.PlanID = O.PlanID
inner join PlanInfo as I on I.PlanInfoId = P.PlanInfoID
inner join Providers as PR on PR.ProviderID = P.ProviderID
where V.Value_LPSTR = @UserName AND V.ItemID = 1
AND P.Closed = 0
AND not exists (
select *
from PlansSuspendState
where PlanID = O.PlanID -- WAS changed to P.PlanID
)
AND ( (PR.UseIn & 0x01) = 1 )
Thanks,
Kris McElroy
[EMAIL PROTECTED]
Internet Systems Engineer
Duracom, INC.
www.duracom.net
----- Original Message -----
From: "Kris McElroy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 16, 2002 3:29 PM
Subject: [VOP RADIUS] RODOPI INTERFACE_VIRCOM USERS
> * This is the VOP Radius mailing list *
> Rodopi sent vircom the log and vircom said that it was a rodopi issue.
The
> thing is that I have a "main rodopi" and a MISP. My MISP worked fine, but
> my "main rodopi" didn't. They use the same RADIUS Server. The thing is
> that the stored procedure was called from vircom, but RODOPI was returning
> incorrect information. I am going to call RODOPI on Monday and see if
they
> can further explain the issue to me and why my guy was able to fix it, but
> they weren't? I will post the issue and fix for you John.
>
> Kris McElroy
> ----- Original Message -----
> From: "Cary Fitch" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, November 16, 2002 2:31 PM
> Subject: [VOP RADIUS] RODOPI INTERFACE_VIRCOM USERS
>
>
> > * This is the VOP Radius mailing list *
> > Was this a Vircom issue or a Rodopi issue? It sounds like Vircom's data
> > call wasn't meshing with Rodopi's data scheme.
> >
> > Cary
> >
> > ----- Original Message -----
> > From: "John Blue" <[EMAIL PROTECTED]>
> > To: "Kris McElroy" <[EMAIL PROTECTED]>
> > Sent: Saturday, November 16, 2002 2:26 PM
> > Subject: [VOP RADIUS] RODOPI INTERFACE_VIRCOM USERS
> >
> >
> > > * This is the VOP Radius mailing list *
> > >
> > > KM> He fixed the issue and it works!!!
> > >
> > > Kris,
> > >
> > > Can you post the exact fix for us? Not that I need it .. I want it
> > > just for fyi.
> > >
> > > Thanks
> > >
> > > John Blue
> > >
> > >
> > > **
> > > To leave this list, send an email to [EMAIL PROTECTED]
> > > and put the word "LEAVE" in the BODY of the email.
> >
> > -.-Spam and virus filtered by modusMail using Norman virus engine.-.-
> >
> > **
> > To leave this list, send an email to [EMAIL PROTECTED]
> > and put the word "LEAVE" in the BODY of the email.
> >
>
>
> **
> To leave this list, send an email to [EMAIL PROTECTED]
> and put the word "LEAVE" in the BODY of the email.
>
**
To leave this list, send an email to [EMAIL PROTECTED]
and put the word "LEAVE" in the BODY of the email.
