Woof!
On Tue, 15 Jun 2010 11:55:13 -0400, Douglas Hubler <[email protected]>
wrote:
> Essentially, the sipXivr is saving dates in a format that is tied to
> the language of the installation and I think should pick a format that
> is language agnostic. Leave the locale to sipXconfig's rendering
> layer.
Well, that's one way of looking at it...the other is that sipXconfig's
inability to parse the date while in the same locale is a bug. ;-)
The date format was chosen to match sipXvmxl's as closely as possible, so
that in an upgrade situation, voicemails created before the upgrade were
still accessible.
There are three consumers of this date:
1. sipXvxml (created it in the first place, and thankfully removed from
4.2 so we don't care about it reading it anymore)
2. sipXivr (needs to read sipXvxml's version, so that voicemails
created pre-4.2 can still be read)
3. sipXconfig (needs to read sipXvxml and sipXivr's version)
I don't recall if sipXvxml's output is locale sensitive or not, and I
don't care to dredge it up to check--but I'd bet it is. Fixing the locale
as 'c' (or whatever the Java equivalent is) should solve it.
--Woof!
_______________________________________________
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/
