compare_open_sip_stacks

合集下载

通元微指纹识别模组TFP625R 用户手册说明书

通元微指纹识别模组TFP625R用户手册厦门通元微智能科技有限公司目录1.产品规格 (1)2.Pin map (3)3. 概念解释 (3)1）资源开销 (3)2）模组参数 (4)3）指纹库 (4)4.通讯协议 (5)1)数据包格式 (5)2）命令码 (6)3）反馈码 (7)5. 命令 (8)GetImg (8)Img2Tz (9)Match (10)Search (10)RegModel (11)StoreModel (11)LoadChar (12)UpChar (13)DownChar (14)UpImage (15)DeleteChar (16)Empty (17)SetSysPara (17)ReadSysPara (18)SetPwd (19)VfyPwd (19)SetAddr (20)ReadINFPage (21)WriteNotePad (22)ReadNotePad (22)TemplateNum (23)ReadConList (23)Cancel (24)GetMinEmptyID (25)AutoEnroll (26)AutoIdentify (28)6.使用流程 (30)7.休眠与唤醒 (31)8.测试环境 (33)9.技术支持 (34)欢迎使用通元微指纹识别模组TFP625R 。

本文将为客户使用本模组进行指纹识别开发提供必要的说明信息。

本模组为单机指纹识别模组。

模组可以进行指纹注册、指纹识别、指纹验证等功能。

本模组支持UART通讯方式。

1.产品规格TFP625R具有模组自学习功能。

该功能会提升指纹识别的准确率。

匹配同一指纹，在匹配若干次后，匹配分数有所提升。

2.P in map连接器类型：FPC-0.5-6P: 6Pin 条形连接器，间距0.5mm。

3. 概念解释1）资源开销2）模组参数3）指纹库图3-3，模板与特征在Flash 中的对应成员0 成员1特征2N-1。

i.MX8 8X Linux BSP L5.4 Rev. 1 应用笔记说明书

AN13275如何在新的 iMX8/8X 板上启用 Linux BSP L5.4Rev. 1 — 2023年5月26日应用笔记如何在新的 iMX8/8X 板上启用 Linux BSP L5.4 1 介绍1.1 目标本应用笔记介绍了在新的自定义 i.MX 8/8X 板上启用标准 Linux BSP L5.4 的一般过程，帮助用户快速移植标准Linux BSP 版本代码到自定义 i.MX 8/8X 板上，并提示用户注意那些需要修改的关键部分。

1.2 示例板本应用笔记使用 i.MX 8QXP 汽车参考板作为示例板，因为标准的 Linux BSP 版本不支持该参考板。

更多详细信息，请联系恩智浦代表。

该板的硬件设计基于 i.MX8QXP MEK 板，但有如下变化：•i.MX 8QXP C0 芯片•三星汽车级 LPDDR4 和 eMMC5.1•MIPI-CSI，配备 NVP6324 汽车 AHD 解决方案•LVDS 显示器，配备 TI DS90UB947/948 Serdes（通过FPD Link III），用于汽车应用•MIPI-DSI 显示器，配备 Maxim 96752/96755 Serdes（通过 GMSL2），用于汽车应用•恩智浦 TJA1101 汽车 100 Mbps 以太网 PHY•用于 Carplay/AA 的 USB3.0 host 和用于调试的 USB2.0 OTG图 1. i.MX 8QXP 汽车参考板1.3 Linux BSP 版本本应用笔记以 L5.4.47_2.2.0 Linux BSP 版本为例。

如需查询所有 i.MX Linux BSP 的版本，请参见 Embedded Linux for i.MX Applications Processors。

如何在新的 iMX8/8X 板上启用 Linux BSP L5.4以下章节介绍了移植SCFW、ATF、U-Boot 和 Linux 内核的一般过程。

openocd使用方法 -回复

openocd使用方法-回复OpenOCD (Open On-Chip Debugger)是一个开源项目，用于调试嵌入式系统的软件工具。

它提供了与实时处理器和程序调试接口（如JTAG、SWD等）通信的能力，以及访问处理器内部寄存器和内存的能力。

本文将详细介绍OpenOCD的使用方法，以帮助初学者迅速上手。

1. 安装OpenOCD首先，我们需要安装OpenOCD软件。

OpenOCD可以在多个操作系统上使用，包括Windows、Linux和macOS。

在安装之前，我们需要现有一个支持JTAG或SWD接口的调试器硬件，并连接到目标设备上。

在Windows上，可以从OpenOCD官方网站下载并安装Windows二进制文件。

安装完成后，将OpenOCD的安装路径添加到系统的环境变量中，以便在命令行中直接使用。

在Linux上，可以使用包管理器（如apt、yum等）安装OpenOCD。

例如，在Ubuntu上，可以运行以下命令安装OpenOCD：sudo apt-get install openocd2. 编写OpenOCD配置文件接下来，我们需要编写一个OpenOCD的配置文件，以告诉OpenOCD 如何与目标设备交互。

配置文件通常使用OpenOCD的“.cfg”扩展名，并包含一系列命令和选项。

以下是一个简单的配置文件示例：# 设置调试接口interface jlink# 设置目标设备jtag newtap target1 cpu -irlen 4 -expected-id 0x12345678# 配置连接速度adapter_khz 1000# 设置目标设备的处理器和调试接口set _CHIPNAME riscvset _WORKAREASIZE 0x8000set _CPUTAPID 0x12345678上述示例中，我们选择了J-Link作为调试接口，创建了一个新的JTAG tap和目标设备之间的连接。

我们还设置了适配器的时钟速度，以及目标设备的处理器类型、工作区大小和CPU tap ID。

opensips control panel 使用

开启一个全面的文章评估并撰写opensips control panel（OCP）的功能和应用，以帮助你更深入地理解这个主题。

1. opensips control panel 简介opensips control panel（OCP）是一个基于opensips SIP服务器的管理界面，它提供了一系列功能和工具，用于管理opensips服务器和呼叫路由。

OCP可以帮助管理员更轻松地监控服务器状态、配置路由规则、管理用户账号等。

2. OCP的功能和应用OCP提供了丰富的功能和应用，包括但不限于以下几点：- 实时监控：通过OCP，管理员可以实时监控opensips服务器的状态，包括注册用户、并发呼叫数、负载情况等，以便及时发现和解决问题。

- 路由管理：OCP允许管理员配置和管理呼叫路由规则，包括路由策略、转发规则等，以实现呼叫的灵活控制和管理。

- 用户管理：管理员可以通过OCP管理用户账号，包括添加新用户、修改权限、查看用户使用情况等，以保证用户的正常使用和安全性。

3. 从简到繁的探讨OCP在深入探讨OCP的功能和应用时，我们可以从简到繁地进行：- 从OCP的基本功能入手，介绍其界面布局和常用功能，帮助你轻松上手。

- 逐步介绍OCP的高级功能，如实时监控、路由管理、用户管理等，以帮助你更全面地理解其强大之处。

- 可以讨论一些高级应用场景，如如何通过OCP实现负载均衡、高可用性等，以帮助你更深入地理解其在实际项目中的应用。

4. 个人观点和理解在我看来，OCP是一个非常实用和强大的工具，它可以帮助管理员更轻松地管理opensips服务器，提高系统的稳定性和安全性。

通过OCP的实时监控和灵活的配置管理，可以更好地满足实际项目的需求，提升系统的性能和用户体验。

总结回顾通过本文的深入探讨，相信你已经对opensips control panel有了更深入的了解。

你可以通过实践和深入研究，进一步挖掘其更多的功能和应用，以应对复杂的实际项目需求。

SIP Phone Support (SPS) 版本1.0 维护和健康检查指南说明书

