[nickybrg]

<!--# The "Resync_Periodic" field defines the interval (in seconds) between 1 provisioning cycle and the rest. Since this is the stage 2 file, this is set to 86400 seconds (24 hours).-->
<Resync_Periodic group="Provisioning/Configuration_Profile">86400</Resync_Periodic>

what would you change this too? Any ideas?

It was 12 hours by default and we changed it to 24. We did it like this so

You provision the phone out of office hours - (Maintenance normally should be made out of office hours. )
timer will start from out of office hours.
Lke this the phone will provision every 24 hours, out of office hours. user will not notice because he/she will be out of office hours and cisco phonebook is always updated and config is accurate in case changes are made.

However I think we can increase this to a week. Let me know if you have any ideas on this.

[netswork]

Thanks for that info. I think one week would be a better time. What would be best is if the actual time could be set rather than starting a timer from the point of provisions. If we could set the time to resync during a time that best suited the customer would be an optimal solution. If a change was made to the phone that required a restart, I think that phone would be restarted then rather than waiting for a 24 hour restart period.

Its my understanding that an actual time can be set to resync in the later versions of firmware.

[efounco]

This is how "Resync_Periodic" works:

1. "Resync_Periodic" tells the phone, in seconds, how often the phone should check for provision changes on the network and/or reboot. This is set to 86400 (24 hours) by the default 3CX template. Also, this amount is offset by a random interval so that all the phones on the network don't re-sync at once.
2. "Resync_At_HHmm" specifics the time, in 24 hour format, when the phones should check for provision changes on the network and/or reboot. This is not defined by the default 3CX template and is blank by default. Also, this amount is offset by a random interval so that all the phones on the network don't re-sync at once.

When the phone re-syncs, unless there's a discrepancy between the 3CX provisioning template and the phone's settings, it shouldn't re-provision the phone.

OK, now let's assume that the phones are all connected and working properly. Someone receives a voicemail message because they are on vacation. The 3CX phone system turns the message waiting indicator on to indicate that there's a message waiting in voicemail. Unfortunately, when the phone re-syncs that night, it gets to this line in the 3CX provisioning template:

<Message_Waiting group="Info/Ext_1_Status">No</Message_Waiting>

and determines that there's a discrepancy in the phone's settings (because the value is Yes). Thus, it re-provisions the phone and reboots...

See the problem here? If you have "Resync_Periodic" defined in the 3CX provisioning template along with "Message_Waiting" set to "No", the phone will ALWAYS re-provision and reboot itself if there's a message waiting.

2 things become of this:

1. The phone re-provisions when it's not necessary
2. The message waiting indicator light gets turned off even if a message is waiting.

BTW, we have "Resync_Periodic" set to "" (nothing). We also added "Resync_At__HHmm" and set it to "0200" (2am). I like the ability to control approximately when my phones reboot versus being at the mercy of an amount with random intervals.

[netswork]

Thanks for your reply efounco.

What is the need for <Message_Waiting group="Info/Ext_1_Status">No</Message_Waiting> and can it just be removed?

[efounco]

Thanks for your reply efounco.

What is the need for <Message_Waiting group="Info/Ext_1_Status">No</Message_Waiting> and can it just be removed?

You can either comment it out or completely remove it. Anything that's not specifically assigned by the provisioning template is not modified when the phone re-provisions itself.

[nickybrg]

I followed your advice

Set MWI to yes
Set resync at 2am.
At 11 pm I left a voicemail MWI went on.
In the morning I came back - MWI was turned off.

Guess that this is not working. Can you send me your template as it is?

You are correct - the resync is resetting the lamp on the MWI indicator. But I cannot fix this whether I put Yes or no. The only workaround i see is to provision once a week. At least I have my MWI indicators for a week. Using SPA 502 504 508 509 525 - basically all the spa ranges.

The moment we nail this, we will issue an online update with all these changes. Before I want to make sure that everything is ok.

[nickybrg]

I confirmed - everything is ok.

The first prov will loose voicemail MWI only. from that point onwards, things will work perfectly.

Send me your template just in case. So I can compare it with ours and possibly take some ideas for improvement.
Thanks for the heads up.

[efounco]

Don't change the MWI value to Yes, just remove or comment the line out completely. When the phone reboots and re-provisions, you want the phone to retain it's setting prior to rebooting. The value could be yes or no, so you don't want to hard code a value into the provisioning template.

Here's a semi-recent copy of our provisioning template for the 504G+500S. It's been heavily modified since because I'm working on a script that interfaces with it to give us multi-extension capabilities without creating custom templates for each and every user.

Code: Select all

