Linksys SPA9000 Administrator Guide

Version 3.0

Corporate Headquarters Linksys 121 Theory Drive Irvine, CA 92617 USA http://www.linksys.com Tel: 949 823-546-5797 Fax: 949 823-1100
Specifications are subject to change without notice. Linksys is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. Other brands and product names are trademarks or registered trademarks of their respective holders. Linksys SPA9000 Administrator Guide Copyright 2006 Cisco Systems, Inc. All rights reserved.

CONTENTS

Preface
Document Audience xi How This Document is Organized Document Conventions xii Related Documentation Technical Support

xiii xiii xii

CHAPTER
Using the Linksys Voice System
The Linksys Voice System 1-1 Overview 1-1 SPA400 SIP-PSTN Gateway and Voicemail 1-2 Auto-Attendant 1-3 SPA9000 System Features 1-3 Additional Features When Used with SPA900 Series IP Phones Technology Background 1-6 Session Initiation Protocol 1-6 SPA9000 Media Proxy 1-7 Using the SPA9000 with a Firewall or Router 1-8 SPA400 SIP-PSTN Gateway 1-8 Network Address Translation (NAT) 1-9 NAT Overview 1-9 NAT Types 1-10 Simple Traversal of UDP Through NAT 1-10 SIP-NAT Interoperation 1-11 SPA9000 Architecture 1-11 Architectural Components 1-12 Multicast Addressing and Group Paging 1-13 Configuration Options 1-14 Interactive Voice Response 1-14 Setup Wizard 1-14 Administration Web Server 1-14 Local Client Configuration and Registration
Linksys SPA9000 Administrator Guide Version 3.0

Contents

Remote Provisioning of the SPA9000 Where to Go From Here

Getting Started

Implementing LVS 6-1 Using the SPA9000 and SPA400 as a VoIP PBX System Using the SPA9000 as a Media Proxy 6-3 Using the LVS as a Key System 6-3 SPA9000 Hardware 6-4 SPA9000 Back Panel 6-5 The Front Panel 6-5 SPA400 Hardware 6-6 Bandwidth Requirements 6-6 Caring for Your Hardware 6-7 Making the Physical Connections 6-8 Using the Interactive Voice Response Interface 6-9 Using the IVR Menu 6-9 IVR Options 6-10 Entering a Password through the IVR 6-12 Initial Setup and Configuration 6-13 Licensing 6-13 Using DHCP or Static IP Addressing 6-13 Using the Wizard for Initial Configuration 6-14 Using the Wizard to Upgrade Software 6-19 Setting the SPA9000 Administrator Account Password Using the Administration Web Server 6-23 Connecting to the Administration Web Server Administrator Account Privileges 6-25 Advanced Methods of Configuration 6-26 Web Interface URLs 6-26 Upgrade URL 6-26 Resync URL 6-26 Reboot URL 6-27 Provisioning 6-27 Provisioning Capabilities 6-27 Configuration Profile 6-28 Client Auto-Configuration 6-29 Manual Client Configuration 6-30 Client Registration
Troubleshooting and Configuration FAQ
Configuring Voice Service and Voicemail Completing the Voicemail Configuration

3-1 3-1

Using the Wizard to Configure ITSP Voice Services and Voicemail
Configuring the SPA400 for PSTN Connectivity or Voicemail 3-8 Understanding How the SPA400 Interacts with the SPA9000 3-8 Using the SPA9000 Setup Wizard to Configure the SPA400 3-8 Using the Administration Web Server to Configure the SPA400 3-11 Accessing the Administration Web Server 3-12 Configuring the SPA400 to Connect to the SPA9000 3-12 Configuring the SPA9000 to Register the SPA400 3-15 Configuring the SPA400 Voicemail Services 3-15 Configuring the SPA9000 Voicemail Settings 3-16 Configuring SPA400 Voicemail Accounts 3-17 Configuring a SPA IP Phone for Voice Mail Service SPA400 Voicemail Options

3-20 3-18

Managing Voicemail 3-20 How Voicemail Works 3-21 Checking Voicemail from an External Number Depositing Voicemail 3-22 Subscribing to Voicemail Notification 3-23
Configuring SPA9000 Features

4-1 4-1

