GXE502X User Manual 11/2/2009
80
P404=&GS extension-1&
P405=&GS extension-1&
P406=&GS password-1&
#*******************************************************************
2. How does template file become configuration file and loaded into Grandstream product?
When Grandstream Terminal Device boot up in the same LAN with GXE5000(LAN Port), it will go
through following process:
Issue DHCP Request, acquire both IP address and the TFTP server IP through DHCP Option 66,
here GXE5000 function as DHCP Server.
Issue TFTP request for configuration file with name “cfg000b82xxxxxx”. Here the TFTP
request contains Grandstream proprietary extensions that contain Grandstream Product model
information, see following example:
Trivial File Transfer Protocol
Opcode: Read Request (1)
Source File: /GXV-3000/cfg000b8209ba7d
Type: octet
Option: blksize = 1024
Option: tsize = 0
Option: timeout = 4
Option: grandstream_MODEL = GXV-3000
Option: grandstream_NAT = 1
Option: grandstream_ID = 000b8209ba7d
Option: grandstream_REV_BOOT = 001.001.003.002
Option: grandstream_REV_PHONE = 001.001.003.014
When GXE5000 received the TFTP request, it will base on the product model to look up the
template file and generate the device configuration file dynamically.
3. Template file name format.
Product-Model-base-provision, here Product-Model has to be the product model shown in the tftp
option, e.g., GXP-2000 or GXV-3000, their template file will be GXP-2000-base-provision and GXV-
3000-base-provision, respectively.
4. Template file management.
Currently GXE5000 contains following product templates:
Unknown/BT-100/BT-110/BT-200/GXP-2000/GXP-2020/GXV-3000/GXW-4004/GXW-4008/HT-
286/HT-386/HT-487/HT-488/HT-496
Here Unknown is a special template that it will only assign variables to P34/P35/P36/P47, in case a
TFTP request does not contain a known product model or no model option in the TFTP request.