SIP?VoIP?測試交流群: 323827101

歡迎大家轉載。為保留作者成果，轉載請注明出處。http://blog.csdn.net/netluoriver。有些文件在資源中也能夠下載。假設你沒有積分。能夠聯系我索要！

3.6Adding calls to a test(為測試腳本添加呼叫)

To add a call, use the?add a call?link of the corresponding party (see in the figure above) and get to the?Create new call?screen.

加入一個呼叫,在對應的一端使用add a call?鏈接 (見上圖)和開始創(chuàng)建新的呼叫。

Here the command line parameters to pass to SIPp can be set up (the corresponding parameters are stated in round brackets, e.g.,?-timeout) or (-m), but first

這里的命令行參數能夠設置SIPp(用圓括號規(guī)定對應的參數。比如：(-timeout)或(-m)),但首先

·choose an?Executable?(the version of SIPp you want to use, defined in?config.ini.php. See section?Config file?for more details).

選擇一個可運行文件(在config.ini.php中定義你想用的SIPp版本號。

查看Config file一節(jié)獲得很多其它具體信息)

·choose a?Scenario?defined earlier in the?Manage scenarios?tab (Section?Manage scenarios).

在管理場景選項卡中選擇一個前面定義的場景

·if a client scenario is used, enter a?Remote host. This is where SIPp addresses its messages to.

假設已經用了一個client場景，輸入一個遠程主機地址。

這個地址就是SIPp要發(fā)送給對端的消息地址。

·check the?Monitor call?checkbox, if during the test execution realtime feedback of the test progress should be displayed. In that case the tester can also influence the test by pausing it, or by adjusting the packet rate (See section?Run a test?for more details).

檢查監(jiān)視呼叫復選框，假設在測試腳本時，會實時顯示測試過程。在那種情況下測試者通過暫停或調整包的速率也會影響測試效果(查看執(zhí)行一個測試一節(jié)獲得更加具體信息)

·check the?Log?checkbox, if log files (-trace_err, -trace_logs, -trace_rtt, -trace_stat) should be stored in the database.

檢查日志復選框，日志文件(-trace_err, -trace_logs, -trace_rtt, -trace_stat)是否存儲到數據庫中。

If the given configuration options are not enough, the?Extended parameters?text field can be used to pass any command line parameters to SIPp. The?Extended parameters?are not evaluated or modified in any way. It is up to the administrator to use a correct syntax. There may be some command line options that do not work, or even cause SIPp to hang (i.e.?-bg).

假設所給的配置選項不夠用。Extended parameters?文本框能夠給SIPp傳遞不論什么命令行參數。?Extended parameters由管理員使用正確的語法。

它并不以不論什么方式評估或改動。或許會有一些命令行選項不可用或引起SIPp掛起(比如-bg選項)

If a parameter is specified in the form and also as?extended parameter, the?extended parameter?has the higher priority, and overwrites the other.

假設在表格中指定了一個參數，而且也作為擴展參數，那么擴展參數會有更高的優(yōu)先權，并重寫還有一個

Global parameters (applied to any call) can be defined in the?AVP Section?of the?config.ini.php. These have the lowest priority.

在?config.ini.php中的AVP Section能定義全局參數(應用于不論什么呼叫)。這些有最低優(yōu)先權。

3.7Modify a test / create a new test version(改動/創(chuàng)建一個新的測試腳本)

Tests and calls can be modified at any time. If a test has already runs, a crucial modification of the test would mean that test information belonging to these runs is lost, and thus the run is not reproducible anymore. To avoid this, a new version is created automatically.

測試腳本和呼叫可能在不論什么時候都能夠被改動。

假設一個測試腳本已經執(zhí)行了。改動測試腳本意味著屬于這些執(zhí)行的測試信息會丟失,從而執(zhí)行不再重現了。為了避免這樣的情況，會自己主動創(chuàng)建一個新的版本號。

Simply switch between the versions of a test by clicking the version numbers. A version can even be deleted by using the?remove this version?link, but then all its runs are lost too.

通過點擊版本號號能夠實現兩個版本號的簡單切換。以致能夠用?remove this version鏈接來刪除一個版本號。但這樣做，所有有關這個版本號的測試消息也會刪除。

