Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Restricting login speed
Igor Tarasenko wrote:
]
]Try to separate clients by means of Called ID attribute if you have
]different numbers
]fo K56 and V34 modems.
]For Clients which use K56 define in Radius Profile one Called ID (DNIS) for
]V34 client
]other.
]Refer to Radius Configuration Guide 3-36
]Best Regards,
sure... but that doesn't solve our problem. we have a 500+ line v.34 string
(not ascend gear). it is filled to saturation every night from
7:30pm to 2am. we have added a small (soon to be much larger) k56flex
string (using a 4048). the problem that we want to solve is that of
v.34 users (in other words they do not have k56 capable modems) dialing
into the 4048 and thus turning our K56Flex string into nothing more than
an extension of our v.34 string. In other words, we want to use our
4048 to exclusively serve users who have K56 capable modems.....but
we have not found any way to prevent the modems in the 4048 from
negotiating down to v.34.
also, individual radius profiles are not practical.... we authenticate
via a unix passwd file, which is linked to campus DCE, and supports
about 50,000 users. pretty much everything is done with the radius
default profile.
]>as far as i know, you can only distinguish between async (v.34, k56, etc)
]>and sync (isdn). we really wanted to limit our 4048 to not accept
]>async calls at speeds less than 33.7kbps, in order to prevent v.34
]>users from tying up all of our k56 modems (we have a seperate dial
]>string for v.34 users). however we were told by ascend that this
]>was not currently possible, but might be in the future....
++ 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: