Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

info about Cloud Service Caller still up to date? #33

Open
dimmu311 opened this issue Nov 24, 2021 · 2 comments
Open

info about Cloud Service Caller still up to date? #33

dimmu311 opened this issue Nov 24, 2021 · 2 comments

Comments

@dimmu311
Copy link

I'm currently working on my own implementation of the cloud caller. i redirect the dns queries from caller.loxone.com to my own web server.
To the request <http: //caller.loxone.com: 80/cgi-bin/loxlive/call.pl? ......> I answer according to the given example. In addition, information on the cloud caller says that the miniserver ignores the answer.

I think that is not correct (anymore). Immediately after the request is sent to the caller, an error message appears in the Loxone Monitor and a push message is issued that the caller is not active.
See this example from Loxone Monitor:
2021-11-23 22: 57: 22.658; Critical 509 QUITTED, MINISERVER_NAME - Error Loxone Caller Service, all, Miniserver (Uuid 1111111111-0000-2222-ffff141234567890)

I think the miniserver is expecting (maybe in newer firmware) an answer.

@bate
Copy link

bate commented Nov 24, 2021

Thats easy, just proxy the request to the correct loxone server and reply back to the miniserver to track the response.
But thats an http call without ssl check .. ok easy then.

@dimmu311
Copy link
Author

I thought about that too. But there is a little problem.
The original server checks whether a caller license is activated for the Miniserver Mac address.
So either I need to know a mac address that has an active license or I need to buy a license

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants