The node agent server generates unique port assignments by default.
缺省情况下，节点代理服务器会生成唯一端口分配。
Start the node agent server and verify that the system output and error logs do not contain any unexpected exceptions.
请启动节点代理服务器，并验证系统输出和错误日志中是否包含任何异常。
The next major step is to create the function that makes the phone call once the user agent server addresses have been set.
设置了用户代理服务器地址后，下一个主要步骤是创建进行电话呼叫的功能。
It initiates the request to the second user agent server (UAS-2) after getting a successful response from the first server.
从第一个服务器成功获取响应之后，启动对第二个用户代理服务器(UAS - 2)的请求。
Unlike a proxy that forwards on the requests, a B2BUA acts as both a user agent server (UAS) and a user agent client (UAC) to further participate in the SIP transaction.
与转发请求的代理不同，B2BUA 同时充当进一步参与SIP 事务的用户代理服务器 (UAS)和用户代理客户机 (UAC)。
Against native storage and agent server storage, the paper puts forward new path supplement algorithm, and use test cases to prove its efficiency.
针对本地缓存和代理服务器缓存，提出了一种新的路径补充算法，并用测试用例验证其有效性。
In Version 6.1, when you federate an application server node into a deployment manager cell, the deployment manager instantiates the node agent server process on the application server node.
在Version 6.1中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
In Version 6.0, when you federate an application server node into a deployment manager cell, the deployment manager instantiates the node agent server process on the application server node.
在Version 6.0中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
Otherwise, try to limit the number of events and invocations at the Remote Management Agent server.
否则，请尝试在RemoteManagementAgent服务器上限制事件和调用的数量。
To test the Remote Management Agent server performance, a custom tool was developed that created a configurable number of General Agents (GAs).
为了测试RemoteManagementAgent服务器性能，开发了一个自定义工具，来创建其数量可配置的普通代理(General Agent, GA)。
Note that although the Remote Management Agent server was stressed for a 2 hour time period, it did not crash, and it continued to process events.
请注意，尽管对RemoteManagementAgent服务器进行了2个小时的压力测试，但并没有导致其崩溃，仍然在继续处理事件。
From this testing, the following limits were discovered for the Remote Management Agent server with the hardware and software configuration described previously.
通过此测试，发现了采用前述硬件和软件配置的RemoteManagementAgent服务器的以下极限。
Note that these are the limits of what the Remote Management Agent server can handle while dedicating most of its processing power to handling events and invocations.
请注意，这些是RemoteManagementAgent服务器将大部分处理能力都用于处理事件和调用时的极限。
If the Remote Management Agent server is expected to receive more than 1000 events per minute or 6000 invocations per minute, adding an additional CPU is the best solution.
如果预期RemoteManagementAgent服务器将接收每分钟超过1000个事件或6000个调用，则最佳解决方案是添加更多的CPU。
If the Remote Management Agent server is expected to receive more than 1000 events per minute or 6000 invocations per minute, adding an additional CPU is the best solution.
如果预期RemoteManagementAgent服务器将接收每分钟超过1000个事件或6000个调用，则最佳解决方案是添加更多的CPU。
应用推荐