Using the Wizard to Configure SPA9000 Voice Features Configuring Client Stations 4-2 Configuring Client Extensions 4-4 Configuring Shared Extensions 4-5 Configuring a Call Hunt Group 4-6 Using the Wizard for Localization 4-7 Using Dial Plans 4-9 Configuring Dial Plans 4-9 Dial Plan Digit Sequences 4-9 Dial Plan Rules 4-10 Dial Plan Examples 4-11 Dial Plan Timers 4-12 Interdigit Long Timer 4-12 Interdigit Short Timer 4-12

Dial Plans

Basic Call Management 4-13 Receiving External Phone Calls 4-13 Calling Between Client Stations 4-13 Client Stations Calling an External Number 4-14 External Users Calling the SPA9000 4-15 Supporting Multiple DID Numbers Per Line Interface
Managing Call Forwarding 4-17 How Call Forwarding Works 4-17 Using Call Hunt Groups 4-19 Overview 4-19 Configuring a Hunt Group Rule 4-19 Using the Contact List Parameter 4-20 Using the Administration Web Server to Configure Hunt Groups 4-21 Client Station Blind Transfers External Caller To DID/Hunt Group 4-22 Using Shared Line Appearance 4-22 Managing Call Pickup 4-25 Directed Call Pickup 4-25 Group Call Pickup 4-26 Call Park and Pickup 4-26 Multicast and Group Paging

SIP Settings 6-49 Subscriber Information 6-51 Dial Plan 6-53 NAT Settings 6-55 Proxy and Registration 6-55

APPENDIX

Acronyms Glossary
The LVS 9000 solution includes a line of IP communication products including desktop IP phones, an IP PBX, and PSTN gateway This guide describes basic administration and use of the Linksys SPA9000 IP PBX and the SPA400 PSTN gateway. It contains the following sections:
Document Audience, page xi How This Document is Organized, page xii Document Conventions, page xii Related Documentation, page xiii

Document Audience

This document is written for the following audience:
Service providers offering services using LVS products VARs and resellers who need LVS configuration references System administrators or anyone who performs LVS installation and administration This guide does not provide the configuration information required by specific service providers. Please consult with the service provider for specific service parameters.
Preface How This Document is Organized
How This Document is Organized
This document is divided into the following chapters and appendices. Chapter Chapter 1, Using the Linksys Voice System. Chapter 2, Getting Started. Chapter 3, Configuring Voice Service and Voicemail. Chapter 4, Configuring SPA9000 Features. Contents This chapter introduces the SPA9000 IP PBX and the SPA400 PSTN gateway. This chapter describes how to establish connectivity between the SPA9000, the SPA400, and other components. This chapter describes how to configure voice services and SPA400 or ITSP-hosted voicemail. This chapter describes how to configure SPA9000 features.
Chapter 5, Configuring the LVS This chapter describes how to configure or write XML scripts for the Auto-Attendant Auto-Attendant. Chapter 6, SPA9000 Field Reference Appendix A Acronyms. Appendix B Glossary. This chapter lists the function and usage for each field or parameter on the SPA9000 administration web server pages. This appendix provides the expansion of acronyms used in this document. This appendix defines the terms used in this document.

Document Conventions

The following are the typographic conventions used in this document. Typographic Element Boldface <parameter> Meaning Indicates an option on a menu or a literal value to be entered in a field. Angle brackets (<>) are used to identify parameters that appear on the configuration pages of the SPA9000 administration web server. The index at the end of this document contains an alphabetical listing of each parameter, hyperlinked to the appropriate table in Chapter 6, SPA9000 Field Reference Indicates a variable that should be replaced with a literal value. Indicates code samples or system output.

Getting Started Troubleshooting and Configuration FAQ
This section provides solutions to problems that may occur during the installation and operation of the SPA9000. If you can't find an answer here, check the Linksys website at www.linksys.com.
1. The SPA9000 did not automatically assign an extension number to the Linksys IP Phone, and the phone Ext LED is yellow instead of green. There are two solutions to the common causes of this problem. First solution: A. Connect an analog phone to the SPA9000 and access the IVR by pressing ****. B. Press 180# to hear the multicast address and port assigned to the SPA9000. C. If the problem is with a SPA901, perform these steps to verify and correct the multicast address: Use option 180# on the IVR to determine the multicast address of the phone that is not getting configured.
If the addresses or ports are different, press 181# to set the address and port of the phone to match the SPA9000. Use a * to separate each set of digits in the IP address and before the port number.
D. If the problem is with any SPA900 Series phone with an LCD display, perform these steps to verify and correct the multicast address: Press the Menu button (to the right of the 6) and scroll down to Network and press Select.
Scroll to the bottom of the Network list (you can get there quickly by pressing the up arrow) and view the Multicast Address. If the address and port does not match the SPA9000, press Edit, and enter the correct address and port. Then press OK.
E. Restart the SPA900 Series phone. Second solution: A. Open the web browser on the administration computer. B. Enter http://ipaddress/admin/router/status. C. Write down the Current IP of the SPA9000. (This is the Internet IP address.) D. Access the phone administration web server at the following URL: http://phone_ip_address/ To determine the IP address of the phone, press the Menu button and select Network from the LCD menu. For a SPA901 phone, use IVR option 110#. E. Make sure the configured proxy server on the phone matches the SPA9000 IP address. (Refer to the phone documentation for details.) 2. The IP phone can make internal calls to other IP phones and analog phones but it cannot make external calls. Check to see if the SPA9000 line is registered. Follow these steps: A. Open the web browser on the administration computer. B. Enter http://ipaddress/admin/voice/advanced. C. On the Voice - Info screen, check to see if the Line 1 Status indicates that the Registration State says, Registered. D. If it is not registered, then verify that the User ID, Proxy, and Password supplied by your Internet Telephony Service Provider (ITSP) are valid (these settings are configured on the Line page).

The Ethernet port on the SPA9000 is not intended for use to connect the device to the network.
B. Direct your web browser to the following URL: http://192.168.0.1/admin/router/status C. If you do not get a response, ping the interface to verify that it is working, or use IVR option #210 to verify the address on the LAN interface. D. Click PBX Status on the Line tab. 12. How do I access the SPA9000 if I forget my password? By default, the Admin account has no password. If a password is set for this account and you do not know what it is, you have to reset the device to its factory defaults. There are two options for resetting the device: Option 877778 resets the unit to the configuration shipped from the ITSP and erases any configuration completed locally by the user. Option 73738 resets the unit to the configuration shipped by Linksys and erases local configuration any provisioning configured by the ITSP. To reset the SPA9000 to the factory defaults, perform the following steps: A. Connect an analog phone to the SPA9000 and access the IVR by pressing ****. B. Press 877778# to reset the unit to the defaults as it shipped from the ITSP or press 73738# to reset the unit to the defaults as it shipped from Linksys.
C. Press 1 to confirm the operation. Press * to cancel the operation. D. Login to the unit using the Admin account without a password and reconfigure the unit. 13. My SPA9000 is behind a NAT device or firewall and Im unable to make a call or Im only receiving a one-way connection. What should I do? A. Configure your router to port forward TCP port 80" to the ip address currently being used by SPA. If you do this often, we suggest that you use static IP address for the SPA, instead of DHCP. (For help with port forwarding, consult your router documentation) B. On the Line tab of the administration web server, change the value of <Nat Mapping Enable> to yes. On the SIP tab; change <Substitute VIA Addr> to yes, and <EXT IP> to the IP address of your router. C. Make sure you are not blocking the UDP PORT 5060,5061 and port for UDP packets in the range of 16384-16482. Also, disable SPI if this feature is provided by your firewall. Identify the SIP server to which the SPA9000 is registering, if it supports NAT, using the <Outbound Proxy> parameter. D. Adjust the NAT keepalive variables as follows: E. Check the following settings on the administration web server: F. Add a STUN server to allow traversal of UDP packets through the NAT device. On the SIP tab of the administration web server, set <STUN Enable> to yes, and enter the IP address of the STUN server in <STUN Server>. STUN (Simple Traversal of UDP through NATs) is a protocol defined by RFC 3489, that allows a client behind a NAT device to find out its public address, the type of NAT it is behind, and the port associated on the Internet connection with a particular local port. This information is used to set up UDP communication between two hosts that are both behind NAT routers. Open source STUN software can be obtained at the following website: http://www.voip-info.org/wiki-Open+Source+VOIP+Software

