01-27-2020, 02:03 PM
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: 192.168.10.114" -X POST http://192.168.10.127 -u admin:MYPASSWORD
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 192.168.10.127:80...
* TCP_NODELAY set
* Connected to 192.168.10.127 (192.168.10.127) port 80 (#0)
* Server auth using Basic with user 'admin'
> POST / HTTP/1.1
> Host: 192.168.10.127
> Authorization: Basic YWRtaW46bnNvbHZl
> User-Agent: curl/7.68.0
> Accept: */*
> Content-Type: text/xml
> Referer: 192.168.10.114
> 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
<
<html>
<body>
<div id="_RES_INFO_"></div>
</body>
</html>* Connection #0 to host 192.168.10.127 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
Thanks
Paul
Sorted added --digest
curl --verbose -d "xml=<YealinkIPPhoneTextScreen Beep = \"yes\"><Title>test</Title><Text>2222</Text></YealinkIPPhoneTextScreen>" -H "Content-Type: text/xml" -H "Referer: 192.168.10.114" -H "Connection: Keep-alive" -X POST http://192.168.10.127 --digest -u admin:MYPASSWORD
C:\Users\nsolv>curl --verbose -d "xml=<YealinkIPPhoneTextScreen Beep = \"yes\"><Title>test</Title><Text>2222</Text></YealinkIPPhoneTextScreen>" -H "Content-Type: text/xml" -H "Referer: 192.168.10.114" -X POST http://192.168.10.127 -u admin:MYPASSWORD
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 192.168.10.127:80...
* TCP_NODELAY set
* Connected to 192.168.10.127 (192.168.10.127) port 80 (#0)
* Server auth using Basic with user 'admin'
> POST / HTTP/1.1
> Host: 192.168.10.127
> Authorization: Basic YWRtaW46bnNvbHZl
> User-Agent: curl/7.68.0
> Accept: */*
> Content-Type: text/xml
> Referer: 192.168.10.114
> 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
<
<html>
<body>
<div id="_RES_INFO_"></div>
</body>
</html>* Connection #0 to host 192.168.10.127 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
Thanks
Paul
Sorted added --digest
curl --verbose -d "xml=<YealinkIPPhoneTextScreen Beep = \"yes\"><Title>test</Title><Text>2222</Text></YealinkIPPhoneTextScreen>" -H "Content-Type: text/xml" -H "Referer: 192.168.10.114" -H "Connection: Keep-alive" -X POST http://192.168.10.127 --digest -u admin:MYPASSWORD