About a minute after I sent my message, I found the RadCheckOnline sp and
added one line to the end:
CREATE PROCEDURE RadCheckOnline @UserName varchar(64) AS
Select Count(*) From CallsOnline Where UserName=@UserName and
AND NasIdentifier LIKE '123.123.%'
I used the first two octets of an IP address there because all local NASes
have the same first two octets and all roaming NASes are something
This should also do the trick, right?
The first two lines of the sp were never modified and came from whatever
Emerald script generated the sp a while back.
> Josh Hillman wrote:
> > Dale,
> > What stored procedure do I modify to allow roaming dial-up connections
> > connect even if Emerald sees them online already? I don't need to
> > anything for our local dial-ups since that works fine and also uses SNMP
> > concurrency checking.
> > Unfortunately, we're apparently not receiving some of the stop records
> > our roaming customers when they disconnect, so Emerald still thinks
> > online and therefore subsequent connections for these people are being
> > rejected because of concurrency (eventhough they're not online). I
> > use SNMP concurrency checking for the roaming people.
For more information about this list (including removal) go to: