This Message was undeliverable due to the following reason:
The following destination addresses were unknown (please check
the addresses and re-mail the message):
Please reply to Postmaster@neptune.yebo.co.za
if you feel this message to be in error.
--===========================_ _= 721130(11364)
Received: from relay01.iafrica.com ([220.127.116.11]) by neptune.yebo.co.za
(Post.Office MTA Undefined release Undefined
ID# 0-54426U40000L40000S0V35) with ESMTP id AAA1724
for <firstname.lastname@example.org> Fri, 16 Oct 1998 00:28:57 +0200
Received: from [18.104.22.168] (helo=walnut.iea-software.com)
by relay01.iafrica.com with esmtp (Exim 1.92 #2)
id 0zTvsZ-000795-00; Fri, 16 Oct 1998 00:28:21 +0200
Received: from walnut.iea-software.com (walnut.iea-software.com [22.214.171.124]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za002428 for <email@example.com> Thu, 15 Oct 1998 15:17:23 -0700
Received: from [126.96.36.199] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id ctlbaaaa for <firstname.lastname@example.org> Thu, 15 Oct 1998 15:17:20 -0700
Date: Thu, 15 Oct 1998 17:24:34 CDT
Content-Type: text/plain; charset=us-ascii
From: "MailingList Receiver" <email@example.com>
Subject: callback/emerald/radius attributes
X-Mailer: <IMail v4.06>
>> RadiusNT 2.5, Emerald, PM-3 -
>> I have a user that we will be setting up with ISDN >>service that we will need to dialback to avoid toll >>charges.
>> The customer will be running a 3com router with NAT.
>The last I heard, 3Com Office Connect routers do NOT >support
>call back. I almost bought one until I found that out. :(
> They will need to dial-up, authenticate into our system >then have the PM-3 drop them, dial them back and make the >permanent connection.
> Is this possible and what lines in the SA record need to >be set? I am also assuming there will need to be a >location set into the PM-3..
> Reply to the list please as I didn't find anything in the >archive for this -
>You might be able to use the RADIUS call back attributes, >but this isn't
>easy task to accomplish.
Just off the phone with customer and 3Com told them they were sent the wrong model router to do it on their end. I just wish to be able to at least attempt to perform accounting on this circuit.
I assume there is a way to specify the RADIUS call back attributes thru the client's SA record. Particularly, if I am going to send a command to initiate a call from the PM-3's location table, which RADIUS attribute(s) are used for that? This isn't very clear to me looking thru the RadiusNT documentation and comparing notes with the PM-3 command line/radius guide. I suppose this is an idea that is implemented rarely - if ever - from Emerald.
You all are `da Experts.
--===========================_ _= 721130(11364)--