[asterisk-bugs] [JIRA] (ASTERISK-21765) FILE function's length argument counts from beginning of file rather than the offset - also not consistently

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206644#comment-206644 ] 

Rusty Newton commented on ASTERISK-21765:
-----------------------------------------

Confirmed. Though I'm guessing the documentation has just always been wrong and hasn't been fixed. The consistency issue should be a bug.

I also happen to have 1.8.15 on hand, the behavior is the same there. 
{quote}
Base on previous version Asterisk
{quote}
What older version behaved differently for you?



                
> FILE function's length argument counts from beginning of file rather than the offset - also not consistently
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21765
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21765
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Functions/func_dialplan
>    Affects Versions: 11.2.1, 11.3.0
>         Environment: AsteriskNow64 3.0.0
> Asterisk 11.2.1 and Asterisk 11.3.0
>            Reporter: John Zhong
>
> AsteriskNow64 3.0.0 running under VMWare workstation.
> There are two issues have been found while I am testing our HiTPM with AsteriskNow64 3.0.0 integration.
> Reproduce steps:
>   1) Install netcat
>   2) Create two test files as:
>      echo 0123456789 >/tmp/0123456789.txt
>      base64 -w 0 /var/lib/asterisk/sounds/en/vm-login.ulaw > /tmp/vm-login.ulaw.b64
>   3) Run: ifconfig;nc -l 4573
>   4) Add a peer for SIP client into sip.conf
>   5) Create an extension for an AGI(agi://[the_ip_address_of_nc_listen_on]) 
>   6) Call the AGI extension
>   7) If setup is correct, the nc windows should have AGI headers
>   8) Send following commands by nc:
> {noformat}
>      GET VARIABLE FILE("/tmp/0123456789.txt,2,5")
>      and 
>      GET VARIABLE FILE("/tmp/vm-login.ulaw.b64,4080,5100")
> {noformat}
>   9) Verify the result:
> {noformat}
>      GET VARIABLE FILE("/tmp/0123456789.txt,2,5")
>      200 result=1 (234)
> {noformat}
>      Base on previous version Asterisk and current document, it should
>      return (23456), the first argument is offset and the second argument
>      should be length, but it is the 1 before the end position now. OK, 
>      let's treat it as what it is, go further to see another bug. If you
>      count the result of FILE("/tmp/vm-login.ulaw.b64,4080,5100"), the
>      length is 1023, not the expected 1020.
> {noformat}
>      GET VARIABLE FILE("/tmp/vm-login.ulaw.b64,4080,5100")
>      200 result=1
> (qq2uu8nMRT06LS4uKSssLCsuPERGyL69ra2spqinp6utt8ffSTkwLCkoKCgoLCwqPVlEwbO9qqmso6aop6yvucl4RTsvLComKCgoKSssMlNK1bG8rKWsoqOnpKqvt8BuQUEtKy0kKCglKisrLUZYTrK3taKtpp+ro6Wxr73iT0A0LC4nJiokKSsqLzFQW+Svu6ykrqGiq6KrsLDL5k07Mi0rJikoJiwqLTMwXf3nrreuo6ykoqulqbO1xGhIPS4tKyUpJyYsKi43MVbQ6bCvsqOpqKCqqaizucFvQz0wKiwlJiolLC0sOjZBx9e7q7OnpKyhp62mtby7WE0/Ly4rJygoJystLjg8PN7EzK6tr6KpqqGuqqvCudpHSzMuLSgoKCcqLS42PD9M076/ra2uo6uppbGqscO6XE1FLzErKCooKSwtMjk9S0vcusiuq7Skqq2ksa2uxL3oTEY2MC0qKSkqKy8xOj5FU1G+v8CptKyksaeps6u3wcRqRz01LSwpJyspLTIyPj9MUF26xript6insKWsr6u9vMlOSzovLiooKSkqLy82Pj5XTWK4yrapuKinsaSsr6q6v8dQRDsuLSsnKikrLzA4PkFPVFu/vb6rsK6lrqmnsKuxwMRkRTwwLSsnKSkpLjE1P0FKak7et8m0qrinqK+krK6qur/NUDs3LigrJSYsKDE3NkxLWN5f3LbAu6m3rKWzp6izqrbMyU43Ni0nKiYlLCovPDtNa2jUzmu/tM+urL2lrLKjsLGsyNTjOzIxKCYpJCgtLDhDSeXX0sXI4sG1zLStwKqruaiuuK7B9e8+LzApJSkmKC8vPFZkzcPIv8HV68HB7rW6yqq2uKe2tK7I3O07MDAnJiklKzM0SvXewL7Ivsj+YWbMV9i23rCsvKWqsai2ztZGLy4qIicmJjEzP+zbxrzFw8F5XEpu10W8u8ynrq6gq6yrvmpTNigrJB8oJSk4PFDGvryzvMK9alE+QfQ417nfqqqtoKapq7jmRTgpJyUfJCc)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira