MMS bearer setup
While looking into why "autoconfigure" doesn't pick up my provider from m-b-p-i I noticed that mmsd doesn't look for an mms
type bearer but rather looks up the currently connected bearer and if that doesn't have the needed mmsc
and mmsproxy
attributes simply skips autoconfigure. I see two possible solutions (besides keeping the current behavior):
- lookup the MMS bearer for the relevant data but keep using one of the already connected bearers (which I guess is what happen in practice atm when people hand configure their MMS)
- teach mmsd to connnect the mms bearer
Those two things aren't exclusive we could do 1. first and then add 2. later on. @kop316 pointed out that mmsd currently isn't in the business of managing bearers and I can imagine that some things become complicated so maybe we want to cook up a tool to configure mms bearers on the command line first to test things out?