cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1131
Views
0
Helpful
5
Replies

Unity does not answer anymore.

rivabe123
Level 1
Level 1

We had Unity working.

We could select the voicemail pilot.

We left a message at the subscriber voicemail box and the subscriber got the MWI-ON message.

After listening to the message we deleted the message. However the MWI stayed on.

We forced the MWI-OFF by dialing the MWI-OFF number (after changing some calling search spaces).

Strange thing we have now is that we are able to dial the voicemail pilot, however it keeps ringing and doesn't get connected to the voicemail.

Iám able to dial the voicemail ports (after changing some CSS). But I don't see them entering the port monitor tool.

Below I have the output of the dbwalker utility.

Any reason why my voicemail does not let the wav file play??

================================================================

Running dbWalker version:4.0.39

0:0:Search for '(error)' or '(warning)' to find logged errors and warnings.

Starting walk at:10/30/2007 16:04:31 PM

Local Unity Version=4.2(1.0)

Local server name= SPFSVUNITY1

Backend is Exchange 2000 or 2003

================================================================

Running dbWalker based on user input. User=SPFBEHEER\UnityAdmin

Storage Info

Unity is logging diagnostic and data files to: D:\CommServer\Logs\

That drive has:

41948.93 Megs total

39343.71 Megs free

93.79% available free space

Unity is temporarily storing voice messages for UMR to: D:\CommServer\UnityMTA\

That drive has:

41948.93 Megs total

39343.71 Megs free

93.79% available free space

*** Starting location object walk ***

Checking cross box transfer and login tables

*** Starting DTMFAccessID Table walk ***

26 entries checked.

Checking for duplication ParentObjectID entries in DTMFAccessID table

*** Starting General System Checks ***

Primary server name found='SPFSVUNITY1'

Checking LastModifiedTime column for all entries in the Configuration table

*** Starting subscriber walk ***

*** Starting call handler walk ***

*** Starting subscriber template walk ***

*** Starting directory handler walk ***

*** Starting interview handler walk ***

*** Starting Distribution List walk ***

*** Starting routing rules walk ***

Rule Name=Attempt Forward to Greeting

Rule Name=Attempt Sign-In

Rule Name=Default Call Handler

Set to go to call handler with alias=openinggreetingch

*** Checking For Orphaned Table Entries ***

*** Check For Orphaned WAV Files ***

1605:(error) stranded wav file name=D:\CommServer\Stream Files\ESubscriberVoiceName.wav

You can fix this by selecting the 'Removed orphaned WAV files automatically' option and re running dbWalker

1605:(error) stranded wav file name=D:\CommServer\Stream Files\UnaddressedFaxesVoiceName.wav

You can fix this by selecting the 'Removed orphaned WAV files automatically' option and re running dbWalker

*** Check for orphaned GlobalSubscriber table entries ***

Database walk complete at:10/30/2007 16:04:39 PM

Errors Found: 2

Fixed Count: 0

Warning Count: 0

5 Replies 5

Rajesh Revuru
Level 4
Level 4

How is your Hunt group setup for your voicemail setup?

Did you try "Re-sync" MWI on the UTIM?

Hi -

These DBWalker errors are not causing the problem you are seeing. Since you have been making changes in CCM, I would check your Unity ports in your CallManager server and make sure they are registered. I would also reset the CallManager hunt list for your voicemail ports (which will cause Unity ports to reregister with CallManager).

Ginger

The voicemail ports are registered. Also resetting the total callmanager did not do the trick.

Resynching the MWI did not help either.

The voicemail ports are registered. Also resetting the total callmanager did not do the trick.

Resynching the MWI did not help either.

I have created a hunt group which is in the VMPilotPT and when calling this number it goes to the hunt list which has all the answering port in it. This number keeps ringing and does not seem to get the voicemail.

Hi guys, I think I have fixed it. The reason why I had this issue is not known to me. Maybe you guys can help me with this.

What I had done after all was working is run disaster backup.

Last thing I could do before doing a new install was putting back the UnityReg.reg.

So I have and all is working again.

I have attached the registry good and bad to this mail. So you can have a look at this.