natedev Posted February 18, 2009 Report Share Posted February 18, 2009 This should work http://www.pbxnsip.com/protect/pbxctrl-rhes4-3.3.0.3147For Cent OS, please use http://www.pbxnsip.com/protect/pbxctrl-centos5-3.3.0.3147 I'm having the same problem with pbxnsip 3.2.0.3144 (win32) running on Windows 2008 Standard x64. Would you have a new build for that as well? Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 19, 2009 Report Share Posted February 19, 2009 Tested the Red Hat version and the problem is resolved. Will you have a set of release notes for this build when you officially release it? Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 19, 2009 Report Share Posted February 19, 2009 I'm having the same problem with pbxnsip 3.2.0.3144 (win32) running on Windows 2008 Standard x64. Would you have a new build for that as well? We should be able to provide one for Win32 also. Probably today. Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 19, 2009 Report Share Posted February 19, 2009 I'm having the same problem with pbxnsip 3.2.0.3144 (win32) running on Windows 2008 Standard x64. Would you have a new build for that as well? Here is the Windows version http://www.pbxnsip.com/protect/pbxctrl-3.3.0.3147.exe Quote Link to comment Share on other sites More sharing options...
natedev Posted February 20, 2009 Report Share Posted February 20, 2009 Here is the Windows version http://www.pbxnsip.com/protect/pbxctrl-3.3.0.3147.exe Thanks! Hey... do you have a document with some of the changes? I noticed a few new features. Quote Link to comment Share on other sites More sharing options...
natedev Posted February 20, 2009 Report Share Posted February 20, 2009 Here is the Windows version http://www.pbxnsip.com/protect/pbxctrl-3.3.0.3147.exe I'm experiencing serious regression problems with this build and had to revert to 3.2.0.3144. Here's what I observed: - Calls to extension 100 went to extension 201 - Calls to extension 201 went to extension 100 - When I rebooted the Polycom SoundPoint IP 670, I got an error when it booted up causing it to go into an endless reboot cycle. Replacing 3.3.0.3147 with 3.2.0.3144 resolved these issues immediately. I still have the voicemail problems though. Quote Link to comment Share on other sites More sharing options...
natedev Posted February 23, 2009 Report Share Posted February 23, 2009 Here is the Windows version http://www.pbxnsip.com/protect/pbxctrl-3.3.0.3147.exe Do you have a newer build that fixes the other issues (like calling one extension rings another one, and Polycoms crash when rebooting - probably a mistake in the XML for the phone config)? Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 24, 2009 Report Share Posted February 24, 2009 Do you have a newer build that fixes the other issues (like calling one extension rings another one, and Polycoms crash when rebooting - probably a mistake in the XML for the phone config)? Do you have the logs for the calling one extension rings another one? Quote Link to comment Share on other sites More sharing options...
natedev Posted February 26, 2009 Report Share Posted February 26, 2009 Do you have the logs for the calling one extension rings another one? Sorry - I don't. I had to take that version down in a panic. Quote Link to comment Share on other sites More sharing options...
natedev Posted March 4, 2009 Report Share Posted March 4, 2009 Do you have the logs for the calling one extension rings another one? Here are some things I ran into with 3.2 and 3.3: http://forum.pbxnsip.com/index.php?showtop...post&p=9700 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.