> Hi,
>
> I'm not sure which list this is more appropiate on so I have sent it to
> both.
>
> I'm having a weird problem that when I restart radiusd (version 2.0.1),
> my pm3 refuses to answer any calls and autoblocks all channels. To fix
> this I have to issue the command "set isdn-switch ts014" (Macrolink in
> Australia) and then reboot the pm3.
>
Hmm..not quite sure how this could be happening as a result of restarting
the RADIUS daemon. Might be coincidence unless something really odd is
going on. It has no concept of what a PRI/T1 channel or a switch even is.
What happens when you kill radiusd completely? Also what is the output
of a "show isdn" and "show lineX" before and after you restart radiusd?
Also, whatever the problem is you may be able to do a "reset lineX"
instead of changing the switch type having to reboot.
> Has anyone else had similar problems, or have a reason why this is doing
> this?
>
> Regards,
>
>
> Richard Lennerts
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-radius' in the body of the message.
>
>
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.