CALLBACK AUTHENTICATION WITH SECURID Token Code expires

Hi,
I would like to authenticate my callback users with SecurID,
My chief wants so.
The problem is that to connect whit dialin to my NAS cisco and the first

authentication take more or less a minute (this phare is ok) so
 when Cisco requires authentication after callback the token code is no
more
valid (The token code is valid only for 60 seconds).
I read that exist a Parameter "nocallback-verify" that perhaps disable
authentication after callback,
On my radius configuration I write: VPair = "lcp:nocallback-verify=1".
But it

doesn't change nothing
How can I solve my problem?
How can I configure GNU RADIUS to solve this problem?
Thanks in advance
Carlo
Sergey Poznyakoff wrote:

Sergey Poznyakoff wrote:

> > But I 'm using SecurID for authentication:
> > When Cisco do the callback there is another authentication for my
user,
> > But the token code that I write when I dial  my NAS is no more
valid,
> > the token code change every 60 seconds, so it tell me that
> > authentication fail and callback fails too.
> > How can I avoid this?
> > I think that I would tell to my NAS cisco to avoid callback
> > authentication.
> > I adde in my raddb/users AVPair = "lcp:nocallback-verify=1".
> > But it doesn't change nothing
>
> In other words: you wish to allow the callback for usual users (those
> who are authenticated via a username/password pair) and to disable
> callback for SecurID users. Is that right?
>
> Regards,
> Sergey