This Message was undeliverable due to the following reason:
The following destination addresses were unknown (please check
the addresses and re-mail the message):
SMTP <macmilan@yebo.co.za>
Please reply to Postmaster@neptune.yebo.co.za
if you feel this message to be in error.
--===========================_ _= 9069213(19324)
Content-Type: message/rfc822
Received: from relay01.iafrica.com ([196.7.0.160]) by neptune.yebo.co.za
(Post.Office MTA Undefined release Undefined
ID# 0-54426U40000L40000S0V35) with ESMTP id AAA29685
for <macmilan@yebo.co.za> Fri, 16 Oct 1998 05:07:37 +0200
Received: from [207.53.165.8] (helo=walnut.iea-software.com)
by relay01.iafrica.com with esmtp (Exim 1.92 #2)
for macmilan@sprintlink.co.za
id 0zU0EF-0007VR-00; Fri, 16 Oct 1998 05:07:01 +0200
Received: from walnut.iea-software.com (walnut.iea-software.com [207.53.165.8]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za002446 for <emerald@iea-software.com> Thu, 15 Oct 1998 19:56:50 -0700
Received: from [203.162.3.234] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id cambaaaa for <emerald@iea-software.com> Thu, 15 Oct 1998 19:56:46 -0700
Received: from mail.vnn.vn by hanoi-fw-ex.vnn.vn
via smtpd (for external.iea-software.com [207.53.165.3]) with SMTP; 16 Oct 1998 03:02:55 UT
Received: from newsrv.cmchanoi.cmc.com ([202.167.114.207]) by mail.vnn.vn
(Netscape Mail Server v2.02) with ESMTP id AAA21813
for <emerald@iea-software.com> Fri, 16 Oct 1998 10:02:49 +0700
Received: from mdaemon.cmc.com.vn (localhost [127.0.0.1]) by newsrv.cmchanoi.cmc.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
id VAX1GPL1; Fri, 16 Oct 1998 22:01:21 +0700
Received: from MDaemon Pop Client [203.162.0.24] by mdaemon.cmc.com.vn [127.0.0.1] with POP (MDaemon.v2.7.SP3.T) for <emerald@iea-software.com> Fri, 16 Oct 1998 21:01:54 +0700
Received: from hanoi-fw.vnn.vn [203.162.0.100] by mr-hn.vnn.vn [203.162.0.24] with SMTP (MDaemon.v2.7.SP3.R) for <DTHue@hn.cmc.com.vn> Fri, 16 Oct 1998 08:23:46 +0700
Received: from walnut.iea-software.com ([207.53.165.8]) by hanoi-fw.vnn.vn
via smtpd (for mr-hn.vnn.vn [203.162.0.24]) with SMTP; 16 Oct 1998 01:27:04 UT
Received: from walnut.iea-software.com (walnut.iea-software.com [207.53.165.8]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za002428 for <emerald@iea-software.com> Thu, 15 Oct 1998 15:17:23 -0700
Received: from [206.85.21.2] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id ctlbaaaa for <emerald@iea-software.com> Thu, 15 Oct 1998 15:17:20 -0700
Date: Thu, 15 Oct 1998 17:24:34 CDT
Message-Id: <199810151724.AA1973223974@rwts.qcom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: "MailingList Receiver" <list_rx@qcom.net>
Reply-To: <list_rx@qcom.net>
X-Sender: <list_rx@rwts.qcom.net>
To: emerald@iea-software.com
Subject: callback/emerald/radius attributes
X-Mailer: <IMail v4.06>
X-DomainScript: iea-software.com\\script.mml
X-Script: \\FilterScript.mml
X-UserScript: iea-software.com\emerald\script.mml
X-MDaemon-Deliver-To: emerald@iea-software.com
>> 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
>an
>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.
Thanks
--===========================_ _= 9069213(19324)--