support

trixbox Pro 2.0 - FindMe not working

callinectes
Posts: 200
Member Since:
2007-05-12

I am seeing the following message when trying to update/enable FindMe: "Could not open FindMe settings file. Please contact support." This occurs on servers that both have, and do not have, the "Configuration failure" message at the top of the screen so it seems to be unrelated. I have called into support numerous times today and have not been able to get through (I am currently on hold in the queue again 64 minutes and counting) - I assume fonality is swamped with calls related to upgrade issues.



kerryg
Posts: 6416
Member Since:
2006-05-31
They will get back to you as

They will get back to you as soon as they can. Please post your server ID.

--

Kerry Garrison
trixbox Community Director
VoipSpeak.net - Asterisk Tutorials



callinectes
Posts: 200
Member Since:
2007-05-12
The servers that this needs

The servers that this needs to work on soon are 112999 and 118378. 118378 is actually standing by to test - very touchy customer.

Thanks!



samy
Posts: 157
Member Since:
2006-10-21
Hi callinectes, Can you

Hi callinectes,

Can you verify those two servers' FMFM are working for you properly?

Thanks,
Samy

--

Samy Kamkar
Fonality Director of Engineering



callinectes
Posts: 200
Member Since:
2007-05-12
The FindMe settings are in

The FindMe settings are in place now - they saved without the error. I have informed the customer to test and make sure it is working. I will update you if it fails.

Thank you.



jjshoe
Posts: 32
Member Since:
2007-08-13
Glad to hear it's working,

Glad to hear it's working, let us know if we can be of further help.

Thanks,
Joel
Fonality Engineer



callinectes
Posts: 200
Member Since:
2007-05-12
Not completely working - on

Not completely working - on the one server we had to get this working on today it would not work properly when a findme call went out over an analog line - we had to add a voip provider to get it working. I created a ticket to address the issue and evidently its been escalated to the development team.



jjshoe
Posts: 32
Member Since:
2007-08-13
What was your support ticket

What was your support ticket number so I can look into this? I haven't seen anything roll into our queue yet :)

Thanks,
Joel
Fonality Engineer



callinectes
Posts: 200
Member Since:
2007-05-12
The ticket is 1014898. I

The ticket is 1014898. I was working with Dean.



pcsknox
Posts: 42
Member Since:
2007-07-03
I am having the same issue.

I am having the same issue. I dont have the server live to test it.. but i get the " Could not open FindMe settings file. Please contact support. " Error after I work on the FMFM settings. I did have the config banner issue yesterday but it is gone today.

Server 119212

Thanks,



Mike Joyce
Posts: 424
Member Since:
2007-03-07
I went ahead and synced your

I went ahead and synced your system. Can you verify that this problem is resolved?

Thanks,
Mike



pcsknox
Posts: 42
Member Since:
2007-07-03
Thanks Mike, Everything

Thanks Mike, Everything looking swell!



keystoneit
Posts: 27
Member Since:
2006-09-04
Same problem with a server moved to new hardware

I ran into this last night on 109192. We recently reinstalled that server on different hardware. Could you guys please re-sync that system?

Thanks!

Pat



Mike Joyce
Posts: 424
Member Since:
2007-03-07
Pat, I just checked your

Pat,

I just checked your system and I found that all files were currently in sync. What problem are you having exactly?

Thanks,
Mike



keystoneit
Posts: 27
Member Since:
2006-09-04
Same as original post

"Could not open FindMe settings file. Please contact support."



ryanv
Posts: 7
Member Since:
2008-05-05
Same issue.

"Could not open FindMe settings file. Please contact support."

I'm getting the same error for the Call Center edition server#: 119834. I receive this error as I try to save an extension's FindMe settings.

Thank you for helping.



keystoneit
Posts: 27
Member Since:
2006-09-04
I called in about this

Some files needed to be pushed to the server, I also told them #119834 needed the same thing done, so that one should clear up also.



ryanv
Posts: 7
Member Since:
2008-05-05
Issue resolved

My issue was resolved by Support re-syncing/updating my files. Seems like the issue was caused from a bad Pro standard to Call Center migration.

Thank you to those who helped.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.