- Joined
- Jul 23, 2020
- Messages
- 2
- Reaction score
- 0
Hello,
Problem: need to intial config a Grandstream HT802 - but the 3cx XML which I need to "upload manually configuration to HT802" looks "defective/empty"?
Download the provisioning XML via
DASHBOARD / FXS/DECT > HT802 the FILE has below CONTENT
GOAL: the Grandstream HT802 should only be used with a Toshiba MFP for outgoing faxes.
https://www.3cx.com/voip-gateways/grandstream-ht-fxs/
Step Step 2: Add and Choose Device with Mac address, assign extension
> we have done.
Content of XML:
<html>
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>
https://customer-pbx.my3cx.de:5000/provisioning/xxxxxx/cfgXXXXXXXX.xml
https:///10.1.1.1.de:5000/provisioning/xxxxxx/cfgXXXXXXXXXXXX.xml
http://customer-pbx.my3cx.de:5000/provisioning/xxxxxx/cfgXXXXXXXX.xml
http:///10.1.1.1.de:5000/provisioning/xxxxxx/cfgXXXXXXXX.xml
I have a internal network with non-rfc-conform network: e.g. 1.70.147.1
But our SNOM + 3cx DEBIAN Linux had a own IP Range 10.1.1.1 "RFC-CONFORM"
Problem: need to intial config a Grandstream HT802 - but the 3cx XML which I need to "upload manually configuration to HT802" looks "defective/empty"?
Download the provisioning XML via
DASHBOARD / FXS/DECT > HT802 the FILE has below CONTENT
GOAL: the Grandstream HT802 should only be used with a Toshiba MFP for outgoing faxes.
https://www.3cx.com/voip-gateways/grandstream-ht-fxs/
Step Step 2: Add and Choose Device with Mac address, assign extension
> we have done.
Content of XML:
<html>
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>
https://customer-pbx.my3cx.de:5000/provisioning/xxxxxx/cfgXXXXXXXX.xml
https:///10.1.1.1.de:5000/provisioning/xxxxxx/cfgXXXXXXXXXXXX.xml
http://customer-pbx.my3cx.de:5000/provisioning/xxxxxx/cfgXXXXXXXX.xml
http:///10.1.1.1.de:5000/provisioning/xxxxxx/cfgXXXXXXXX.xml
I have a internal network with non-rfc-conform network: e.g. 1.70.147.1
But our SNOM + 3cx DEBIAN Linux had a own IP Range 10.1.1.1 "RFC-CONFORM"
Last edited: