I'd like to confirm, I see the same problem. When a user with russian (utf8) display name leaves a vm message, I see the following problems: 1. Message recipient can not hear message through his phone. The call to the vm is established, but when dtmf tone '1' (to listen to inbox messages) is sent, the call is dropped. 2. Message recipient can not login to his web ui, due to "internal error occurred". I guess, this happens because the first page a user sees is his vm inbox, where "problematic" message exists.
When the same user has ascii display name, all works fine. A snapshot with the problem (INFO log level) is available at ftp://sipx:[email protected]/sipx-configuration-beaver.sip.nstel.ru.tar.gz. The snapshot contains both good and bad voice mail. A user 3853 with ascii display name left a vm message for 3840 at 08:57. This message is then succsessfully heared by 3840. The same user 3853 with russian utf8 display name left a vm message for 3840 at 09:00. And that message is not available, though files in /var/sipxdata/mediaserver/data/mailstore/3840/inbox are present. I use sipx 4.2.1-018971 2010-08-17T02:19:33 build34 installed from iso. But in this version vm did not work at all, untill I updated sipxivr package up to 4.2.1-18970.9.1 version (it was 4.2.1-18970.8.1). Is it a bug in the voicemail system or a configuration problem? Is there an issue in the tracker? Should I create one? Thanks and regards, Nikolay. > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Alexey Kanukhin > Sent: Friday, August 27, 2010 2:11 AM > To: Worley, Dale R (Dale) > Cc: [email protected] > Subject: Re: [sipx-users] Problem with sipXecs 4.2.1 voice > mail and caller Display Name in Unicode > > You can find sipXecs snapshot file at following link: > https://docs.google.com/uc?id=0B7frGZobn9jyN2YyNmNhMTAtZjU4My0 0NGY1LWExNzctM2IxN2ZiNGRlMzgz&export=download&authkey=CN2omfwN&hl=en > You can find captured packets at following link: > https://docs.google.com/uc?id=0B7frGZobn9jyNzkxZWNiNWYtMGI5Yy0 0ZmJjLWFhODAtNjk0ODc1ODMyNjEz&export=download&authkey=CILQqOcE&hl=en > Problem Call-ID is: OGMyOGUxODExMGVjZTY1NDRjMTY3NDE1YzU1ODg2NDk. > > -- > Sincerely yours, > Alexey Kanukhin > > > On Thu, Aug 26, 2010 at 7:09 PM, Worley, Dale R (Dale) > <[email protected]> wrote: > > ________________________________________ > > From: Alexey Kanukhin [[email protected]] I captured a voice mail > > session by the Wireshark tool. The captured packets are in the > > attached file. > > ________________________________________ > > > > I want to see a sipXecs *snapshot*, which captures far more > information than Wireshark and makes diagnosis much easier. > > > > Also, unfortunately, I can't see e-mail attachments with > this account, so you'll have to put the snapshot some place > where I can retrieve it. > > > > Dale > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
