4.1.10.3 Common methods

 AVATAR

Clicking on the Avatar will allow you to change it. If there is no avatar defined yet, the default image is shown.
The avatar is stored locally in the dialer and on the server. Size 320x480, jpeg format.
After changing the avatar, we send a new image to the server via WebAPI. In response, we get timestamp changes in the universal time format. we also store this information in the dialer, let's call it ALC for avatar last change.
In case of problems with uploading (errors, lack of internet, etc.), you should protect the app so that it will try to upload until it is successful.
 
After successfully sending it to the webapi server, you should send PUBLISH to the SIP server to which you are registered.
In publish, we always send the status "open". In the Note field we send:
<note>
<ALC>timestamp</ALC>
text status here
</note>
 
The ALC timestamp sent in PUBLISH will be the same as we received from webapi.
 
Deleting the avatar

When deleting an avatar, you should send file = NULL to webapi. The server will return timestamp, we publish normally as if it were an avatar change.

Status

Clicking our own name/number will allow you to edit the text. Depending on the platform, it will be a pop-up window with inputtext and the ability to choose statuses Online , Away, Busy and the appply button to save the changes.
After changing the Status, the dialer sends PUBLISH:
 
<note>
New status here
</note>
 

Frist name, Last name, email

Changes to this information are to be sent to the server via webapi. We do not take any additional actions. Of course, this information should also be kept locally in the dialer.
Email must be validated. Moreover, the email must be unique and the server's response must be handled correctly. if the dialer receives information that the email is already taken, display the message "the email is already in use" to the user and set the Email field to "not set"