Yealink Forums

Full Version: T48G w/35.73.0.16 Action URL odd behavior
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
We have set Action URLs for Open DND and Close DND

Open DND
Code:
http://172.16.57.17/yealink/dndset.php?DND=on&exten=4444

Close DND
Code:
http://172.16.57.17/yealink/dndset.php?DND=off&exten=4444

Basically this sets DND in asterisk as using feature code was troublesome (people like to press DND numerous times rapidly...*shrug*)

When DND is activated via DND onscreen button it makes numerous (16???) web requests to web server. Same for when deactivated.

Looking at the web server log we see this after successive activate/deactivate:

Quote:192.168.1.10 - - [12/Nov/2014:14:46:27 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:27 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:27 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:27 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:29 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:31 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:33 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:35 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:38 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:40 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:42 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:44 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:46 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:49 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:51 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:53 -0700] "GET /yealink/dndset.php?DND=on&exten=4444 HTTP/1.1" 200 336 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"

192.168.1.10 - - [12/Nov/2014:14:46:55 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:46:58 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:00 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:02 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:04 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:06 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:09 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:11 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:13 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:15 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:17 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:20 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:22 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:24 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:26 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"
192.168.1.10 - - [12/Nov/2014:14:47:28 -0700] "GET /yealink/dndset.php?DND=off&exten=4444 HTTP/1.1" 200 338 "-" "Yealink SIP-T48G 35.73.0.16 00:15:65:xx:xx:xx"

The first few are rapid but most of the requests are every other second.

Why more than one web call per action? I would think one press of DND equates to one web call.

Anyone else seeing this behavior? I hope this is a bug and not a feature?
Hi Njackson,

It's do an abnormal behavior.
I have sent the issue as a bug to our R&D. Any update will let you know.

Regards,
James
Reference URL's