Select Client Shared Extensions from the Advanced Feature Menu (see Figure 4-6).
Figure 4-6 Client Shared Extensions Option
The system displays the page shown in Figure 4-7.
Figure 4-7 Configuring Internal Shared Extensions
Configure the lines that you want to share and click Submit.
Configuring a Call Hunt Group
A hunt group is a number of extensions that ring when a number is dialed. The call is answered by the first extension that picks up the call. Extensions can be alerted simultaneously or sequentially. See the description of the <Hunt Groups> and the <Contact List> parameters about how to specify a hunting rule. Note that <Contact List> is a per line interface parameter and is applicable to that line interface only. For information about using the administration web server to configure hunt groups, see the Using Call Hunt Groups section on page 4-19. To use the Setup Wizard to configure a hunt group, complete the following steps.
Select Hunt Group from the Advanced Feature Menu (see Figure 4-8).
Figure 4-8 Hunt Group Option
The system displays the page shown in Figure 4-9.

Figure 4-9

Configure Hunt Groups
Click Add Hunt Group to add a group. Click Edit to change an existing group, or click Delete to remove a group. When you click Add Hunt Group, the system displays the page shown in Figure 4-10.
Figure 4-10 Configure Hunt Group
Identify the hunt group and click OK. When the next screen reappears, the new hunt group is added. Click Submit to create the hunt group.
Using the Wizard for Localization
To use the wizard for setting localization settings for the SPA9000, complete the following steps.
Select Configure Advanced Features from the Main Menu. The system displays the Advanced Feature Menu (see Figure 4-11)
Figure 4-11 Advanced Features Menu
Select Localization from the Advanced Feature Menu. The system displays the Localization page (see Figure 4-12)
Figure 4-12 Localization WizardPage 1

Step 3 Step 4 Step 5

Select the correct value for your location from each of the pull-down selection lists. To resync the time with the local administration PC, click Resync to PC time. Click Submit. The system enables the selected options and returns to the Advanced Features menu.
Configuring SPA9000 Features Using Dial Plans

none Do not bridge call transfer (use the normal REFER method) all Bridge all call transfer all except same lineBridge call transfer only if it is between two different line interfaces

REGISTER Enhancement

This enhancement is related to how the SPA retries the SIP REGISTER operation when the current REGISTER has failed. In previous versions of the SPA9000, three parameters, available on the SIP tab of the administration web server, have been used to control the interval between retries after a REGISTER failure:
<Reg Retry RSC> = A comma separated list of failure register response codes. When one of these codes occurs, the SPA9000 waits for a duration equal to the number of seconds defined in the <Reg Retry Invl> parameter. For other failure codes, the SPA9000 uses the value specified in the <Reg Retry Long Intvl> parameter. Note that if the REGISTER request times out waiting for a response, or if the request encounters an ICMP error, the SPA9000 always uses the value specified in the <Reg Retry Intvl> parameter
<Reg Retry Intvl> = Retry interval in seconds <Reg Retry Long Intvl> = Long retry interval in seconds
Chapter 4 Enhancements in Release 5.1
The first part of the REGISTER enhancement adds a randomized delay on top of the corresponding nominal retry interval:
<Reg Retry Random Delay> = range of randomized delay to add to <Reg Retry Intvl> before retrying REGISTER (when <Reg Retry Intvl> is applied) <Reg Retry Long Random Delay> = range of randomized delay to add to <Reg Retry Long Intvl) before retrying REGISTER (when <Reg Retry Long Intvl> is applied)
The second enhancement is to allow exponential back off of the <Reg Retry Intvl> for each retry until it reaches the maximum value defined in the <Reg Retry Intvl Cap> parameter. If the value of the <Reg Retry Intvl Cap> parameter is less than the <Reg Retry Intvl), the exponential back off feature is disabled.
Renew DHCP On SIP Request Timeout
The SPA9000 may sometimes have an invalid IP address even though the DHCP lease has not expired. In these cases, the SPA9000 may not receive any packets until it renews the IP address lease with the DHCP server. The Renew DHCP On SIP Request Timeout feature, introduced in Release 5.1, allows the SPA9000 to discover that the currently assigned IP address is no longer valid. This feature triggers a DHCP lease renewal whenever indicators suggest that the SPA9000 is not receiving packets. The SPA9000 periodically sends SIP requests to register, make calls, and so forth. Each SIP request normally receives a corresponding reply. If the SPA9000 fails to receive a reply to a SIP request this may indicate an invalid local IP address. With this enhancement, when the SPA9000 fails to receive a reply to a SIP request, a timer is started. If no reply to any SIP request is received before the timer expires, the SPA9000 automatically performs a DHCP lease renewal. If the renewal results in the same IP address, no further action is taken. If the renewal results in a new IP address assignment, the SPA9000 reboots.

