The user is unable to create a distribution list on the Cisco Unity 4.0.5 Unified Messaging system and the unknown error, 80072030 error message appears. Rebooting the Cisco Unity server also does not make any change and there are no issues while creating the users on Cisco Unity.
In order to resolve this issue, complete these steps:
Note: Make sure all the check boxes are checked in Step 16.
Run the Message Store Configuration Wizard from the Add/Remove Programs in Cisco Unity.
Make sure to log on using the Cisco Unity installation account. Also note that the Unity services are stopped while the Message Store Configuration wizard runs.
You can also use the Public Distribution List Builder Tool in order to create the distribution list. For more information on Public Distribution List Builder, refer to Public Distribution List Builder.
This problem is documented by the Cisco Bug-ID:CSCec36950
Good day, We are planning to upgrade unity connection from 9.1 to 12.5 currently Unity 9.1 is hosted on esxi version is 6.0 We wish to upgrade esxi to version 6.5we know UC 9.1 is not compatible with esxi 6.5, however if we should upgrade t...
Hi There, We are trying to install CUCM PUB 12.5 and we are struck on the black blank screen from past two hours. we can wee RAM is being utilized 100% and CPU is around 20%. Is this normal? If yes, how long we have to wait until this black screen is...
A customer has a Jabber Directory Integration with LDAP. From the Jabber search, he should be able to search users by various other LDAP Attributes. The feature generally works (e.g. he can search for a City, and it will show him all users that have the C...
HelloIn the macro framework, is there a way I can register to the HttpClientResult response after I send an HTTP get request?In putty, affter sending a xcommand HttpClient get, I get this:*r HttpClientGetResult Body: example I would like to get that ...
I'm struggling to understand why the From in our outbound INVITE to our primary ITSP is using the IP address of our secondary ITSP, instead of the IP address of our CUBEs sending interface. INVITE from Jabber to CUBE is fine:Received:INVITE sip:80781...