we are encountering one critical problem.
FMS and FMG 4.x running on Win 2008 R2 Webserver Edition, setup with external SIP Provider according to quick-start manual.
Directly after fresh setup everything is working fine, calls from flashphone to flashphone, from flashphone to wired telephone via sip-provider, from within flash application to wired telephone - great.
Next morning: if you try to place a call via sip-provider, nothing happens. One entry in the logs says "could not resolve sip host" - but why?
1. step: restarted FMG service - no change
2. step: shutdown and restarted server - no change
3. step: shutdown and restarted server AND then restarted FMG service - calls are functioning again until next morning.
Suspicion: DNS cache, so disabled - but no change
Suspicion: our SDSL gets its provider-enforced disconnection during the night, can this have an impact? We will try to find out next week discussing it with the provider.
As a workaround we would like to do the following:
Schedule a server shutdown and restart via windows scheduler - ok, running BUT how to adress the FMG service directly via batch-file and not manually using the services.msc window?
"Net stop (path)/FMGMaster.exe" returns "Der Name für den Dienst ist ungültig" meaning "the name for the service is not valid".
If anyone has an idea to solve the problem in general or knowledge how to name the service correctly, we will very much appreciate the answer.
Thank you in advance
we have worked out a solution for the problem ourselves, maybe this can help others encountering a similar problem.
As mentioned, we had the suspicion that the enforced-disconnection of SDLS can be a base for the problem - and yes, it was!
We had our provider stop the disconnection (that was possible now) and after that all services with FMS and FMG running smoothly until now.
Happy easter to all.
Europe, Middle East and Africa