This chapter describes how to configure the LVS Auto-Attendant using the IVR, the Setup Wizard, and XML scripting. This chapter contains the following sections:
Configuring Auto-Attendant, page 5-1 Downloading Prompts, page 5-8 Configuring Dial Plans for the Auto-Attendant, page 5-9 Alternative AA Configuration, page 5-10 Switching Between Alternative AAs Using the IVR, page 5-10 XML Scripting for the Auto-Attendant, page 5-13 AA XML Script Examples, page 5-17 Auto-Attendant XML Instructions Set, page 5-22
Configuring Auto-Attendant
This section describes how to configure the prompts and schedule for the Auto-Attendant and includes the following topics:
How the Auto-Attendant Works, page 5-1 Using the IVR to Record Auto-Attendant Prompts, page 5-2 Using the Wizard to Configure the Auto-Attendant, page 5-4 Using the Administration Web Server to Configure the Auto-Attendant, page 5-6
How the Auto-Attendant Works
The Auto-Attendant (aa) is an internal service within the SPA9000. It plays pre-recorded voice messages that offer the caller a menu of choices, so the Auto-Attendant can appropriately direct the call. For example, a greeting could be, Welcome to the abc company. For sales, press 1. For service, press 2. To speak to our operator, press 3. (This is a custom greeting, which you could record using the IVR Menu.) After the caller has made a choice, the call is routed to the appropriate extension. There are three Auto-Attendants available, one for daytime, one for nighttime, and one for weekend or holidays.
Chapter 5 Configuring Auto-Attendant
The daytime Auto-Attendant is preconfigured and enabled by default, and the first message it plays (Prompt ID 1) is suitable for business hours. If you want a caller to hear a different greeting during nighttime (non-business) hours, then you should record a new prompt, such as Prompt ID 5, using the Interactive Voice Response Menu and then configure the Auto-Attendant settings using the administration web server. For example, Prompt ID 5 could say, The company is currently closed. Our business hours are 9 AM to 5 PM, Monday to Friday. When the Auto-Attendant is enabled, it parses and operates on user input (key presses or DTMF tones) following the rules specified in the Auto-Attendant dial plan of the SPA9000. These rules are specified by the AA Dial Plan parameters found on the Voice - SIP screen of the administration web server. For information about configuring the AA Dial Plan, refer to the Configuring Dial Plans for the Auto-Attendant section on page 5-9. The Auto-Attendant allows users to save up to ten prompts. By default, AA fills the first four prompts as listed in Table 5-1.

Table 5-1 Prompts

Prompts ID Prompt1 Prompt2 Prompt3 Prompt4

Default Audio Content If you know your partys extension, you may enter it now. Your call has been forwarded. Not a valid extension, please try again. Goodbye
Users can listen, record, their customized greeting, menu, warning, ending, and so on from IVR, using code 72255. Users can also erase a recorded prompt from IVR. The recorded prompt is encoded with G711U and saved in flash. However, these customized prompts are erased when a factory reset is performed. The maximum length of each prompt is one minute. Users can customize up to 94.5 seconds of audio in addition to the default prompts. When there is not enough memory left, the IVR menu ends the recording automatically. The user can check the AA prompts status from the Auto-Attendant Prompt Status section on the administration web server Voice-Info page.
Using the IVR to Record Auto-Attendant Prompts
This section describes how to use the IVR to record the Auto-Attendant prompts using the IVR. To record Auto-Attendant prompts, complete the following steps from the IVR Menu.
Using an analog telephones connected to the SPA9000, press **** (in other words, press the star key four times). Wait until you hear the following prompt: Linksys configuration menu. Please enter the option followed by the # (pound) key or hang up to exit. Press 72255# to access the Auto-Attendant message settings. You hear, Please enter the message number followed by the # (pound) key. Enter the number of the message you wish to record, review, or delete. You hear, Enter 1 to record. Enter 2 to review. Enter 3 to delete. Enter * to exit. Press 1 on the phone to record a new message.

Chapter 5

Configuring the LVS Auto-Attendant Configuring Auto-Attendant
When the user presses this option, the IVR checks the available buffer size. If there is no more buffer capability, IVR plays the option failed message and returns to the previous menu.
If the buffer space is sufficient, you hear, You may record your message after the tone. When

finished, press #.

