Vodia PBX Posted January 7, 2008 Report Share Posted January 7, 2008 There were a couple of important fixes around the daily sending of emails that caused problems in several places. I think everyone running 2.1 versions should move to that version. The release notes are available at http://wiki.pbxnsip.com/index.php/Release_Notes_2.1.5. Quote Link to comment Share on other sites More sharing options...
Bill H Posted January 7, 2008 Report Share Posted January 7, 2008 Is there a URL to download the newer 2.1.5 version? Bill H Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 7, 2008 Author Report Share Posted January 7, 2008 Is there a URL to download the newer 2.1.5 version? http://www.pbxnsip.com/software has it! Quote Link to comment Share on other sites More sharing options...
cfcs Posted January 8, 2008 Report Share Posted January 8, 2008 There were a couple of important fixes around the daily sending of emails that caused problems in several places. I think everyone running 2.1 versions should move to that version. The release notes are available at http://wiki.pbxnsip.com/index.php/Release_Notes_2.1.5. I installed this update on my CS410 and my fxo ports stopped working. I installed an older image and they started working again. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 8, 2008 Author Report Share Posted January 8, 2008 I installed this update on my CS410 and my fxo ports stopped working. I installed an older image and they started working again. Try disabling the pass-through mode. This seems to be an ongoing pain in the neck, especially with the CS410 PSTN gateway. You can do this from the web interface (once that you are logged in as admin) with http://1.2.3.4/reg_status.htm?save=save&am...s_through=false. Quote Link to comment Share on other sites More sharing options...
cfcs Posted January 9, 2008 Report Share Posted January 9, 2008 Try disabling the pass-through mode. This seems to be an ongoing pain in the neck, especially with the CS410 PSTN gateway. You can do this from the web interface (once that you are logged in as admin) with http://1.2.3.4/reg_status.htm?save=save&am...s_through=false. That didn't work. Quote Link to comment Share on other sites More sharing options...
phsean Posted January 9, 2008 Report Share Posted January 9, 2008 Would someone be able to point me to an authoritative pbxnsip version of the polycom 2.2.2 config xml files? I don't see the files anywhere in the full 2.1.5 version, and will need to merge our custom settings into them before we can go live with the new support. Thanks! (Last time they were hidden in a forum beta full-build, but I don't see one for 2.1.5 -- looks like Kristan obtained them somehow -- always a step or two ahead of me ) Quote Link to comment Share on other sites More sharing options...
Kristan Posted January 9, 2008 Report Share Posted January 9, 2008 Would someone be able to point me to an authoritative pbxnsip version of the polycom 2.2.2 config xml files?<snip> looks like Kristan obtained them somehow -- always a step or two ahead of me I don't think I'm ahead of anyone! I have the polycom supplied 2.2.2 reference files, but not the PBXnSIP customised versions. I'd be quite interested to have a look at them myself I have to admit, just to see the differences. Quote Link to comment Share on other sites More sharing options...
Kristan Posted January 9, 2008 Report Share Posted January 9, 2008 Actually it looks like we're all behind, polycom released SIP 3.0 firmware on the 4th Jan...! Quote Link to comment Share on other sites More sharing options...
phsean Posted January 9, 2008 Report Share Posted January 9, 2008 How about that... I see the user and admin's guide, but not any release notes on their main support pages; I wonder what's new. Quote Link to comment Share on other sites More sharing options...
hosted Posted January 10, 2008 Report Share Posted January 10, 2008 Actually it looks like we're all behind, polycom released SIP 3.0 firmware on the 4th Jan...! Where my Polycom Partner login only shows v2.2.2? Quote Link to comment Share on other sites More sharing options...
phsean Posted January 10, 2008 Report Share Posted January 10, 2008 Where my Polycom Partner login only shows v2.2.2? Wish I had one. The User and Admin guides for SIP 3.0 that I see are here: http://www.polycom.com/usa/en/support/voic...oint_ip430.html Quote Link to comment Share on other sites More sharing options...
Kristan Posted January 10, 2008 Report Share Posted January 10, 2008 My partner login is a waste of time, I never seem to be able to do anything from there! I was speaking to our supplier and he mentioned it was available. I have the release notes but no firmware as yet (it hasn't appeared on the FTP server). One major change is that polycom have launched what they call their 'Productivity Suite'. It's a set of optional features (including LDAP directory access amongst others) that you have to buy an extra license for (per phone). It's not like their stuff isn't expensive enough already! Quote Link to comment Share on other sites More sharing options...
RobertO Posted January 10, 2008 Report Share Posted January 10, 2008 Today our PBX crashes (2.1.5.2357 (Win32)). The only thing I can see is an entry in the System-Eventlog. Service "pbxnsip PBX" stopps unexpectly (translated). In the Application-Eventlog there is no entry. Are there any other log-files that I can send you to identify the problem? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 11, 2008 Author Report Share Posted January 11, 2008 Are there any other log-files that I can send you to identify the problem? Is there anything suspicious with memory usage or the number of threads? Quote Link to comment Share on other sites More sharing options...
RobertO Posted January 11, 2008 Report Share Posted January 11, 2008 Nothing conspicuous to see. Memory and CPU usage is extremly low. Have heart that at this time a user has a problems with callbach on busy. So today I have disabled "Offer Camp On". May be this could be a hint. Quote Link to comment Share on other sites More sharing options...
phsean Posted January 14, 2008 Report Share Posted January 14, 2008 Pbxnsip: Sorry to nag, but is there a "stock" pbxnsip version of the Polycom 2.2.0 config files? Thanks! Quote Link to comment Share on other sites More sharing options...
ap_6200 Posted January 14, 2008 Report Share Posted January 14, 2008 Call Park – Multiple Lines I’ve found an issue where Call Park fails when you have multiple lines registered on a phone (happened to be a Polycom 501) on SIP version 2.2.0.0047. Going through the normal process to park a call produces the "call park has failed" message. Is this a known bug with this version or not? Does anyone know of any workarounds? This could cause a lot of problems down the road. Thanks! Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 14, 2008 Author Report Share Posted January 14, 2008 You mean, the phone sends a star code to the PBX? And that results in the "call park has failed"? Is it a phone config problem or a problem of the PBX handling the star code? Quote Link to comment Share on other sites More sharing options...
phsean Posted January 14, 2008 Report Share Posted January 14, 2008 Call Park – Multiple Lines Haven't done it (we use star codes to park), but if the phone park softbutton is what you're using to park a call and it's config'd to always park a call at a hardcoded orbit #, then I could see you getting an error message if it tried to park two calls on the same orbit. Quote Link to comment Share on other sites More sharing options...
ap_6200 Posted January 14, 2008 Report Share Posted January 14, 2008 You mean, the phone sends a star code to the PBX? And that results in the "call park has failed"? Is it a phone config problem or a problem of the PBX handling the star code? I mean that when we dial *85 - on any phone with only 1 line configured - Call Park works perfectly. On phones with multiple lines (2 or more) - The Call Park fails using *85 ( or even *85xxx to park it to a specific extension) Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 14, 2008 Author Report Share Posted January 14, 2008 I mean that when we dial *85 - on any phone with only 1 line configured - Call Park works perfectly. On phones with multiple lines (2 or more) - The Call Park fails using *85 ( or even *85xxx to park it to a specific extension) I still don't get it. Lines equal lines in the registration tab of the extension in the PBX? Quote Link to comment Share on other sites More sharing options...
ap_6200 Posted January 15, 2008 Report Share Posted January 15, 2008 I still don't get it. Lines equal lines in the registration tab of the extension in the PBX? Yes: Example: Extension 900 - Registered 2 Regs Extension 901 - Registered 1 Reg Extension 902 - Registered 2 Regs On ONE Polycom Phone - 2.2 firmware and PBXnSIP 2.1.5 - I have Line 1 - 901 Attempting to place any active call on CALL PARK using the *85 feature code results in a successful "CALL PARK" On ONE Polycom Phone - 2.2 firmware and PBXnSIP 2.1.5 - I have Line 1 - 900 I have Line 2 - 902 Attempting to place any active call on CALL PARK using the *85 feature code results in a "CALL PARK FAILED" Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 15, 2008 Author Report Share Posted January 15, 2008 Okay. Anything in the log like: "Could not find call of user ... that should be parked", "The call of user ... cannot be parked", or "The call of user ... cannot be parked as there was no free orbit available in ..."? Quote Link to comment Share on other sites More sharing options...
hosted Posted January 16, 2008 Report Share Posted January 16, 2008 FYI polycom SIP 3.0 is now online. 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.