natedev

Regarding the missing PnP field labels in 3.3.0.3152 (win32 on Windows 2008 x64): I only had a single file in /html called polycom_sip.xml. It's essentially the 3.1.2 SIP file from Polycom with the pbxnsip parameters entered into it. There's nothing else in /html. When trying to enter a MAC address into the Registration page, we didn't see any errors in the log. Just looked like it ignored the Save operation. I'll try that suggestion regarding increasing the delay before voicemail picks up and see if it affects the call forking to my cell. Thanks. Also - thank you for the link to the newer build. I'll run some tests against it right now to see if any of these have gone away. One thing I suspect as a possible problem is that as these new builds come out, I wonder if there's some legacy configuration in my files that is affecting things. It might be good to have a mechanism that can audit all the XML config files and even offer the option to get rid of deprecated settings (possibly tied to a backup of the old settings before doing that).

Here are some things I ran into with 3.2 and 3.3: http://forum.pbxnsip.com/index.php?showtop...post&p=9700

I posted a few of the things that I've seen under 3.2 and 3.3 here: http://forum.pbxnsip.com/index.php?showtop...post&p=9700

Here are some issues that I observed with this pre-release (3.3.0.3152 on Windows 2008 x64): - When calling in from a cellphone that is associated with an extension, when I hit 3 to go to the auto-attendant, it appears to be treating it as though I hit 3 then 3 again (which goes to a hunt group). Reverting to 3.2.0.3144 resolves this issue. - When I login as the system administrator and navigate to Settings -> PnP, the field labels are missing. Reverting to 3.2.0.3144 resolves this issue. - Calls coming in through our trunk were being misrouted. For example, calls to x100 rang x201 and vice versa. There were many examples of this severe behavior. We tried deleting and recreating extensions but it didn't help. Reverting to 3.2.0.3144 resolves this issue. - For Accounts (extensions), when I entered a MAC address on the Registration page and hit Save, the MAC address was not retained. I had to directly edit the extension XML files and restart the pbxnsip service. Reverting to 3.2.0.3144 resolves this issue. - The address book couldn't be seen on our Polycoms (Directories button -> Contact Directory...). Reverting to 3.2.0.3144 resolves this issue. - We use Polycom SoundPoint IP 670s and SoundStation 7000s (BootROM 4.1.2.0037, SIP 3.1.2.0392) with pbxnsip. We took the Polycom SIP file from Polycom's support website, parameterized it, and placed it in /html as polycom_sip.xml. When we upgraded to pbxnsip 3.3.0.3152, we found that many of the parameters were being ignored such as {sip-port layer} and {parameter transport}. This causes the phones to get a "Config Error" then repeatedly go into a reboot cycle. The behavior has been seen in all the other 3.3 builds as well. Reverting to 3.2.0.3144 resolves this issue. Our current issues with 3.2.0.3144 are: - Voicemails are delivered to us via email but not retained so we can access them from the phone. We do have Accounts -> Email -> After sending a message set to "Keep message as new message" (side note: need to shorten that gramatically to "Keep new message"). This has been a problem since we began using pbxnsip 3.0. Sometimes, voicemails do stay in the system but only about 10% of the time. - Call forking to cellphones only works about 25% of the time. This functionality wasn't working well under 3.0 either. Hope this helps! Let me know if there's a newer build of 3.3 that you'd like me to test. Regards, Nate

3.3.0.3147 was supposed to address this though we found some other serious problems with Polycoms, and calls routing to wrong extensions.

Sorry - I don't. I had to take that version down in a panic.

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)?

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.

Thanks! Hey... do you have a document with some of the changes? I noticed a few new features.

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?

Let me second this one! We have two trunks - CALLCentric and Broadvox. We have one line with CALLCentric and 5 with Broadvox. When all five lines on Broadvox are used up (co lines 1-5), we want it to automatically select co6 on CALLCentric. We've got the dial-plan setup that way and the failover set but it doesn't work.

Turned out to be a license issue.

