You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

MelwareDE 670b17998c Original idea was to use L1/L2 state to manage mapping of outgoing calls to available hardware resources for E.1/T.1 only. This functionality is not availeble for BRI: the state of L2 is newer known: even if we know local L2 activation policy we do not know the remote on and do not know if L2 activation works without problems. But now it is requested to show the state of BRI interfaces. The code is modified to maintain two states: functional and visual one. Functional is used for E.1/T.1 only. Visual is used for every one.		12 years ago
..
divastatus.c	Original idea was to use L1/L2 state to manage mapping of outgoing calls to available hardware resources for E.1/T.1 only. This functionality is not availeble for BRI: the state of L2 is newer known: even if we know local L2 activation policy we do not know the remote on and do not know if L2 activation works without problems. But now it is requested to show the state of BRI interfaces. The code is modified to maintain two states: functional and visual one. Functional is used for E.1/T.1 only. Visual is used for every one.	12 years ago
divastatus.h	Original idea was to use L1/L2 state to manage mapping of outgoing calls to available hardware resources for E.1/T.1 only. This functionality is not availeble for BRI: the state of L2 is newer known: even if we know local L2 activation policy we do not know the remote on and do not know if L2 activation works without problems. But now it is requested to show the state of BRI interfaces. The code is modified to maintain two states: functional and visual one. Functional is used for E.1/T.1 only. Visual is used for every one.	12 years ago
divastatus_ifc.h	Add 'capi ifcstatus' CLI command	13 years ago
divastatus_parameters.h	Use information about hardware for distribution of media processing resources across CAPI controllers. Clean up.	13 years ago