3.8Duplicate a test(復制一個測試腳本)

If a test is duplicated using the?duplicate test?link, the currently displayed version of the test is copied into version 1 of the duplicate. The new name of the duplicate is composed with the original name followed by the word?copy. A duplicate initially has no runs.

假設用duplicate test鏈接復制了一個測試腳本，當前顯示的測試版本號被復制到副本的版本號1中。用原來的名稱加上單詞copy來顯示新副本的名稱。副本初始化不會執(zhí)行

3.9System information(系統(tǒng)信息)

In the?System information?tab, the page is split in 3 areas. First a list of currently running SIPp instances is displayed. Then the available free disk space is stated. Finally there is a list with the versions of SIPp that are defined in the?config.ini.php?file, along with their verbose screens.

在System information標簽頁。分成了3個區(qū)域。currently running SIPp instances顯示在第一個。然后規(guī)定了可用的磁盤空間。

最后的一個列表顯示了在?config.ini.php文件中定義的SIPp版本號號，連同他們的具體的屏幕。

3.10Kill a hanging SIPp instance(殺死一個掛起的SIPp實例)

An admin can try to kill an instance of SIPp by pressing the corresponding red?X?button in the list of currently running SIPp instances. Although SIPp runs that are not started through the web frontend are also in the list, they cannot be killed.

在當前執(zhí)行的SIPp列表中通過點擊紅色?X??????button來殺死一個SIPp實例。不是從web頁面執(zhí)行的SIPp實例，在web頁面不能殺死。

3.11Config file（配置文件）

A line in the config file with a leading ; is a comment and has no effect to the configuration.

在配置文件的開頭部分是一個描寫敘述，不會影響到配置。

The configuration file is divided in three sections respectively tagged with
[EXECUTABLES], [AVP], and [CONFIG].

配置文件被分成三部分，分別用[EXECUTABLES], [AVP]和[CONFIG]來標記。

?

·In the?[EXECUTABLES]-section SIPp executables and their versions can be specified. At least one executable is mandatory.

在[EXECUTABLES]部分是SIPp可運行文件，能夠指定運行實例。

當中至少有一個SIPp可運行文件。

·In the?[AVP]-section global command line parameters for SIPp can be specified in form of attribute-value pairs (attribute = value).?

在[AVP]部分以屬性-值對的形式(屬性=值)指定了SIPP全局命令行參數。

I.e. most parameters of SIPp (without the leading -) will be accepted (see?sipp -h?for more details).

比如,接受SIPp（參數中沒有-）的大多數參數（用命令“sip -h”獲得很多其它信息）