Regarding the "Rewrite global numbers" dropdown on the Trunk Settings, I read this in the Wiki: "When you are using a trunk, you might have to represent the telephone number is a specific format. For example, in the NANPA area, you might want to use 10 or 11 digits to represent a national number. If you are using several trunks, you can represent the same number in different styles depending on the trunk" The documentation doesn't spell out what this setting really does. Can anyone provide an example of how this setting affects users? Does it just reformat the caller ID? I've tried changing it but haven't seen any effects.

We have pbxnsip 3.2.0.3144 (Win32) running on 64-bit Windows 2008 Standard. One thing we're experiencing is that voicemails that are sent as attachments are not being retained (message light on phone goes out and checking for messages tells me I have zero). On each extension's email settings, we've selected "Send message as attachment to email" and "Keep message as new message". I think this may be a defect. Anyone else running this version and experiencing this?

Bill, Thank you so much for your reply. I'll set that up. Might be a while until my lines fill up again but this sounds like the logical solution. Thanks again, Nate

If I have two trunks in one domain - one that can handle five simultaneous calls (let's call it TrunkA) and the other which can handle one (TrunkB), is it possible for me to setup the dial plan to prioritize TrunkA such that the first five outbound calls travel through it and the sixth goes out on Trunk B? Here's a simplification of the dial plan that I created: Pref Trunk Pattern Replacement 100 TrunkA xxxxxxxxxx 1xxxxxxxxxx 200 TrunkB xxxxxxxxxx 1xxxxxxxxxx I have CO lines setup for TrunkA - co1 co2 co3 co4 co5. For TrunkB, I have co6. If co1-5 are in use, pbxnsip 3.1.2.3120 doesn't use co6 for the sixth outbound call (assuming I'm dialing 10 digits). Is there a way to do that? Seems like it's trying to get the sixth line on TrunkA.

Think I know what the issue was. If you use the # after direct destinations, you have to use it on all of them including the dial by name.

Yeah, we only have one auto-attendant and the correct message is being played and the direct destinations all work.

Got the auto-attendant setup as extension 777 with these options: 1# calls a hunt group for sales 2# calls an agent group for tech support 3# calls a hunt group for human resources 4# calls the hunt group for finance 5# dial by name 0# connects to an extension designated as the operator Extensions are 3-digits. When I test it by dialing 777 from my extension, it works perfectly. If I type in an extension briskly, it connects to the correct extension (even if the first digit is one of the direct destinations above). When I call our trunk from my cell phone, I get the auto-attendant. But if I try to type in an extension number (same pace as when I do it from my extension), it connects to one of the direct destinations instead. For example, I try typing 100 but it connects me to 1 (sales hunt group). I realize I could renumber all of my extensions to be in the 600 or 900 range but it's a pain to do that and it would change how I wanted to organize extensions. It works so well from internally. I just don't understand what the issue is from outside calls. Anyone have any suggestions?

Thanks - now I get it!

Since upgrading to 3.1.x, I've noticed that I get the following options when I call in through a trunk that specifies the auto-attendant as the recipient... To place an outbound call, press 1. To go to your mailbox, press 2. To go to the auto-attendant, press 3. I just want it to go straight to the auto-attendant like before. Any ideas on how to disable this feature? Thanks in advance, Nate

Just downloaded 3.1.2.3120. I see the general release notes for 3.1. Is there anything information about the changes made in this latest build? Thanks, Nate

Thanks - great suggestion. It accomplishes just what I needed.

Not sure if anyone else is running into this but when we add an entry to the Domain Address Book (Domain -> Settings -> Address-Book), all the existing entries disappear in the table above until the pbxnsip service is restarted. Also, if I change the result length from 10 to 20 or 50, it doesn't seem to remember that setting and always goes back to 10 which is too short, IMO, for a default.

Yep, did all of that. Here's what I've discovered. If Settings -> Ports -> TFTP -> "Generate passwords" is set to "Username/password" required", under 3.0.1.3023, you can login as your extension number and password. Under 3.1.1.3118, you have to specify the domain even if there is only one domain (eg 100@mydomain.com instead of 100). Would this qualify as a bug in that the functionality that was there was removed? Also, the Polycom configuration files that pbxnsip generate (http://<pbx address>/provisioning/polycom_phone_<MAC>.cfg) set reg.<number>.auth.userId to the extension number and not extension@domain.