Record the new message and press #. After you record the message, you hear, To save, enter 1. To review, enter 2. To re-record, enter 3. To exit, enter *.
Press 1 to save the new recorded message. When recording finishes and the user agrees to save the prompt, if the recorded prompt is longer than 15 seconds, IVR plays a short one moment, please message to inform the user to wait for several seconds while the save is completed. Figure 5-1 shows the IVR prompt menu call flow.

Figure 5-1

IVR Prompt Menu Call Flow
User enters 72255 from IVR Menu-1 Play prompt (Please enter message number followed by the # key)
User enters prompt key (1-10) Goto menu-2 Menu-2 Play prompt (Enter 1 to record, enter 2 to review, enter 3 to delete, enter * to exit) Goto menu-1
User enters * User enters 2 User enters 1 Menu-3-A Play prompt (You may record your message after the tone. When finished, press #.) User records a prompt Menu-4-A Play prompt (to save enter 1, to review enter 2, to rerecord enter 3, to exit enter *.) User enters 3 Menu-3-B Play prompt (enter 1 to confirm, enter * User enters 1 Erase message Play prompt (Message erased.)

Alternative AA Configuration
The SPA9000 also supports nighttime AA, weekend AA, and holiday AA treatments. (See Figure 5-6.) When an alternate AA treatment is enabled, AA checks the current local time with the corresponding AA date/time range and decides which AA script and answer delay to use. The user needs to generate additional AA scripts for the weekend AA or holiday AA. The off-office AA script can be a very simple node form script. For example:
<aa> <form id= off-time> <audio src= prompt4 bargein= F/> <exit/> </form> </aa>
In this example, when a caller reaches the company at off hours, AA picks up the call and plays audio prompt4, and ends the call automatically by executing the exit/instruction.
The PBX administrator can manually change the current AA treatment using IVR option 79228# (see Table 5-3). The user needs to turn on the corresponding AA service to make this setting take effect.
0For auto AA treatment based on the <Day Time> <Weekends/Holidays> setting 1For day time AA treatment 2For night time AA treatment 3For weekend/holiday AA treatment
Configuring the LVS Auto-Attendant Switching Between Alternative AAs Using the IVR
If the corresponding AA service is not enabled, or there is no valid AA script for the specified AA service, changing the AA treatment has no effect. In this case, the value of the <Current AA> parameter on the Voice - Info page is Inactive.
Table 5-3 Parameter Descriptions
Parameter AA Dial Plan 1/2 AA Script 1/2/3
Description This describes the dial plan rule that the Auto-Attendant uses in a particular <form>. There are three parameters for storing Auto-Attendant scripts. One option is to use these as different treatments for daytime hours, nighttime hours, and weekends/holidays. Each parameter controls whether the corresponding Auto-Attendant service is enabled or disabled. The corresponding IVR code is 79228#
Daytime AA Nighttime AA Weekend/Holiday AA Daytime AA Script Nighttime AA Script Weekend/Holiday AA Script DayTime Answer Delay NightTime Answer Delay Weekend/Holiday Delay
This parameter specifies which script is used for a particular Auto-Attendant treatment. The choices are 1 for the AA script 1 setting, 2 for the AA script 2 setting, and 3 for the AA script 3 setting.
Each Auto-Attendant service has a corresponding delay setting, which is the number of seconds you want the Auto-Attendant to wait before answering. By default, the DayTime Answer Delay setting is 12 seconds. The NightTime and Weekend/Holiday Answer Delay settings are set to 0 (the Auto-Attendant answers immediately).

Dialplan Statement

The following dialplan statement determines the dialplan ID that the current menu dialog follows.
<dialplan src = dp1/>
The user input is passed by the dial plan first, then the passed result is fed into the menu instruction if the input matches a dial rule. Otherwise, AA executes the nomatch instruction, unless that instruction is empty.

AA Instructions

This section includes the following topics:
Audio Instruction, page 5-15 Action Instruction, page 5-15 Noinput Instruction , page 5-15 Nomatch Instruction, page 5-16 Menu Matched InstructionRecognition of Touch Tone (DMTP) Key Presses, page 5-16

Audio Instruction

The following is an example of the audio instruction:
<audio src= prompt1 bargein= T/>
AA plays the audio file specified in the src attribute. When playing the audio, AA allows the caller to interrupt the current prompt by pressing digits when the bargein attribute is set to T. AA ignores any digits from the caller if bargein is set to F. The default value of the bargein attribute is F. In a <form> dialog, if <audio> dialog is not been defined, AA does not play a prompt. If it is defined, AA first plays the specified prompt, then executes the action instruction described in the next section.

Action Instruction

The action includes:
gotoAA transfers the caller from one dialog state to the other dialog. All dialogs are identified by the attribute id. The value in the id attribute must be unique. Otherwise, AA selects the last valid dialog as the transfer target dialog. For example, <goto link= dir_dlg> xferAA blind transfers the caller to the target and AA ends. Example: <xfer name= Technical Support target= 5000/> The name attribute is optional. target attribute should be a valid target phone number.
exit When this action is reached, AA is stopped, and the call ends. For example, </exit>
In one dialog, only one action can be defined. After the xfer or exit action is performed, AA ends automatically.

Noinput Instruction

The following is an example of the noinput instruction:
<noinput timeout=5 repeat=T> <!audio instruction (optional) --> <!-- action instruction pair (optional) --> </noinput>
The <noinput> dialog can only be used in the menu dialog and is optional. When it is specified, AA executes the audio and action instructions if the user does not input any digits with the value of the <timeout> parameter, in seconds. If the repeat attribute is set to T, AA plays the menu prompt after playing the prompt specified in the <noinput> dialog and ignores the action instruction. If the value is F, AA executes the action instruction. The default value of the repeat attribute is F. Either the audio or the action instruction can be empty. If both are empty, AA does nothing and waits for user input.

Line Enable

Field Line Enable Description To enable this line for service, select yes. Otherwise, select no.

Network Settings

Field SIP ToS/DiffServ Value SIP CoS Value [0-7] RTP ToS/DiffServ Value Description TOS/DiffServ field value in UDP IP packets carrying a SIP message. The default is 0x68. CoS value for SIP messages. The default is 3. ToS/DiffServ field value in UDP IP packets carrying RTP data. The default is 0xb8.
Chapter 6 FXS 1/2 Tab (SPA9000)
RTP CoS Value [0-7] Network Jitter Level
CoS value for RTP data. The default is 6. Determines how jitter buffer size is adjusted by the SPA9000. Jitter buffer size is adjusted dynamically. The minimum jitter buffer size is 30 milliseconds or (10 milliseconds + current RTP frame size), whichever is larger, for all jitter level settings. However, the starting jitter buffer size value is larger for higher jitter levels. This setting controls the rate at which the jitter buffer size is adjusted to reach the minimum. Select the appropriate setting: low, medium, high, very high, or extremely high. The default is high. Controls how the jitter buffer should be adjusted. Select the appropriate setting: up and down, up only, down only, or disable. The default is up and down.

Jitter Buffer Adjustment

SIP Settings
Field SIP Port SIP Remote-Party-ID Description Port number of the SIP message listening and transmission port. The default is 5080. To use the Remote-Party-ID header instead of the From header, select yes. Otherwise, select no. The default is yes.

SIP Debug Option

SIP messages are received at or sent from the proxy listen port. This feature controls which SIP messages to log. The choices are as follows:
noneNo logging. 1-lineLogs the start-line only for all messages. 1-line excl. OPTLogs the start-line only for all messages except OPTIONS requests/responses. 1-line excl. NTFYLogs the start-line only for all messages except NOTIFY requests/responses. 1-line excl. REGLogs the start-line only for all messages except REGISTER requests/responses. 1-line excl. OPT|NTFY|REGLogs the start-line only for all messages except OPTIONS, NOTIFY, and REGISTER requests/responses. fullLogs all SIP messages in full text. full excl. OPTLogs all SIP messages in full text except OPTIONS requests/responses. full excl. NTFYLogs all SIP messages in full text except NOTIFY requests/responses. full excl. REGLogs all SIP messages in full text except REGISTER requests/responses. full excl. OPT|NTFY|REGLogs all SIP messages in full text except for OPTIONS, NOTIFY, and REGISTER requests/responses.

Proxy and Registration

Field Proxy Use Outbound Proxy Description SIP proxy server for all outbound requests. Enable the use of <Outbound Proxy>. If set to no, <Outbound Proxy> and <Use OB Proxy in Dialog) is ignored. The default is no. Outbound Proxy Use OB Proxy In Dialog SIP Outbound Proxy Server where all outbound requests are sent as the first hop. Whether to force SIP requests to be sent to the outbound proxy within a dialog. Ignored if <Use Outbound Proxy> is no or <Outbound Proxy> is empty. The default is yes.

Field Register

Description Enable periodic registration with the <Proxy>. This parameter is ignored if <Proxy> is not specified. The default is yes. Allow making outbound calls without successful (dynamic) registration by the unit. If No, dial tone will not play unless registration is successful. The default is no. Allow answering inbound calls without successful (dynamic) registration by the unit. If proxy responded to REGISTER with a smaller Expires value, the PAP2T will renew registration based on this smaller value instead of the configured value. If registration failed with an Expires too brief error response, the PAP2T will retry with the value given in the Min-Expires header in the error response. The default is 3600.
Expires value in sec in a REGISTER request. PAP2T will periodically renew registration shortly before the current registration expired. This parameter is ignored if <Register> is no. Range: 0 (231 1) sec

Make Call Without Reg

Register Expires

Ans Call Without Reg

Use DNS SRV DNS SRV Auto Prefix
Whether to use DNS SRV lookup for Proxy and Outbound Proxy. The default is no. If enabled, the PAP2T will automatically prepend the Proxy or Outbound Proxy name with _sip._udp when performing a DNS SRV lookup on that name. The default is no. This parameter sets the delay (sec) after which the PAP2T will retry from the highest priority proxy (or outbound proxy) servers after it has failed over to a lower priority server. This parameter is useful only if the primary and backup proxy server list is provided to the PAP2T via DNS SRV record lookup on the server name. (Using multiple DNS A record per server name does not allow the notion of priority and so all hosts will be considered at the same priority and the PAP2T will not attempt to fall back after a fail over). The default is 3600 PAP2T will make an internal list of proxies returned in DNS SRV records. In normal mode this list will contain proxies hierarchied by weight and priority if Based on SRV port is configured the PAP2T does normal first, and also inspect the port number based on 1st proxys port on the list. The default is Normal.

4-25 6-29 6-29 4-14, 6-15 4-34 4-9 6-7 6-30 6-30 6-58 6-30 6-30 6-16

Call 1 Decode Latency

Call Redial Code Call Return Code Call Routing Rule
call transfer bridge mode candidate sequences caring for hardware Cfwd All Act Code Cfwd All Deact Code CFWD Bridge Mode Cfwd Busy Act Code Cfwd Busy Deact Code
Call 1 Packet Error Call 1 Packets Lost Call 1 Packets Recv Call 1 Packets Sent Call 1 Peer Name

Cfwd Dial Tone

6-24 6-30 6-30 6-30 6-30 6-34
configuration profile Configuration Wizard Main Menu
Cfwd Last Act Code Cfwd Last Deact Code
Cfwd No Ans Act Code Cfwd No Ans Deact Code Cfwd No Ans Delay check
Configure Advanced Features option Configure Client Stations option Configure SPA400 Confirm Tone

6-11 6-24 6-18 6-19 6-19

change greetings for Auto-Attendant administration web server port DHCP
6-10 6-11 6-11 6-11 6-11 6-11 6-11 6-10 6-10
Configure SPA9000 option connections network physical Contact List CPC Delay Current AA Current Time CW Act Code CPC Duration

6-14 6-8

Ethernet port address firmware version IP address
4-6, 4-15, 4-16, 5-6, 6-52 6-29 6-29 5-13, 6-5 6-2 6-30 6-31 6-31 4-33 6-31 6-31 6-31
LAN IP address MAC address network mask multicast address
primary DNS server WAN IP address CID Act Code CID Deact Code Client Certificate client configuration local manual
1-15 6-30 6-32 4-13 6-31 6-31 6-2
CWCID Act Code CWCID Deact Code CW Deact Code
static gateway IP address
CWFD Bridge Mode CW Per Call Act Code
CW Per Call Deact Code CWT1 Cadence CWT2 Cadence CWT3 Cadence CWT4 Cadence CWT5 Cadence CWT6 Cadence CWT7 Cadence
4-2 6-26 6-26 6-26 6-26 6-26 6-26 6-26 6-26 6-27
client registration client stations calling between configuring firmware

6-19 4-3

configuring with Wizard MAC address

4-3 6-32

CWT8 Cadence CWT Frequency

Conference Act Code

Conference Bridge Ports Conference Bridge URL Conference Tone configuration saving