Revamp of OCTCall and start implementation of OCTToxAV into Submanager

[Chuongv]

Halfway through I realized that we could implement OCTSubmanagerCalls without the use of OCTDBCall. What's important however, is that we need to capture the call duration through OCTMessageAbstract, which hasn't been implemented yet.

Let me know what you think..If the above sounds good, I can start removing OCTDBCall.

Thanks

[dvor]

So, you are planning to store call duration in OCTMessageCall?

I was thinking about implementing call duration not with startDate, but with timer:

• when connection establishes you can start timer, that tick every second
• on every tick you will add 1 second to call duration (which will be stored in OCTMessageCall?)
• if user pauses the call you will pause the timer
• when call ends you simply destroy the timer.

This way if application will be killed (or will crash :open_mouth:) call duration will be still correct.

[dvor]

Let me know what you think..If the above sounds good, I can start removing OCTDBCall.

This looks good and indeed there is no need in OCTDBCall.

[Chuongv]

That sounds like a good idea! I think using something like NSTimer would help with adding seconds to call duration? Anyways, I'll remove my current implementation and create another PR when it's ready

[dvor]

I'm not sure where you will run NSTimer, it is not that easy to do on background thread. You can also take a look at GCD timer.

[dvor]

Okay then.