On Thu, 2009-12-24 at 17:57 -0800, Todd Hodgen wrote: > I had a system running on a 4.0.4 update from a 4.0.3 ISO that I > recently backed, re-installed with ISO 4.0.4 and then reloaded the > backup file – both Configuration and Voicemail. > > > > I had several issues after the restoral that I thought were worth > sharing. > > > > The first was the music on hold. I had installed a wav file, which > did not get installed as part of the backup and restoral. This might > be normal, I’m unclear. However, it appears that the database was > pointing to that file still, as when a call was transferred and music > on hold should have appeared, it instead dropped the call on the > calling party, and the internal extension continued to ring. It > seems either the added files need to be moved as part of the backup, > or something needs to identify if a music file is actually there prior > to trying to play it. Under the music configuration screen, it was > on select. Simply chosing default fixed the issue.
Thanks for the analysis Todd - please file an issue on that right away. > After the restoral, one of my three ITSP gateways did not work – 404 > error. I isolated it to a telephone number in one of my forwarding > rules that had a trailing space. Deleting the space allowed the calls > to process to that forwarding rule. I had a similar issue with 4.0.2 > with an error produced from a trailing space. The error was “* Error > at file /etc/sipxpbx/forwardingrules.xml, line 67, char 36 > > * Message: Datatype error: Type:InvalidDatatypeValueException, > Message:Value 'voip.ms ' does not match regular expression facet > '[a-zA-Z0-9]+(-[a-zA-Z0-9]+)*(\.[a-zA-Z0-9]+(-[a-zA-Z0-9]+)*)*(:[0-9]+)?'.” > Not sure if these are related, but having this error appear was much > appreciated as it gave a good ideas of where to look. Well, clearly that space shouldn't have been there, and yes they were almost certainly related. Do you still have the backup file? If so, please hang on to it so that we can examine it (don't attach it to the issue - unlike a snapshot, it _does_ contain security-critical data). Did you try resending profiles for the system? The forwardingrules file should have been regenerated by that - was the bad file before or after resending profiles (or both) ? > Is there a place this issue that was causing the 404 error would have > been logged? I’m thinking an issue should be written up on these. > Does anyone know of an existing list of items that don’t get copied > during the backup, that will impact the system upon restoral? It > would be good to create a laundry list to look at after a restoral. > I’d be happy to put it together and add it to the wiki. > > > > Regards, > > > > Todd Hodgen > > > > > > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
