Installation guide

Configuring site-to-site call routing for IP telephony 6-5
Chapter 6: IP Telephony Configuration
Wave Global Administrator Guide
T2 Timer. Specifies the maximum duration (in milliseconds) before a request is
retransmitted over UDP or an INVITE response is retransmitted over any
transport protocol. It must be greater than or equal to the value configured in the
T1 Timer. The minimum recommended value is 4000ms.
T4 Timer. Specifies the maximum lifetime of a transaction in the SIP network.
After a transaction completes, it is the amount of time that a UAS will retain the
transaction information in order to subsume late duplicate responses.
5 Click
Apply to save your changes.
Setting up SIP endpoint authentication
Wave supports authentication of inbound requests for SIP endpoints. A SIP endpoint can be
either a SIP extension or a SIP Signaling Control Point (SCP). When properly configured, Wave
can serve as user agent client (UAC), user agent server (UAS), or a back-to-back user agent
(B2BUA) under different call scenarios:
When Wave serves as an UAS or a B2BUA, Wave authenticates and authorizes incoming
requests from clients registering to it or wishing to route calls through it.
When Wave serves as a UAC, it provides appropriate authentication credentials when
challenged by the remote UAS.
Specifically, Wave performs the following SIP endpoint authentication functions:
Authentication of incoming registrations from SIP phones configured as extensions on
Wave.
Authentication of incoming calls from SIP phones configured as extensions on Wave.
Authentication of outbound registrations for SCPs that are challenged by the remote
UAS.
Authentication of outbound calls through SCPs that are challenged by the remote UAS.
In very simple terms, registration is the process of assigning an address to a SIP extension or
SIP SCP, and authentication is the process of verifying the identity of the SIP extension or SIP
SCP before updating the address in the Wave data base.
Release 2.0
September 2010