Re: (ASCEND) Using SNMP to disable Pipe50 calling??

[Phillip Vandry <vandry@Mlink.NET>]

> I have a number of ISDN customers set up with Pipeline 50's 
> connecting to our Max 4048's. Some of these customers are on a 
> 'daytime dedicated' - basically, they can be on 7am-7pm, but not 
> 7pm-7am. While this works out quite well for ourselves and the 
> customer, I'm trying to find a way to make there Pipelines stop 
> connecting in the evening if one of their employees leaves a mail 
> client running and checking mail or something similar - otherwise, 
> they get connected for no good reason and tie up one of our B 
> channels. I can set it up so Radius rejects them, but then they 
> absolutely *hammer* away at the radius server, dialing over and 
> over again (3000+ calls per night).
> 
> What I'd like to do is use snmpwrite (from a system on their end) to 
> disable calling after 7pm, and then re-enable it at 7am. I know how 
> I can do this with one exception; I need to find an appropriate OID. 

There is a MIB for this, but I cannot seem to find a Pipeline with the
right combination of hardware and software to support it. I thought it
only required version 7.x, but I tried on 7.0.3 (DSL-ACAP Pipeline)
and it doesn't seem to work. Anyway, perhaps you will have better luck.

The variable is internetProfile__active in the ASCEND-MIBINTERNETPROFILE-MIB
MIB. It is indexed by the name of the connection profile in decimal ASCII.
For example, if the connection profile you want to disable is called
'test', then you need to look at

internetProfile__active.116.101.115.116

or

.1.3.6.1.4.1.529.23.1.1.1.2.116.101.115.116

You can change most of the other parameters in a connection profile (or
several other profile types) with similar OIDs.

> If not, is there at least a way to make the Pipeline wait longer 
> between redial attempts? I tried the 'Block calls after' and 'Blocked 
> duration' settings in the Session options (for the Connection 
> profile), but they don't seem to have any effect; I suspect the only 
> work if the call itself failed, where in this case the ISDN connection 
> is established, but my radius server is rejecting them - then again 
> that's only a guess.

Hmm... reject them based on caller ID? If you can do that, then you can
reject them without ever connecting the call.

-Phil
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>