These parameters can be overwritten in each individual call by using the?Extended parameters?textarea in the web tool. Take care that you only use parameters that work with every version of SIPp you are using with this tool. If a attribute has no value, but is a switch, use TRUE as a value (e.g.,?aa = TRUE). If a value contains non-alphanumeric characters it needs to be enclosed in double-quotes (").

在web中通過用Extended parameters?文本區(qū)在每一個獨立的呼叫中重寫這些參數。注意，你僅能在正在用的SIPp的版本號中用這個參數（也就是說此版本號中有的命令才干用。畢竟每一個SIPp的版本號功能不一樣，新的版本號功能比較多一些嘛），除非是一個開關，用TRUE作為一個值（比如，aa = TRUE），假設值包括非字母數字的字符須要用雙引號(")括起來。

Parameters not allowed are:?參數不同意是：
i, m, nd, nr, t, p, r, timeout, pause_msg_ign, v, bind_local, inf, sd, sf, sn, stf, trace_msg, trace_shortmsg, trace_screen, trace_err, linebreak trace_timeout, trace_stat, trace_rtt, trace_logs

·In the?[CONFIG]-section you will find program specific parameters, like admin password or MySQL-database connection information...

在[CONFIG]部分你會找到程序指定參數。如管理password或MYSQL-database連接信息……

Refer to the config file?config.ini.php?to get more detailed information about the specific parameters.

關于指定參數請參數配置文件里的config.ini.php獲得很多其它具體信息。

4User guide（用戶向導）

4.1Manage tests（管理測試腳本）

There is a list of available tests in the?Manage tests. If there are many tests, it may be useful to sort the tests by clicking one of the column headings.

在Manage tests中是測試腳本列表。

假設有非常多測試腳本，通過點擊列頭能夠自己主動分類。

4.2Run a test（執(zhí)行一個測試腳本）

Click on a test to get a more detailed view. There choose a version and click on the?run this version?link to open the test popup.

在一個測試項中點擊。會得到一個具體的界面。

選擇一個版本號并點擊run this version鏈接會彈出測試頁面。

Click on?Run test now?to begin testing. Both parties start to process their queues. On the left hand side of each call there is a small image showing the actual state of the call.

在Run test now單擊開始進行測試。兩方開始處理隊列。在每個呼叫的左手邊有一個小圖像顯示呼叫的實際狀態(tài)。

4.3Key commands（keyword命令）

If monitoring is turned on, the test progress can be influenced by using key commands (this is the same as in the command line). First set the focus to the corresponding monitoring screen by clicking on it. When the border of the screen turns red, use the key commands on your keyboard.

假設打開了監(jiān)控。用keyword命令會影響測試進展（用命令行測試也一樣會影響）。首先通過點擊keyword命令，設置焦點到對應的監(jiān)視屏幕。當屏幕的邊界變?yōu)榧t色，使用你的鍵盤鍵入命令。

·0-9?to switch between screens

0-9?切換屏幕

·+ , - , * , /?to adjust packet rate

+ , - , * , /?調整包速率

·q?to soft exit

q軟退出

·p?to pause/resume execution

p暫停/恢復運行

4.4Abort a call / test（停止一個呼叫/測試）

Never close the test window without the test finished, because there may reside SIPp processes running on the server. If for some reason a call does not terminate by itself, there are three possibilities to finish the test anyway:

僅僅有測試完畢后才會關閉測試窗體，因為在服務器中可能駐留SIPp進程。假設因為一些原因一個呼叫沒有自己掛斷，完畢這個測試有三種可能：

·If the call has monitoring turned on, try to end the call with the key command?q?(soft exit).

假設打開了監(jiān)控功能。試試用軟命令q鍵退出（軟退出）

·A call that hangs can be terminated by pressing the red?X?on its right hand side.

通過點擊右側紅色?X?button結束掛起的呼叫。

·The whole test can be stopped with the?Abort test?link at the top of the window.

點擊接窗體頂部的Abort test鏈接來停止結束測試

4.5Runs（執(zhí)行）

After a test has finished, the test window is closed automatically and the created run is displayed. The?exit?and the?std error?column may contain important information (roll the mouse over the columns for more details in a tooltip box). Click the grey eye buttons to download the log files created during the test.

測試完畢后，測試窗體自己主動關閉并創(chuàng)建執(zhí)行過程中的顯示參數。列exit和std error或許包括重要的信息（在懸浮框中滾動鼠標軸獲得更具體的信息）。點擊灰色眼睛button來下載在測試過程中創(chuàng)建的日志文件。

It is possible to return to this page, or to another run, any time. Just navigate to the corresponding test in the?Manage tests?tab, choose the right version and click on a run at the bottom of the page.

可能會返回這個頁面。或返回至還有一個執(zhí)行頁面，僅在Manage tests選項卡中導航到對應的測試中就可以，選擇一個正確的版本號并在頁面底部點擊就可以執(zhí)行。

5Programming guide（程序設計說明）

5.1Database (ER Diagram)（數據庫（ER圖表））

5.2Files（文件）

·add_call.php?is responsible for the?add/modify call?screen. Adds/modifies calls in the database.

·add_call.php在屏幕中代表add/modify call?。在數據庫中代表Adds/modifies?呼叫。

·authentication.php: checks if admin is logged in. It is included everywhere, where admin should have special permissions.

authentication.php:選擇是否admin登錄。它包括了admin訪問權限的不論什么地方。

·Call_Data.php: class Call_Data: contains call specific data (process-id, log filenames...) of a currently running call. It has methods to store log files in the database, delete the log files and determine the exit code after execution. When a call is about to be executed, an object of this class is generated and stored in a session variable.

Call_Data.php:類Call_Data：包括一個當前執(zhí)行呼叫中調用指定的數據（process-id, log filenames...）。

它有把日志文件存儲到數據庫、刪除日志文件和決定運行完后退出的代碼。當運行一個呼叫時，會生成這個類的一個對象并保存一個會話變量。

·config.ini.php: configuration file

config.ini.php:配置文件

·create_run.php: is called from run_progress.php via ajax. It creates a run in the database with the current timestamp.

create_run.php:通過ajax從run_progress.php中調用。在數據庫中創(chuàng)建一個執(zhí)行的當前時間戳。

·dbHelper.php: is where the SQL happens. For each table in the database, there is a corresponding class that handles database communication.

dbHelper.php:?SQL處理的地方，對數據庫中的每一個表來說。都有一個對應的類處理數據庫通信。

·db.php: generates the MySQL database connection object.

db.php:生成MySQL數據庫連接對象

·exec_call.php: is called from?run_progress.php?via ajax. The basic function of this file is to build up the command line, create the XML-scenario file and the CSV-injection file in the system's temporary folder, execute the call and return its process id (pid).

exec_call.php:通過ajax從run_progress.php調用。

這個文件的基本功能是構造命令行，在系統(tǒng)的暫時目錄中創(chuàng)建XML場景文件和CSV注入文件。運行呼叫并返回它的進程id(pid).

·garbagecollector.php: removes all SIPp directories in the system's temp folder that have not been modified for a specific time (defined in?config.ini.php). Further all SIPp processes older than a specific time get killed.

garbagecollector.php:?（暫不會翻譯）

·get_screen.php: During execution of a call this file is requested periodically via ajax. Here the actual monitor-screen is extracted from the screen file, and returned to?status_screen.php?(if monitoring is turned on). Further this file checks if the SIPp process is still running, and if not, it returns exit-code and standard-error tostatus_screen.php.

get_screen.php:在執(zhí)行呼叫期間，通過ajax這個文件會周期的向server進行請求。實際上是從screen文件里導出監(jiān)控屏幕，并將結束輸入至?status_screen.php（假設打開了監(jiān)控功能）。

進一步講。這個文件檢查SIPp進程是否仍在執(zhí)行，假設沒有。tostatus_screen.php會返回的退出代碼和標準錯誤

·helper.php: just some useful functions.

helper.php:僅是一些實用的功能說明

·index.php: redirect to?tests.php.

index.php:重定向到test.php

·info.php: represents the?System information?tab.

info.php:代表System information標簽

·kill_process.php: is called from?run_progress.php?via ajax, if the user wants to kill a SIPp process.

kill_process.php:?假設用戶想殺死SIPp進程。會通過ajax從run_progress.php中調用此文件。

·read_config.php: reads the config file in the three arrays?$executables, $avp,?and?$config. Default values are set if necessary, and there is a function?getConfig-Parameters?that assembles command line parameters from the?AVP?section.

read_config.php:在$executables, $avp,?和$config中讀取配置文件。

假設有必要能夠設置默認值。有一個得到配置參數（getConfig-Parameters）功能是從AVP部分中收集命令行參數。

·run_detail.php: represents the?show run?page.

run_detail.php:代表show run頁面

·run_progress.php: represents the?run test?popup. This is where all the ajax happens. Refer to the file itself for detailed information.

run_progress.php:代表run test?彈出窗。這是全部ajax執(zhí)行的地方，參考此文件獲得至多信息

·scenario_detail.php: represents the?create/modify scenario?screen. Inserts or updates scenario data in the database.

scenario_detail.php:代表create/modify scenario屏幕，在數據庫中插入或場景數據。

·scenarios.php: represents the?Manage scenarios?tab.

scenarios.php:代表Manage scenarios?標簽。

·send_key.php: is called via ajax from?status_screen.php?when the user presses a key on the keyboard.

send_key.php:當用戶在鍵盤中按下一個鍵時，從?status_screen.php?中通過ajax調用send_key.php。

·status_screen.php: is displayed in a iframe in?run_progress.php?during test. Here the status monitor screen of a running SIPp instance is displayed by polling it from the server frequently. Further, keyboard action is sent to?send_key.php, that forwards it to the running SIPp instance.

status_screen.php:測試過程中在一個內嵌框架中顯示?run_progress.php?。會從server頻繁地輪循它來顯示執(zhí)行SIPp實例的監(jiān)控屏幕的狀態(tài)。進一步講，鍵盤的動作發(fā)送到send_key.php，驅動它來執(zhí)行SIPp實例。

·stop_sipp.php: has a function that tries to stop a running SIPp instance. It takes care that the pid belongs to a SIPp process.

stop_sipp.php:嘗試停止一個執(zhí)行的SIPp實例。它負責pid屬于一個SIP進程。

·sys_get_temp_dir.php: provides functions that determine the working directory and the systems temp directory.

sys_get_temp_dir.php:提供限定工作文件夾和系統(tǒng)時時文件夾的功能。

·test_detail.php: represents the?create/modify test?screen.

test_detail.php:代表create/modify test?屏幕

·tests.php: represents the?Manage tests?tab.

tests.php:代表Manage tests?標簽頁。

·view_csv.php: is for downloading CSV files (log files etc.) that are stored in the database.

view_csv.php:下載保存在數據庫中CSV文件（日志文件等）

·view_messages.php: is for downloading the file created by the command line option?-trace_messages. The trace_messages file is not stored in the database because it may be very large, but it is left for a short time in the systems temp folder until the garbage collector removes it.

view_messages.php:下載通過命令行?-trace_messages選項創(chuàng)建的文件。trace_messages文件不會存到數據庫中，因為它或許會很大，可是在系統(tǒng)暫時目錄中一直保留。除非到達垃圾設置值才會被刪除。

·view_text.php: is for downloading text files (log files etc.) that are stored in the database.

view_text.php:下載存在數據庫中的txt文件（日志文件等）

·view_xml.php: is for downloading XML files (scenario files) that are stored in the database.

view_xml.php:?下載存在數據庫中的XML文件（場景文件）

·/js/ajaxConnection.js: crossbrowser function to create an ajax request object in javascript.

/js/ajaxConnection.js:在javascript中跨瀏覽器函數來創(chuàng)建一個ajax的請求對象

·/js/helper.js: some useful javascript functions.

/js/helper.js:一些實用的javascript函數。

·/js/run.js: opens a window for a test run.

/js/run.js:為一個測試執(zhí)行打開一個窗體。

·/js/tooltip.js: provides functions to display tooltip texts.

/js/tooltip.js:提供函數來顯示工具提示文本

·/navigation/pagehead.php: If you want to add a new tab to the navigation, do it here.

/navigation/pagehead.php:假設你想在導航欄中加入一個新的標簽頁，在這里進行操作。

·/navigation/register.php: Here the navigation of the webfrontend is created.

/navigation/register.php:創(chuàng)建webfrontend的導航欄

5.3Command flow during test process（測試過程中的命令流）

by?Mario SMERITSCHNIG [code/documentation]

?Mario SMERITSCHNIG【代碼/文檔】

?

?

?

?

在網上找了一個安裝文檔。地址是：

http://opensource.telkomspeedy.com/wiki/index.php/VoIP_Cookbook:_Installation_of_SIPp_Webfrontend

?

?

拷貝?&提取

mkdir /var/www/sipp cp sipp_webfrontend_v1.2.tgz /var/www/sipp/ cd /var/www/sipp/ tar zxvf sipp_webfrontend_v1.2.tgz mv /var/www/sipp/src/* /var/www/sipp/

創(chuàng)建數據庫

mysql -u root -p password: CREATE DATABASE SIPpDB; USE SIPpDB; \. /var/www/sipp/tables.sql quit

編輯config.ini.php

vi /var/www/sipp/config.ini.php

如：

[EXECUTABLES] 3.0 = "/usr/bin/sipp" ? [CONFIG] db_host = "localhost" db_user = "root" db_pwd = "123456" db_name = "SIPpDB" admin_pwd = ""

?

為了更加easy訪問網頁，清空admin_pwd字段。能夠通過

http://localhost/sipp

來訪問SIPp Webfrontend?。用

username admin password <no password>

?

轉載于:https://www.cnblogs.com/clnchanpin/p/7052450.html

總結

以上是生活随笔為你收集整理的SIPp web frontend(2)的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。