* megaco_cli.c 		- contains CLI commands APIs
   * megaco_stack_alarms.c      - contains Alarm indication APIs from Trillium MEGACO layer

adding status CLI command to fetch peer/sap/transport-server information from Trillium MEGACO stack.

Stack

SG

Conflicts:
	libs/freetdm/mod_freetdm/mod_freetdm.c
	libs/freetdm/src/ftdm_state.c
	libs/freetdm/src/ftmod/ftmod_sangoma_ss7/ftmod_sangoma_ss7_handle.c
	libs/freetdm/src/ftmod/ftmod_sangoma_ss7/ftmod_sangoma_ss7_main.c
	libs/freetdm/src/ftmod/ftmod_sangoma_ss7/ftmod_sangoma_ss7_main.h
	libs/freetdm/src/ftmod/ftmod_sangoma_ss7/ftmod_sangoma_ss7_out.c
	libs/freetdm/src/ftmod/ftmod_sangoma_ss7/ftmod_sangoma_ss7_xml.c

         - restore flushing queue when channel state goes to down

         native bridge mode
         - This is supposed to be included in commit of
           b324f867. Somehow it's
           not included in that commit. Without this change, the
           REL receiving leg always stay in TERMINATING state when
           received an incoming REL message.

         is down and recovered later
         To re-produce this bug:
             1. do CGB on one side
             2. unplug signaling link cable
             3. plug signaling link cable back
             4. do CGU on the blocking side
             5. cic state stay in RESTART for ever
         Fix this problem by sending cic to SUSPENDED state after
         receiving/sending CGU message

         - clear up ACM_SENT & CPG_SENT flag in DOWN state in native
           bridge state machine

         - fill in IEs in INF according to INR request
         - print debug information if IE requested but not supported