ConfDeviceProfileDN

Configuring the Device Profile DN

The cluster switch can support multiple Device Profile DNs (Voice over IP Service DNs of type device-profile). These DNs are used to configure the DN-level parameters that SIP Server dynamically assigns to the device participating in a call.

Configure the Voice over IP Service DN for device-profile

On the Options tab, configure the following parameters:

1. service-type—Enter device-profile.
2. profile-id—Enter a value to identify this profile. SIP Server assigns the profile to a device by matching this value to the content of the User-Agent header in the SIP message. If no device profile is found, then a default device is created (in other words, all device parameters will have default values). The value of the profile-id parameter must either match the value of the User-Agent header or it can be defined as a substring which can be found in the User-Agent header.
   Notes:
   
   • The string is case-sensitive.
   • There is no default value.
   • Changes take effect for the next call.
   • You can set the profile-id to the special value of default-profile. SIP Server uses this profile to handle any device that does include the User-Agent header in its SIP messages (and so cannot be used to match a specific device profile).

A Device Profile DN, set to the default-profile

Device-profile selection process for 3pcc calls

Device profile is selected based on the User-Agent header value received in one of the the SIP messages from the device. If this information is not available, then in all the following scenarios, the default device profile is used. If the default-profile is not created, then all device parameters take their default values.

Scenario	Description
Destination device in any call scenario	Original outgoing INVITE sent to a call destination is always created using default-profile. If the device supplies the User-Agent header in the response to the outgoing INVITE sent by the SIP Server, then this information is used to select the device profile for the device and to replace the existing one.
Origination device in 1pcc inbound call	Device profile is assigned based on the User-Agent header received in the INVITE message from the originating the call.
Origination device of TMakeCall	If the User-Agent header is submitted in the SIP REGISTER request received from this device, then the matching device profile is used.
Origination device of TInitiateCall/TInitiateConference	The consultation call origination device uses the same device profile as the one used for this device in the main call.