Provisioning Guide
Page 12
... remote profile periodically and on power up. Release 2.0 supports a secure first-time provisioning mechanism using network address translation (NAT). Remote Endpoint Control The service provider must be configured to match the account service parameters for the individual customer. This... features of Linksys ATAs: • Reliable remote control of the endpoint, • Encryption of the account by implementing symmetric NAT, a packet filtering strategy which provide definitions and usage guidelines for a specific device. Note This Provisioning Guide is supported by the...
... remote profile periodically and on power up. Release 2.0 supports a secure first-time provisioning mechanism using network address translation (NAT). Remote Endpoint Control The service provider must be configured to match the account service parameters for the individual customer. This... features of Linksys ATAs: • Reliable remote control of the endpoint, • Encryption of the account by implementing symmetric NAT, a packet filtering strategy which provide definitions and usage guidelines for a specific device. Note This Provisioning Guide is supported by the...
Provisioning Guide
Page 22
... un-provisioned devices. Basic HTTP-based SPA provisioning relies on the local TFTP server, if that TFTP server. Typically, this expands to /spa2102.cfg, which means that the specified filepath is relative to a configuration profile using the GET method). In the case of CGI handling resync... and producing the profile on a simple TFTP server for remote deployment. However, once deployed remotely, HTTP offers greater provisioning reliability, given NAT and router protection mechanisms. The SPA is specified via DHCP option 66. In this file on the HTTP GET method for every resync ...
... un-provisioned devices. Basic HTTP-based SPA provisioning relies on the local TFTP server, if that TFTP server. Typically, this expands to /spa2102.cfg, which means that the specified filepath is relative to a configuration profile using the GET method). In the case of CGI handling resync... and producing the profile on a simple TFTP server for remote deployment. However, once deployed remotely, HTTP offers greater provisioning reliability, given NAT and router protection mechanisms. The SPA is specified via DHCP option 66. In this file on the HTTP GET method for every resync ...
Provisioning Guide
Page 54
... via macro expansion. For example, assuming the HTTP server is at establishing a TCP connection between a SPA client behind a firewall or NAT device and a remote provisioning server on host prov.telco.com, which helps to resync using HTTP (with its profile periodically. For example..., the following is a valid Profile_Rule that requests the file spa2102.cfg, in organizing a directory of 000e08012345) requests the profile at the following value: Linksys SPA Provisioning Guide 3-6 Version 3.0 tftp://prov...
... via macro expansion. For example, assuming the HTTP server is at establishing a TCP connection between a SPA client behind a firewall or NAT device and a remote provisioning server on host prov.telco.com, which helps to resync using HTTP (with its profile periodically. For example..., the following is a valid Profile_Rule that requests the file spa2102.cfg, in organizing a directory of 000e08012345) requests the profile at the following value: Linksys SPA Provisioning Guide 3-6 Version 3.0 tftp://prov...
Provisioning Guide
Page 74
... HTTP HTTPS ICMP IGMP ILEC IP ISP ITSP IVR LAN LBR LBRC MC MGCP MOH MOS ms MSA MWI OSI PCB PR PS PSQM PSTN NAT OOB REQT RESP RSC RTP RTT SAS SDP Gateway International Telecommunication Union Hypertext Markup Language Hypertext Transfer Protocol HTTP over SSL Internet Control Message Protocol...
... HTTP HTTPS ICMP IGMP ILEC IP ISP ITSP IVR LAN LBR LBRC MC MGCP MOH MOS ms MSA MWI OSI PCB PR PS PSQM PSTN NAT OOB REQT RESP RSC RTP RTT SAS SDP Gateway International Telecommunication Union Hypertext Markup Language Hypertext Transfer Protocol HTTP over SSL Internet Control Message Protocol...
Provisioning Guide
Page 81
... G726r16_Dynamic_Payload G726r24_Dynamic_Payload G726r40_Dynamic_Payload G729b_Dynamic_Payload NSE_Codec_Name AVT_Codec_Name G711u_Codec_Name G711a_Codec_Name G726r16_Codec_Name G726r24_Codec_Name G726r32_Codec_Name G726r40_Codec_Name G729a_Codec_Name G729b_Codec_Name G723_Codec_Name "100" ; "97" ; "G729ab" ; "G723" ; # *** NAT Support Parameters Handle_VIA_received Handle_VIA_rport Insert_VIA_received Insert_VIA_rport Substitute_VIA_Addr Send_Resp_To_Src_Port STUN_Enable STUN_Test_Enable "No" ; "No" ; "7200" ; "16482" ; "telephone-event" ; "G726-24" ; "No...
... G726r16_Dynamic_Payload G726r24_Dynamic_Payload G726r40_Dynamic_Payload G729b_Dynamic_Payload NSE_Codec_Name AVT_Codec_Name G711u_Codec_Name G711a_Codec_Name G726r16_Codec_Name G726r24_Codec_Name G726r32_Codec_Name G726r40_Codec_Name G729a_Codec_Name G729b_Codec_Name G723_Codec_Name "100" ; "97" ; "G729ab" ; "G723" ; # *** NAT Support Parameters Handle_VIA_received Handle_VIA_rport Insert_VIA_received Insert_VIA_rport Substitute_VIA_Addr Send_Resp_To_Src_Port STUN_Enable STUN_Test_Enable "No" ; "No" ; "7200" ; "16482" ; "telephone-event" ; "G726-24" ; "No...