Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) CLID callback
On Fri, Oct 24, 1997 at 10:09:41AM +0200, Norbert Wegener wrote:
> Andre Beck wrote:
> >
> > On Wed, Oct 22, 1997 at 07:30:09PM -0700, Peter Lalor wrote:
> > > I just finish wading through all the horror stories the Germans were having
> > > with trying to do callback based on CLID. It was so horrible, I'd like to
> > > try it (only in California). ;-)
> >
> > True Masochism ;)
> ..
> ...
> ....
> > On the Max (or other Pipe, let's say on the "initial Caller"):
> >
> > 1) Set the profile to Exp Callback=Yes
> >
> > Thats the simple part. The less simple part is dealing with bad timings
> > of the telco (when the callback arrives on your Max before the refused
> > call is dropped, i.e. the DISCONNECT or RELEASE COMPLETE arrives). If
> > you have such problems, try to use the RADIUS hack (the outgoing pro-
> > file has a wrong IP address, doesn't matter because it is cleared soon
> > anyway, but prevents the Max from seeing a call collision).
> >
>
> We have exactly the same problem. What I do not understand: When I use a
> PC
> with Linux,WfW311 or Win95 as "initial Caller" this works for us. So
> what's Ascend's problem with this?
Linux ISDN (I4L) has been designed to cope with that oddity. Ascend,
however, have added the feature somewhat late in the history of the
firmware. The addition collides with another behavior of the Ascend
firmware: It doesn't allow two connections with the same profile, and
trying to place such second connection is a "call collision" and causes
a "LAN security error". We had hope that with some 4.6C or such, when
"Exp Callback" was introduced, this will be a fix of the problem. The
fix obviously requires that "Exp Callback" changes the profiles be-
havior from "intend to get a connection" to "intend to get a callback
placed". So the call coming back would not collide with this outgoing
call because it would never have been placed with the intention to get
a connection. Bad enough, the real meaning of "Exp Callback" is simply
(my heart had a leap second when I read this first) "after placing this
call, wait 90 seconds until placing the next". This is a quick hack around
instodialing, but not what we expected. Thus the only way to get ISDN
callback running without grief is to fake the outgoing profiles IP
adresses in order to keep the Ascend from detecting a call collision
in this case.
--
Kanther-Line: PGP SSH IDEA MD5 GOST RIPE-MD160 3DES RSA FEAL32 RC4
+-o-+--------------------------------------------------------+-o-+
| o | \\\- Brain Inside -/// | o |
| o | ^^^^^^^^^^^^^^ | o |
| o | Andre' Beck (ABPSoft) beck@ibh-dd.de XLink PoP Dresden | o |
+-o-+--------------------------------------------------------+-o-+
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: