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

Key: XCF-2737
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Richard Kolkovich
Votes: 0
Watchers: 1
Operations

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

MP-124 Config generation NPEs

Created: 2008-08-13 14:10   Updated: Wednesday 13:09
Component/s: audiocodes
Affects Version/s: 3.11.4
Fix Version/s: 3.11.8

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File audiocodes.patch (2 kb)

Environment: CentOS 3.11.4 install CD - yum updated to August 12th nightly RPMs
Issue Links:
Duplicate
 
This issue also reported as:
XCF-2765 Configuration (.ini) files are not ge... Critical Resolved
Related
This issue related to:
XCF-2601 Configuration (.ini) files are not ge... Major Closed
 


 Description  « Hide
When sipXconfig tries to generate the config file for my MP-124, it NPEs. The only thing that appears in the sipXconfig log is:

"2008-08-13 14:09:05,341":ERROR:ProfileManagerImpl:?:java.lang.NullPointerException

So something is eating the RuntimeException along the chain. It appears as if this affects all Audiocodes devices that are configured as Phones (FXS).

 All   Comments   Work Log   Change History      Sort Order:
Richard Kolkovich - 2008-08-21 10:06
I actually found that this bug was patched in the 3.10 branch (http://track.sipfoundry.org/browse/XCF-2601), but it was not patched in trunk. I applied the attached patch to trunk, and the resulting RPMs were fine.

Damian Krzeminski - 2008-11-26 11:18
it was fixed in 3.10 branch - I'll check why it was never merged to mainline

Damian Krzeminski - 2008-11-26 13:09
My mistake: it looks like for some strange reason I blocked 12791 from merging.

http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14106

XCF-2737 Added proper support for versioning AudioCodes FXS gateways.

AudioCodes FXS model now declares two versions (5.0 and 5.2) which automatically adds UI for version selection.
Default version is set to 5.0 (just as in FXO case), admin can change it in UI to 5.2 for each newly added device).