* This is the VOP Radius mailing list * As far as I know it was all of them dialing into the NAS's that were "upgraded".
----- Original Message ----- From: "Keith Schmidt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 23, 2003 9:19 AM Subject: [VOPRadius] Error Message > * This is the VOP Radius mailing list * > Todd > > Was this happening to all of your customers connecting to the same NAS or > was it just a few customers? We only have this problem with a few of our > customers, we can log in with their information without any problems but > they are having intermittent problems logging in (Digital access not > allowed). > > -Keith > > ----- Original Message ----- > From: "Your Own ISP .com" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, December 23, 2003 1:33 AM > Subject: [VOPRadius] Error Message > > > > * This is the VOP Radius mailing list * > > If you are using Megapop then you better turn Digital access on if you > want > > your analog to go through on any of the access points where they have > > updated their equipment. > > > > It broke everything for us and Vircom won't address it for us since we > don't > > have a support contract. > > > > Megapop says they won't help us because it's our problem that we use Vop > > Radius. They say it's the only radius server that is having this problem > > because it's not following the RFC so they say. > > > > In any case, I already argued it out with both Vircom and Megapop and got > > nowhere with either and was forced to allow ISDN on this network until I > > have time to see if there is a better solution. > > > > The problem is that Vop Radius is looking for the attribute "NAS-Port-Type > = > > async" and after they updated their equipment it now comes through as > > "NAS-Port-Type = virtual" vop radius sees this and denies analog access > > unless you are allowing digital access in your setup. This is how we had > to > > fix it because neither side would take responsibility for the problem. > > Megapop in so many words told us it was our problem since we were using a > > Radius product that was not following the standards and Vircom only > > forwarded our calls to the sales dept. to buy a support contract and > refused > > to listen without a $500 payment for a support contract. So, turned out it > > was our problem regardless of the fact that we did not cause the problem. > We > > just paid each side money and waited asked each for help but got a big fat > > nothing. I will not even go into why we don't have a support contract, > > that's a whole other story which I won't discuss on list. > > > > Hopefully this info will save you a lot of time and energy digging out the > > problem, I am actually the one that figured what was happening with this. > > Took me a while then I nailed it.. Of course I thought it would be a piece > > of cake from there, HA! > > > > If anyone comes up with a solution for this that's better than mine, let > me > > know.. > > > > Todd > > > > > > ----- Original Message ----- > > From: "Keith Schmidt" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, December 22, 2003 4:33 PM > > Subject: [VOPRadius] Error Message > > > > > > * This is the VOP Radius mailing list * > > Yes, they are outsourced and our provider just updated their Total control > > chassis over the weekend. > > > > Anyone ever come across this error before? > > > > Thanks > > Keith > > > > > > ----- Original Message ----- > > From: Erik Tijburg > > Sent: 12/22/2003 5:14:06 PM > > To: [EMAIL PROTECTED] > > Subject: [VOPRadius] Error Message > > > > > > Do you use wholesale ports? > > > > > > Erik L. M. Tijburg > > ISP Support Services > > (469) 323-1841 > > [EMAIL PROTECTED] > > > > > > > > > > > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On > > Behalf Of Keith Schmidt > > Sent: Monday, December 22, 2003 4:06 PM > > To: [EMAIL PROTECTED] > > Subject: [VOPRadius] Error Message > > > > > > I have never seen an error like this before; we don't do ISDN or anything > > else like that. Any suggestions on why our customer is getting this error? > > We have had 4 or 5 customers with this problem today. > > > > > > (Reject :02404) 12/22/2003 16:42:20 Invalid Attempt: > [216.221.137.131:1300] > > budd - Digital access not allowed![/8457967442] > > > > > > Thanks > > Keith Schmidt > > > > > > ** > > 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. > ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
