Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Linksys SPA3102 Provisioning File

Discussion in '3CX Phone System - General' started by secutech, Nov 23, 2010.

Thread Status:
Not open for further replies.
  1. secutech

    Joined:
    May 4, 2010
    Messages:
    3
    Likes Received:
    0
    Hi,

    If any of you need to use the LINKSYS SPA 3102 as an ATA device with PSTN line enabled, you can use the attached xml file for provisioning. I've tested it and it works fine. You need to change the DNS & NTP server's to match your network.

    Had to create this manually as the old LINKSYS profile we were using for provisioning SPA 3102 devices stopped working after upgrade to SP4. I was using the default LINKSYS profile which was working perfectly till the upgrade.

    Thought of sharing the file as it could be helpful for someone else.

    Thanks,
    Mazhar
     
  2. secutech

    Joined:
    May 4, 2010
    Messages:
    3
    Likes Received:
    0
    <?xml version="1.0"?>
    <doc xmlns:tcx="http://www.3cx.com">
    <header>
    <type>phone-template</type>
    <name>Linksys SIP Phone</name>
    <url>http://www.linksys.com</url>
    <models>
    <model>Linksys SPA3102-SHOP</model>
    </models>
    <description>Linksys SIP Phone</description>
    <parsers>
    <parser>BLF</parser>
    </parsers>
    </header>
    <data>
    <device>
    <type>phone</type>
    <field name="Name">Linksys SPA-3102-SHOP</field>
    <field name="RebootLink">http://%%rebootip%%/admin/reboot</field>
    <deviceconfig filename="%%mac_address%%.xml">
    <![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

    <flat-profile>

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

    <!--# 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 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">(xx.|&lt;#9,:&gt;xx.&lt;:mad:gw0&gt;)</Dial_Plan_1_>



    <!--########################################################-->
    <!--### 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%% - %%extension_last_name%%</Station_Name>

    <!--# 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>



    <!--########################################################-->
    <!--### 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>



    <Connection_Type group="WAN_SETUP/Connection_Type">DHCP</Connection_Type>
    <HostName group="WAN_SETUP/HostName">%%extension_first_name%%-%%extension_last_name%%</HostName>
    <Primary_DNS group="WAN_SETUP/Primary_DNS">10.81.1.1</Primary_DNS>
    <Secondary_DNS group="WAN_SETUP/Secondary_DNS">10.81.1.3</Secondary_DNS>
    <DNS_Server_Order group="WAN_SETUP/DNS_Server_Order">DHCP,Manual</DNS_Server_Order>
    <Primary_NTP_Server group="WAN_SETUP/Primary NTP Server">10.81.1.1</Primary_NTP_Server>
    <Secondary_NTP_Server group="WAN_SETUP/Secondary_NTP_Server">10.81.1.3</Secondary_NTP_Server>
    <Enable_WAN_Web_Server group="WAN_SETUP/Enable_WAN_Web_Server">Yes</Enable_WAN_Web_Server>
    <WAN_Web_Server_Port group="WAN_SETUP/WAN_Web_Server_Port">80</WAN_Web_Server_Port>

    <Networking_Service group="LAN_SETUP/Networking_Service">Auto</Networking_Service>
    <Enable_DHCP_Server group="LAN_SETUP/Enable_DHCP_Server">No</Enable_DHCP_Server>

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

    <!--# The "Message_Waiting_1_" field specifies whether to activate the MWI lamp when a new message arrives. Valid values are "Yes"==Activate Lamp When New Message Arrives; "No"==Do Not Activate Lamp When New Message Arrives. The provisioning template sets the value to "No"==Activate Lamp When New Message Arrives.-->
    <!--# Important Note: If this setting is changed from "No" to "Yes", most users report that the MWI lamp is always on. With this setting "No", the MWI lamp lights up correctly when there are messages, and switches off correctly when there are no messages.-->
    <Message_Waiting_1_ group="Ext_1/Call_Feature_Settings">No</Message_Waiting_1_>

    <!--# 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">86400</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://10.81.16.6:80/management/provisioning/$MA.xml".-->
    <Profile_Rule group="Provisioning/Configuration_Profile">http://10.81.16.6:80/management/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>



    <!--########################################################-->
    <!--### 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">10.81.1.1</Primary_NTP_Server>
    <Time_Zone group="Regional/Miscellaneous">GMT+03:00</Time_Zone>
    <Daylight_Saving_Time_Rule group="Regional/Miscellaneous"></Daylight_Saving_Time_Rule>

    </flat-profile>

    ]]>

    </deviceconfig>
    </device>
    </data>
    </doc>
     
Thread Status:
Not open for further replies.