...
| Setting | Description |
|---|---|
| Packet types | The types of IP packets that you know Echo should look for when inspecting passing traffic on your network adapter. If you know for sure that your audio signal or media packets will never be TCP packets, you should deselect TCP to save CPU load; the less traffic that Echo needs to inspect, the more concurrent calls it can handle with the same hardware. |
| SIP port(s) | The UDP/TCP port number(s) that will be used for SIP signalling traffic on your network. Usually this is a single port (5060) but, in the case of media proxies or multiple SIP registrars on the same network segment, further ports may need to be entered here. |
| Cisco SCCP port | The TCP/UDP port that you expect Cisco SCCP (Skinny) packets to be transmitted on. This value is normally port 2000. |
| Session timeout | This value (in seconds) specifies the maximum amount of time that Echo will continue monitoring a SIP or SCCP session in the event of no traffic, before it considers the session abandoned. |
...
| HTML |
|---|
...
<p>When you have finished configuring Echo, press |
...
the <span class="button">Apply</span> button to save the settings to disk. |
...
</p> <p>To start the Echo service, press |
...
the <span class="button">Start</span> button inside the Service status panel.</p> |
| Info |
|---|
You can verify that the Echo service is running by connecting to its web service at: http://localhost:8080/ If you changed the Web server settings (above), the address may differ. |
...