[asterisk-dev] CLI manager logout

[BJ Weschke]

Matt Riddell wrote:
> On 11/11/2008 11:08 a.m., Clod Patry wrote:
>   
>> hi guys,
>>
>> I faced the problem where a customer called me and reported some
>> "weird" connection that he was not sure.
>> example:
>> deer*CLI>  manager show connected
>>    Username         IP Address
>>    pv               64.34.139.75
>>    abc             64.34.139.75
>> deer*CLI>
>>
>>
>> Right now, there's no way to logout a connected manager user.
>>
>> So I realized there was no quick way for a CLI user to logout
>> connected session. The only way that is possible is via a restart now.
>>
>> What I've in mind is something like a CLI command: manager logout<session_id>.
>>
>> But, since sessions doesnt have an id, this makes the logout
>> "impossible", since N username could connect from M IP addresses.
>> In case 1 username are connected from 3 differents IP, which one will
>> we logout? We can't.
>>
>> What do you think about having something like an id in the struct
>> mansession, so we could identify the session.
>> That will leads to a possible manager logout<session_id>, which will
>> be much more simpler for the CLI users.
>>     
>
> Alternatively you could do
>
> manager logout y from x.x.x.x
>
>   
 I think I prefer that format as proposed the best. You may end up taking out multiple sessions with it, but in the case of trying to eliminate someone from a rogue IP, I think it's probably the right way to go about it.

--
Bird's The Word Technologies, Inc.
http://www.btwtech.com/