04-17-2014, 09:46 PM
Hi,
I have a question concerning the DSSKey-Field with the Yealink 28.
We want to show certain information about the active account ($active_user) via XML-Browser.
Input of "http://192.168.224.1/menu/Home/menu?test=$ip" in an action URL leads to the correct server request of
"GET /menu/Home/menu?test=192.168.225.29 HTTP/1.1" 200 - "-" "Yealink SIP-T28P 2.72.0.30 00:15:65:4a:03:c6".
However, input of
"http://192.168.224.1/menu/Home/menu?test=$ip" with a DSSKey-Field "Type=XML Browser" is not completed and leads to
"GET /menu/Home/menu?test=$ip HTTP/1.1" 200 - "-" "Yealink SIP-T28P 2.72.0.30 00:15:65:4a:03:c6"
Instead of the "$ip" we would need the correct address.
Similar problems exist with other key types (memory, line, programmable).
Are we doing something wrong or is this a bug? Is there any chance of changing this behaviour?
Greetings,
Helmut Celina
I have a question concerning the DSSKey-Field with the Yealink 28.
We want to show certain information about the active account ($active_user) via XML-Browser.
Input of "http://192.168.224.1/menu/Home/menu?test=$ip" in an action URL leads to the correct server request of
"GET /menu/Home/menu?test=192.168.225.29 HTTP/1.1" 200 - "-" "Yealink SIP-T28P 2.72.0.30 00:15:65:4a:03:c6".
However, input of
"http://192.168.224.1/menu/Home/menu?test=$ip" with a DSSKey-Field "Type=XML Browser" is not completed and leads to
"GET /menu/Home/menu?test=$ip HTTP/1.1" 200 - "-" "Yealink SIP-T28P 2.72.0.30 00:15:65:4a:03:c6"
Instead of the "$ip" we would need the correct address.
Similar problems exist with other key types (memory, line, programmable).
Are we doing something wrong or is this a bug? Is there any chance of changing this behaviour?
Greetings,
Helmut Celina