# SIP Peer Profile Assignment by Incoming DID

## Purpose

This form can be used to assign incoming digits from both SIP Service Providers and Gateways. You can associate a telephone number assigned by a SIP Service Provider to a particular SIP Peer based on the information present in the Request-URI. Typically, the Service Provider provides a range of numbers.

All incoming calls should be authenticated by challenge-based authentication or by verifying the caller's IP address. When entries are added to this form, ensure that the appropriate authentication is enabled in the SIP Peer Profile form to prevent unauthorized incoming calls. In some rare instances, such as when receiving calls with a tel:: URI, no other authentication may be available.

If a dialed incoming number is not provisioned in this form, MiVoice Business will attempt to match the peer's incoming address to one of the configured SIP Peer Profile forms based on the information present in the Request-URI. If it finds one that matches, it will use this form and apply the policy based on the matched SIP Peer Profile.

The first address compared against is the "Alternate Destination Domain", if configured and enabled. If not enabled, the incoming address is compared to the IP Address or FQDN programmed in the Network Elements form associated with each SIP Peer profile.

If no match is found, a SIP "404 Not Found" message is returned. If this message is received when the number does exist, you may need to enter the DID range in this form and associate a SIP Peer profile to the number(s).

Use this form when performing the following tasks:

- Program SIP Trunks

## Field Descriptions

Parameter | Description | Default Value
Incoming DID Range | Enter one or more telephone numbers or identifiers as provided by your service provider. The maximum number of digits per telephone number is 26. You can enter a mix of ranges and single numbers (for example, "6135554000-6135554400,6135554500"). The entire field width is limited to 60 characters. Use a comma to separate telephone numbers/identifiers and ranges. Use a dash (-) to indicate a range of telephone numbers. The first and last characters cannot be a comma or a dash. If the entries do not fit within the 60 character maximum, you can create a new entry for the same profile. Use a '*' to reduce the number of entries that need to be programmed. This is a type of "prefix identifier", and cannot be used as a range with '-'. For example, the string "11*" would be used to associate a peer with any number in the range from 110 up to the maximum digits per telephone number (In this case, 11999999999999999999999999.) Note that the string "11" by itself would not count as a match, as the '*' represents 1 or more digits. The following combinations are valid: 0010* 2000-3000,55*,8000 50*,33* The following combinations are invalid: 55*-66* cannot use as a range 55*,5505 overlapcan In addition to numeric characters, you can also enter alphanumeric single identifiers, including identifiers with special characters !$%&'()*+-./;=?_~ within single quotation marks ('). If the identifier provided by your service provider is rejected, add the identifier within single quotation marks ('). For example the following combinations are valid within single quotation marks ('): 'CCT-U57-x1','CCT-U57-x2' 'Trk!1000' NOTE: Error checking is performed on the digit strings entered, and overlaps are NOT allowed on a per entry and per form basis. For example, if a user added a single entry containing the following "6000-7000, 6500", an error would be generated since "6500" is covered by "6000-7000". On the other hand, if there is an entry that uses the string "6000-7000,7200", and the user added a new entry "7100-8000", this entry would be rejected since it conflicts with the previous entry ("7200" lies between the range of "7100-8000"). | Blank
SIP Peer Profile Label | Select the SIP Peer label. These are defined in the SIP Peer Profile form. | Blank
Comment | Optional. Use this field to record information that may be use to you or others later on. | Blank