> I have yet to get an ISDN call to successfully come into our PM-3's.
Try dialing back into the PM3 from itself (i.e attach <port> then dial).
Of course, this won't work if you have the line setup for incoming only
though.
>
> Right now, we are trying to get Ascend Pipelines (50s, 75s, and 130s) to
> connect in. But it just isn't working.
>
> If I telnet in and watch the connection, I will see the username pop up in
> a "show sessions" screen, but the status is always "DISCONNECTING". If I
> do a "show s#", I will see DISCONNECTING and it will say "Protocol Error".
> What does this mean?
If you are seeing the username show up with a "DISCONNECT" status, this
usually means an authentication problem. Make sure that the Ascend is set
up to "Send PAP" but not "Recv" or do CHAP. Also, a "set console", "set
debug 0x51" would probably be very helpful, since it will show you exactly
what is happening during the login. I haven't seen the "Protocol Error"
message before, that is coming from the ISDN module.
>
> I don't know if this is a PM issue, or a RADIUS issue. There are no
> entries in the RADIUS accounting log.
They are not completing authentication then. Check above mentioned
settings on the Ascend, as well as the user's RADIUS entry.
>
> I assume that ISDN users can be authenticated from the RADIUS server,
> correct? Do I need any special configuration to do this?
Yes. Nope.
>
> Also, what are Directory Numbers? Do I need to configure those?
This is in the manual. Depends on your setup, most likely no.
>
> We are running ComOS 3.7.2 and RADIUS NT 2.0.1.
>
> I'd love to hear from anyone who has successfully gotten Ascend equipment
> to call into a PM-3.
>
> Thanks in advance,
>
> Dave
----
Josh Richards - <jrichard@livingston.com>
Beta Engineer
Lucent Technologies (Remote Access Business Unit)
(previously Livingston Enterprises, Inc.)
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.