Configuration Note ContentsVersion 1.0 3 May 2013 Table of Contents1Introduction ......................................................................................................... 7 2 Free Disk Space .. (9)2.1 Procedure (9)2.2 Expected Results ................................................................................................... 9 3 CPU Usage (11)3.1 Procedure (11)3.2 Expected Results ................................................................................................. 11 4 Memory Usage and Handles Count .. (13)4.1 Procedure (13)4.2 Expected Results ................................................................................................. 13 5 SPS Log Files . (15)5.1 Procedure (15)5.2 Expected Results ................................................................................................. 15 6 CDR Files .. (17)6.1 Procedure (17)6.2 Expected Results ................................................................................................. 17 7 Windows Events Logs .. (19)7.1 Procedure (19)7.2 Expected Results ................................................................................................. 19 8 Virtual Machine Logs and Events .. (21)8.1 Procedure (21)8.1.1 Microsoft Hyper-V Server ........................................................................................21 8.1.2 VMware .. (21)8.2 Expected Results ................................................................................................. 21 9 Antivirus Software (23)9.1 Procedure (23)9.2 Expected Results ................................................................................................. 23 10 System Backup . (25)10.1 Procedure (25)10.2 Expected Results ................................................................................................. 25 11 SPS License . (27)11.1 Procedure (27)11.2 Expected Results ................................................................................................. 27 12 Database Synchronization Status.. (29)12.1 Procedure (29)12.2 Expected Results (29)Preventative Maintenance & Health-Check Procedures13SPS Diagnostics (31)13.1Procedure (31)13.2Expected Results (31)Configuration Note 4 Document #: LTRT-31330Configuration Note NoticesVersion 1.0 5 May 2013 NoticeThis document describes the preventative maintenance and health check procedures to be performed by administrators of the SPS system.Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee the accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document and other documents can be viewed at /downloads .© Copyright 2013 AudioCodes Ltd. All rights reserved.This document is subject to change without notice.Date Published: May-7-2013TrademarksAudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect, VoIPerfectHD, What’s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners.WEEE EU DirectivePursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product.Customer SupportCustomer technical support and service are generally provided by AudioCodes’ Distributors, Partners, and Resellers from whom the product was purchased. For technical support for products purchased directly from AudioCodes, or for customers subscribed toAudioCodes Customer Technical Support (ACTS), contact **********************.Documentation FeedbackAudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our Web site at /downloads .Related DocumentationPreventative Maintenance & Health-Check ProceduresReader's NotesConfiguration Note 6 Document #: LTRT-31330Configuration Note 1. Introduction Version 1.0 7 May 20131 IntroductionThis document describes the preventative maintenance and health check procedures to be performed by administrators of the SPS system.The procedures consist of checking the following:⏹Free Disk Space ⏹CPU Usage ⏹Memory Usage and Handles Count ⏹SPS Log Files ⏹CDR Files ⏹Windows Events Logs ⏹Virtual Machine Logs and Events ⏹Antivirus Software ⏹System Backup ⏹SPS License Check ⏹Database Synchronization Status ⏹ SPS DiagnosticsPreventative Maintenance & Health-Check ProceduresReader's NotesConfiguration Note 8 Document #: LTRT-31330Configuration Note 2. Free Disk Space Version 1.0 9 May 20132Free Disk Space The following procedure checks the hard drive to ensure there is sufficient disk space. 2.1 Procedure1.Open the SPS Web interface; the MobilityPLUS For Microsoft® Lync™ Server Home Page appears. 2. Under the System Status group, check C free disk space .2.2Expected Results You should expect a minimum free disk space of 10 GB.Preventative Maintenance & Health-Check ProceduresReader's NotesConfiguration Note 10 Document #: LTRT-31330Configuration Note 3. CPU Usage 3 CPU UsageThe following procedure checks the system CPU usage during both idle time and busyhour.3.1 Procedure1. Open the SPS Web interface.2. Open the System Status page (Status & Diagnostics> System Status> SystemStatus).3. Check the CPU usage in the 'CPU' column for the following services:•SPS Core•SPS Switch•SPS Manager•TFTP Server•FTP Server3.2 Expected Results⏹In idle mode, expect a CPU usage of less than 5%.⏹Make sure that during busy hour, the system CPU does not exceed 80%.⏹Check the total server CPU load. Make sure other services installed on the sameoperating system are not performing high CPU loads.Note: Other services may influence system stability and service reliability.Reader's NotesConfiguration Note 4. Memory Usage and Handles Count 4 Memory Usage and Handles CountThe following procedure checks memory usage and handles count.4.1 Procedure1. Open the SPS Web interface.2. Open the System Status page (Status & Diagnostics> System Status> SystemStatus).3. Check the memory usage in the'Private Memory/Working Set' column for thefollowing services:•SPS Core•SPS Switch•SPS Manager•TFTP Server•FTP Server4. Check the 'Handles' column for the following services:•SPS Core•SPS Switch•SPS Manager•TFTP Server•FTP Server4.2 Expected Results⏹The maximum memory usage depends on the number of simultaneous calls.⏹Compare the memory usage in idle state with the memory usage during busy hour, inorder to verify that the memory usage in idle state returns to its normal value.⏹In idle state, you should expect the following usage values:•SPS Core should be less than 2000•SPS Switch should be less than 2000•SPS Manager should be less than 500⏹In normal state, the number of handles depends on the number of calls but should notexceed the following values:•SPS Core should be less than 5000•SPS Switch should be less than 30000•SPS Manager should be less than 1000⏹Check the total server memory and 'Handles' usage. Make sure other servicesinstalled on the same operating system are not using high memory/handles usage,Note: Other services may influence system stability and service reliability.Reader's NotesConfiguration Note 5. SPS Log Files 5 SPS Log FilesThe following procedure checks the size of the log files and verifies if there are anyerrors/warnings in the log files.5.1 Procedure1. Open the SPS Web interface.2. Open the Application Logs page (Status & Diagnostics> Logs & Alarms>Application Logs).3. Click the button on the right side of the appropriate application, to see the contents ofthe log file; the Application Logs Activity page appears.4. From the 'activity_log CSV'drop-down list, select Show last 100 log lines.5. Inspect the log file and check for errors and warnings.5.2 Expected Results⏹Make sure there are no special errors or exceptions.⏹If there are errors or exceptions, the system tries to provide additional informationabout the problem cause.⏹If a recurring error or exception occurs, contact your Customer Support.⏹The system automatically deletes old log files from the system.⏹Periodically monitor the system log file size and verify that the log files are not largerthan 100 MB.Reader's NotesConfiguration Note 6. CDR Files 6 CDR FilesThe following procedure checks the CDR files.6.1 Procedure1. Open the SPS Web interface.2. Open the SPS CDR Files page (Status & Diagnostics > CDR > SPS CDR Files).3. Click Download to display the CDR file.4. Check the CDR records that appear in the spreadsheet.6.2 Expected Results⏹The CDR records should match the actual calls made (Call Duration, Time of Day).⏹Make sure the CDR folder includes no more than 30 records.⏹The system automatically deletes old CDR files from the system.Reader's NotesConfiguration Note 7. Windows Events Logs 7 Windows Events LogsThe following procedure checks the Windows events logs and searches for critical issues.7.1 Procedure1. Connect to the SPS server using Remote Desktop.2. Start the Windows Event Viewer.3. Click Windows Logs > Application.4. Check the level of events for the SPS task under the 'Source' column. Check forerrors, warnings etc.5. Click on Windows Logs > System.6. Check for exceptions.7. Click Applications & Service Logs > Lync.8. Check the level of events for the SPS task under the 'Source' column. Check forerrors, warnings etc.7.2 Expected Results⏹No errors and exceptions during normal operation.⏹If recurring errors or warnings events appear, contact your Customer Support.⏹Check the Event Viewer for warnings or errors of other services installed on the sameoperating system.⏹Other services may influence system stability and service reliability.Reader's NotesConfiguration Note 8. Virtual Machine Logs and Events 8 Virtual Machine Logs and EventsThe following procedure checks the Virtual Machine (VM) logs and events.8.1 ProcedureUse your virtualization software to check virtual machine logs and events. Use one of thefollowing:⏹Microsoft Hyper-V Server⏹VMware8.1.1 Microsoft Hyper-V ServerMicrosoft Hyper-V Server logs useful information to diagnose a problem. All Hyper-V eventlogs are stored in the Event Viewer under 'Applications and Services Logs', 'Microsoft','Windows'.There are then 10 categories of Hyper-V events to look at. First check the Hyper-V-VMMScategory.8.1.2 VMwareIf you are using a VM other than HyperV, such as VMware, monitor the VM according tothe VM tools. You should have these tools at the data center.8.2 Expected Results⏹There should be no errors or exceptions during normal operation.⏹If there are recurring errors or warnings events, contact your Customer Support.Reader's NotesConfiguration Note 9. Antivirus Software 9 Antivirus SoftwareThe following procedure checks that the antivirus program is up to date and doesn’t blockthe SPS operation.9.1 Procedure1. Make sure your antivirus program is up-to-date with the latest updates.2. Make sure that if the antivirus program is setup to perform a massive scan on allcomputer folders, it is scheduled for non-working hours or when the system is idle.3. Verify that the antivirus program installed on the system does not block access to SPSfiles or main folders.4. Make sure the antivirus program does not affect the SPS process or slow theperformance of the server.9.2 Expected ResultsThe antivirus program should consume minimum of CPU resources.Reader's NotesConfiguration Note 10. System Backup 10 System BackupThe following procedure describes how to perform the system backup. The backup copy isuseful if the system needs to be restored due to a hardware malfunction or as a result of asystem settings restore.10.1 Procedure1. Perform the system backup according to the procedure detailed in the SPS BackupRestore Configuration Note Ver.1.0 document.2. Perform the backup operation once week if constant changes are made to the system.3. The backup file should be stored in a safe external storage.4. Save several historical backup copies (e.g. last 4 backups).5. If the SPS is installed on a VM, perform a full backup of the VM system.6. Schedule the backup operation during non-working hours or when the system is in idlemode.7. If a change is made to the system configuration, perform the backup operation beforestarting the new change.10.2 Expected ResultsNAReader's NotesConfiguration Note 11. SPS License 11 SPS LicenseThe following procedure checks that the system license is still active. Besides other licenseinformation, it displays the Expiration Date and how many days are left before expiration. 11.1 Procedure1. Open the SPS Web interface.2. Open the License Information page (Configuration> License> LicenseInformation).3. Under the 'License Information' group check the following:•Expiration Date•Days Left4. Under the 'Users Information' group, check the following:•Maximum users•Current registered users11.2 Expected Results⏹If the system is already utilizing 90% of its license, purchase an additional license inorder to be able to extend system capacity when needed.⏹If the system is running in 'Evaluation Mode' with an expiration date, make sure youpurchase a permanent license. The system stops operating when the license expires.Reader's NotesConfiguration Note 12. Database Synchronization Status 12 Database Synchronization StatusThe following procedure checks the database synchronization status.12.1 Procedure1. Open the SPS Web interface.2. Open the Database Synchronization page (Status & Diagnostics> Database>Database Synchronization).3. From the For last synchronization time on server drop-down list, select theappropriate server.4. Click here.12.2 Expected ResultsVerify that each synchronization is done at intervals, less than ten minutes.Reader's NotesConfiguration Note 13. SPS Diagnostics 13 SPS DiagnosticsThe following procedure describes the SPS diagnostics tests to be performed.13.1 Procedure1. Open the SPS Web interface.2. Open the SPS Diagnosis page (Status & Diagnostics > System Diagnostic > SPS).3. Click Show Application Endpoint State to verify the Application Endpoint State.4. Click Certificate Expiration Date to verify the Certificate Expiration Date.13.2 Expected Results⏹For the application endpoint state, the following message is displayed: ApplicationEndpoint is ready; its state is ‘Established’.⏹For the certificate expiration date, verify that there are enough days left to renew thecertificate.Version 1.0 31 May 2013Configuration Note。

NXP SCM-i.MX 6 Series Yocto Linux 用户指南说明书

