Alberto Montilla Mon, 04/27/2009 - 10:03

Dear Sir;

No guide is available but please find attached the instructions. As you may already know, please be aware that SPA9XX family is provisioned as a SIP third party end point, meaning you need the DLUs required for activating the product as basic or advanced. SPA922 can be configured as basic as it is one line.

CallManager Configuration

The CallManager configuration required to support a SPA9xx series phone is straightforward.  The minimum configuration required is the creation of a CallManager end user record, and the creation of a ‘third-party SIP device’ record.

End User Configuration

The end user record should be created first.  This user record is associated with the third-party SIP device record, and is used to map the incoming SIP registration from the phone to the third-party SIP device record.  When the phone registers with CallManager, it authenticates using the credentials of this user record, and each user record is associated with at most, one third-party SIP device record.  This allows CallManager to associate each phone with the appropriate configuration record.

There are no specific requirements for the user record configuration beyond the minimum configuration required by CallManager.  The important parameters from the perspective of the SPA9xx phone are the username and password.  Beyond this, the end user record should be configured according to the requirements of the CallManager installation and in accordance with the Cisco Unified CallManager Administration Guide.

Third-Party SIP Device Configuration

Two types of third-party SIP device are defined in CallManager - Basic and Advanced.  Basic SIP devices are defined as single-line devices with no video capability, while advanced devices support either multiple lines, or video capability.  Note that a multi-line device such as a SPA962 may be associated with a basic device record, but in that event, it may only be configured with a single line.

Regardless of which device type is selected, the steps required to configure the device are the same in each case.  Details of the configuration process may be found in the Cisco Unified CallManager Administration Guide, and this process should be followed while taking note of the following points:

·      An MRGL supporting only unicast music-on-hold should be selected, as the SPA9xx phones do not support the CallManager implementation of multicast music-on-hold

·      The username of the end user record created above should be selected as the ‘Digest User’ under the ‘Protocol Specific Information’ section of the configuration page

Optional Configuration

In addition to the above, the following, optional configuration may be applied:

·      Navigate to System > Enterprise Parameters > CCMUser Parameters and change the ‘Show Call Forwarding’ setting to ‘False’.  This will prevent conflicts between call forwarding settings applied through the phone user interface and those applied through the CCMUser web page.

SPA9xx Configuration

The configuration of the SPA9xx series phone is also relatively straightforward, with a relatively small number of parameters requiring modification to allow interoperability with CallManager.  Note that this section only addresses configuration parameters relating to CallManager interoperability.  Parameters that affect the user experience, or those required to localise the phone to the country in question, are not addressed unless that parameter has an impact on interoperability with CallManager.

The following configuration settings are required to allow the SPA9xx phone to register with CallManager and to make and receive calls:

Parameter

Comments

Ext ‘x’ Tab
Proxy & Registration

Proxy

The proxy field should be that of an appropriate call processing server.  Can be set to an IP address of host name.  A UDP port may also be specified.

User ID

The ‘User ID’ field should be set to the directory number associated with that line in CallManager

Password

The ‘Password’ field should be set to the password for the end user record in CallManager that is discussed above

Use Auth ID?

Set to ‘Yes’

Auth ID

The ‘Auth ID’ should be set to the user ID of the end user record in CallManager that is discussed above



SIP Tab
Linksys Key System

Linksys Key System

Set to ‘No’ to prevent the generation of unnecessary multicast traffic

Regional
Call Progress Tones

Holding Tone

If music-on-hold is in use, then this field should be set to blank.  This prevents the phone generating tone-on-hold over the top of the music being played.

Phone Tab
General

Station Name

The station name parameter controls the label displayed at the top right corner of the phone display.  The equivalent label on a 79xx series phone is typically set to the directory number of the phone combined with the ‘External Number Mask’

Voicemail Number

Setting the voicemail number to the voicemail pilot number associated with the CallManager system allows the operation of the envelope button on the phone

Phone Tab
Line Key ‘x’

Short Name

This parameter controls the label displayed next to the line button on the phone.  On the 79xx series phones, this is typically set to the extension number associated with that line.

Phone Tab
Supplementary Services

Blind Transfer Serv.

Set to ‘No’ to prevent the BTXFR softkey from being displayed.  The TXFR softkey can provide both attended and unattended transfer service in the CallManager environment.

Cfwd Busy Serv.

Set to ‘No’ to prevent conflict between call forward settings on phone and call forward settings in CallManager.  Call forward busy setting may be controlled by CallManager administrator.

Cfwd No Ans Serv.

Set to ‘No’ to prevent conflict between call forward settings on phone and call forward settings in CallManager.  Call forward no answer setting may be controlled by CallManager administrator.

Ext ‘x’ Tab
Dial Plan

Dial Plan

The ‘Dial Plan’ field should be set to a dial plan string that incorporates all the valid, dialable numbers for the installation, including valid PSTN number patterns, as well as internal extension ranges.

Enable IP Dialing

This should be set to ‘No’ as CallManager does not support IP dialing.

User Tab
Call Forward

Cfwd Busy Dest.

This field should be left blank to avoid any conflict with the call forward settings in CallManager.

Cfwd No Ans Dest.

This field should be left blank to avoid any conflict with the call forward settings in CallManager.



Regards
Alberto



Actions

This Discussion