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

Key: XCF-2529
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Anushree Ganguly
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

HA : CDR page gives an Internal Exception when sipxcallresolver agent is not Running in the Distributed machine.

Created: 2008-05-07 04:54   Updated: 2008-08-25 23:55
Component/s: CDRs
Affects Version/s: 3.10.2, 3.11.2
Fix Version/s: 4.0

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. GZip Archive cdr_exception-earth.qantom.int.tar.gz (917 kb)
2. GZip Archive cdr_exception-moon.qantom.int.tar.gz (553 kb)
3. Text File cdr_exception.txt (21 kb)
4. File Response in local systems.bmp (1.60 Mb)

Environment:
sipxproxy 3.10.2-012521 2008-05-02T23:02:58 oem-centos5
sipxproxy 3.11.2-012494 2008-05-01T03:28:40 oem-centos5


 Description  « Hide
Preconditions :
1.All the required services in the master's and Distributed machine are Running.

Steps to Reproduce :
1.Stop the sipxcallresolveragent service in the Distributed machine.
2.Go to Diagonostics --> CDR

Result :
An internal Exception occurs.

Observation:
Can be related to XECS-1399

 All   Comments   Work Log   Change History      Sort Order:
Damian Krzeminski - 2008-05-07 08:23
Is it only HA? What if you stop the local callresolver only?

Anushree Ganguly - 2008-05-08 01:07
Yes ,This is a HA specific problem.In local systems , the CDR page displays an error message "Unable to Display active calls.Callresolver is not available." when the callresolver is stopped .CDR displays only the historic page.Active link is absent. I am Attaching the screenshot "Response in local systems" that describes this behavior.
Verified in the following builds :
sipxproxy 3.11.2-012452 2008-04-26T19:20:48 oem-centos5

and

sipxproxy 3.10.2-012521 2008-05-02T23:02:58 oem-centos5

Shruthi Sarpamale - 2008-06-25 03:50
This issue continues to exist in ecs-3.10.1-008652-012944-i386 iso.