Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

[ftmod_misdn] Make misdn_handle_mph_information_ind() cope with hfcsusb-style MPH_INFORMATION_IND messages.

Only two mISDN hardware drivers emit MPH_INFORMATION_IND messages and both use a different payload:

	- hfcsusb (HFC-based USB dongle) sends a set of ph_info + ph_info_ch structures
	  which contain the complete state information of the port
	  (including internal hw-specific state and flags).

	- hfcmulti which sends a single integer, a single L1_SIGNAL_* event.

We now try to guess the type of message from the payload length.

The hfcmulti signals are converted to FreeTDM alarm flags; the hfcsusb
state/flags are defined in kernel internal hw-specific headers and are ignored ATM (todo).
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Add MISDN_MSG_DATA() helper macro for easy access to mISDN message
payload.

Add forward declaration of misdn_handle_mph_information_ind() and use
it in misdn_activate_channel().
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

No reason to keep it around for longer.
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Add missing mISDN event/message types (e.g. MPH_INFORMATION_IND)
and use a helper macro (MISDN_EVENT_TYPE) to define the entries,
like we already do for misdn_control_types[].
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

add presence-disable-early sofia option to send non-specifc presence messages w/o special case for early

FS-3881 try this, i think the contact in the notify is causing the phone to change the destination for future subs

s not simply ignored.

commenting this out completely until a better solution is implemented.  also FYI you should be refreshing .update on each commit that changes the lib or any of its mods to force a rebuild from the top level

FS-3864 --resolve no philosophical constraint here.  Just saying since FS is a b2bua the message really does terminate at US but its find to do 202 per this patch

FS-3870 --resolve that is amazing that nobody found this before, we've probably been vulnerable to that bug for years