04-13-2005 11:20 AM - edited 03-20-2019 05:43 AM
Users on my system are receiving a message indicating that they have added the maximum number of users to their private distribution list after the 25th member via the TUI. The Unity Administration guide indicates that there is not a limit on the number of users that can be added to a Private Distribution List.
Is there a 25 user limit?
Is this a configurable parameter?
Thanks in advance for any assistance!
Solved! Go to Solution.
04-13-2005 03:00 PM
This is a conversation bug - it's a hold over from when we used to have to cram all the private list members into a binary blob and stuff it into an extended property on an Exchange 5.5 object back in the day - there were space limitations so we had to cap the members of the DL.
The SA/PCA removed this restriction a while ago, but the TUI just missed it - it's tracked in this bug:
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed43179&Submit=Search
sounds like the limitation is fixed in the upcoming 4.0(5) release.
04-13-2005 03:00 PM
This is a conversation bug - it's a hold over from when we used to have to cram all the private list members into a binary blob and stuff it into an extended property on an Exchange 5.5 object back in the day - there were space limitations so we had to cap the members of the DL.
The SA/PCA removed this restriction a while ago, but the TUI just missed it - it's tracked in this bug:
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed43179&Submit=Search
sounds like the limitation is fixed in the upcoming 4.0(5) release.
04-13-2005 03:11 PM
Very good. Thanks for the information!
04-15-2005 10:41 AM
OK..We implemented this fix and the 25 user limit appears to be resolved.
However, now when I add users to Private lists using the TUI, many of the extensions that I add and that are confirmed by Unity as having been added are not appended to the list of names.
For example, if I
1) access list private list 1 and add 10 extensions
2) Verify that prompt verifies all names were added
3) Exit the list and press 2 to play back the names
Sometimes 10 names will be added to the list and other times anywhere from 0 to 9 names will be added.
The system is 3 4.04 SR1 Unity servers partnered with 3 exchange 2K servers.
Any idea what could cause this issue?
Thanks,
Robert
04-15-2005 10:58 AM
Please disregard previous email. I was able to verify that the users were pressing # instead of * after adding their names.
Amazingly enough, when we press the correct keys, it works.
Sorry for any inconvenience!
04-15-2005 01:32 PM
Jeff:
We changed the value to 0x64(100) and when we try to add more users than 25 some where around 30+ we get failsafe message stating system un available. and we see below in application log
This is on unity 4.0.4 Sr1 with exchange offbox. and mailstore is not offline. users can still get their VMs
Do we have to make it 999 for it to work properly ?
***
EVT_SUB_METHOD_HRESULT
ID: 119
Source: CiscoUnity_ConvSubscriber
Message: An unexpected error has occured while a
subscriber is on the phone with Unity. This can
potentially result in the subscriber hearing the
failsafe conversation. Technical details are - %1
returned [%2] on line %3 of file %4.
An unexpected error has occured while a subscriber is
on the phone with Unity. This can potentially result
in the subscriber hearing the failsafe conversation.
Technical details are - %1 returned [%2] on line %3 of
file %4.
***
04-15-2005 01:42 PM
Just out of curiosity, do your users have access to CPCA? I think it's easier to manage Private DLs from the web interface. And there are no limits enforced, like Jeff pointed out earlier.
04-15-2005 02:04 PM
Problem is we donot or cannot enable PCA for all users. This is kind of green field install of around 8000 users and its VM only solution. If I enable PCA for all users I have to deal with big security issue of allusers using same AD password. As there is no way to change the PCA password/AD passowrd from unity's PCA. ( I was told some time in the future its going to be Phone PIN )& Customer's AD policies doesn't allow the user to change passowrd on other domains. and in our situation VM is in totally diff AD.even though there is a IP connectivity they cannot change password for Voice AD.so to answer your question we can do it for few users and we can do it per user basis but there is no way I can do it for 8000+users.
04-15-2005 02:49 PM
Yes, you should set it to 999 - I believe the conversation back end code looks for that value specifically to mean "unlimited", it doesn't look at it as the limit of users (i.e if you put in 95 it wont stop at 95 users I don't believe) - either way, the note does specifically say 999 so I'd stick with that.
04-21-2005 07:17 AM
Jeff,
Any idea whether this setting should be 999 in decimal or Hex? We set it to 999 Decimal (3EF Hex) and we still receive the fail safe message occassionally when users press the * key from the TUI after entering their PDL members.
Thanks,
Robert
04-21-2005 07:48 AM
should be decimal 999 - if you're getting failsafe, it's probably for another reason - you should probably open a TAC case specific to that.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide