User's Manual

• If the Credential Name string is not empty, the Credential Name and the IP
address of the far-end is searched for in the following fields in the identity
certificate provided by the SIP entity:
- CN value from the subject
- subjectAltName.dNSName
- subjectAltName.uniformResourceIdentifier (For IP address comparison,
IP address string is converted to SIP:W.X.Y.Z before comparison.
W.X.Y.Z is the remote socket IPV4 address. Also, case insensitive search
is performed in this case)
With entity links from both Session Manager instances, checking the Override Port &
Transport with DNS SRV check box on the SIP entity form indicates that both the Port and
Protocol (Transport) on the SIP entity form are ignored.
• If you select the check box, the port and transport administered in the local host name
resolution table is used, which could override the entity link.
• If the FQDN is not in the local table and DNS is consulted, if you have not selected the
check box, only an A-Record lookup is done in DNS to resolve the host name to an IP
address. Transport and port specified in the entity link are used. If you selected the check
box, a full DNS lookup (as described in RFC 3263) is done, and the transport and port
specified in the entity link could be overridden.
Creating SIP Entities
About this task
Use the SIP entities screen to create SIP entities. To administer minimal routing via Session
Manager, you need to configure a SIP entity of type Communication Manager and a second
SIP entity of type Session Manager.
Procedure
1. On the System Manager console, under Elements, click Routing.
2. Click Elements, click Routing.
3. Click Routing > SIP Entities.
4. Click New.
5. Enter the Name of the SIP entity in the Name field.
6. Enter the FQDN or IP address of the SIP entity in the FQDN or IP Address field.
7. Select the type of SIP entity from the drop-down menu in the Type field.
8. If you need to specify the Location for the SIP entity, click the drop-down selector
for the Location field and select a location.
Managing Session Manager routing
278 Administering Avaya Aura
®
Session Manager November 2010
Comments? [e-mail]