<?xml version="1.0"?>
<doc xmlns:tcx="http://www.3cx.com">
  <header>
    <type>phone-template</type>
    <version>22502</version>
    <time>2010-05-17 15:00:00</time>
    <name>Cisco SIP Phone</name>
    <url>http://www.cisco.com</url>
    <models>
      <model>Custom ( Cisco SPA-504G + SPA-500S)</model>
    </models>
    <description>Cisco SIP Phone</description>
    <parsers>
      <parser>BLF</parser>
    </parsers>
 <rebootParams>
      <event-name>reboot</event-name>
    </rebootParams>
 <resyncParams>
  <event-name>check-sync</event-name>
 </resyncParams>
 <firmwareParams>
  <event-name>check-sync</event-name>
 </firmwareParams>
 <dst variableName ="dstEnableDisable" enable ="Yes" disable = "No">
 </dst>
 <languages>
 <!--The first entry is the selected entry in management console-->
 <option value="English-US">
 <item name = "langwebUI">English-US</item>
 </option>   
 <option value="Deutsch">
    <item name = "langwebUI">Deutsch</item>
 </option>
 <option value="Espanol">
 <item name = "langwebUI">Espanol</item>
 </option>
 <option value="Francais">
 <item name = "langwebUI">Francais</item>
 </option>
 <option value="Italiano">
 <item name = "langwebUI">Italiano</item>
 </option>
 <option value="Nederlands">
 <item name = "langwebUI">Nederlands</item>
 </option>
 </languages>
 <timezoneParams param="time_timezone_linksys">
 <!--The first entry is the selected entry in management console-->
 <option value="GMT-05:00">GMT-5:00 (US Eastern Time, New York)</option>
 <option value="GMT-12:00">GMT-12:00 (International Date Line West)</option>
 <option value="GMT-11:00">GMT-11:00 (Midway Island, Samoa)</option>
 <option value="GMT-10:00">GMT-10:00 (US Hawaiian Time)</option>
 <option value="GMT-09:00">GMT-9:00 (US Alaska Time)</option>
 <option value="GMT-08:00">GMT-8:00 (US Pacific Time, Los Angeles)</option>
 <option value="GMT-07:00">GMT-7:00 (US Mountain Time, Denver)</option>
 <option value="GMT-06:00">GMT-6:00 (US Central Time, Chicago)</option>
 <option value="GMT-04:30">GMT-4:30 (Venezuela)</option>
 <option value="GMT-04:00">GMT-4:00 (Atlantic Time, Quebec)</option>
 <option value="GMT-03:30">GMT-3:30 (Newfoundland)</option>
 <option value="GMT-03:00">GMT-3:00 (Greenland)</option>
 <option value="GMT-02:00">GMT-2:00 (Mid-Atlantic)</option>
 <option value="GMT-01:00">GMT-1:00 (Azores, Cape Verdi Is.)</option>
 <option value="GMT">GMT(London, Dublin, Edinburgh, Lisbon, Casablanca, Monrovia)</option>
 <option value="GMT+01:00">GMT+1:00 (Paris,Amsterdam, Berlin, Rome, Vienna, Madrid, Warsaw, Brussels)</option>
 <option value="GMT+02:00">GMT+2:00 (Israel, Cairo, Athens, Helsinki, Istanbul, Buchrest)</option>
 <option value="GMT+03:00">GMT+3:00 (Moscow, Kuwait, Baghdad, Tehran, Nairobi)</option>
 <option value="GMT+03:30">GMT+3:30 (Tehran)</option>
 <option value="GMT+04:00">GMT+4:00 (Abu Dhabi, Baku)</option>
 <option value="GMT+04:30">GMT+4:30 (Kabul)</option>
 <option value="GMT+05:00">GMT+5:00 (Islamabad, Ekaterinburg, Karachi, Tashkent)</option>
 <option value="GMT+05:30">GMT+5:30 (Chennai, New Delhi, Mumbai)</option>
 <option value="GMT+05:45">GMT+5:45 (Kathmandu)</option>
 <option value="GMT+06:00">GMT+6:00 (Almaty, Astana. Dhaka, Novosibirsk)</option>
 <option value="GMT+06:30">GMT+6:30 (Rangoon)</option>
 <option value="GMT+07:00">GMT+7:00 (Bankok, Jakarta, Hanoi, Krasnoyarsk)</option>
 <option value="GMT+08:00">GMT+8:00 (Beijing, Singapore, Taipei, Kuala Lumpur, Irkutsk, Perth)</option>
 <option value="GMT+09:00">GMT+9:00 (Japan, Korea, Yakutsk)</option>
 <option value="GMT+09:30">GMT+9:30 (Adelaide, Darwin)</option>
 <option value="GMT+10:00">GMT+10:00 (Brisbane, Sydney, Melbourne, Canberra, Guam, Hobart)</option>
 <option value="GMT+11:00">GMT+11:00 (Magadan, Solomon Is., New Caledonia)</option>
 <option value="GMT+12:00">GMT+12:00 (Auckland, Wellington, Fiji)</option>
 <option value="GMT+13:00">GMT+13:00 (Nuku'alofa)</option>
 </timezoneParams>
 <Codecspriorities>
      <Codecspriority variableName="codec1" priority="1">
        <!--The first entry is the selected entry in management console-->
        <option value="G711u">G711u</option>
  <option value="G711a">G711a</option>
        <option value="G729a">G729a</option>
        <option value="G722">G722</option>
      </Codecspriority>
      <Codecspriority variableName="codec2" priority="2">
        <!--The first entry is the selected entry in management console-->
        <option value="G711a">G711a</option>
  <option value="G711u">G711u</option>
        <option value="G729a">G729a</option>
        <option value="G722">G722</option>
      </Codecspriority>
      <Codecspriority variableName="codec3" priority="3">
        <!--The first entry is the selected entry in management console-->
        <option value="G722">G722</option>
  <option value="G711u">G711u</option>
  <option value="G711a">G711a</option>
        <option value="G729a">G729a</option>
      </Codecspriority>
    </Codecspriorities>   
  </header>
    <blftype>
      <extension>
        <value>fnc=sd+blf+cp;</value>
      </extension>
   <speeddial>
        <value>fnc=sd;</value>
      </speeddial>
   <customspeeddial>
        <value>fnc=sd;</value>
      </customspeeddial>
      <queuelogin>
        <value>fnc=sd;</value>
      </queuelogin>
   <profilestatus>
        <value>fnc=sd;</value>
      </profilestatus>
   <parkextension>
        <value>fnc=sd+blf;</value>
      </parkextension>
  </blftype>
  <data>
    <device>
      <type>phone</type>
      <field name="Name">Cisco SIP Phone</field>
      <deviceconfig filename="%%mac_address%%.xml">
<![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<flat-profile>


<!--########################################################-->
<!--###           SIP Settings for Identity 1            ###-->
<!--###  Note: Access phone xml param console via        ###-->
<!--###           http://ip/admin/spacfg.xml             ###-->
<!--########################################################-->

<!--# The "Line_Enable_1_" field enables or disables Identity 1 on the phone. Valid values are "Yes"==Enable Identity; "No"==Disable Identity. The provisioning template sets the value to "Yes"==Enable Identity.-->
<Line_Enable_1_ group="Ext_1/General">Yes</Line_Enable_1_>

<!--# The "SIP_Port_1_" field specifies which port number the phone should listen on for SIP Traffic. Valid values are 1 to 65535. The provisioning template sets the value to 5060 which is the standard SIP Port.-->
<SIP_Port_1_ group="Ext_1/SIP_Settings">5060</SIP_Port_1_>

<!--# The "Referor_Bye_Delay_1_" field specifies the time that the cisco phone will track the call after a transfer. Default value is 4-->
<Referor_Bye_Delay_1_ group="Ext_1/SIP_Settings">0</Referor_Bye_Delay_1_>

<!--# The Extension Number must be specified in the "User_ID_1" field. The "extension_number" variable will be replaced by the Extension's Extension Number.-->
<User_ID_1_ group="Ext_1/Subscriber_Information">%%extension_number%%</User_ID_1_>

<!--# The "Use_Auth_ID_1_" field enables or disables the phone to use the Authentication ID to register itself with 3CXPS. Valid values are "Yes"==Register Using Authentication ID; "No"==Do Not Register Using Authentication ID. The provisioning template sets the value to "Yes"==Register Using Authentication ID.-->
<Use_Auth_ID_1_ group="Ext_1/Subscriber_Information">Yes</Use_Auth_ID_1_>

<!--# The Authentication ID must be specified in the "Auth_ID_1_" field. The "extension_auth_id" variable will be replaced by the Extension's Authentication ID.-->
<Auth_ID_1_ group="Ext_1/Subscriber_Information">%%extension_auth_id%%</Auth_ID_1_>

<!--# The Authentication Password must be specified in the "Password_1_" field. The "extension_auth_pw" variable will be replaced by the Extension's Authentication Password.-->
<Password_1_ group="Ext_1/Subscriber_Information">%%extension_auth_pw%%</Password_1_>

<!--# The "Display_Name_1_" field contains the Caller Name which the phone will send to 3CXPS. The "extension_first_name" and "extension_last_name" variables will be replaced by the Extension's First Name and Last Name.-->
<Display_Name_1_ group="Ext_1/Subscriber_Information">%%extension_first_name%% %%extension_last_name%%</Display_Name_1_>

<!--# The "Register_1_" field specifies whether the phone should register with the SIP Registrar - in this case 3CXPS. Valid values are "Yes"==Register with SIP Registrar; "No"==Do Not Register With SIP Registrar. The provisioning template sets this value to "Yes"==Register with SIP Registrar to enable interaction with 3CXPS.-->
<Register_1_ group="Ext_1/Proxy_and_Registration">Yes</Register_1_>

<!--# The "Proxy_1_" field contains the ip address and SIP port of the SIP Registrar and Proxy - in this case 3CXPS. The "pbx_ip" and "param::sipport" variables will be replaced by the IP Address and SIP Port of 3CXPS.-->
<Proxy_1_ group="Ext_1/Proxy_and_Registration">%%pbx_ip%%:%%param::sipport%%</Proxy_1_>

<!--# The "Use_Outbound_Proxy_1_" field specifies whether the phone should use an Outbound Proxy to deliver outgoing SIP messages. Valid values are "Yes"==Use Outbound Proxy; "No"==Do Not Use Outbound Proxy. The provisioning template sets the value to "No"==Do Not Use Outbound Proxy.-->
<Use_Outbound_Proxy_1_ group="Ext_1/Proxy_and_Registration">No</Use_Outbound_Proxy_1_>

<!--# The "DNS_SRV_Auto_Prefix_1_" field specifies whether the phone should make DNS lookups for SRV records when attempting to contact the Proxy or the Outbound Proxy. Valid values are "Yes"==Make DNS Lookups For SRV Records; "No"==Do Not Make DNS Lookups for SRV Records. The provisioning template sets the value to "No"==Do Not Make DNS Lookups for SRV Records.-->
<DNS_SRV_Auto_Prefix_1_ group="Ext_1/Proxy_and_Registration">No</DNS_SRV_Auto_Prefix_1_>

<!--# The "Register_Expires_1_" field specifies the length of time (in seconds) the phone will be registered with 3CXPS. The phone will attempt to re-register with 3CXPS before this time expires. The provisioning template sets the value to 900 (15 minutes). Valid values are any positive integer.-->
<Register_Expires_1_ group="Ext_1/Proxy_and_Registration">900</Register_Expires_1_>

<!--# The "Dial_Plan_1_" field specifies which number combinations are allowed. Since 3CXPS takes all necessary routing decisions directly, the dialplan is set to "[x*]." to allow any sequence of keys to be dialed and sent to 3CXPS.-->
<Dial_Plan_1_ group="Ext_1/Dial_Plan">[x*].</Dial_Plan_1_>

<!--# Auto_Ans_Page_On_Active_Call_1_" field prevents a call from being interrupted during a intercom or page.-->
<Auto_Ans_Page_On_Active_Call_1_ group="Ext_1/Call_Feature_Settings">No</Auto_Ans_Page_On_Active_Call_1_>

<!--#Audio configuration codec settings-->
<Preferred_Codec_1_ group="Ext_1/Audio_Configuration">%%codec1%%</Preferred_Codec_1_>
<Use_Pref_Codec_Only_1_ group="Ext_1/Audio_Configuration">No</Use_Pref_Codec_Only_1_>
<Second_Preferred_Codec_1_ group="Ext_1/Audio_Configuration">%%codec2%%</Second_Preferred_Codec_1_>
<Third_Preferred_Codec_1_ group="Ext_1/Audio_Configuration">%%codec3%%</Third_Preferred_Codec_1_>
<G729a_Enable_1_ group="Ext_1/Audio_Configuration">Yes</G729a_Enable_1_>
<G722_Enable_1_ group="Ext_1/Audio_Configuration">Yes</G722_Enable_1_>

<Extension_1_ group="Phone/Line_Key_1Phone/Line_Key_1">1</Extension_1_>
<Short_Name_1_ group="Phone/Line_Key_1">%%extension_auth_id%%</Short_Name_1_>
<Share_Call_Appearance_1_ group="Phone/Line_Key_1">private</Share_Call_Appearance_1_>
<Extended_Function_1_ group="Phone/Line_Key_1"></Extended_Function_1_>


<!--########################################################-->
<!--###            SIP Settings for Identity 2           ###-->
<!--########################################################-->

<Extension_2_ group="Phone/Line_Key_2">1</Extension_2_>
<Share_Call_Appearance_2_ group="Phone/Line_Key_2">private</Share_Call_Appearance_2_>
<Extended_Function_2_ group="Phone/Line_Key_2"></Extended_Function_2_>
<Short_Name_2_ group="Phone/Line_Key_2">%%extension_auth_id%%</Short_Name_2_>


<!--########################################################-->
<!--###            SIP Settings for Identity 3           ###-->
<!--########################################################-->

<Extension_3_ group="Phone/Line_Key_3">1</Extension_3_>
<Share_Call_Appearance_3_ group="Phone/Line_Key_3">private</Share_Call_Appearance_3_>
<Extended_Function_3_ group="Phone/Line_Key_3"></Extended_Function_3_>
<Short_Name_3_ group="Phone/Line_Key_3">%%extension_auth_id%%</Short_Name_3_>


<!--########################################################-->
<!--###         SIP Settings for Identity 4 (DID)        ###-->
<!--########################################################-->

<!--# The "Line_Enable_4_" field enables or disables Identity 4 on the phone. Valid values are "Yes"==Enable Identity; "No"==Disable Identity. The provisioning template sets the value to "Yes"==Enable Identity.-->
<Line_Enable_4_ group="Ext_4/General">Yes</Line_Enable_4_>

<!--# The "SIP_Port_4_" field specifies which port number the phone should listen on for SIP Traffic. Valid values are 1 to 65535. The provisioning template sets the value to 5060 which is the standard SIP Port.-->
<SIP_Port_4_ group="Ext_4/SIP_Settings">5060</SIP_Port_4_>

<!--# The "Referor_Bye_Delay_4_" field specifies the time that the cisco phone will track the call after a transfer. Default value is 4-->
<Referor_Bye_Delay_4_ group="Ext_4/SIP_Settings">0</Referor_Bye_Delay_4_>

<!--# The Extension Number must be specified in the "User_ID_4" field. The "extension_number" variable will be replaced by the Extension's Extension Number.-->
<User_ID_4_ group="Ext_4/Subscriber_Information">###Change This Value###</User_ID_4_>

<!--# The "Use_Auth_ID_4_" field enables or disables the phone to use the Authentication ID to register itself with 3CXPS. Valid values are "Yes"==Register Using Authentication ID; "No"==Do Not Register Using Authentication ID. The provisioning template sets the value to "Yes"==Register Using Authentication ID.-->
<Use_Auth_ID_4_ group="Ext_4/Subscriber_Information">Yes</Use_Auth_ID_4_>

<!--# The Authentication ID must be specified in the "Auth_ID_4_" field. The "extension_auth_id" variable will be replaced by the Extension's Authentication ID.-->
<Auth_ID_4_ group="Ext_4/Subscriber_Information">###Change This Value###</Auth_ID_4_>

<!--# The Authentication Password must be specified in the "Password_4_" field. The "extension_auth_pw" variable will be replaced by the Extension's Authentication Password.-->
<Password_4_ group="Ext_4/Subscriber_Information">###Change This Value###</Password_4_>

<!--# The "Display_Name_4_" field contains the Caller Name which the phone will send to 3CXPS. The "extension_first_name" and "extension_last_name" variables will be replaced by the Extension's First Name and Last Name.-->
<Display_Name_4_ group="Ext_4/Subscriber_Information">%%extension_first_name%% %%extension_last_name%%</Display_Name_4_>

<!--# The "Register_4_" field specifies whether the phone should register with the SIP Registrar - in this case 3CXPS. Valid values are "Yes"==Register with SIP Registrar; "No"==Do Not Register With SIP Registrar. The provisioning template sets this value to "Yes"==Register with SIP Registrar to enable interaction with 3CXPS.-->
<Register_4_ group="Ext_4/Proxy_and_Registration">Yes</Register_4_>

<!--# The "Proxy_4_" field contains the ip address and SIP port of the SIP Registrar and Proxy - in this case 3CXPS. The "pbx_ip" and "param::sipport" variables will be replaced by the IP Address and SIP Port of 3CXPS.-->
<Proxy_4_ group="Ext_4/Proxy_and_Registration">%%pbx_ip%%:%%param::sipport%%</Proxy_4_>

<!--# The "Use_Outbound_Proxy_4_" field specifies whether the phone should use an Outbound Proxy to deliver outgoing SIP messages. Valid values are "Yes"==Use Outbound Proxy; "No"==Do Not Use Outbound Proxy. The provisioning template sets the value to "No"==Do Not Use Outbound Proxy.-->
<Use_Outbound_Proxy_4_ group="Ext_4/Proxy_and_Registration">No</Use_Outbound_Proxy_4_>

<!--# The "DNS_SRV_Auto_Prefix_4_" field specifies whether the phone should make DNS lookups for SRV records when attempting to contact the Proxy or the Outbound Proxy. Valid values are "Yes"==Make DNS Lookups For SRV Records; "No"==Do Not Make DNS Lookups for SRV Records. The provisioning template sets the value to "No"==Do Not Make DNS Lookups for SRV Records.-->
<DNS_SRV_Auto_Prefix_4_ group="Ext_4/Proxy_and_Registration">No</DNS_SRV_Auto_Prefix_4_>

<!--# The "Register_Expires_4_" field specifies the length of time (in seconds) the phone will be registered with 3CXPS. The phone will attempt to re-register with 3CXPS before this time expires. The provisioning template sets the value to 900 (15 minutes). Valid values are any positive integer.-->
<Register_Expires_4_ group="Ext_4/Proxy_and_Registration">900</Register_Expires_4_>

<!--# The "Dial_Plan_4_" field specifies which number combinations are allowed. Since 3CXPS takes all necessary routing decisions directly, the dialplan is set to "[x*]." to allow any sequence of keys to be dialed and sent to 3CXPS.-->
<Dial_Plan_4_ group="Ext_4/Dial_Plan">[x*].</Dial_Plan_4_>

<!--# Auto_Ans_Page_On_Active_Call_4_" field prevents a call from being interrupted during a intercom or page.-->
<Auto_Ans_Page_On_Active_Call_4_ group="Ext_4/Call_Feature_Settings">No</Auto_Ans_Page_On_Active_Call_4_>

<!--#Audio configuration codec settings-->
<Preferred_Codec_4_ group="Ext_4/Audio_Configuration">%%codec1%%</Preferred_Codec_4_>
<Use_Pref_Codec_Only_4_ group="Ext_4/Audio_Configuration">No</Use_Pref_Codec_Only_4_>
<Second_Preferred_Codec_4_ group="Ext_4/Audio_Configuration">%%codec2%%</Second_Preferred_Codec_4_>
<Third_Preferred_Codec_4_ group="Ext_4/Audio_Configuration">%%codec3%%</Third_Preferred_Codec_4_>
<G729a_Enable_4_ group="Ext_4/Audio_Configuration">Yes</G729a_Enable_4_>
<G722_Enable_4_ group="Ext_4/Audio_Configuration">Yes</G722_Enable_4_>

<Extension_4_ group="Phone/Line_Key_4">4</Extension_4_>
<Short_Name_4_ group="Phone/Line_Key_4">DID</Short_Name_4_>
<Share_Call_Appearance_4_ group="Phone/Line_Key_4">private</Share_Call_Appearance_4_>
<Extended_Function_4_ group="Phone/Line_Key_4"></Extended_Function_4_>


<!--########################################################-->
<!--###          Generic SIP Or Phone Settings           ###-->
<!--########################################################-->

<!--# The "Station_Name" field contains the a name to identify the phone - typically visible at the top of the LCD display in later firmware versions. The "extension_first_name" and "extension_last_name" variables will be replaced by the Extension's First Name and Last Name.-->
<Station_Name group="Phone/General">%%extension_first_name%%</Station_Name>

<!--# The "Reorder_Delay" field defines after how many seconds the phone will play a Reorder Tone (fast busy) after the remote caller hangs up. Valid values a 0-254, and 255 which means that the phone will NOT play a Reorder Tone after the remote caller hangs up.-->
<Reorder_Delay group="Regional/Control_Timer_Values__sec_">255</Reorder_Delay>

<!--# The "Programmable_softkey_enable" enables the function of changing the function of the programmable call keys-->
<Programmable_Softkey_Enable group="Phone/Programmable_Softkeys">Yes</Programmable_Softkey_Enable>

<!--# The "Connected_Key_List" field defines which soft keys are visible while a call is connected. This template configured them to present the more commonly used functions in the main screen-->
<Connected_Key_List group="Phone/Programmable_Softkeys">confLx|7;flash|7;xferLx|2;conf|3;xfer|4;toggle|4;redial|5;dir|6;bxfer|1;park|8;phold</Connected_Key_List>

<!--# The "Interdigit_Long_Timer" specifies the maximum time (in seconds) allowed between dialed digits, when there is no match in the dialplan. Since the dialplan set by the provisioning template is "[x*]." (so any sequence will match), this is set to the default value of 10 seconds.-->
<Interdigit_Long_Timer group="Regional/Control_Timer_Values__sec_">12</Interdigit_Long_Timer>

<!--# The "Interdigit_Short_Timer" specifies the maximum time (in seconds) allowed between dialed digits, when there is a match in the dialplan. The provisioning template sets this value to 10 seconds.-->
<Interdigit_Short_Timer group="Regional/Control_Timer_Values__sec_">10</Interdigit_Short_Timer>

<!--#Reorganize default ring tones so that phone uses simple as default-->
<Ring1 group="Phone/Ring_Tone">n=Simple-1;w=2;c=1</Ring1>
<Ring2 group="Phone/Ring_Tone">n=Simple-2;w=2;c=2</Ring2>
<Ring3 group="Phone/Ring_Tone">n=Simple-3;w=2;c=3</Ring3>
<Ring4 group="Phone/Ring_Tone">n=Simple-4;w=2;c=4</Ring4>
<Ring5 group="Phone/Ring_Tone">n=Simple-5;w=2;c=5</Ring5>
<Ring6 group="Phone/Ring_Tone">n=Classic-1;w=3;c=1</Ring6>
<Ring7 group="Phone/Ring_Tone">n=Classic-2;w=3;c=2</Ring7>
<Ring8 group="Phone/Ring_Tone">n=Classic-3;w=3;c=3</Ring8>
<Ring9 group="Phone/Ring_Tone">n=Classic-4;w=3;c=4</Ring9>
<Ring10 group="Phone/Ring_Tone">n=Office;w=4;c=1</Ring10>
<Ring11 group="Phone/Ring_Tone">n=Pulse;w=5;c=1</Ring11>
<Ring12 group="Phone/Ring_Tone">n=Du-dut;w=6;c=1</Ring12>


<!--########################################################-->
<!--###                   SIP/SIP Parameters             ###-->
<!--########################################################-->

<!--This requires firmware spa50x-30x-7-4-8a and upwards. This parameter improves blind transfers via speed dials.-->
<Keep_Referee_When_REFER_Failed group="SIP/SIP_Parameters">Yes</Keep_Referee_When_REFER_Failed>


<!--########################################################-->
<!--###                   RTP Settings                   ###-->
<!--########################################################-->

<!--# The "RTP_Packet_Size" field specifies the packetization rate for each RTP packet delivering audio. Valid values are from 0.010 to 0.160 (in steps of 0.010). The provisioning template sets the value to 0.020 to ensure correct interaction with other phones, gateways, and voip providers which do not support non-standard values.-->
<RTP_Packet_Size group="SIP/RTP_Parameters">0.020</RTP_Packet_Size>


<!--########################################################-->
<!--### VoiceMail and Message Waiting Indicator Settings ###-->
<!--########################################################-->

<!--# The "Mailbox_ID_1_" field specifies the which identity represents the VoiceMail account at the Registrar - in this case 3CXPS. Since with 3CXPS the Extension Number represents the identity of both phone AND VoiceMail, this value must be the same as the Extension Number. The "extension_number" variable will be replaced with the phone's Extension Number.-->
<Mailbox_ID_1_ group="Ext_1/Call_Feature_Settings">%%extension_number%%</Mailbox_ID_1_>

<!--# The "Voice_Mail_Number" field contains the destination number for the VoiceMail service. The "vm_number" variable will be replacd by the 3CXPS VoiceMail Menu Extension Number.-->
<Voice_Mail_Number group="Phone/General">%%vm_number%%</Voice_Mail_Number>


<!--########################################################-->
<!--###         Provisioning Settings - Stage 2          ###-->
<!--########################################################-->

<!--# Linksys Provisioning is a 2-stage process. The phone will, by default after a factory reset, search for a configuration file "SPAxxx.cfg" (where xxx is the model number, so for example, for a Linksys SPA-962, the filename would be "spa962.cfg"). Since we need each phone to have a different extension number, in stage 2 we need to define a "<mac_address>.xml" file that instructs the phone to retrieve its own settings.-->
 
<!--# The "Resync_Periodic" field defines the interval (in seconds) between 1 provisioning cycle and the rest. Since this is the stage 2 file, this is set to 86400 seconds (24 hours).-->
<Resync_Periodic group="Provisioning/Configuration_Profile"></Resync_Periodic>
 
<!--# The "Profile_Rule" field defines the URL path and filename for the configuration file. This will be the configuration file for the stage 2, and there must have a phone-specific filename. The $MA is a Linksys Internal variable which represents the phone's MAC Address, so in stage 2 the phone will search for a filename such as "0001a2b3c4d5.xml". The provisioning template sets the value to "http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/$MA.xml".-->
<Profile_Rule group="Provisioning/Configuration_Profile">http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/$MA.xml</Profile_Rule>

<!--# The "User_Configurable_Resync" field defines whether a user can manually adjust the Provisioning Server from the Phone Keys directly. Valid values are "Yes"==Allow Adjustment of Provisioning Server from Phone; "No"==Do Not Allow Adjustment of Provisioning Server from Phone. The provisioning template sets the value to "Yes"==Allow Adjustment of Provisioning Server from Phone.-->
<User_Configurable_Resync group="Provisioning/Configuration_Profile">Yes</User_Configurable_Resync>

<!--# The "XML_Directory_Service_Name" and "XML_Directory_Service_URL" fields define the name and the provisioning location for the phone to retrieve the 3CX Company Phonebook.-->
<XML_Directory_Service_Name group="Phone/XML_Service">Eagle Foundry</XML_Directory_Service_Name>
<XML_Directory_Service_URL group="Phone/XML_Service">http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/cisco_phonebook_custom.xml</XML_Directory_Service_URL>


<!--########################################################-->
<!--###              Remote Reboot Settings              ###-->
<!--########################################################-->

<!--# The "Auth_Resync-Reboot_1_" field specifies whether a remote request to SIP Identity 1 on the phone to reboot should be authenticated. Valid values are "Yes"==Require Authentication for Remote Reboot; "No"==Do Not Require Authentication for Remote Reboot. The provisioning template sets the value to "No"==Do Not Require Authentication for Remote Reboot.-->
<Auth_Resync-Reboot_1_ group="Ext_1/SIP_Settings">No</Auth_Resync-Reboot_1_>

<!--# The "Blind_Attn-Xfer_Enable_1_" field specifies whether the phone should deliver an Attended Transfer request using the Blind Transfer mechanism instead. Valid values are "Yes"==Use Blind Transfer Mechanism for Attended Transfer Requests; "No"==Do Not Use Blind Transfer Mechanism for Attended Transfer Requests. The provisioning template sets the value to "Yes"==Use Blind Transfer Mechanism for Attended Transfer Requests.-->
<Blind_Attn-Xfer_Enable_1_ group="Ext_1/Call_Feature_Settings">Yes</Blind_Attn-Xfer_Enable_1_>


<!--########################################################-->
<!--###              Time and DST Settings               ###-->
<!--########################################################-->

<Primary_NTP_Server group="System/Optional_Network_Configuration">%%param::time_ntp_server%%</Primary_NTP_Server>
<Time_Zone group="Regional/Miscellaneous">%%param::time_timezone_linksys%%</Time_Zone>
<Daylight_Saving_Time_Enable group="Regional/Miscellaneous">%%dstEnableDisable%%</Daylight_Saving_Time_Enable>
<Daylight_Saving_Time_Rule group="Regional/Miscellaneous">start=%%param::time_dst_start_month%%/%%param::time_dst_start_day%%/0;end=%%param::time_dst_end_month%%/%%param::time_dst_end_day%%/0;save=0:%%param::time_dst_saving_minutes%%:0</Daylight_Saving_Time_Rule>


<!--########################################################-->
<!--###             Firmware Update Settings             ###-->
<!--########################################################-->
 
<Upgrade_Enable group="Provisioning/Firmware_Upgrade">Yes</Upgrade_Enable>
<Upgrade_Rule group="Provisioning/Firmware_Upgrade">http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/firmware/%%firmware%%</Upgrade_Rule>
<Upgrade_Error_Retry_Delay group="Provisioning/Firmware_Upgrade">86400</Upgrade_Error_Retry_Delay>


<!--########################################################-->
<!--###                 Language Settings                ###-->
<!--########################################################-->
 
<Dictionary_Server_Script group="Regional/Miscellaneous">serv=http://%%pbx_ip%%:%%pbx_http_port%%/provisioning/firmware/;d0=English-US;x0=spa50x_30x_en_v745.xml;d1=Deutsch;x1=spa50x_30x_de_v745.xml;d2=Espanol;x2=spa50x_30x_es_v745.xml;d3=Francais;x3=spa50x_30x_fr_v745.xml;d4=Italiano;x4=spa50x_30x_it_v745.xml;d5=Nederlands;x5=spa50x_30x_nl_v745.xml</Dictionary_Server_Script>
<Language_Selection group="Regional/Miscellaneous">%%langwebUI%%</Language_Selection>
<Default_Character_Encoding group="Regional/Miscellaneous">UTF-8</Default_Character_Encoding>


<!--########################################################-->
<!--###                 Remote Extension                 ###-->
<!--########################################################-->


<!--########################################################-->
<!--###                 Networking V-LAN                 ###-->
<!--########################################################-->

<!--#VLAN ID Tagging on or off for the SW Port (802.1q).#-->
<Enable_VLAN group="System/VLAN_Settings">No</Enable_VLAN>
<!--#VLAN ID (0..4095) Which sets the ID number for the VLAN SW Port (802.1q).#-->
<VLAN_ID group="System/VLAN_Settings">1</VLAN_ID>
<!--#VLAN ID Tagging on or off for the PC Port (802.1q).#-->
<Enable_PC_Port_VLAN_Tagging group="System/VLAN_Settings">No</Enable_PC_Port_VLAN_Tagging>
<!--#VLAN ID (0..4095) Which sets the ID number for the PC Port  (802.1q).#-->
<PC_Port_VLAN_ID group="System/VLAN_Settings">1</PC_Port_VLAN_ID>
<!--#Sets the Priority of the PC Port to the Phones Switch Port (802.1q).#-->
<PC_Port_VLAN_Highest_Priority group="System/VLAN_Settings">No Limit</PC_Port_VLAN_Highest_Priority>
 

<!--########################################################-->
<!--###                 Other Settings                   ###-->
<!--########################################################-->

<!--# Phone Web Admin password-->
<Admin_Passwd group="System/System_Configuration">####Change This Value###</Admin_Passwd>


<!--########################################################-->
<!--###                  BLF Settings                    ###-->
<!--########################################################-->

<!--# The "Unit_1_Key_1" field contains a string value which specifies the type of functionality to assign to the first key on the SPA-932 Sidecar unit, and which extension number to monitor. The provisioning template sets the value to "fnc=sd+blf+cp;sub=blf1@%%pbx_ip%%;nme=100" - unless BLF is not being used for the key, in which case the value will be blank.-->
<!--# The string value contains 2 sections, separated by a ";" character.-->
<!--# The first section must contain "fnc=sd+blf+cp" - which basically means SpeedDial + BLF + CallPickup.-->
<!--# The second section must contain the extension identity for whose notifications the phone will subscribe, in the format "sub=blf1@%%pbx_ip%%" - where the variables "blf1" and "pbx_ip" will be replaced by the extension number chosen from the 3CX Management Console, and the IP Address of the 3CXPS machine.-->
<!--# The second key is identified by the "Unit_1_Key_2" field, and will contain "sub=blf2@%%pbx_ip%%" (note reference to the "blf2" variable); the third key is identified by the "Unit_1_Key_3" field  and will contain "sub=blf3@%%pbx_ip%%" (note reference to the "blf3" variable); and so on.-->

<Unit_1_Enable group="Attendant_Console/General">yes</Unit_1_Enable>
<Unit_2_Enable group="Attendant_Console/General">no</Unit_2_Enable>
<Server_Type group="Attendant_Console/General">RFC3265_4235</Server_Type>
<Attendant_Console_Call_Pickup_Code group="Attendant_Console/General"></Attendant_Console_Call_Pickup_Code>
<Subscribe_Delay group="Attendant_Console/General">5</Subscribe_Delay>

{IF blf1}
<Unit_1_Key_1 group="Attendant_Console/Unit_1">%%value%%sub=%%blf1%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf1%%</Unit_1_Key_1>
{ELSE}
<Unit_1_Key_1 group="Attendant_Console/Unit_1"></Unit_1_Key_1>
{ENDIF}

{IF blf2}
<Unit_1_Key_2 group="Attendant_Console/Unit_1">%%value%%sub=%%blf2%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf2%%</Unit_1_Key_2>
{ELSE}
<Unit_1_Key_2 group="Attendant_Console/Unit_1"></Unit_1_Key_2>
{ENDIF}

{IF blf3}
<Unit_1_Key_3 group="Attendant_Console/Unit_1">%%value%%sub=%%blf3%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf3%%</Unit_1_Key_3>
{ELSE}
<Unit_1_Key_3 group="Attendant_Console/Unit_1"></Unit_1_Key_3>
{ENDIF}

{IF blf4}
<Unit_1_Key_4 group="Attendant_Console/Unit_1">%%value%%sub=%%blf4%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf4%%</Unit_1_Key_4>
{ELSE}
<Unit_1_Key_4 group="Attendant_Console/Unit_1"></Unit_1_Key_4>
{ENDIF}

{IF blf5}
<Unit_1_Key_5 group="Attendant_Console/Unit_1">%%value%%sub=%%blf5%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf5%%</Unit_1_Key_5>
{ELSE}
<Unit_1_Key_5 group="Attendant_Console/Unit_1"></Unit_1_Key_5>
{ENDIF}

{IF blf6}
<Unit_1_Key_6 group="Attendant_Console/Unit_1">%%value%%sub=%%blf6%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf6%%</Unit_1_Key_6>
{ELSE}
<Unit_1_Key_6 group="Attendant_Console/Unit_1"></Unit_1_Key_6>
{ENDIF}

{IF blf7}
<Unit_1_Key_7 group="Attendant_Console/Unit_1">%%value%%sub=%%blf7%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf7%%</Unit_1_Key_7>
{ELSE}
<Unit_1_Key_7 group="Attendant_Console/Unit_1"></Unit_1_Key_7>
{ENDIF}

{IF blf8}
<Unit_1_Key_8 group="Attendant_Console/Unit_1">%%value%%sub=%%blf8%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf8%%</Unit_1_Key_8>
{ELSE}
<Unit_1_Key_8 group="Attendant_Console/Unit_1"></Unit_1_Key_8>
{ENDIF}

{IF blf9}
<Unit_1_Key_9 group="Attendant_Console/Unit_1">%%value%%sub=%%blf9%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf9%%</Unit_1_Key_9>
{ELSE}
<Unit_1_Key_9 group="Attendant_Console/Unit_1"></Unit_1_Key_9>
{ENDIF}

{IF blf10}
<Unit_1_Key_10 group="Attendant_Console/Unit_1">%%value%%sub=%%blf10%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf10%%</Unit_1_Key_10>
{ELSE}
<Unit_1_Key_10 group="Attendant_Console/Unit_1"></Unit_1_Key_10>
{ENDIF}

{IF blf11}
<Unit_1_Key_11 group="Attendant_Console/Unit_1">%%value%%sub=%%blf11%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf11%%</Unit_1_Key_11>
{ELSE}
<Unit_1_Key_11 group="Attendant_Console/Unit_1"></Unit_1_Key_11>
{ENDIF}

{IF blf12}
<Unit_1_Key_12 group="Attendant_Console/Unit_1">%%value%%sub=%%blf12%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf12%%</Unit_1_Key_12>
{ELSE}
<Unit_1_Key_12 group="Attendant_Console/Unit_1"></Unit_1_Key_12>
{ENDIF}

{IF blf13}
<Unit_1_Key_13 group="Attendant_Console/Unit_1">%%value%%sub=%%blf13%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf13%%</Unit_1_Key_13>
{ELSE}
<Unit_1_Key_13 group="Attendant_Console/Unit_1"></Unit_1_Key_13>
{ENDIF}

{IF blf14}
<Unit_1_Key_14 group="Attendant_Console/Unit_1">%%value%%sub=%%blf14%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf14%%</Unit_1_Key_14>
{ELSE}
<Unit_1_Key_14 group="Attendant_Console/Unit_1"></Unit_1_Key_14>
{ENDIF}

{IF blf15}
<Unit_1_Key_15 group="Attendant_Console/Unit_1">%%value%%sub=%%blf15%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf15%%</Unit_1_Key_15>
{ELSE}
<Unit_1_Key_15 group="Attendant_Console/Unit_1"></Unit_1_Key_15>
{ENDIF}

{IF blf16}
<Unit_1_Key_16 group="Attendant_Console/Unit_1">%%value%%sub=%%blf16%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf16%%</Unit_1_Key_16>
{ELSE}
<Unit_1_Key_16 group="Attendant_Console/Unit_1"></Unit_1_Key_16>
{ENDIF}

{IF blf17}
<Unit_1_Key_17 group="Attendant_Console/Unit_1">%%value%%sub=%%blf17%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf17%%</Unit_1_Key_17>
{ELSE}
<Unit_1_Key_17 group="Attendant_Console/Unit_1"></Unit_1_Key_17>
{ENDIF}

{IF blf18}
<Unit_1_Key_18 group="Attendant_Console/Unit_1">%%value%%sub=%%blf18%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf18%%</Unit_1_Key_18>
{ELSE}
<Unit_1_Key_18 group="Attendant_Console/Unit_1"></Unit_1_Key_18>
{ENDIF}

{IF blf19}
<Unit_1_Key_19 group="Attendant_Console/Unit_1">%%value%%sub=%%blf19%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf19%%</Unit_1_Key_19>
{ELSE}
<Unit_1_Key_19 group="Attendant_Console/Unit_1"></Unit_1_Key_19>
{ENDIF}

{IF blf20}
<Unit_1_Key_20 group="Attendant_Console/Unit_1">%%value%%sub=%%blf20%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf20%%</Unit_1_Key_20>
{ELSE}
<Unit_1_Key_20 group="Attendant_Console/Unit_1"></Unit_1_Key_20>
{ENDIF}

{IF blf21}
<Unit_1_Key_21 group="Attendant_Console/Unit_1">%%value%%sub=%%blf21%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf21%%</Unit_1_Key_21>
{ELSE}
<Unit_1_Key_21 group="Attendant_Console/Unit_1"></Unit_1_Key_21>
{ENDIF}

{IF blf22}
<Unit_1_Key_22 group="Attendant_Console/Unit_1">%%value%%sub=%%blf22%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf22%%</Unit_1_Key_22>
{ELSE}
<Unit_1_Key_22 group="Attendant_Console/Unit_1"></Unit_1_Key_22>
{ENDIF}

{IF blf23}
<Unit_1_Key_23 group="Attendant_Console/Unit_1">%%value%%sub=%%blf23%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf23%%</Unit_1_Key_23>
{ELSE}
<Unit_1_Key_23 group="Attendant_Console/Unit_1"></Unit_1_Key_23>
{ENDIF}

{IF blf24}
<Unit_1_Key_24 group="Attendant_Console/Unit_1">%%value%%sub=%%blf24%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf24%%</Unit_1_Key_24>
{ELSE}
<Unit_1_Key_24 group="Attendant_Console/Unit_1"></Unit_1_Key_24>
{ENDIF}

{IF blf25}
<Unit_1_Key_25 group="Attendant_Console/Unit_1">%%value%%sub=%%blf25%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf25%%</Unit_1_Key_25>
{ELSE}
<Unit_1_Key_25 group="Attendant_Console/Unit_1"></Unit_1_Key_25>
{ENDIF}

{IF blf26}
<Unit_1_Key_26 group="Attendant_Console/Unit_1">%%value%%sub=%%blf26%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf26%%</Unit_1_Key_26>
{ELSE}
<Unit_1_Key_26 group="Attendant_Console/Unit_1"></Unit_1_Key_26>
{ENDIF}

{IF blf27}
<Unit_1_Key_27 group="Attendant_Console/Unit_1">%%value%%sub=%%blf27%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf27%%</Unit_1_Key_27>
{ELSE}
<Unit_1_Key_27 group="Attendant_Console/Unit_1"></Unit_1_Key_27>
{ENDIF}

{IF blf28}
<Unit_1_Key_28 group="Attendant_Console/Unit_1">%%value%%sub=%%blf28%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf28%%</Unit_1_Key_28>
{ELSE}
<Unit_1_Key_28 group="Attendant_Console/Unit_1"></Unit_1_Key_28>
{ENDIF}

{IF blf29}
<Unit_1_Key_29 group="Attendant_Console/Unit_1">%%value%%sub=%%blf29%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf29%%</Unit_1_Key_29>
{ELSE}
<Unit_1_Key_29 group="Attendant_Console/Unit_1"></Unit_1_Key_29>
{ENDIF}

{IF blf30}
<Unit_1_Key_30 group="Attendant_Console/Unit_1">%%value%%sub=%%blf30%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf30%%</Unit_1_Key_30>
{ELSE}
<Unit_1_Key_30 group="Attendant_Console/Unit_1"></Unit_1_Key_30>
{ENDIF}

{IF blf31}
<Unit_1_Key_31 group="Attendant_Console/Unit_1">%%value%%sub=%%blf31%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf31%%</Unit_1_Key_31>
{ELSE}
<Unit_1_Key_31 group="Attendant_Console/Unit_1"></Unit_1_Key_31>
{ENDIF}

{IF blf32}
<Unit_1_Key_32 group="Attendant_Console/Unit_1">%%value%%sub=%%blf32%%@%%pbx_ip%%:%%param::sipport%%;nme=%%blf32%%</Unit_1_Key_32>
{ELSE}
<Unit_1_Key_32 group="Attendant_Console/Unit_1"></Unit_1_Key_32>
{ENDIF}


</flat-profile>

]]>
   </deviceconfig>

   </device>
