SIP Entities

Last Updated : Dec 06, 2018 |

A SIP network consists of a number of SIP entities. Examples of a SIP Entity include:

  • Session Manager

  • Communication Manager

  • Session Border Controller

  • SIP trunks

With the Endpoint Concentrator type, you can have up to 1000 connections from a single IP address. The single IP address can be shared by multiple Windows instances running on a virtualized server. SIP Link Monitoring is disabled for this SIP Entity type.

When Session Manager receives a request where the host part of the request-URI is the IP address of the Session Manager, the Session Manager associates one of the administered domains with the port on which the request was received. For more information about failover groups, see Failover Groups.

In cases when Session Manager cannot associate any administered routing policies, the request is sent to the SIP entity that is administered as an outbound proxy. If no outbound proxy is provisioned, then Session Manager will proxy the request on its own.

The system searches the IP Address by default when any string is configured in the Credential Name. The Credential name is a regular expression string and follows Perl version 5.8 syntax. The following are examples of entering information in the Credential name:

  • For www.sipentity.domain.com, enter the string www\.sipentity\.domain\.com.

  • For 192.14.11.22, enter the string 192\.14\.11\.22.

  • You can search for a subset of the string or you can create a wild card search. For example, to search for domain.com as a substring, enter the string domain\.com.