Avaya SM61 - Manual (Page 20)

MJH; Reviewed:
SPOC 8/4/2011 Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
20 of 47
Sagemcom_SM61
5. Add SIP Entities
A SIP Entity must be added for Session Manager and for each SIP-based telephony
system supported by it using SIP trunks. During compliance testing, a SIP Entity was
added for the Session Manager itself, Communication Manager, and the XMediusFAX
fax server.
Navigate to RoutingSIP Entities, and click the New button (not shown) to add a
SIP Entity. The configuration details for the SIP Entity defined for Session Manager
are as follows:
Under General:
 Name: a descriptive name
 FQDN or IP Address: 10.64.21.31 as specified in Figure 1. This is the IP
address assigned to the SM-100 security module installed in the Session
Manager.
 Type: select Session Manager
Under Port, click Add, then edit the fields in the resulting new row as shown below:
 Port: 5061. This is the port number on which the system listens for SIP
requests.
 Protocol: TLS. The TLS transport protocol was used between Session Manager
and Communication Manager.
 Default Domain: select the SIP Domain created in Step 2.
 Repeat the three bullets above, but select 5060 for Port and UDP for Protocol.
The UPD protocol was used between Session Manager and the XMediusFAX
fax server.
Default settings can be used for the remaining fields. Click Commit to save the SIP
Entity definition.