Yealink Forums

Full Version: Push xml with firmware 84 - 403 forbidden always
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Using curl (or MS-Windows C++) I'm unable to push xml to my T27G as I just get a 403 forbidden always.

C:\Users\nsolv>curl --verbose -d "xml=<YealinkIPPhoneTextScreen Beep = \"yes\"><Title>test</Title><Text>2222</Text></YealinkIPPhoneTextScreen>" -H "Content-Type: text/xml" -H "Referer:" -X POST -u admin:MYPASSWORD
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying
* Connected to ( port 80 (#0)
* Server auth using Basic with user 'admin'
> POST / HTTP/1.1
> Host:
> Authorization: Basic YWRtaW46bnNvbHZl
> User-Agent: curl/7.68.0
> Accept: */*
> Content-Type: text/xml
> Referer:
> Content-Length: 106
* upload completely sent off: 106 out of 106 bytes
* Mark bundle as not supporting multiuse
< HTTP/1.1 401 Unauthorized
< WWW-Authenticate: Digest realm="PUSH Authentication",nonce="78945123",algorithm="MD5",qop="auth"
< Content-Type: text/html
< Transfer-Encoding: chunked
< Date: Mon, 27 Jan 2020 13:59:37 GMT
< Server: embed httpd
<div id="_RES_INFO_"></div>
</html>* Connection #0 to host left intact

I have my admin web password and remote control password set the same. I have action uril allow IP set to any. What else do I need to do to allow server initiated push xml?

Or has basic authentication for push xml been removed? And only MD5 is supported now?

Any help very much appreciated

Sorted added --digest

curl --verbose -d "xml=<YealinkIPPhoneTextScreen Beep = \"yes\"><Title>test</Title><Text>2222</Text></YealinkIPPhoneTextScreen>" -H "Content-Type: text/xml" -H "Referer:" -H "Connection: Keep-alive" -X POST --digest -u admin:MYPASSWORD
We have the same problem here. Currently testing with a T42S, firmware

When trying to do Push XML, I not only get the HTTP/1.1 403 Forbidden header, but also a small HTML snippet saying Domain is not trusted!

I noticed I get the same error if I try to access the web interface via the OpenVPN link.

Did you have any luck finding a solution?

Best regards, Roel
Hi! I found that this setting:

wui.secure_domain_list = any
made it possible to send XML Push messages over the OpenVPN link.

Best regards, Roel
Reference URL's