PJSUA2 Documentation, Release 1.0-alpha
3.1.4 Call
This class represents an ongoing call (or speaking technically, an INVITE session) and can be used to manipulate it,
such as to answer the call, hangup the call, put the call on hold, transfer the call, etc.
3.1.5 Buddy
This class represents a remote buddy (a person, or a SIP endpoint). You can subscribe to presence status of a buddy to
know whether the buddy is online/offline/etc., and you can send and receive instant messages to/from the buddy.
3.2 General Concepts
3.2.1 Class Usage Patterns
With the methods of the main classes above, you will be able to invoke various operations to the object quite easily. But
how can we get events/notifications from these classes? Each of the main classes above (except Media) will get their
events in the callback methods. So to handle these events, just derive a class from the corresponding class (Endpoint,
Call, Account, or Buddy) and implement/override the relevant method (depending on which event you want to handle).
More will be explained in later sections.
3.2.2 Error Handling
We use exceptions as means to report error, as this would make the program flows more naturally. Operations which
yield error will raise Error exception. If you prefer to display the error in more structured manner, the Error class has
several members to explain the error, such as the operation name that raised the error, the error code, and the error
message itself.
3.2.3 Asynchronous Operations
If you have developed applications with PJSIP, you’ll know about this already. In PJSIP, all operations that involve
sending and receiving SIP messages are asynchronous, meaning that the function that invokes the operation will
complete immediately, and you will be given the completion status as callbacks.
Take a look for example the makeCall() method of the Call class. This function is used to initiate outgoing call to a
destination. When this function returns successfully, it does not mean that the call has been established, but rather it
means that the call has been initiated successfully. You will be given the report of the call progress and/or completion
in the onCallState() callback method of Call class.
3.2.4 Threading
For platforms that require polling, the PJSUA2 module provides its own worker thread to poll PJSIP, so it is not
necessary to instantiate own your polling thread. Having said that the application should be prepared to have the
callbacks called by different thread than the main thread. The PJSUA2 module itself is thread safe.
Often though, especially if you use PJSUA2 with high level languages such as Python, it is required to disable PJSUA2
internal worker threads by setting EpConfig.uaConfig.threadCnt to 0, because the high level environment doesn’t like
to be called by external thread (such as PJSIP’s worker thread).
12 Chapter 3. PJSUA2-High Level API
剩余270页未读，继续阅读
其实我是luckpaper
- 粉丝: 0
- 资源: 1
我的内容管理
展开
最新资源
- ExtJS 2.0 入门教程与开发指南
- 基于TMS320F2812的能量回馈调速系统设计
- SIP协议详解：RFC3261与即时消息RFC3428
- DM642与CMOS图像传感器接口设计与实现
- Windows Embedded CE6.0安装与开发环境搭建指南
- Eclipse插件开发入门与实践指南
- IEEE 802.16-2004标准详解：固定无线宽带WiMax技术
- AIX平台上的数据库性能优化实战
- ESXi 4.1全面配置教程：从网络到安全与实用工具详解
- VMware ESXi Installable与vCenter Server 4.1 安装步骤详解
- TI MSP430超低功耗单片机选型与应用指南
- DOS环境下的DEBUG调试工具详细指南
- VMware vCenter Converter 4.2 安装与管理实战指南
- HP QTP与QC结合构建业务组件自动化测试框架
- JsEclipse安装配置全攻略
- Daubechies小波构造及MATLAB实现
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
