old ascend pipeline p50 and bi-dir chap/pap in profiles
DComTalk.com Forum Index DComTalk.com
Discussion of VoIP, VPN, Video Conferencen, DSL and other data commucations.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web dcomtalk.com
old ascend pipeline p50 and bi-dir chap/pap in profiles

 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Modems
Author Message
JavierC
Guest





Posted: Tue Dec 14, 2004 3:45 pm    Post subject: old ascend pipeline p50 and bi-dir chap/pap in profiles Reply with quote

Hi,

We have an old ascend pipeline p50 (SW v. 6.0.0) acting as a central
connection point to several remote locations. For each one of them
there is a "connection profile" and static routing configured and it is
working ok. All the remote locations initiate the call to the central
old p50.

Now we need to create a new "connection profile" to manage ISDN
communications to another location, and we would like to use the same
fixed IP address schema. New modem hould initiate the call and the old
p50 should answer and route the IP packets to a Unix W.S.

But it seems that we are having problems with the implementation of
CHAP, since SW version 6.0.0 of the old p50 do not support
bi-directional CHAP/PAP.

For the new connection i have tried first a Cisco isdn modem and then a
Lucent pl50 (sw v. 7.3.4). With the Cisco i was only able to dial from
old p50 to Cisco, but not the other way with CHAP.

With the new pl50, when i am configuring a profile for it (to act as a
remote call originator), it does not permit to use uni-directional CHAP
to allow for the old equipment. Also, it forces to use a Send PW and a
Receive PW. (It should enable me to use only Receive PW if i need to,
as i really do).

Whenever a profile is detected as incomming call a "LAN security error"
is produced and the connection drops inmediately. The only solution i
have found is to use generic Answer profile, but then i am not able to
manage static IP routing to both end Unix WorkStations.

- Is there a way to use "connection profiles" in such situation
with uni-directional CHAP/PAP?
- If we use a generic Answer profile (Ethernet -> Answer ) how
i can manage static IP routing now without using "Ethernet --> Static
Rtes", (since this would require a "connection profile" associated with
it) ?

Upgrade SW is not an option here, since for several remote locations
passwd profiles and it is problematic to upgrade all the remote
locations.

Any help appreciated.

Thanks.
Javier C.
Madrid (Spain)
Back to top
 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Modems All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Solutions: Telephone Systems Electronics Satellite TV Tech & Gadgets
Powered by phpBB