歡迎大家轉載，爲保留作者成果，轉載請註明出處，http://blog.csdn.net/netluoriver，有些文件在資源中也可以下載！如果你沒有積分，可以聯繫我索要！
With SIPp web frontend you can（通過SIPp web 前端你能）
·upload XML templates (SIPp scenarios) and CSV injection files(上傳XML模板（SIPp場景）和CSV注入字段)
·create and modify test processes using these files（用這些字段創建並修改測試流程）
·manage test versions（管理測試版本）
·run created test processes（運行創建的測試流程）
·display realtime feedback during test runs（在測試過程中實時顯示反饋）
·store created test information in a database（存儲創建測試信息至數據庫中）
·Scenario(場景)
A user can upload XML files containing SIP call flows, named scenario files. Optionally, one can upload a CSV field injection file. These files are stored along with a scenario name and a description. There are also some standard scenarios, that cannot be modified
(from the command line parameter -sn, e.g., uac, uas, regexp, ...)
一個用戶可以上傳包含SIP呼叫流的XML文件，叫做場景文件。可選地，一次能上傳一個CSV的注入文件。存儲的帶有場景名稱和描述的文件。也有一些標準場景，但是不能修改（用命令行參數 –sn生成,例如，生成uac/uas/regexp/….的默認場景）
·Call（呼叫）
A call consists of all information necessary to run one instance of SIPp. Thus a SIPp executable, a scenario, and a collection of parameters (e.g., destination ip-address).
呼叫的所有必要的信息來保證運行一個SIPp實例。這樣就可以使SIPp可執行、運行一個場景、測試參數的採集（例如：目的IP地址）。
·Call
sequence（呼叫序列）
In some test scenarios it is not enough to run only one call. For example in a first call SIP user agents get registered at a SIP proxy, in a second call those user agents communicate with a server, and in a last call the registrations are removed again. Thus
a call sequence is an ordered list of calls, that can be executed automatically one by one.
在一些測試場景中，只有一個呼叫是不夠的。例如，在一個SIP代理中第一次呼叫註冊的代理用戶，第二次呼叫那些用戶代理與服務器進行通信，在最後一次呼叫時註冊再次被移除。因此呼叫序列是一個呼叫的有序列表，這個就可以自動地一個接着一個執行。
·Call
sequence pair / call parties（呼叫序列對/呼叫對）
SIPp webfrontend has the capability to execute two calls in a test simultaneously. This is useful for example if you want to simulate a server and a client communicating with each other. In this case two call sequences can be defined each in a separate party
(A party and B
party).
SIPp webfrontend有在一個測試中同時執行兩個呼叫的能力。如果你想模擬一個服務端和一個客戶端相互通信是非常有用。在這種情況下兩個呼叫序列可以分別定義（A對和B對）
·Test（測試）
A test can be a call, a call sequence or a call sequence pair. There also may be several versions of a test that can be executed.
一個測試可以是一個呼叫，一個呼叫序列或一個呼叫序列對。也可能是幾個能執行的測試腳本。
·Run（運行）
After a test has been executed, collected information (e.g., about the progress, test parameters, date and time, log files...) is stored as a run for further processing.
執行一個測試後，存儲採集的信息（例如：關於處理、測試參數、日期和時間、日誌文件….）作進一步處理。
3.1Installation instructions（安裝說明）
For detailed installation instructions refer to the file INSTALL.TXT shipped with the SIPp webfrontend package.
詳細的安裝說明請參考SIPp webfrontend包裏面的INSTALL.TXT文件。
In order to act as an admin, you first need to login to the admin section by entering the correct password, defined in the config file config.ini.php with the parameteradmin_pwd. If you want everybody to be admin, assign admin_pwd an empty password (admin_pwd="").
爲了以admin身份執行操作，你首先需要輸入正確的密碼，在配置文件config.ini.php的parameteradmin_pwd進行定義。如果你想所有人以admin進行操作，設置admin_pwd爲空即可(admin_pwd=””)
There is a list of scenarios available for creating tests in the manage scenarios tab. Scenarios tagged with the word default are SIPp default scenarios, and cannot be modified or removed. Change the order of the scenarios by using the arrow up and the arrow down buttons, or remove a scenario by pressing the red X button. To modify a scenario, just click the row of the scenario, and to create a new scenario use the create new scenario link.
在管理場景的標籤中顯示了創建測試的有效場景。帶default標記爲SIPp默認場景，這些是不能修改和刪除的。用向上箭頭或向下箭頭按鈕來改變場景的順序，按紅色X按鈕來刪除一個場景。僅點擊場景的那一地就可以修改場景了。用create new scenario 鏈接創建一個新場景。
3.3Create / modify a scenario（創建/修改一個場景）
To create a scenario, a name has to be specified and a XML scenario file has to be given (upload the file by pressing the corresponding Browse... button). Optionally the user can enter a description, upload a CSV injection file and enter a bind_local ip address to instruct a server to listen only to the given address instead to all available (see sipp -h for more details).
創建一個場景時需要給場景指明一個名稱和一個XML場景文件（通過點擊相應的 Browse... 按鈕）。在可選項Description中可以寫一些對場景文件的描述，上傳一個CSV注入文件並輸入一個bind_local(綁定本機)的ip地址來通知服務器去偵聽，僅當綁定的IP地址有效時功能才正常可用（查看 sipp –h命令獲得詳細信息）
After you have created a scenario, you can modify it any time if you want. You can even remove a CSV file or replace the XML file.
創建一個場景後，你能在任何時候都可以修改。你也可以刪除一個CSV文件或替換XML文件。
Note（注意）
When you modify a scenario, you do not implicitly modify all tests using the scenario. Tests use copies of the scenarios to stay consistent with test runs.
當你修改一個場景時，不要在原來的場景中進行修改，用一個複本進行修改以保證原來的場景還可以正常運行。
Open the Manage tests tab to get a list of available tests.
打開Manage tests 標籤會出現一個測試列表
·to completely delete a test press the red X button
按紅色X按鈕刪除一個測試
·to modify a test, click on the corresponding table row
點擊相應的錶行修改一個測試
·to create a new test, use the create new test link
點擊 create new test鏈接創建一個新測試
For more information about this window see section Manage tests in the User guide.
關於這個窗口的更多信息請在用戶指南中查看 Manage tests部分
To create a test（爲了創建一個測試）
·enter a test title into the name field
在Name中輸入一個測試標題
·optionally enter a test description into the description field
可以在Description中輸入對測試場景的一些描述
·click on the save test link
點擊save test鏈接
After an empty test is created, it is in its version 1. Now calls can be added. A call is an instruction to SIPp, so a test is an instruction set. There are two parties the calls can be added, the A party and the B party. The calls in a party are executed one by one like in a queue, but the two parties are executed simultaneously. With this the parties can communicate with each other.
創建一個空的測試後，顯示版本爲1.現在添加一個呼叫，對SIPp夠一個呼叫就是一個指令，因此一個測試就是一個指令集。可以添加兩部分的呼叫，A端和B端。在一端會一個接一個的執行呼叫，就像是一個序列，但可以兩端同時執行。A端與B端可以相互通信。
Sometimes the A party and the B party should not begin the execution at the same time (e.g., the client waits for the server to start). In this case a party can be delayed using the corresponding delay dropdown field.
有時A端和B端可能不同時執行（例如，客戶端需要等待服務器啓動）。在這種情況下一端，一方能用相應的delay dropdown字段延時
The test screen is split in 3 areas. In the first (upper) one, the test name and description can be modified, and the entire test can be duplicated or removed. In the second (middle) area calls can be added, removed or reordered. The third (lower) area shows the test-runs that has been done with the current version.
測試屏幕中分3個區域。在第一個（上位）中，可以修改測試名稱和描述，整個測試可以被重寫或刪除。在第二個（中間）區域可以添加、刪除或重新排序。第三個（下部）區域中顯示了運行測試的當前版本。