| VOICE CONVERSATION | ||||||||||||||||
| VaxStandardSDK is peer-to-peer based VoIP solution. It connects two persons over the direct peer-to-peer connection to have real-time voice talk over the LAN, WAN or Internet. | ||||||||||||||||
![]() |
||||||||||||||||
| Steps to initiate and Connect to the listening end: | ||||||||||||||||
| - Person A executes the application containing the VaxVoice component. | ||||||||||||||||
| - Person B executes the application containing the VaxVoice component. | ||||||||||||||||
| - Person B enters the Listening Port and waits for the connection. | ||||||||||||||||
| - Person A enters the Person B’s IP & Listening Port and sends the connection request. | ||||||||||||||||
| - Person B gets the notification and accepts the connection. | ||||||||||||||||
| - On successful connection, both start talking using headphones/speakers and microphone. | ||||||||||||||||
| Sequence of Method Calls: | ||||||||||||||||
|
||||||||||||||||
|
Successfully Connected and having Voice Talk |
||||||||||||||||
|
||||||||||||||||
|
|
||||||||||||||||
|
* For more information about methods, see the Method Details Document * |
||||||||||||||||
| Listening server, remains in the listening state, during the Voice Session. However, if the listening end changes its status to BUSY, and a client tries to connect to the listening end, that client will get STATUS EVENT CODE: 55 (which means the listening server is BUSY). | ||||||||||||||||
| On Server side, OnConnectionEvent is triggered with client IP and Port, to establish or accept the connection. AcceptIncomingCall Method can be called by passing the client IP and Port. | ||||||||||||||||