© 2017 NXP B.V.SCM-i.MX 6 Series Yocto Linux User'sGuide1. IntroductionThe NXP SCM Linux BSP (Board Support Package) leverages the existing i.MX 6 Linux BSP release L4.1.15-2.0.0. The i.MX Linux BSP is a collection of binary files, source code, and support files that can be used to create a U-Boot bootloader, a Linux kernel image, and a root file system. The Yocto Project is the framework of choice to build the images described in this document, although other methods can be also used.The purpose of this document is to explain how to build an image and install the Linux BSP using the Yocto Project build environment on the SCM-i.MX 6Dual/Quad Quick Start (QWKS) board and the SCM-i.MX 6SoloX Evaluation Board (EVB). This release supports these SCM-i.MX 6 Series boards:• Quick Start Board for SCM-i.MX 6Dual/6Quad (QWKS-SCMIMX6DQ)• Evaluation Board for SCM-i.MX 6SoloX (EVB-SCMIMX6SX)NXP Semiconductors Document Number: SCMIMX6LRNUGUser's GuideRev. L4.1.15-2.0.0-ga , 04/2017Contents1. Introduction........................................................................ 1 1.1. Supporting documents ............................................ 22. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX .. 2 2.1. Host setup ............................................................... 2 2.2. Host packages ......................................................... 23.Building Linux OS for SCM i.MX platforms .................... 3 3.1. Setting up the Repo utility ...................................... 3 3.2. Installing Yocto Project layers ................................ 3 3.3. Building the Yocto image ....................................... 4 3.4. Choosing a graphical back end ............................... 4 4. Deploying the image .......................................................... 5 4.1. Flashing the SD card image .................................... 5 4.2. MFGTool (Manufacturing Tool) ............................ 6 5. Specifying displays ............................................................ 6 6. Reset and boot switch configuration .................................. 7 6.1. Boot switch settings for QWKS SCM-i.MX 6D/Q . 7 6.2. Boot switch settings for EVB SCM-i.MX 6SoloX . 8 7. SCM uboot and kernel repos .............................................. 8 8. References.......................................................................... 8 9.Revision history (9)Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloX1.1. Supporting documentsThese documents provide additional information and can be found at the NXP webpage (L4.1.15-2.0.0_LINUX_DOCS):•i.MX Linux® Release Notes—Provides the release information.•i.MX Linux® User's Guide—Contains the information on installing the U-Boot and Linux OS and using the i.MX-specific features.•i.MX Yocto Project User's Guide—Contains the instructions for setting up and building the Linux OS in the Yocto Project.•i.MX Linux®Reference Manual—Contains the information about the Linux drivers for i.MX.•i.MX BSP Porting Guide—Contains the instructions to port the BSP to a new board.These quick start guides contain basic information about the board and its setup:•QWKS board for SCM-i.MX 6D/Q Quick Start Guide•Evaluation board for SCM-i.MX 6SoloX Quick Start Guide2. Enabling Linux OS for SCM-i.MX 6Dual/6Quad/SoloXThis section describes how to obtain the SCM-related build environment for Yocto. This assumes that you are familiar with the standard i.MX Yocto Linux OS BSP environment and build process. If you are not familiar with this process, see the NXP Yocto Project User’s Guide (available at L4.1.15-2.0.0_LINUX_DOCS).2.1. Host setupTo get the Yocto Project expected behavior on a Linux OS host machine, install the packages and utilities described below. The hard disk space required on the host machine is an important consideration. For example, when building on a machine running Ubuntu, the minimum hard disk space required is about 50 GB for the X11 backend. It is recommended that at least 120 GB is provided, which is enough to compile any backend.The minimum recommended Ubuntu version is 14.04, but the builds for dizzy work on 12.04 (or later). Earlier versions may cause the Yocto Project build setup to fail, because it requires python versions only available on Ubuntu 12.04 (or later). See the Yocto Project reference manual for more information.2.2. Host packagesThe Yocto Project build requires that the packages documented under the Yocto Project are installed for the build. Visit the Yocto Project Quick Start at /docs/current/yocto-project-qs/yocto-project-qs.html and check for the packages that must be installed on your build machine.The essential Yocto Project host packages are:$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-devThe i.MX layers’ host packages for the Ubuntu 12.04 (or 14.04) host setup are:$ sudo apt-get install libsdl1.2-dev xterm sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidocThe i.MX layers’ host packages for the Ubuntu 12.04 host setup are:$ sudo apt-get install uboot-mkimageThe i.MX layers’ host packages for the Ubuntu 14.04 host s etup are:$ sudo apt-get install u-boot-toolsThe configuration tool uses the default version of grep that is on your build machine. If there is a different version of grep in your path, it may cause the builds to fail. One workaround is to rename the special versi on to something not containing “grep”.3. Building Linux OS for SCM i.MX platforms3.1. Setting up the Repo utilityRepo is a tool built on top of GIT, which makes it easier to manage projects that contain multiple repositories that do not have to be on the same server. Repo complements the layered nature of the Yocto Project very well, making it easier for customers to add their own layers to the BSP.To install the Repo utility, perform these steps:1.Create a bin folder in the home directory.$ mkdir ~/bin (this step may not be needed if the bin folder already exists)$ curl /git-repo-downloads/repo > ~/bin/repo$ chmod a+x ~/bin/repo2.Add this line to the .bashrc file to ensure that the ~/bin folder is in your PATH variable:$ export PATH=~/bin:$PATH3.2. Installing Yocto Project layersAll the SCM-related changes are collected in the new meta-nxp-imx-scm layer, which is obtained through the Repo sync pointing to the corresponding scm-imx branch.Make sure that GIT is set up properly with these commands:$ git config --global "Your Name"$ git config --global user.email "Your Email"$ git config --listThe NXP Yocto Project BSP Release directory contains the sources directory, which contains the recipes used to build, one (or more) build directories, and a set of scripts used to set up the environment. The recipes used to build the project come from both the community and NXP. The Yocto Project layers are downloaded to the sources directory. This sets up the recipes that are used to build the project. The following code snippets show how to set up the SCM L4.1.15-2.0.0_ga Yocto environment for the SCM-i.MX 6 QWKS board and the evaluation board. In this example, a directory called fsl-arm-yocto-bsp is created for the project. Any name can be used instead of this.Building Linux OS for SCM i.MX platforms3.2.1. SCM-i.MX 6D/Q quick start board$ mkdir fsl-arm-yocto-bsp$ cd fsl-arm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.2.2. SCM-i.MX 6SoloX evaluation board$ mkdir my-evb_6sxscm-yocto-bsp$ cd my-evb_6sxscm-yocto-bsp$ repo init -u git:///imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m scm-imx-4.1.15-2.0.0.xml$ repo sync3.3. Building the Yocto imageNote that the quick start board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX are commercially available with a 1 GB LPDDR2 PoP memory configuration.This release supports the imx6dqscm-1gb-qwks, imx6dqscm-1gb-qwks-rev3, and imx6sxscm-1gb-evb. Set the machine configuration in MACHINE= in the following section.3.3.1. Choosing a machineChoose the machine configuration that matches your reference board.•imx6dqscm-1gb-qwks (QWKS board for SCM-i.MX 6DQ with 1 GB LPDDR2 PoP)•imx6dqscm-1gb-qwks-rev3 (QWKS board Rev C for SCM-i.MX 6DQ with 1GB LPDDR2 PoP) •imx6sxscm-1gb-evb (EVB for SCM-i.MX 6SX with 1 GB LPDDR2 PoP)3.4. Choosing a graphical back endBefore the setup, choose a graphical back end. The default is X11.Choose one of these graphical back ends:•X11•Wayland: using the Weston compositor•XWayland•FrameBufferSpecify the machine configuration for each graphical back end.The following are examples of building the Yocto image for each back end using the QWKS board for SCM-i.MX 6D/Q and the evaluation board for SCM-i.MX 6SoloX. Do not forget to replace the machine configuration with what matches your reference board.3.4.1. X11 image on QWKS board Rev C for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-x11 imx6dqscm-1gb-qwks-rev3 source fsl-setup-release.sh -b build-x11$ bitbake fsl-image-gui3.4.2. FrameBuffer image on evaluation board for SCM-i.MX 6SX$ DISTRO=fsl-imx-fb MACHINE=imx6sxscm-1gb-evb source fsl-setup-release.sh –b build-fb-evb_6sxscm$ bitbake fsl-image-qt53.4.3. XWayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-xwayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh –b build-xwayland$ bitbake fsl-image-gui3.4.4. Wayland image on QWKS board for SCM-i.MX 6D/Q$ DISTRO=fsl-imx-wayland MACHINE=imx6dqscm-1gb-qwks source fsl-setup-release.sh -b build-wayland$ bitbake fsl-image-qt5The fsl-setup-release script installs the meta-fsl-bsp-release layer and configures theDISTRO_FEATURES required to choose the graphical back end. The –b parameter specifies the build directory target. In this build directory, the conf directory that contains the local.conf file is created from the setup where the MACHINE and DISTRO_FEATURES are set. The meta-fslbsp-release layer is added into the bblayer.conf file in the conf directory under the build directory specified by the –e parameter.4. Deploying the imageAfter the build is complete, the created image resides in the <build directory>/tmp/deploy/images directory. The image is (for the most part) specific to the machine set in the environment setup. Each image build creates the U-Boot, kernel, and image type based on the IMAGE_FSTYPES defined in the machine configuration file. Most machine configurations provide the SD card image (.sdcard), ext4, and tar.bz2. The ext4 is the root file system only. The .sdcard image contains the U-Boot, kernel, and rootfs, completely set up for use on an SD card.4.1. Flashing the SD card imageThe SD card image provides the full system to boot with the U-Boot and kernel. To flash the SD card image, run this command:$ sudo dd if=<image name>.sdcard of=/dev/sd<partition> bs=1M && syncFor more information about flashing, see “P reparing an SD/MMC Card to Boot” in the i.MX Linux User's Guide (document IMXLUG).Specifying displays4.2. MFGTool (Manufacturing Tool)MFGTool is one of the ways to place the image on a device. To download the manufacturing tool for the SCM-i.MX 6D/Q and for details on how to use it, download the SCM-i.MX 6 Manufacturing Toolkit for Linux 4.1.15-2.0.0 under the "Downloads" tab from /qwks-scm-imx6dq. Similarly, download the manufacturing tool for the SCM-i.MX 6SoloX evaluation board under the "Downloads" tab from /evb-scm-imx6sx.5. Specifying displaysSpecify the display information on the Linux OS boot command line. It is not dependent on the source of the Linux OS image. If nothing is specified for the display, the settings in the device tree are used. Find the specific parameters in the i.MX 6 Release Notes L4.1.15-2.0.0 (available at L4.1.15-2.0.0_LINUX_DOCS). The examples are shown in the following subsections. Interrupt the auto-boot and enter the following commands.5.1.1. Display options for QWKS board for SCM-i.MX 6D/QHDMI displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'U-Boot > run bootcmd5.1.2. Display options for EVB for SCM-i.MX 6SXNote that the SCM-i.MX 6SX EVB supports HDMI with a HDMI accessory card (MCIMXHDMICARD) that plugs into the LCD connector on the EVB.Accessory boards:•The LVDS connector pairs with the NXP MCIMX-LVDS1 LCD display board.•The LCD expansion connector (parallel, 24-bit) pairs with the NXP MCIMXHDMICARD adapter board.LVDS displayU-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} ${dmfc} video=mxcfb0:dev=ldb,1024x768M@60,if=RGB666 ldb=sep0'U-Boot > run bootcmdHDMI display (dual display for the HDMI as primary and the LVDS as secondary)U-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24video=mxcfb1:dev=ldb,LDBXGA,if=RGB666'U-Boot > run bootcmdLCD displayu-boot > setenv mmcargs 'setenv bootargs ${bootargs}root=${mmcroot} rootwait rw video=mxcfb0:dev=lcd,if=RGB565'u-boot> run bootcmd6. Reset and boot switch configuration6.1. Boot switch settings for QWKS SCM-i.MX 6D/QThere are two push-button switches on the QWKS-SCMIMX6DQ board. SW1 (SW3 for QWKS board Rev B) is the system reset that resets the PMIC. SW2 is the i.MX 6Dual/6Quad on/off button that is needed for Android.There are three boot options. The board can boot either from the internal SPI-NOR flash inside the SCM-i.MX6Dual/6Quad or from either of the two SD card slots. The following table shows the switch settings for the boot options.Table 1.Boot configuration switch settingsBoot from top SD slot (SD3)Boot from bottom SD slot (SD2)Boot from internal SPI NORDefault1.References6.2. Boot switch settings for EVB SCM-i.MX 6SoloXThis table shows the jumper configuration to boot the evaluation board from the SD card slot SD3.7. SCM uboot and kernel repositoriesThe kernel and uboot patches for both SCM-i.MX 6 QWKS board and evaluation board are integrated in specific git repositories. Below are the git repos for SCM-i.MX 6 uboot and kernel:uBoot repo: /git/cgit.cgi/imx/uboot-imx.gitSCM Branch: scm-imx_v2016.03_4.1.15_2.0.0_gakernel repo: /git/cgit.cgi/imx/linux-imx.gitSCM branch: scm-imx_4.1.15_2.0.0_ga8. References1.For details about setting up the Host and Yocto Project, see the NXP Yocto Project User’s Guide(document IMXLXYOCTOUG).2.For information about downloading images using U-Boot, see “Downloading images usingU-Boot” in the i.MX Linux User's Guide (document IMXLUG).3.For information about setting up the SD/MMC card, see “P reparing an SD/MMC card to boot” inthe i.MX Linux User's Guide (document IMXLUG).9. Revision historyDocument Number: SCMIMX6LRNUGRev. L4.1.15-2.0.0-ga04/2017How to Reach Us: Home Page: Web Support: /supportInformation in this document is provided solely to enable system and softwareimplementers to use NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein.NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequentia l or incidental damages. “Typical”parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including “typicals,” must be valida ted for each customer application by customer’s technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: /SalesTermsandConditions .NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, Freescale, and the Freescale logo are trademarks of NXP B.V. All other product or service names are the property of their respective owners.ARM, the ARM Powered logo, and Cortex are registered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved. © 2017 NXP B.V.。

