>What is the app you are using?
>Does it do PPP or staight Term sessions?
>How were you delivering Caller ID info to the app server before?
>L2TP might help you, as Telephone numbers are passed through it.
The application server is something we wrote ourselves. The current
dialup platform uses modem chassiseses attached to PM25's. Each port on
the PM25 is configured to accept incoming tcp connections and route
them to the serial port, i.e. telnet to port 6010 on the portmaster and
you're talking to the modem on serial port 10 (I forget what the
manual calls this).
The application server takes over all management of the modems. It
sends AT commands to configure the modems, and it recognizes incoming
calls by parsing the RING strings that the modem transmits. Of course,
caller ID is retrieved between the first and second ring. The PM
is basically being used as a dumb box of serial ports.
You can imagine why we'd like to redesign this. Each modem is dedicated
to an individual application server (we're running six servers for
different contracts) so there's no economies of scale. The unusual
portmaster configuration precludes handling other sorts of traffic on
the same equipment. And the hardware cost is higher than a PM3 or PM4
would be.
I'll see what I can find out about L2TP, but from what I understand of
it we'd have to build L2TP into the application server.
The frustrating part is that the PM 3/4 is so close to meeting our
needs, and this shortcoming is so *arbitrary*. There's no fundamental
reason why you can't look up caller ID from the tcp stream information,
the capability just isn't in there.
-- Kenneth Herron kherron@sgum.mci.com +1 916 649 6142 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>