| VoIP Termination Multi-Service Framework Solution |
| 1. Introduction on multi-service framework |
| Purposes of implementation of the multi-service framework include: |
--To provide universal applicational framework for different types of SIP Phone. One set of code can be used by softphones at PC/PDA, or by end points as SIP phones
--To separate functions as service control from signal control
--To separate functions as service implementation from media control |
| The multi-service framework is used to implement services including: |
--Audio calls
--Video calls
--Interoperation between different users
--Standard features independent of protocols as MGCP, H.248, SIP, H323, H.323M and etc.
--Extra services independent of protocols
--Development of services by users |
| The multi-service framework can be used by: |
--Audio/Video Telephone
--Software Phone
--SIP Software Phone |
| 2. The multi-service model |
|
Figure 1 The multi-service model |
| The multi-service framework consists of the following modules: |
a) SIP Protocol Stack
responsible for transaction control of SIP signals and call control
b) SUA (SIP User Agent)
responsible for call control of SIP multi-call (one call refers to an endpoint calls another) transaction
signals
c) JPF (Juphoon Phone Framework)
responsible for transaction and media control of each endpoint, media negotiation in signals, receiving
call requests and orders of transaction control from users and informing users of inbound calls and
relative states
d) Softphone GUI, Telephone UI, IAD UI
implanted for users. For instance, Softphone GUI is a phone interface which has call button, answer
button and etc. Telephone UI has buttons as pick up, hang up, dial, switchhook flash and etc.
e) AUDIO and VIDEO
an abstract layer of media control. JPF is able to control media channels and directions (send only or
receive only) as long as it uses interfaces (for example, Audio_StrmCreate used to create a media
stream) furnished by AUDIO and VIDEO. AUDIO layer is responsible for implementing driver
interfaces with tangible audio cards or DSP as well as the maintenance of RTP media control. All
implementations related to Audio QoS are implemented in this module. |
| 3. The multi-service model |
|
| Collaboration components provided by users: |
--DSP Service
Provides audio Codec, such as G.711 A/U, G723.1, G729 and audio QoS components, such as echo cancellation, mute suppression and etc.
--Video Service
Provides components to sample video data and display
--Telephone Service
Provides interfaces to enable the functions as hang up, pick up and dial, and offers LCD display component. |
|
Figure 3 User interaction of the multi-service framework |
| 4. The multi-service framework concepts |
|
Figure 4 Concepts about the multi-service framework |
| 5. The multi-service thread model |
|
Figure 5 The thread model of the multi-service framework |
