Skip to content

GitLab

Last edited by Sourav Das
Page history
This is an old version of this page. You can view the most recent version or browse the history.

Other Important Topics

Some More Informations

To create an interactive UI that can show all relevant information one may need to use the following Items.

  1. CallStates : CallStates as it's name suggests signifies the current state of the calling framework. Call States can be any among the following
        CallState.INITIATING
        CallState.READY
        CallState.TRYING
        CallState.INVITE
        CallState._180_RING
        CallState._183_PROGRESS
        CallState._181_CALL_BEING_FORWARDED
        CallState._200_OK
        CallState.BAD_REQUEST
        CallState.INCOMING
        CallState.ON_HOLD
        CallState.BYE

We get these call states in updateCallstate() function in SDKSIPListener interface. Every state has it's own Meaning and the UI should be designed according to the current Updated state. For example CallState._200_OK means that a call is currently going on. You can also get the current state from SIPProvider.getcallState too but that is not recommended

  1. Error Codes: You can get any error code integer value. You can use those errorcodes' meaning to show to the UI why their calls failed if necessary. eg. 403, 404, 486 etc.

  2. Display Status: SDKSIPListener can update the Display Status. The Display status is shown in the UI. Available DIsplay Statuses are:

        DisplayStatus.InvalidLogin
        DisplayStatus.Empty
        DisplayStatus.InvalidCode
        DisplayStatus.Registered
        DisplayStatus.Registering
        DisplayStatus.Unregistered

You can control what to show in the main UI according to the display status.