opensips 安装及基本配置

opensips 安装及基本配置.txt人生在世，难敌宿命，沉沦其中。

我不爱风尘，似被前缘误！！我只为我最爱的人流泪“我会学着放弃你，是因为我太爱你”赢了你,我可以放弃整个世界opensips 安装及基本配置1 . 官方网站 / 的 download 中下载 opensips 软件包2 . 编译：Java代码1. tar zxvf opensips-1.6.2-tls_src.tar.gz2. cd opensips-1.6.2-tlstar zxvf opensips-1.6.2-tls_src.tar.gzcd opensips-1.6.2-tls3 . 安装之前更改 makefile ：删除 Makefile 中的 exclude_modules 的 db-mysql,使opensips使用mysql数据4. 安装make all可能会缺少一下工具，缺少什么装什么就是了。

另外可能提示找不到mysql.h等文件，只要把文件拷贝到对应的地方就行了。

make install默认安装路径 /usr/local 下5. 配置 vim /usr/local/etc/opensips/opensipsctlrc，把 mysql 的相关的注释去掉Java代码1. ## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, or DBTEXT, by default noneis loaded2. # If you want to setup a database with opensipsdbctl, you must at least specify3. # this parameter.4. DBENGINE=MYSQL5. ## database host6. DBHOST=localhost7. ## database name (for ORACLE this is TNS name)8. DBNAME=opensips9. # database path used by dbtext or db_berkeley10. DB_PATH="/usr/local/etc/opensips/dbtext"11. ## database read/write user12. DBRWUSER=opensips13. ## password for database read/write user14. DBRWPW="opensipsrw"15. ## database read only user16. DBROUSER=opensipsro17. ## password for database read only user18. DBROPW=opensipsro19. ## database super user (for ORACLE this is 'scheme-creator' user)20. DBROOTUSER="root"21. # user name column22. USERCOL="username"## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, or DBTEXT, by default none is loaded# If you want to setup a database with opensipsdbctl, you must at least specify # this parameter.DBENGINE=MYSQL## database hostDBHOST=localhost## database name (for ORACLE this is TNS name)DBNAME=opensips# database path used by dbtext or db_berkeleyDB_PATH="/usr/local/etc/opensips/dbtext"## database read/write userDBRWUSER=opensips## password for database read/write userDBRWPW="opensipsrw"## database read only userDBROUSER=opensipsro## password for database read only userDBROPW=opensipsro## database super user (for ORACLE this is 'scheme-creator' user)DBROOTUSER="root"# user name columnUSERCOL="username"6. 执行 opensips/sbin/ 下的 opensipsdbctlJava代码1. ./opensipsdbctl create ( 生成 opensips 数据库 )./opensipsdbctl create ( 生成 opensips 数据库 )7. 这个时候如果重新登录phpmyadmin，会看到已经新建了opensips数据库8. opensips的运行Java代码1. /usr/local/sbin/下的opensipsctl start来启动opensips2. ps aux | grep opensips 检查应该已经运行了。

Participant用户指南

第版8.5Participant 用户指南法律声明♦本文档中的内容如有更改，恕不另行通知；这些内容亦不构成 AT&T Inc.之承诺。

♦本文档所叙述的软件与/或数据库按照许可协议或保密协议提供。

软件与/或数据库只允许按照协议进行使用或复制。

购买者可出于备份目的制作一份本软件的副本。

♦AT&T Connect Participant 应用程序整合了获得 DSP Algorithms 公司 () 许可的回声消除技术。

♦未经 AT&T Inc. 明确书面同意，不得出于购买者个人使用之外的任何目的，以任何形式或通过任何电子或机械手段（包括影印、录制或信息存储与检索系统）复制或传输本“用户指南”的任何部分。

♦除非另有说明，本文所含的所有公司、产品、街道地址以及人员的名称均纯属虚构，其用途仅限于介绍 AT&T Connect 产品的用法。

♦Windows 是 Microsoft Corporation 的商标。

所有其它商标属于各自的拥有者。

目录第 1 章 (8)AT&T Connect Participant 应用程序简介 (8)会议中的主持人和与会人角色 (8)AT&T Connect 与 AT&T TeleConference Service 中的角色 (9)第 2 章 (10)安装AT&T Connect Participant 应用程序 (10)系统要求 (10)从 Web 进行 Participant 安装 (11)从光盘安装 (11)第 3 章 (12)开始使用AT&T Connect Participant 应用程序 (12)Participant 窗口 (12)状态面板 (13)开始页面 (14)第 508 部分符合性 (14)使用辅助菜单 (15)第 4 章 (18)召开 Web 会议 (18)邀请他人加入 Web 会议 (19)加入会议 (20)将 AT&T TeleConference Service 用于 Web 会议音频 (25)使用“呼我” (27)断开与重新连接事件 (28)第 5 章 (30)使用与会人工具 (30)使用表情 (30)使用便条 (31)发送便条 (32)回复/转发便条 (34)删除便条 (34)保存便条 (34)定义便条设置 (35)暂时离开事件 (36)扩展 Participant 窗口 (37)将音频静音/取消静音 (37)使用白板 (38)清除白板 (39)在显示器上指点 (39)在白板上书写 (40)在白板上绘制线条与形状 (40)在白板上绘制对号 (41)保存白板内容 (41)插入文件 (41)使用电子邮件邀请其他与会人 (43)响应问题与调查 (43)查看响应统计数据 (45)第 6 章 (46)演示人工具 (46)演示人权限 (46)传递演示人权限 (48)通过电话与拨出邀请 (48)链接与会人数据和音频流 (49)重命名与会人 (50)使用举手列表 (50)清除与会人 (51)启用广播模式 (52)查看事件材料的加载状态 (52)将文件加载到白板 (53)查看文件属性 (53)重新发送文件 (54)删除文件 (54)查看文件状态 (55)文件类型 (55)插入 PowerPoint 文件 (56)将插入的文件设置为在白板外部打开 (58)事件设置 (59)第 7 章 (60)高级演示人选项 (60)Web 会议中的应用程序共享 (60)与 Web 会议与会人共享应用程序 (60)使用“应用程序共享导航栏” (62)以“远程指导”方式共享应用程序 (65)定义应用程序共享设置 (65)定义输出带宽控制 (65)定义图像质量 (67)定义快捷键 (68)显示应用程序共享导航栏 (68)将 Participant 窗口定义成在“放大”模式中打开 (68)发起调查 (69)共享响应统计数据 (73)执行 Web 浏览 (73)第 8 章 (76)高级 Participant 应用程序选项 (76)概述 (76)定义用户界面语言 (77)定义连接协议/代理设置 (78)定义服务器设置 (79)第 9 章 (80)图标与状态消息 (80)工具栏图标 (80)状态消息 (80)与会人列表图标 (81)第 10 章 (84)Log Submission 实用程序 (LSU) (84)LSU 激活 (84)自动激活 (84)手工激活 (84)使用 LSU (85)发送报告 (85)发送操作失败时 (87)查看收集的数据（可选） (88)第 1 章 AT&T Connect Participant 应用程序简介AT&T Connect 借助可视化演示与互动方面的基于 PC 的工具，扩展了AT&T TeleConference Service (ATCS) 的语音会议功能。

opensips安装及配置

一、opensips安装1.更新系统yum –y updateyum install gcc makeyum install flex bison ncurses libncurses-dev ncurses-devel yum install mysql mysql-server mysql-libs mysql-devel2.将安装包放入/var/local目录下面3.tar –zxvf opensips-1.9.1_src.tar.gz4.cd opensips-1.9.1-tls5. make menuconfig如图：往下执行选择mysql数据库模块制定安装目录 /usr/local/opensips_proxy/如上图：红色部分为指针选择，蓝色部分为指定程序安装目录提示：程序安装目录最好指定到公共文件目录中，据测试放到用户目录中，启动会出问题，个人出现过BUG，故作此提示配置完成之后需要对配置进行保存，如下图最后在主菜单里选"Compile And Install Opensips"安装时界面如下：出现上图内容部分表示安装已经成功完成，配置完成之后需要对配置进行保存，。

