8945 and visual voicemail

[Charles Federico]

Hello Everyone,

I am testing out a 8945 with the latest firmware installed.  When I run visual voicemail it reports back to me the following in the logs

00:00:21:22.454 - [XSI][ERR]xsi.viewControllerFactoryMap() unsupported object

00:00:21:22.454 - [XSI][ERR]========================================

00:00:21:22.454 - [XSI][ERR]xsi.viewControllerFactoryMap() return fail  object:

00:00:21:22.456 - [XSI][ERR]MIDlet-Jar-Size:345578

MIDlet-1:VisualVoicemail,,com.cisco.vtg.midlet.voicemail.VisualVMMidlet

MIDlet-Jar-URL:/midlets/TNP/VisualVoicemail.jar

MIDlet-Jar-RSA-SHA1:J4XIunVcSz7kyUntiddozKyVhZc8EA7Yi+a/vpzQGVAXZIx+CAtFD

00:00:21:22.456 - [XSI][ERR]========================================

On the phone simply "Unsupported XML Object

visual voicemail is working fine on the 79xx and 99xx phones that we have here.  So this begs the question, is visual voicemail supported on the89xx phones?

cucm 8.6

1 pub

3 subs

UC 8.6

1 sub

1 pub

firmware

SCCP8941_8945.9-3-2-11

thank you

[will.alvord]

Nope.  No visual voicemail on the 89xx phones.

[matgear]

Hi Will,

I know this post s a little old, but Load 9.3(4) of the 89xx seems to bee supported with Visual Voicemail.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8941_8945/firmware/9_3_4/english/release_notes/P415_BK_R20BE6A8_00_rn-9_3_4-8941-8945/P415_BK_R20BE6A8_00_rn-9_3_4-8941-8945_chapter_00.html

However I seem to be running into the issue you are when setting up a Service URL on the phone.

If I use the default Voicemail button, and select the option of Visual Voicemail, everything works well.

But as I mentioned, setting up a Service URL creates an Unsupported XML object.

Has anyone seen this, or found a resolution?

[pedram]

Hi

If the user receives incorrect pin error message from day one then it might be also the case?

[Carlo Poggiarelli]

Hi,

I would give a try by modifying the url.

Let me know 

Regards

Carlo

[Carlo Poggiarelli · Accepted solution]

Hi.

Maybe too late to answer you, but the issue was in the service name.

Make sure that you enter VisualVoicemail as service name without spaces.

That did the trick for me

HTH

Regards

Carlo