History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XCF-2399
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Chaitra Sharma
Votes: 0
Watchers: 0
Available Workflow Actions

Resolve
Request Information
Operations

If you were logged in you would be able to see more operations.
sipXconfig

Few fields got disabled for all the users with the message as 'voicemail is not available for this user' on User Identification page

Created: 2008-03-28 09:10   Updated: 2008-05-01 06:28
Component/s: LDAP
Affects Version/s: 3.10.1
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. GZip Archive sipx-configuration-sun.qantom.int.tar.gz (7.94 Mb)
2. GZip Archive snapshot_XCF-2399_Reproduced.gz (1.33 Mb)

Image Attachments:

1. Blank_user.JPG
(80 kb)

2. New_user.JPG
(126 kb)

3. Screenshot_XCF-2399.JPG
(125 kb)
Environment:
 sipxproxy 3.10.1-012137 2008-03-28T01:34:32 oem-centos5
  sipxconfig 3.10.1-012137 2008-03-28T01:44:57 oem-centos5


 Description  « Hide

While performing Sanity and regression tests on scs-3.10.1-008615-012137-i386.iso build, the error as shown in New_user.jpg was observed.
After this error, when Phone2 rejected calls from Phone1( both having voicemail permissions enabled previously), the prompt " That extension is not valid . Thank You. Good Bye" was played.

One of the suspicion is that, LDAP Import from Active Directory tests were being executed simultaneously might have led to the system going into bad shape.

Attached Files:
1. New_user.jpg
2.sipx-configuration-sun.qantom.int.tar

Note: Please login to the following system for further investigation.
Machine Name: sun.qantom.int
Password" root1234

 All   Comments   Work Log   Change History      Sort Order:
Damian Krzeminski - 2008-03-28 09:28
That means that sipXconfig for some reason does not have access to voicemail directory.

According to sipXconfig.properties it should be located here:

mailboxManagerImpl.mailstoreDirectory=/var/sipxdata/mediaserver/data/mailstore

Check if it exist and verify the ownership.


Chaitra Sharma - 2008-03-28 09:47
mailboxManagerImpl.mailstoreDirectory=/var/sipxdata/mediaserver/data/mailstore
is present under sipxconfig.properties.in file and ownership of this file is as follows:

-rw-r--r-- 1 sipxchange sipxchange 3.4K Mar 28 15:52 sipxconfig.properties
-rw-r--r-- 1 sipxchange sipxchange 3.7K Mar 28 15:15 sipxconfig.properties.in

Thanks,
Chaitra

Raghu Venkataramana - 2008-03-28 10:12
The mailstore directory also exists and has the right permission

[root@sun ~]# ls -alh /var/sipxdata/mediaserver/data/mailstore/
total 20K
drwxr-xr-x 4 sipxchange sipxchange 4.0K Mar 28 20:08 .
drwxr-xr-x 6 sipxchange sipxchange 4.0K Mar 28 20:07 ..
drwxr-xr-x 2 sipxchange sipxchange 4.0K Mar 28 20:07 124
drwxr-xr-x 2 sipxchange sipxchange 4.0K Mar 28 20:08 125
[root@sun ~]# ls -alh /var/sipxdata/mediaserver/data/mailstore/125
total 32K
drwxr-xr-x 2 sipxchange sipxchange 4.0K Mar 28 20:08 .
drwxr-xr-x 4 sipxchange sipxchange 4.0K Mar 28 20:08 ..
-rw-r--r-- 1 sipxchange sipxchange 23K Mar 28 20:08 savemessage.vxml

Chaitra Sharma - 2008-04-10 08:38
This issue appears to be an intermittent issue, But when it occurs few of the fields get disabled for all the users with a message 'voicemail is not available for this user'
Mentioned below is the scenario in which we found this issue.

1. Setup an MS Exchange server with Active Directory.
2. Add following users
Peter Sampras- with unified messaging enabled - associated with a mailbox policy having Min PIN Length=4 and user extension 99900
Andrew Agassy - without unified messaging enabled
Note: There was a default user Administraror as well, without unified messaging enabled

3. Now navigate to System -->LDAP /AD
4. Click on the LDAP Server quick link.
5.Here enter the details of the Active Directory Server being used and click Continue button.
6. On the LDAP / Active Directory server page enable the following Object classes and click on Continue button.
inetOrgPerson : Enabled
organizationalPerson : Enabled
person : Enabled
residentialPerson : Enabled
top : Enabled
User : Enabled

7. On the next LDAP / Active Directory server page enter the following:
Search base = CN=Users,DC=scslab,DC=qantom,DC=int
User Object Class = person
Filter = proxyAddresses=*
User ID attribute = displayName
First name attribute = displayName
Last name attribute = displayName
Alias attribute = []
Email attribute = []
User group attribute = []
Pin attribute = []
Default PIN = 1234
Confirm default PIN = 1234
SIP password attribute = []
Click on Continue button.

8. LDAP Import Preview page is displayed.
9. Now click on Import button
10. A message " LDAP import initiated. Go to Job Status page to monitor import operation progress." is displayed.

Observation:
1. A new blank user without userid, First name and last name as shown in 'Blank_user.jpg' is displayed on Users page.
2. Few fields got disabled for all the users with the message as 'voicemail is not available for this user' on User Identification page as shown in 'Screenshot_XCF-2399.jpg'
3. After this error, when Phone2 rejected calls from Phone1( both having voicemail permissions enabled previously), the prompt " That extension is not valid . Thank You. Good Bye" was played

11. Click on Import button again, the 'blank' user disappears from the Users table,
It appears again if the Import button is clicked again
12. The same issue was reproduced when 'TelephoneNumber' was used instead of 'DisplayName'

Attachments
1. Screenshot_XCF-2399
2. Blank_user.jpg
3. snapshot_XCF-2399_Reproduced

 

Chaitra Sharma - 2008-04-11 01:04
This is not a SCS specific issue. Hence changed the Security Level.

Chaitra Sharma - 2008-04-11 01:12
The ECS build used to reproduce this issue was:

sipxproxy 3.10.1-012233 2008-04-08T21:10:31 oem-centos5
sipxconfig 3.10.1-012233 2008-04-08T21:26:00 oem-centos5
sipxvxml 3.10.1-012233 2008-04-08T21:15:18 oem-centos5

Thanks,
Chaitra