二、opensips-cp安装1. yum install httpd php php-mysql php-xmlrpc php-pearpear install MDB2pear install MDB2#mysqlpear install MDB2#mysqlipear install log2. 将opensips-cp_5.0.tgz上传opensip-cp到/var/www目录中tar zxvf opensips-cp_5.0.tgzmv 5.0 opensips-cp3.检查M4是否安装yum install m4三、stop-daemon安装将apps-sys-utils-start-stop-daemon-IR1_9_18-2.tar.gz安装包放入/var/local目录下面，并执行下列命令yum install gcc gcc-c++ m4 make automake libtool gettext openssl-develtar xvfz apps-sys-utils-start-stop-daemon-IR1_9_18-2.tar.gzmv apps/sys-utils/start-stop-daemon-IR1_9_18-2/ ./rm -rf appscd start-stop-daemon-IR1_9_18-2/gcc start-stop-daemon.c -o start-stop-daemoncp start-stop-daemon /usr/sbin/四、opensips配置1.进入sbin目录，并配置cd /usr/local/opensips_proxy/sbin/./osipsconfig进入Generate OpenSIPS Script-> Residential script->Configure Residential Script最后选择Generate Residential Script，保存之后再退出。

OpenSIPS用户状态定阅发布配置说明

OpenSIPS用户状态定阅发布配置说明一、简介用户可通过SIP客户端发布自己当前的使用状态（在线、繁忙、离线等），其它SIP客户端可定阅通讯录中的成员状态，从而可以达到获取客户端中某些用户当前的客户端使用状态。

此功能除了需要SIP客户端的支持，还需要OpensSIPS服务中presence模块和xcap模块的支持，详细配置说明如下：二、配置若当前OpenSIPS服务器不支持presence模块和xcap模块，需要对OpenSIPS服务进行重新编译。

进入OpenSIPS源码目录输入make menuconfig进入编译配置界面：1.进入Configure Compile Options->Configure Excluded Modules, 勾选presence、presence_dialoginfo、presence_mwi、presence_xml、xcap、xcap_client返回并保存，如下图：2.进入Compile And Install OpenSIPS，此时开始编译和安装，结束后会返回到菜单界面。

3.进入Exit & Save All Changes 退出，安装完毕。

在shell终端中输入osipsconfig进入OpenSIPS脚本文件配置界面，并选择Generate OpenSIPS Script -> Residential Script -> Configure Residential Script，勾选USE_PRESENCE，如下图：然后返回选择Generate Residential Script，则会保存文件到/usr/etc/opensips/opensips_residential_xxxx-xx-xx_xx:xx:xx.cfg，回到/usr/etc/opensips目录下，将原来的opensips.cfg文件重命名，将新创建的cfg文件保存为opensips.cfg文件，然后vi 打开opensips.cfg文件，编辑：1.找到#### PRESENCE modules部分，在下面添加：loadmodule "presence_mwi.so"loadmodule "presence_xcapdiff.so"2.替换modparam("presence", "server_address", "sip:xxx.xxx.xxx.xxx:5060") # CUSTOMIZE ME为服务器IP地址。

exosip osip 交叉编译

exosip和osip是两种常用于SIP（会话初始协议）协议栈实现的开源软件库，它们可以帮助开发人员在其应用程序中实现基于SIP协议的通信功能。

在某些情况下，由于开发环境的限制，我们可能需要进行交叉编译来将这些库移植到不同的评台上，本文将重点介绍如何使用交叉编译工具来将exosip和osip库移植到目标评台上。

1. 了解交叉编译的基本概念在开始介绍如何进行exosip和osip库的交叉编译之前，我们首先需要了解一些基本的概念。

交叉编译是指在一种评台上开发、编译出在另一种不同的评台上运行的应用程序的过程。

在实际应用中，我们可能需要在PC机上编译出在嵌入式评台上运行的程序，这就需要用到交叉编译工具链。

2. 准备交叉编译工具链在进行交叉编译之前，我们需要先准备好交叉编译工具链。

交叉编译工具链包括交叉编译器、交叉连接器、交叉汇编器等，它们用于将源代码编译成目标评台上可执行的程序。

可以从官方全球信息湾或者第三方渠道下载已经编译好的交叉编译工具链，也可以自行编译搭建交叉编译环境。

3. 配置编译环境在准备好交叉编译工具链之后，我们需要配置编译环境，以便将exosip和osip库移植到目标评台上。

配置编译环境包括设置交叉编译器的路径、指定目标评台的系统类型、设置编译选项等。

具体的配置步骤和方法可以参考官方文档或者相关的教程。

4. 下载源代码在配置好编译环境之后，我们需要下载exosip和osip库的源代码，这些源代码通常是以压缩包的形式发布在官方全球信息湾上，也可以从版本控制系统如Git、SVN等获取最新的源代码。

下载源代码后，我们需要解压缩并进行一些基本的配置。

5. 编译和安装在下载和配置完源代码之后，我们可以使用交叉编译工具链来编译和安装exosip和osip库。

编译和安装过程通常包括配置编译选项、执行编译命令、进行单元测试、安装到目标系统等步骤。

在编译和安装过程中可能会遇到一些依赖库缺失、编译错误等问题，这就需要我们根据具体情况进行调试和解决。

exosip2学习总结

exosip2协议栈学习总结1、exosip2协议栈介绍eXosip是Osip2的一个扩展协议集，它部分封装了Osip2协议栈，使得它更容易被使用。

使用 sip 协议建立多媒体会话是一个复杂的过程，exosip 库开发的目的在于隐藏这种复杂性。

正如它的名称所表示的，eXosip2 - the eXtended osip Library，它扩展了osip 库，实现了一个简单的高层API。

通过使用exosip，我们可以避免直接使用osip 带来的困难。

需要注意，exosip 并不是对osip 的简单封装包裹，而是扩展。

Osip 专注于sip 消息的解析，事务状态机的实现，而exosip 则基于osip 实现了call、options、register、publish 等更倾向于功能性的接口。

当然，这些实现都是依赖于底层osip 库已有的功能的。

2、exosip的模块构成2.1 底层连接管理extl.c、extl_udp.c、extl_tcp.c、extl_dtls.c、extl_tls.c 是与网络连接有关的文件。

实现了连接的建立，数据的接收以及发送等相关的接口。

其中，extl_udp.c 为使用UDP 连接的实现，extl_tcp.c 为使用TCP 连接的实现。

Extl_dtls.c 以及extl_tls.c 都是使用安全socket 连接的实现。

2.2 内部功能模块实现Jauth.c、jcall.c、jdialog.c、jevents.c、jnotify.c、jpublish.c、jreg.c、jrequest.c、jresponse.c、jsubscribe.c 等文件实现了内部对一些模块的管理，这些模块正如其文件名所表示的，jauth.c主要是认证，jcall.c 则是通话等等。

2.3 上层API 封装实现Excall_api.c、exinsubsription_api.c、exmessag_api.c、exoptions_api.c、expublish_api.c、exrefer_api.c、exregister_api.c、exsubsribtion_api.c 这几个以api 为后缀的文件，实现各个子模块的管理。

exoSip开发手册

3 SIP messages and call control API ..........................................................................................21 3.1 eXosip2 INVITE and Call Management.....................................................................21 3.1.1 Functions .........................................................................................................21 3.1.2 Function Documentation .................................................................................22 3.2 eXosip2 request outside of dialog ...............................................................................29 3.2.1 Functions .........................................................................................................29 3.2.2 Function Documentation .................................................................................29 3.3 eXosip2 OPTIONS and UA capabilities Management ...............................................31 3.3.1 Functions .........................................................................................................31 3.3.2 Function Documentation .................................................................................31 3.4 eXosip2 Publication Management ..............................................................................33 3.4.1 Functions .........................................................................................................33 3.4.2 Function Documentation .................................................................................33 3.5 eXosip2 REFER and blind tranfer Management outside of calls................................35 3.5.1 Functions .........................................................................................................35 3.5.2 Function Documentation .................................................................................35 3.6 eXosip2 REGISTER and Registration Management ..................................................37 3.6.1 Functions .........................................................................................................37 3.6.2 Function Documentation .................................................................................37 3.7 eXosip2 SUBSCRIBE and outgoing subscriptions.....................................................39 3.7.1 Enumerations...................................................................................................39

XRA1403 1405评估板用户手册说明书

