Improve operator profile support, including properly parsing operator_tune requests

[Jalle19]

Fixes #1046, hopefully

[Jalle19]

@Yuri666 do you have this CAM? It wants to tune to 12226L @ 36E, 12226L @ 56E or 12188L @ 160E

[Jalle19]

@Delitants please also try this branch at some point with the NTV CAM or whatever it is

[Yuri666]

@Yuri666 do you have this CAM? It wants to tune to 12226L @ 36E, 12226L @ 56E or 12188L @ 160E CAM needs interaction. [26/06 22:28:48.358 AD4]: CA 4 ======= MMI menu ======= [26/06 22:28:48.358 AD4]: [UI 0] Viaccess Conditional Access [26/06 22:28:48.358 AD4]: [UI 1] NTV-PLUS Operator Profile (OP) [26/06 22:28:48.358 AD4]: [UI 2] Press 'OK' to confirm, 'EXIT' to quit [26/06 22:28:48.358 AD4]: [UI 3] Do you want to activate the NTV-PLUS Operator Profile for satellite signal? [26/06 22:28:48.358 AD4]: [UI 4] YES [26/06 22:28:48.358 AD4]: [UI 5] NO

And now 12226L @ 36E disabled.

[Yuri666]

I think better way to enable operator profile - put CAM in TV and use cam menu. Different CAMs use different behaviours to interactions during enable operator profile

[Jalle19]

Interesting, can you try this branch and post a complete log with -v ca?

[Yuri666]

minisatip.log

[Delitants]

Interesting, can you try this branch and post a complete log with -v ca?

I have no longer NTV cam active, stopped paying for it long time ago. The main concern now is tivusat cam.

[Jalle19]

@Yuri666 unfortunate that the CAM requires MMI to activate the profile. The specification says that this should be done using the operator profile command set, where the host has an opportunity to say that it is "non-interactive".

[Jalle19]

@Yuri666 any chance you could post another log where you have first activated the profile in a TV, then put the CAM back to minisatip?