Strangeness with creating a config for Cisco SPA303?

Question

SIP

Good afternoon!
When creating xml with settings that will be loaded by this phone via tftp, I noticed such oddities - for some reason, some elements specified in the general spa303.cfg file are not used by the phone, and if they are inserted into a specialized config using the MAC address, for example 3cce73d4986f.cfg, then settings apply!
An example of such elements:

<Proxy_1_ group="Ext_1/Proxy_and_Registration">10.1.5.2</Proxy_1_> 
<Select_Logo group="Phone/General">Text Logo</Select_Logo> 
<Select_Background_Picture group="Phone/General">Text Logo</Select_Background_Picture> 
<Softkey_Labels_Font group="Phone/General">Auto</Softkey_Labels_Font> 
<Screen_Saver_Enable group="Phone/General">Yes</Screen_Saver_Enable> 
<Screen_Saver_Wait group="Phone/General">60</Screen_Saver_Wait> 
<Screen_Saver_Icon group="Phone/General">Background Picture</Screen_Saver_Icon> 
<Extension_1_ group="Phone/Line_Key_1">1</Extension_1_> 
<Short_Name_1_ group="Phone/Line_Key_1">Line 1</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"/> 
<Extension_2_ group="Phone/Line_Key_2">1</Extension_2_> 
<Short_Name_2_ group="Phone/Line_Key_2">Line 2</Short_Name_2_> 
<Share_Call_Appearance_2_ group="Phone/Line_Key_2">private</Share_Call_Appearance_2_> 
<Extended_Function_2_ group="Phone/Line_Key_2"/> 
<Extension_3_ group="Phone/Line_Key_3">1</Extension_3_> 
<Short_Name_3_ group="Phone/Line_Key_3">Line 3</Short_Name_3_> 
<Share_Call_Appearance_3_ group="Phone/Line_Key_3">private</Share_Call_Appearance_3_> 
<Extended_Function_3_ group="Phone/Line_Key_3"/> 
<Transport_Protocol group="Provisioning/Configuration_Profile">tftp</Transport_Protocol> 
<Time_Format group="User/Supplementary_Services">24hr</Time_Format> 
<Date_Format group="User/Supplementary_Services">day/month</Date_Format>

Many elements are common and I would like to put them in a common config, help.
Also, the phone does not accept DHCP option 121, which contains static routes for computers, what should I do with this?

Answer 1

Alas, you will have to put up with the need to have a separate config for each phone. If you want to do something really smart, you can use XSLT to generate configs from an XML list of numbers and a common parameter file.
As for option 121, there is no way: phones should be kept in a separate VLAN with normal routing without these crutches. You can also configure direct_media on the PBX (Asterisk perhaps?) so that all conversations go through the server, then all that remains is to provide a route from phones to the server, but the server will have to gateway RTP through itself.