REV. 1.0.0 XRA1403/1405 EVALUATION BOARD USER’S MANUAL INTRODUCTIONThis user’s manual is for the XRA1403/1405 16-bit evaluation board. Table 1 shows the different devices and packages that the evaluation board supports. This user’s manual will describe the hardware setup required to operate the different packages.1.0QUICK STARTTo verify communication with the GPIO expander, the following steps are recommended:1.1Connect external +5V power supply to J8 pin 11.2Connect J12 pin 13 and 14 to ground of external power supply1.3Connect to MCU SPI interface for:SPI clock (SCK_SCL signal at J5 pin11)SO (SO_SPI signal at J5 pin17)SI (SI_SPI signal at J5 pin21)CS# (CS#_SPI signal at J5 pin19)1.4From the MCU, write the following registers:GCR1 = 0x00GCR2 = 0x00If the LEDs turn on, the communication with the GPIO expander is successful.To disable connection to LEDs, remove jumpers on J28, J29, J30 and J31. Connect to external inputs or outputs at J3 and J4.2.0HARDWARE SETUP2.1Packages descriptionThe evaluation board supports all 4 packages of the XRA1403 and XRA1405. The ordering part number, package and location on the board is shown below in Table 1. Table 2 lists the evaluation board ordering part numbers.T ABLE 1: P ACKAGE L ISTO RDERING P ART N UMBER P ACKAGE L OCATION XRA1403IL24-F 24-pin QFN U4XRA1403IG24-F 24-pin TSSOP U5XRA1405IL24-F 24-pin QFN U4XRA1405IG24-F 24-pin TSSOP U5T ABLE 2: E VALUATION B OARD O RDERING P ART N UMBERSP ART N UMBERXRA1403IL24-0B-EBXRA1403IG24-0B-EBXRA1405IL24-0B-EBXRA1405IG24-0B-EBXRA1403/1405 EVALUATION BOARD USER’S MANUAL REV. 1.0.0 2.2Jumper Settings2.2.1Common JumpersThe following jumpers apply to all the 4 packages of XRA1403 and XRA1405:T ABLE 3: C OMMON J UMPER S ETTINGSJ UMPERS F UNCTIONS C OMMENTSJ8Selects the supply voltage to generate the +1.8V power supply for the board 1&2 selects +5V (default, Pin 1 -- Test point for external +5V) 2&3 selects +PN OTE: Not installed. Trace between 1 & 2J9Selects the supply voltage to generate the +2.5V power supply for the board 1&2 selects +5V (default)2&3 selects +PN OTE: Not installed. Trace between 1 & 2J13Selects the supply voltage to generate the +3.3V power supply for the board 1&2 selects +5V (default)2&3 selects +PN OTE: Not installed. Trace between 1 & 2J10Selects the supply voltage for +VDDP Used only for the XRA1405Jumper in 1&2 selects +3.3VJumper in 3&4 selects +2.5VJumper in 5&6 selects +1.8VJ11Selects the supply voltage for +VDD Jumper in 1&2 selects +3.3V (default)Jumper in 3&4 selects +2.5VJumper in 5&6 selects +1.8VJ12Not used for XRA140x Installed but not usedJ14Not used for XRA140x Installed but not usedJ6Not used Installed but not usedJ27LEDs N OTE: Not installed. Pin 2 is connected to GND J3Header for testing GPIO[15:8] of bothTSSOP and QFN packageInstalled. Connect to external input/output.J4Header for testing GPIO[7:0] of both TSSOP and QFN package Installed. Connect to external input/output. Remove jumpers on J28, J29, J30 and J31 after test.J2Header for internal test Not installedJ5Header for XRA1403 and XRA1405 sig-nals and spare signalsInstalled. Connect SPI signals from this header to MCU.J7Header for UART signals and spare sig-nals Not installed. Some GPIO signals and spare signals are accessi-ble at this headerREV. 1.0.0 XRA1403/1405 EVALUATION BOARD USER’S MANUAL 2.2.2XRA1403IL24-FThe following jumpers apply to the XRA1403IL24-F:T ABLE 4: J UMPER S ETTINGS F OR XRA1403IL24-FJ UMPERS F UNCTIONS C OMMENTSJ28Header for connecting GPIO[7:0] signals of QFN package Jumper in pin 1 & J29 pin1 connects GPIO0 to LED Jumper in pin 2 & J29 pin 3 connects GPIO1 to LED Jumper in pin 3 & J29 pin 5 connects GPIO2 to LED Jumper in pin 4 & J29 pin 7 connects GPIO3 to LED Jumper in pin 5 & J29 pin 9 connects GPIO4 to LED Jumper in pin 6 & J29 pin 11 connects GPIO5 to LED Jumper in pin 7 & J29 pin 13 connects GPIO6 to LED Jumper in pin 8 & J29 pin 15 connects GPIO7 to LEDJ29Header for connecting GPIO[7:0] signals of TSSOP package to LEDs 1&2 connects GPIO0 to LED - 0 ohm resistor on board3&4 connects GPIO1 to LED - 0 ohm resistor on board5&6 connects GPIO2 to LED - 0 ohm resistor on board7&8 connects GPIO3 to LED - 0 ohm resistor on board9&10 connects GPIO4 to LED - 0 ohm resistor on board 11&12 connects GPIO5 to LED - 0 ohm resistor on board 13&14 connects GPIO6 to LED - 0 ohm resistor on board 15&16 connects GPIO7 to LED - 0 ohm resistor on boardJ30Header for connecting GPIO[15:8] signals of TSSOP package to LEDs 1&2 connects GPIO8 to LED - 0 ohm resistor on board3&4 connects GPIO9 to LED - 0 ohm resistor on board5&6 connects GPIO10 to LED - 0 ohm resistor on board7&8 connects GPIO11 to LED - 0 ohm resistor on board9&10 connects GPIO12 to LED - 0 ohm resistor on board 11&12 connects GPIO13 to LED - 0 ohm resistor on board 13&14 connects GPIO14 to LED - 0 ohm resistor on board 15&16 connects GPIO15 to LED - 0 ohm resistor on boardJ31Header for connecting GPIO[15:8] signals of QFN package Jumper in pin 1 & J30 pin 1 connects GPIO8 to LED Jumper in pin 2 & J30 pin 3 connects GPIO9 to LED Jumper in pin 3 & J30 pin 5 connects GPIO10 to LED Jumper in pin 4 & J30 pin 7 connects GPIO11 to LED Jumper in pin 5 & J30 pin 9 connects GPIO12 to LED Jumper in pin 6 & J30 pin 11 connects GPIO13 to LED Jumper in pin 7 & J30 pin 13 connects GPIO14 to LED Jumper in pin 8 & J30 pin 15 connects GPIO15 to LEDJ81Selects the supply voltage for +VDD for 24-pin QFN packages Jumper in 2&4 selects +VDD (default) Jumper in 1&3 selects +VDD Jumper in 3&5 selects +VDDJ82Selects the corresponding signal for pin18 of 24-pin QFN packageN OTE: Use J87 pin 2 & 3J83Selects the corresponding signal for pin23 of 24-pin QFN package Jumper in 2&4 selects SI signal (default) Jumper in 1&3 selects A1 signal Jumper in 3&5 selects A1 signalJ84Selects the corresponding signal for pin24 of 24-pin QFN package Jumper in 2&4 selects RESET# signal (default) Jumper in 1&3 selects A2 signalJumper in 3&5 selects RESET# signalXRA1403/1405 EVALUATION BOARD USER’S MANUAL REV. 1.0.0J85Selects the corresponding signal for pin20 of 24-pin QFN package Jumper in 2&4 selects SO signal (default) Jumper in 1&3 selects SDA signal Jumper in 3&5 selects SDA signalJ86Selects the supply voltage for +VDDP for 24-pin QFN packages Installed but not used for XRA1403IL24-F Jumper in 1&2 selects +VDDPJumper in 2&3 selects +VDDPJ87Selects the corresponding signal for pin18 of 24-pin QFN package Jumper in 2&3 selects CS# signal (default) Jumper in 1&2 selects A0 signalJ88Selects the corresponding signal for pin23 of 24-pin QFN package Installed but not used for XRA1403IL24-F Jumper in 1&2 selects +VDD signal Jumper in 2&3 selects +VDD signalJ89Selects the corresponding signal for pin24 of 24-pin QFN package Installed but not used for XRA1403IL24-F Jumper in 1&2 selects RESET# signal Jumper in 2&3 selects SI signalJ90Selects the corresponding signal for pin20 of 24-pin QFN package Installed but not used for XRA1403IL24-F Jumper in 1&2 selects SDA signal Jumper in 2&3 selects SO signalJ71, J72, J73, J74, J75, J76, J77, J78, J79, J80Not used for XRA1403IL24-F Not installed.T ABLE 4: J UMPER S ETTINGS F OR XRA1403IL24-FJ UMPERS F UNCTIONS C OMMENTSREV. 1.0.0 XRA1403/1405 EVALUATION BOARD USER’S MANUAL 2.2.3XRA1403IG24-FThe following jumpers apply to the XR1403IG24-F:T ABLE 5: J UMPER S ETTINGS F OR XRA1403IG24-FJ UMPERS F UNCTIONS C OMMENTSJ28Header for connecting GPIO[7:0] signalsof QFN packageInstalled but not usedJ29Header for connecting GPIO[7:0] signals of TSSOP package to LEDs Jumper in 1&2 connects GPIO0 to LED Jumper in 3&4 connects GPIO1 to LED Jumper in 5&6 connects GPIO2 to LED Jumper in 7&8 connects GPIO3 to LED Jumper in 9&10 connects GPIO4 to LED Jumper in 11&12 connects GPIO5 to LED Jumper in 13&14 connects GPIO6 to LED Jumper in 15&16 connects GPIO7 to LEDJ30Header for connecting GPIO[15:8] signals of TSSOP package to LEDs Jumper in 1&2 connects GPIO8 to LED Jumper in 3&4 connects GPIO9 to LED Jumper in 5&6 connects GPIO10 to LED Jumper in 7&8 connects GPIO11 to LED Jumper in 9&10 connects GPIO12 to LED Jumper in 11&12 connects GPIO13 to LED Jumper in 13&14 connects GPIO14 to LED Jumper in 15&16 connects GPIO15 to LEDJ31Header for connecting GPIO[15:8] signalsof QFN packageInstalled but not usedJ71Selects the supply voltage for +VDD for 24-pin TSSOP packages Jumper in 2&4 selects +VDD (default) Jumper in 1&3 selects +VDD Jumper in 3&5 selects +VDDJ72Selects the corresponding signal for pin21 of 24-pin TSSOP packageN OTE: Use J78 pin 2 & 3J73Selects the corresponding signal for pin 2 of 24-pin TSSOP package Jumper in 2&4 selects SI signal (default) Jumper in 1&3 selects A1 signal Jumper in 3&5 selects A1 signalJ74Selects the corresponding signal for pin 3 of 24-pin TSSOP package Jumper in 2&4 selects RESET# signal (default) Jumper in 1&3 selects A2 signalJumper in 3&5 selects RESET# signalJ75Selects the corresponding signal for pin23 of 24-pin TSSOP package Jumper in 2&4 selects SO signal (default) Jumper in 1&3 selects SDA signal Jumper in 3&5 selects SDA signalJ76Selects the supply voltage for +VDDP for 24-pin TSSOP packages Installed but not used for XRA1403IG24-F Jumper in 1&2 selects +VDDPJumper in 2&3 selects +VDDPJ77Selects the corresponding signal for pin 2 of 24-pin TSSOP package Installed but not used for XRA1403IG24-F Jumper in 1&2 selects +VDD signal Jumper in 2&3 selects +VDD signalJ78Selects the corresponding signal for pin21 of 24-pin TSSOP package Jumper in 2&3 selects CS# signal (default) Jumper in 1&2 selects A0 signalXRA1403/1405 EVALUATION BOARD USER’S MANUAL REV. 1.0.0J79Selects the corresponding signal for pin 3 of 24-pin TSSOP package Installed but not used for XRA1403IG24-F Jumper in 1&2 selects RESET# signal Jumper in 2&3 selects SI signalJ80Selects the corresponding signal for pin23 of 24-pin TSSOP package Installed but not used for XRA1403IG24-F Jumper in 1&2 selects SDA signal Jumper in 2&3 selects SO signalJ81, J82, J83, J84, J85, J86, J87, J88, J89, J90Not used for XRA1403IG24-F Not installedT ABLE 5: J UMPER S ETTINGS F OR XRA1403IG24-FJ UMPERS F UNCTIONS C OMMENTSREV. 1.0.0 XRA1403/1405 EVALUATION BOARD USER’S MANUAL 2.2.4XRA1405IL24-FThe following jumpers apply to the XRA1405IL24-F:T ABLE 6: J UMPER S ETTINGS F OR XRA1405IL24-FJ UMPERS F UNCTIONS C OMMENTSJ28Header for connecting GPIO[7:0] signals of QFN package Jumper in pin 1 & J29 pin 1 connects GPIO0 to LED Jumper in pin 2 & J29 pin 3 connects GPIO1 to LED Jumper in pin 3 & J29 pin 5 connects GPIO2 to LED Jumper in pin 4 & J29 pin 7 connects GPIO3 to LED Jumper in pin 5 & J29 pin 9 connects GPIO4 to LED Jumper in pin 6 & J29 pin 11 connects GPIO5 to LED Jumper in pin 7 & J29 pin 13 connects GPIO6 to LED Jumper in pin 8 & J29 pin 15 connects GPIO7 to LEDJ29Header for connecting GPIO[7:0] signals of TSSOP package to LEDs 1&2 connects GPIO0 to LED - 0 ohm resistor on board3&4 connects GPIO1 to LED - 0 ohm resistor on board5&6 connects GPIO2 to LED - 0 ohm resistor on board7&8 connects GPIO3 to LED - 0 ohm resistor on board9&10 connects GPIO4 to LED - 0 ohm resistor on board 11&12 connects GPIO5 to LED - 0 ohm resistor on board 13&14 connects GPIO6 to LED - 0 ohm resistor on board 15&16 connects GPIO7 to LED - 0 ohm resistor on boardJ30Header for connecting GPIO[15:8] signals of TSSOP package to LEDs 1&2 connects GPIO8 to LED - 0 ohm resistor on board3&4 connects GPIO9 to LED - 0 ohm resistor on board5&6 connects GPIO10 to LED - 0 ohm resistor on board7&8 connects GPIO11 to LED - 0 ohm resistor on board9&10 connects GPIO12 to LED - 0 ohm resistor on board 11&12 connects GPIO13 to LED - 0 ohm resistor on board 13&14 connects GPIO14 to LED - 0 ohm resistor on board 15&16 connects GPIO15 to LED - 0 ohm resistor on boardJ31Header for connecting GPIO[15:8] signals of QFN package Jumper in pin 1 & J30 pin 1 connects GPIO8 to LED Jumper in pin 2 & J30 pin 3 connects GPIO9 to LED Jumper in pin 3 & J30 pin 5 connects GPIO10 to LED Jumper in pin 4 & J30 pin 7 connects GPIO11 to LED Jumper in pin 5 & J30 pin 9 connects GPIO12 to LED Jumper in pin 6 & J30 pin 11 connects GPIO13 to LED Jumper in pin 7 & J30 pin 13 connects GPIO14 to LED Jumper in pin 8 & J30 pin 15 connects GPIO15 to LEDJ81Selects the supply voltage for +VDD for 24-pin QFN packages Installed but not used for XRA1405IL24-F Jumper in 1&3 selects +VDDJumper in 3&5 selects +VDDJumper in 2&4 selects +VDDJ82Selects the corresponding signal for pin18 of 24-pin QFN package Installed but not used for XRA1405IL24-F Jumper in 1&3 selects A0 signalJumper in 3&5 selects A0 signalJumper in 2&4 selects CS# signalXRA1403/1405 EVALUATION BOARD USER’S MANUAL REV. 1.0.0J83Selects the corresponding signal for pin23 of 24-pin QFN package Installed but not used for XRA1405IL24-F Jumper in 1&3 selects A1 signalJumper in 3&5 selects A1 signalJumper in 2&4 selects SI signalJ84Selects the corresponding signal for pin24 of 24-pin QFN package Installed but not used for XRA1405IL24-F Jumper in 1&3 selects A2 signal Jumper in 3&5 selects RESET# signal Jumper in 2&4 selects RESET# signalJ85Selects the corresponding signal for pin20 of 24-pin QFN package Installed but not used for XRA1405IL24-F Jumper in 1&3 selects SDA signal Jumper in 3&5 selects SDA signal Jumper in 2&4 selects SO signalJ86Selects the supply voltage for +VDDP for 24-pin QFN packages Jumper in 2&3 selects +VDDP (default) Jumper in 1&2 selects +VDDPJ87Selects the corresponding signal for pin18 of 24-pin QFN package Jumper in 2&3 selects CS# signal (default) Jumper in 1&2 selects A0 signalJ88Selects the corresponding signal for pin23 of 24-pin QFN package Jumper in 2&3 selects +VDD signal (default) Jumper in 1&2 selects +VDD signalJ89Selects the corresponding signal for pin24 of 24-pin QFN package Jumper in 2&3 selects SI signal (default) Jumper in 1&2 selects RESET# signalJ90Selects the corresponding signal for pin20 of 24-pin QFN package Jumper in 2&3 selects SO signal (default) Jumper in 1&2 selects SDA signalJ71, J72, J73, J74, J75, J76, J77, J78, J79, J80Not used for XRA1405IL24-F Not installed.T ABLE 6: J UMPER S ETTINGS F OR XRA1405IL24-FJ UMPERS F UNCTIONS C OMMENTSREV. 1.0.0 XRA1403/1405 EVALUATION BOARD USER’S MANUAL 2.2.5XRA1405IG24-FThe following jumpers apply to the XR1405IG24-F:T ABLE 7: J UMPER S ETTINGS F OR XRA1405IG24-FJ UMPERS F UNCTIONS C OMMENTSJ28Header for connecting GPIO[7:0] signalsof QFN packageInstalled but not usedJ29Header for connecting GPIO[7:0] signals of TSSOP package to LEDs Jumper in 1&2 connects GPIO0 to LED Jumper in 3&4 connects GPIO1 to LED Jumper in 5&6 connects GPIO2 to LED Jumper in 7&8 connects GPIO3 to LED Jumper in 9&10 connects GPIO4 to LED Jumper in 11&12 connects GPIO5 to LED Jumper in 13&14 connects GPIO6 to LED Jumper in 15&16 connects GPIO7 to LEDJ30Header for connecting GPIO[15:8] signals of TSSOP package to LEDs Jumper in 1&2 connects GPIO8 to LED Jumper in 3&4 connects GPIO9 to LED Jumper in 5&6 connects GPIO10 to LED Jumper in 7&8 connects GPIO11 to LED Jumper in 9&10 connects GPIO12 to LED Jumper in 11&12 connects GPIO13 to LED Jumper in 13&14 connects GPIO14 to LED Jumper in 15&16 connects GPIO15 to LEDJ31Header for connecting GPIO[15:8] signalsof QFN packageInstalled but not usedJ71Selects the supply voltage for +VDD for 24-pin TSSOP packages Installed but not used for XRA1405IG24-F Jumper in 1&3 selects +VDDJumper in 3&5 selects +VDDJumper in 2&4 selects +VDDJ72Selects the corresponding signal for pin21 of 24-pin TSSOP package Installed but not used for XRA1405IG24-F Jumper in 1&3 selects A0 signalJumper in 3&5 selects A0 signalJumper in 2&4 selects CS# signalJ73Selects the corresponding signal for pin 2 of 24-pin TSSOP package Installed but not used for XRA1405IG24-F Jumper in 1&3 selects A1 signalJumper in 3&5 selects A1 signalJumper in 2&4 selects SI signalJ74Selects the corresponding signal for pin 3 of 24-pin TSSOP package Installed but not used for XRA1405IG24-F Jumper in 1&3 selects A2 signalJumper in 3&5 selects RESET# signal Jumper in 2&4 selects RESET# signalJ75Selects the corresponding signal for pin23 of 24-pin TSSOP package Installed but not used for XRA1405IG24-F Jumper in 1&3 selects SDA signal Jumper in 3&5 selects SDA signal Jumper in 2&4 selects SO signalJ76Selects the supply voltage for +VDDP for 24-pin TSSOP packages Jumper in 2&3 selects +VDDP (default) Jumper in 1&2 selects +VDDPNOTICEEXAR Corporation reserves the right to make changes to the products contained in this publication in order to improve design, performance or reliability. EXAR Corporation assumes no responsibility for the use of any circuits described herein, conveys no license under any patent or other right, and makes no representation that the circuits are free of patent infringement. Charts and schedules contained here in are only for illustration purposes and may vary depending upon a user’s specific application. While the information in this publication has been carefully checked; no responsibility, however, is assumed for inaccuracies.EXAR Corporation does not recommend the use of any of its products in life support applications where the failure or malfunction of the product can reasonably be expected to cause failure of the life support system or to significantly affect its safety or effectiveness. Products are not authorized for use in such applications unless EXAR Corporation receives, in writing, assurances to its satisfaction that: (a) the risk of injury or damage has been minimized; (b) the user assumes all such risks; (c) potential liability of EXAR Corporation is adequately protected under the circumstances.Copyright 2011 EXAR CorporationDatasheet October 2011.Send your UART technical inquiry with technical details to hotline: ************************.Reproduction, in part or whole, without the prior written consent of EXAR Corporation is prohibited.XRA1403/1405 EVALUATION BOARD USER’S MANUAL REV. 1.0.0 3.0TECHNICAL SUPPORTIf there are any questions, please send an e-mail to ************************.J77Selects the corresponding signal for pin 2 of 24-pin TSSOP package Jumper in 2&3 selects +VDD signal (default)Jumper in 1&2 selects +VDD signal J78Selects the corresponding signal for pin 21 of 24-pin TSSOP package Jumper in 2&3 selects CS# signal (default)Jumper in 1&2 selects A0 signal J79Selects the corresponding signal for pin 3 of 24-pin TSSOP package Jumper in 2&3 selects SI signal (default)Jumper in 1&2 selects RESET# signal J80Selects the corresponding signal for pin23 of 24-pin TSSOP package Jumper in 2&3 selects SO signal (default)Jumper in 1&2 selects SDA signalJ81, J82, J83, J84,J85, J86,J87, J88,J89, J90Not used for XRA1405IG24-FNot installed T ABLE 7: J UMPER S ETTINGS F OR XRA1405IG24-FJ UMPERSF UNCTIONS C OMMENTS。

