Auto Provisioning with Chunked encoding
Last modified date: 2019/06/01 Views: 1384
Description


Provisioning the phone with Dynamic generated configure file, which is sent from server as a Chunked response. Both HTTP and HTTPS are supported by Yealink IP Phones.

Resolution


Both HTTP and HTTPS are supported Chunked encoding on Yealink IP phone.

The format will be as below:

Chunked-Body   = *chunk
                        last-chunk
                        trailer
                        CRLF

chunk          = chunk-size [ chunk-extension ] CRLF
                        chunk-data CRLF
chunk-size     = 1*HEX
last-chunk     = 1*("0") [ chunk-extension ] CRLF

chunk-extension= *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
chunk-ext-name = token
chunk-ext-val  = token | quoted-string
chunk-data     = chunk-size(OCTET)
trailer        = *(entity-header CRLF)

 

The chunk-size field is a string of hex digits indicating the size of the chunk. The chunked encoding is ended by any chunk whose size is    zero, followed by the trailer, which is terminated by an empty line.

 

The reference file:

https://tools.ietf.org/html/rfc2616#section-14.40


Product Type
SIP-T58V , SIP-T58A , SIP-T56A , SIP VP-T49G , T4S , SIP-T48G , SIP-T46G , SIP-T42G , SIP-T41P , SIP-T40G , SIP-T40P , SIP-T29G , SIP-T27G , SIP-T23G , SIP-T23P , SIP-T21(P) E2 , SIP-T19(P) E2 , W52P , VP530 , SIP-T38G , SIP-T32G , CP860 , SIP-T28P , SIP-T26P , SIP-T22P , SIP-T21P , SIP-T20P , SIP-T19P , SIP-T27P
Version
V80 or higher
200/200
Please login to post your comment