Error: Error receiving packet: Connection refused ...

2002-04-20 Thread Do-Risika RAFIEFERANTSIARONJY
Hi all, Does anyone have explanations for these errors. They appeared after the system was rebooted after crashing, but they disappear 1 or 2 minutes after ?!? Sat Apr 20 16:44:08 2002 : Auth: Login OK: [so.co.im] (from nas nas3 port 15 cli 202238259) Sat Apr 20 16:44:08 2002 : Error: Error

Re: Error: Error receiving packet: Connection refused ...

2002-04-20 Thread Alan DeKok
Do-Risika RAFIEFERANTSIARONJY [EMAIL PROTECTED] wrote: Does anyone have explanations for these errors. They appeared after the system was rebooted after crashing, but they disappear 1 or 2 minutes after ?!? Sat Apr 20 16:44:08 2002 : Auth: Login OK: [so.co.im] (from nas nas3 port 15 cli

isdn and caller-id

2002-04-20 Thread Petre L. Daniel
heya. i got a allied telesyn ar 395 router for isdn. i cant see no caller-id with radwho nor dialup_admin .. everything seems okei in the freeradius conf.. what can i do to see the telephone numbers? with the portmaster i cna see them. -- Petre L. Daniel,System Administrator, Canad Systems

Re: isdn and caller-id

2002-04-20 Thread Alan DeKok
Petre L. Daniel [EMAIL PROTECTED] wrote: i got a allied telesyn ar 395 router for isdn. i cant see no caller-id with radwho nor dialup_admin .. everything seems okei in the freeradius conf.. what can i do to see the telephone numbers? Fix your NAS. The RADIUS server will only log what it

Re: isdn and caller-id

2002-04-20 Thread Roy Hooper
Be sure your telco is providing you with caller-ID data in the first place. All major brand gear (Cisco, Ascend, Livingston) I've encountered is very happy to send the caller-ID info when the gear itself gets it. Some gear can probably be configured not to send caller-ID. Caller-ID may not be