Opensips 配置文件

NOTE: a DB (like db_mysql) module must be also loaded */ #loadmodule "auth.so"
#loadmodule "auth_db.so" #AUTH_DB 模块是以数据库为基础的认证模块 /* uncomment next line for aliases support
－1－
Opensips 配置文件
#tls_private_key = "/usr/local/etc/opensips/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/opensips/tls/user/user-calist.pem"
####### 模块（Modules Section） ######## 包含了外部库的列表，这些外部库是核心所没有的但却是能够展现其功能的。模#### #####块的加载使用 loadmodule
#set module path mpath="/usr/local/lib/opensips/modules/"
# ----- acc params ----/* what sepcial events should be accounted ? */ modparam("acc", "early_media", 1) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1)
sluggishlogstderrorno器会打印信息到则syslog会被使用logfacilityloglocal0forkyesyes程会在在后台运行有候在前台运行也很重要可以来找到脚本如果错误forkdisabledopensips只能听一个网卡udp接口允children4每个udp地址打开子tcp程没有影响

Opensips 配置文件

Opensips 配置文件
sunky045@
Opensips 配置文件 Opensips.conf
####### 全局定义（Global Parameters）文件的这一部分包含了 OpenSIPS 的几个工作参 #######数，包括 SIP 服务的监听 ip 端口对和 debug 等级。#########
#要使用明文密码
#modparam("auth_db", "password_column", "password")
#modparam("auth_db", "db_url",
#
"mysql://opensips:opensipsrw@localhost/opensips")
####### 模块（Modules Section） ######## 包含了外部库的列表，这些外部库是核心所没有的但却是能够展现其功能的。模#### #####块的加载使用 loadmodule
#set module path mpath="/usr/local/lib/opensips/modules/"
sunky045@
# ----- auth_db params -----
/* uncomment the following lines if you want to enable the DB based
authentication */
#modparam("auth_db", "calculate_ha1", yes) #calculate_hal 告诉 auth_db 模块
fork=yes children=4

