Log in

nSolvePaul · 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

roelvanmeer · 03-09-2020 07:47 PM

We have the same problem here. Currently testing with a T42S, firmware 66.83.188.5.

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

roelvanmeer · 03-10-2020 12:47 PM

Hi! I found that this setting:

Code:

wui.secure_domain_list = any

made it possible to send XML Push messages over the OpenVPN link.

Best regards, Roel

Possibly Related Threads...
Thread:		Author	Replies:	Views:	Last Post
	How do I request a SIP licence (to "downgrade" from SFB firmware)?	jaimet2	4	535	04-16-2024 11:17 PM Last Post: complex1
	MP4 Recovery Firmware	simone	1	556	03-22-2024 02:37 PM Last Post: stevediaz
	VP59 Firmware Invalid ROM - 95.15.0.136	mcaplan	0	722	12-27-2023 02:42 PM Last Post: mcaplan
	Firmware phones T33G	esoriano	1	1,040	12-13-2023 02:50 AM Last Post: complex1
	VP59 not updating firmware	lmrn1	0	1,173	07-30-2023 12:01 AM Last Post: lmrn1
	MP54 Firmware	guywonnacott	2	4,532	03-02-2023 12:20 AM Last Post: guywonnacott
	Yealink WH62 Firmware	Ikheo	0	1,684	12-01-2022 09:34 PM Last Post: Ikheo
	T29G firmware 46.83.0.130 question	Chris708	2	3,376	09-03-2022 12:10 AM Last Post: Chris708
	xml push beep when on call	jimk4484	0	1,591	07-08-2022 03:39 AM Last Post: jimk4484
	T56A firmware bin/rom files	ftardie	1	3,735	05-25-2022 11:04 PM Last Post: complex1

Threaded Mode \| Linear Mode Push xml with firmware 84 - 403 forbidden always
Author	Message