See: Description
| Package | Description |
|---|---|
| com.laserscorpion.rttapp.db |
The database layer handles saving persistent data in a SQLiteDatabase.
|
| com.laserscorpion.rttapp.rtp |
The RTP package implements the call layer, which as of now is all within RTTCall.
|
| com.laserscorpion.rttapp.sip |
Most of the SIP layer is made up of SipClient.
|
| com.laserscorpion.rttapp.ui |
The UI layer is the part the user sees and touches, the 5 different screens that each manage a
different part of the registration/call process.
|
Source code on GitHub
RTTApp is split into several layers: UI, SIP, and call, plus the database package which is not specific to one layer. Most functionality in setting up calls and managing app state is in the SIP layer, in particular in the SipClient. The real-time text functionality is provided by Omnitor's RFC 4103/t.140 library, at the lowest level, outside the com.laserscorpion.rttapp package, though this is managed via the RTTCall.
--------------
| UI layer |
--------------
|
--------------
| SIP layer | (SipClient)
--------------
|
--------------
| Call layer | (RTTCall)
--------------
|
--------------
| RTP layer | (JRTP, Omnitor t140)
--------------