IPS常见问题处理

IPS常见问题处理参考文档：《dialogic串音单通问题的分析方法.doc》Dialogic卡相关问题七号卡问题1.Dialogic信令网关日志查看1)判断信令栈是板卡方式还是主机方式1103 09:08:37 [MANX] run stacks on host2)从OAMServer读取配置信息，生成Config.txt和System.txt两个文件(在c:\septel下) 1103 09:08:37 [MANX] writing config.txt and system.txt3)通过gctload加载配置文件，对7号信令卡进行配置1103 09:08:37 [MANX] try to run gctload1103 09:08:39 [MANX] try to start service Septel1103 09:08:39 [MANX] check service gctserv state1103 09:08:39 [MANX] start service gctserv4)检查配置和信令卡启动结果，如果有错误，会在check boot result…后面显示错误代码1103 09:08:40 [MANX] check boot result...1103 09:08:47 [MANX] board 0: SS7.DC3 V1.51103 09:08:47 [MANX] Hardware Rev 2, RAM 32M, Slot 5 .Firmware Ver1.02Electronic serial number: 01-00000737CB03-82License serial number: 02-0000008C9110-901103 09:08:47 [MANX] activate link 0 ok.1103 09:08:47 [MANX] configuration done1103 09:08:48 [ISP0] stack information: SS#7 ISUP 4.0.5)等待Link UP，和信令路由成功：Console上会显示Link ? in Service，只有Link UP并且路由通了后，DPC才可用，MG才能注册对应的中继1103 09:13:04 [ISP0] DPC 0x010106 UnAvailable.1103 09:13:05 [ISP0] DPC 0x010106 UnAvailable.1103 09:13:07 [ISP0] DPC 0x010106 UnAvailable.1103 09:13:07 [ISP0] DPC 0x010106 UnAvailable.1103 09:13:41 [ISP0] DPC 0x010106 Available.1103 09:13:41 [ISP0] DPC 0x010106 Available.1103 09:13:41 [ISP0] DPC 0x010106 Available.1103 09:13:41 [ISP0] DPC 0x010106 Available.1103 09:13:41 [SRVX] EVT: DPC 0x010106 resumed..6)等待MG注册消息1103 09:13:42 [SRVX] recv register request for span 12, from 0x00500021.1103 09:13:42 [SRVX] span 12 is free.1103 09:13:42 [SRVX] span 12 is available.1103 09:13:42 [SRVX] the span 12 is registered.1103 09:13:42 [SRVX] totally 2 groups in span 121103 09:13:42 [SRVX] check group info 0 in span 12 ok.1103 09:13:42 [SRVX] check group info 1 in span 12 ok7) 通道复位1103 09:13:42 [ISPX] <12, 1> send RSC.1103 09:13:42 [ISP0] <12, 1> recv RLC (RSC confirmed)8) 启动成功，可看见呼叫信令日志呼叫信令日志格式：DA TETIME [协议＋节点号] <SPANID, CHANNEL> send/recv 信令消息内容协议对应TUP或ISP，节点号对应7号信令节点。

Opensips安装指南

Opensips安装指南第一部分：安装Opensips1.环境准备yum install gccyum install mysql mysql-server mysql-develyum install flex bison ncurses libncurses-dev ncurses-devel2.安装过程（1）下载opensipswget /pub/opensips/2.2.1/src/opensips-2.2.1.tar.gz解压：tar zxvf opensips-2.2.1.tar.gz（2）安装：进入安装文件夹，执行make menuconfig，将弹出如下界面在Configure Compile Options 中选择exclude 中选择cd_mysql 然后执行Compile And Install OpenSIPS然后退出，执行make 再执行make install，其实应该都不用执行这两个命令，直接在前面就已经安装好了。

(3) 安装中问题安装完之后，可能是前面需要修改安装路径，所以导致我们的安装的opensips 的路径有些怪异，全部都在/usr/local 下面，包括我们要修改配置文件时，需要在/usr/local/etc/opensips/opensip.cfg启动opensips时，需要在/usr/local/sbin/opensipsctl start 这样的启动方式要解决这个问题，就可以通过在make menuconfig 中通过然后就会弹出来关于安装路径的修改3.配置过程（1）配置IP地址，即是配置opensips 所在的服务器的真实IP地址打开：/usr/local/etc/opensips/opensip.cfg找到listen=udp:127.0.0.1:5060 # CUSTOMIZE ME修改为listen=udp:192.168.1.XXX:5060（2）启动opensip/usr/local/sbin/opensipsctl 启动（3）数据库配置①对MYSQL的支持vim /usr/local/etc/opensips/opensipsctlrc将DBENGINE=MYSQL 去掉注释在防火墙中开放3306端口，并给数据库用户root创建密码然后同时要将相关的配置信息配置到opensipsctlrc 文件中②创建数据库表进到/usr/local/sbin 目录，里面有一个文件opensipsdbctl执行 ./opensipsdbctl create 然后会提示输入root的密码会有几个选择项，只要全部按Y就行了。

SIP服务器测试工具SIPp使用指导

SIP服务器性能测试工具SIPp使用指导Contents1安装及概述： (1)1.1SIPp安装 (2)1.2SIPp使用 (3)1.2.1 uac.bat： (3)1.2.2 data.csv： (4)1.2.3 uac.xml： (4)2常见问题： (8)2.1uas.bat (8)2.2uas.xml (9)3操作截图： (13)3.1uac： (13)3.2uas： (14)1 安装及概述：SIPp是一个测试SIP协议性能的工具软件。

这是一个GPL的开放源码软件。

它包含了一些基本的SipStone用户代理工作流程（UAC和UAS），并可使用INVITE和B YE 建立和释放多个呼叫。

它也可以读XML的场景文件，即描述任何性能测试的配置文件。

它能动态显示测试运行的统计数据（呼叫速率、信号来回的延迟，以及消息统计）。

周期性地把CSV统计数据转储，在多个套接字上的TCP和UDP，利用重新传输管理的多路复用。

在场景定义文件中可以使用正规表达式，动态调整呼叫速率。

SIPp可以用来测试许多真实的SIP设备，如SIP代理，B2BUAs,SIP媒体服务器，SIP/x网关，SIP PBX，等等，它也可以模仿上千个SIP代理呼叫你的SIP系统。

SIPp的网址：/，这里可以下载最新版的SIPp软件，并且有英文资料可供查阅。

1.1 SIPp安装SIPp提供Linux，Windows和HPUX平台的版本。

Windows平台上的安装很简单，下面说一下Linux下的安装。

首先，可以从/projects/sipp/files/sipp/3.2/下载最新版的SIPp，解压之后就得到一个rpm文件，你可以使用rpm命令来完成安装。

如果你拿到的是绿色版的SIPp，那么你需要对其重新编译才能使用。

SIPp是用C++写的，因此系统必须支持G++才可成功编译。

SIPp支持四种不同的安装模式：1) 没有TLS支持与密码验证支持：a) # tar -xvf sipp-1.1rc6.tar.gzb)# cd sipp-1.1.rc6c)# makeMake出来的sipp文件就是一个可执行的文件，只需要搭配场景xml文件与csv文件即可进行SIP测试，这是最常用的安装。

sip性能优化

由于工作的原因，需要对osip协议栈进行优化，前段时间在论坛上看到lw3223兄对于osip协议栈hash查找事务的讨论，鉴于此把自己这段时间对osip的优化和心得总结出来大家共享一下。

写的比较匆忙，有点乱，大家见谅了。

众所周知，Osip协议栈是用C语言编写，实现了SIP协议基于事务层的处理，后来作者对协议栈进行了扩展，提供了call级的操作处理，也就是eXosip。

Osip小巧，灵活，易扩展，比较方便用来实现UA，但是用作proxy的话性能上有点满足不了需求（听说有个改良版的partysip，没用过，我们这里只讨论osip 的优化），有必要对其进行优化一番。

这里使用的是最新3.0.1的版本，有些固有的影响性能的因素，比如消息的解析，复制，转换到字符串以及释放等暂不予讨论，大家有什么好的方案也可以一起讨论一下。

我们可以围绕协议栈线程主执行函数_eXosip_execute()来展开对它的优化工作。

1.1 SIP Message到transaction的映射Osip性能低下的一个重要原因便是有太多的for循环，尤其是在事务层SIP消息到事务的匹配，好在osip 预留了hash的处理方法，为我们的优化节省了不少的工作量。

打开编译宏HA VE_DICT_DICT_H，协议栈便会使用libdict库对四种事务进行hash的插入，查找，删除等。

如果您手头有这个库，到这里这一步就可以完成了。

由于这个库不是linux自带的，你可能需要自己给协议栈实现一个hash算法，增加osip_hash.c 和osip_hash.h两个文件基本上就OK了。

经过测试，这项操作对性能的提升约1/10左右。

由于测试的压力较小，因此查询效率的提升不是很明显，但是当呼叫量和并发数较大时，对性能的改善应该会比较明显。

1.2 Osip状态机的处理效率协议栈处理事务事件（这里指osip事件，非eXosip事件）的主函数是osip_xxx_execute()，在这里xxx 分别代表osip的四种状态机ict, ist, nict, nist，以下如未经特别说明均使用该准则。