</data>   
</doc>



[nickybrg]

Yes you are correct. In the meantime I contacted cisco. They told me the same thing.

I will release a template update tomorrow that will provision it to null (empty)

That value gets set to yes when a message is received. This is why it was rebooting all the time. As you explained earlier.

[netswork]

Awesome post and good information here.

Efounco,

Do you know of a way to modify in the template how it labels the lines on the phone set for shared park lines? I would rather it say Park 1, park 2, park 3 than SP 1, SP2, SP3.

I dug through the xml but I am not certain where I can change this value.


Thanks in advance.

[efounco]

Awesome post and good information here.

Efounco,

Do you know of a way to modify in the template how it labels the lines on the phone set for shared park lines? I would rather it say Park 1, park 2, park 3 than SP 1, SP2, SP3.

I dug through the xml but I am not certain where I can change this value.


Thanks in advance.

All of our phone's have 500s sidecars installed, so I simple print out a new label that reads "Park 1".

In all seriousness, are you referring to the short names on the LCD that are provisioned for shared parking? You can label the short names for each line accordingly:

<Short_Name_2_ group="Phone/Line_Key_2">Park 1</Short_Name_2_>
<Short_Name_3_ group="Phone/Line_Key_2">Park 2</Short_Name_3_>
etc...

[netswork]

Ill look over the template again and see if I can get this worked out. I found where I can modify the actual provisioning file that is generated for the phone to re-lable the short name...I just could not figure out where in the template to modify the variable that was labeling the park lines SP 0.


The only other thing I would like to change in the SPA provisioning template is when you add a 500 side car it then configures all of the lines on the 525's to the users extension. I dont understand the reasoning for this. My customers never have more than 2-3 calls on a phone at one time.

I need to figure out how to modify the tempalte so that it just configures the first 2 buttons with the users extensions and then allows the other 3 buttons to be configured for BLF or whatever.

[nickybrg]

SPx is hardcoded.
There are 3 Cisco templates. Cisco, Cisco with sidecar. And Cisco. 525 with sidecar. Use a combination of cisco and Cisco 525 with sidecar to provision2 line keys and the remaining for blf. The Cisco template does this.