fix session timer failure when freeswitch is generating the sdp and there are enough dynamic codecs enabled to conflict with the 2833 pt (4 by default)

Prior to this change, calling flush_inbound_reg with @domain will
reboot all matching devices (if reboot is specified), but will not
actually flush the matching registrations.

         proper alarm handling for R2 calls

add send-presence-on-register (true|false|first-only) param to sofia and api command sofia global debug [presence|sla|none]

add send-presence-on-register (true|false|first-only) param to sofia and api command sofia global debug [presence|sla|none]

- Use the newly introduced FTDM_SPAN_USE_PROCEED_STATE flag and FTDM_CHANNEL_STATE_PROCEED.

- Update ftmod_libpri's state machine table (taken from ftmod_sangoma_isdn).

- Move pri_destroycall() to HANGUP_COMPLETE state.

- Try to get a little bit closer to the ISDN states by using pri_acknowledge() in RINGING,
  pri_progress() in PROGRESS and pri_proceeding() in PROCEED state.

- Go to PROGRESS_MEDIA in on_progress() only if there is inband indication available, go to
  PROGRESS if not.

- Go to RINGING state in on_ringing() and remove PROGRESS_MEDIA check.

NOTE: One libpri error message and a VETO (PROGRESS -> RINGING) warning to investigate,
      but changes seem to work fine nonetheless.

Tested-by: SparFux (#freeswitch / #freeswitch-de  @ irc.freenode.net)
Signed-off-by: Stefan Knoblich <s.knoblich@axsentis.de>

freetdm: ISDN-Fix for d-channel indexing, causing improper configuration on non-consecutive logical spans

fix seg related to ptime mismatch + CNG + PLC (if you ever get purple ptime mismatch warnings you want this patch)