tree 932d980086ff31e6d08571ff12aa1bd781a8db96
parent 5e5d94cd1b81e3ac0cd9b4423567d56394f15fac
author Harald Welte <laforge@gnumonks.org> 1477772599 +0200
committer Harald Welte <laforge@gnumonks.org> 1478078454 +0000

mncc_builtin: Properly reject DTMF

As per TS 23.014, a GSM MSC must implement mobile-originated DTMF
generation.  We gate the DTMF signalling messages to MNCC, and expect
the external MNCC handler to deal with it.  However, the internal MNCC
handler simply ignored such singalling messages, rather than rejecting
DTMF altogether.

It turns out failure to respond to START DTMF will cause some phones to
behave in interesting ways, particularly with modem
firmware v6.01.00, see https://osmocom.org/issues/1817).  In this case
the phone is not able to release the call as the pending response to the
START DTMF is probably keping a reference or lock of some sort.

Change-Id: I336f0cd0a6396b522d228479a417fd4d606157ac