I found a problem here but it may not completely match your expectations.
I reviewed the RFC 4028 and checked against the code and I discovered we should not be putting a Min-SE in any response at all besides a 422:

section 5:

   The Min-SE header field MUST NOT be used in responses except for
   those with a 422 response code.  It indicates the minimum value of
   the session interval that the server is willing to accept.

I corrected this problem and implemented the 422 response so if you request a value lower than the minimum specified for the profile.
If the value is equal or higher to the minimum, it will be reflected in the Session-Expires header in the response and no Min-SE will be present.

FS-5997 regression from commit 70accd9f this caused some attended transfers to calls with multiple targets to get the abondoned channels to be stuck on write lock

add generic keepalive system and implement it in sofia to send MESSAGE or INFO packets in-dialog at specified interval.

Adds app: enable_keepalive 0|<seconds>
This app can be run in the dialplan or with execute_on_* type variables for B-legs.

Adds sofia param: keepalive-method  : defaults to MESSAGE can also be "INFO"
This param sets which SIP method to use.

FS-6447 --resolve return subscriber-absent platform-code 20 if <dial> is attempted to user that is not registered

Upgrade to OpenSSL 1.0.1g in Windows build (Visual Studio 2010 and 2012)

Automated leak detectors find leaked memory on shutdown.  Cleaning up
after ourselves on shutdown eliminates noise from these reports.

The rc variable here was always initialized but the compiler couldn't
see that because of the lack of an unconditional else clause.

We were leaking one event (~539 bytes) for every subscribe packet
received with both an "event: as-feature-event" and an authorization
header.

FS-353

Tested with several libmemcached versions between 0.31 and
1.0.18. Unfortunately the API is extremely volatile and awkward to
use. Packaging scripts still need addressing.

FS-353

Per the automake manual these should go in LIBADD.

http://www.gnu.org/software/automake/manual/html_node/Program-and-Library-Variables.html

FS-353
Signed-off-by: Travis Cross <tc@traviscross.com>

FS-353
Signed-off-by: Travis Cross <tc@traviscross.com>

The net effect here is the code looks more "regular" and reads more
linearly.

Previously we would continue considering phrase actions even after
receiving a break action; we would only break on the next input
clause.  It appears the intent here was to break before the next
action.

If we get SWITCH_STATUS_BREAK then we didn't get
SWITCH_STATUS_SUCCESS.

We're breaking out of the loop here anyway, so setting done to true is
useless.

We were leaking memory when break_on_match was set or when we received
back SWITCH_STATUS_BREAK from a callee as we were failing to free
field_expanded_alloc.

If pattern is null we're setting it to a non-null value, so this
branch will always be taken.

Use `git diff -w` or `git log -p -w` to see what's going on in this
commit.

In the event of a memory error, we were trying to free a null pointer
while leaking the allocation for field_expanded_alloc.

These variables aren't used outside of this for loop, so they should
be declared within it.