Reflexes phone unable to connect to voice guide after migrat
Posted: 24 Nov 2009 09:04
I have a release in R6.0 f1.602.3 that I’m upgrading to R9.0 h130134.
After migration the reflexes phone (4035/4020) is not able to listen to the voice guide.
- Vgstat on the SUVG board show the VG message as it should be.
- Use tone test and non of the VGs are heard from the Reflexes phone, just tone. On the analogue and 9-series there is no problem.
- When doing tone test with analogue phone, vgemis show the played vg.
- When doing tone test with Reflexes phone, vgemis show nothing.
- Tried the migration by using mao before recover (i.e. before fichges force_recover_dico) and after but both give me the same problem.
- Tried migrating first to R6.0.1 f1.603.1 (and also R9.0 h1.301.27 and R9.0 h1.301.31) and the problem seems to be consistent on all of them (i.e. no access to VG on Reflexes).
- There is no problem if I create a blank new database on R9.0. So the database I originally backup in R6.0 is corrupted???
Is there ways to fix the database (maybe before or after migration R9)? I don’t want to rebuild the database from scratch.
Are there any traces that I can launched to check what’s wrong with this?
Many thanks!
After migration the reflexes phone (4035/4020) is not able to listen to the voice guide.
- Vgstat on the SUVG board show the VG message as it should be.
- Use tone test and non of the VGs are heard from the Reflexes phone, just tone. On the analogue and 9-series there is no problem.
- When doing tone test with analogue phone, vgemis show the played vg.
- When doing tone test with Reflexes phone, vgemis show nothing.
- Tried the migration by using mao before recover (i.e. before fichges force_recover_dico) and after but both give me the same problem.
- Tried migrating first to R6.0.1 f1.603.1 (and also R9.0 h1.301.27 and R9.0 h1.301.31) and the problem seems to be consistent on all of them (i.e. no access to VG on Reflexes).
- There is no problem if I create a blank new database on R9.0. So the database I originally backup in R6.0 is corrupted???
Is there ways to fix the database (maybe before or after migration R9)? I don’t want to rebuild the database from scratch.
Are there any traces that I can launched to check what’s wrong with this?
Many thanks!