Kristan

Do the developers hate me yet? Would it be possible so that the substitutions for date, time, extension etc.. can be folders, not just part of the filename? So if I do $r/$d/rec-$t-$i-$u-$n.wav as the recording location, it'll give me a folder for each day there was a call recorded on, then time within that? or /$r/$u/$d/rec-$t-$i-$n.wav would be recordings/extension/day/rec-time-direction-number.wav Thanks!

On larger systems, it's a bit of a pain to have to enter all the extensions that *aren't* allowed to see your status via dialog permissions. To maintain backward compatibility, is there any chance you could add functionality so that you can prefix extension numbers with, say, a + symbol, which would mean "disallow all others, except this one". For example, in a 10 extension system, 100 - 109, if I want 101 & 102 to be able to subscribe/pickup 100, at the moment in 100 I have to do 103 104 105 106 107 108 109 Which would be the equivalent of +101 +102 I don't know how feasible that is - as an alternative maybe can we have an option on the extension or maybe domain for dialog permissions to be inclusive or exclusive? So change the option, and dialog permissions are denied by default, instead of allowed. As long as this option defaults to "allowed", you could keep it compatible with previous versions.

That'll be it Oh well, if I'm in a good mood tomorrow I might change the cell phone dial and switch them to 3 digits. Though there's 60 of them to do so maybe not

You definitely want the files from the 2.2 SIP firmware, then modify them to match the PBXnSIP ones (there's not too much) as the files with PBXnSIP didn't seem to work very well with 2.2 for me. In particular after provisioning, they wouldn't register after a reboot (kinda bad) and the screen display on the 550's wasn't quite right. Using the files in the polycom firmware fixed both these issues. I've also had a problem where on a 330, the first entry on the addressbook would set itself to the second line. No idea why - as a fix I've just disabled the directory option in the polycom_sip.xml file! As they don't need the directory, it's no biggie. We'll see what happens on monday when they actually start using the phones...

We've had this happen a couple of times on full 2.1 systems (only 2.1 thou.) Sequence goes; transfer call, talk to person, then person gets sent to VM and call to phone is killed. Is there some kind of timeout going on? We've never managed to catch it in the logs.

Strange, *001-*009 don't work, just get "this feature is currently unavailable". *010 and upwards seem ok. How annoying

If you have a look through the RC versions of 2.1 (the one with the full installer) - I'm pretty sure all the config files were in the html folder. If it's still up, try downloading that one and installing it on a spare box. The polycoms are provisioned, they get put on desks to today, and the switchover from their old PBX is on Friday night. This will be our biggest (and most complex) deployment so far.... Fingers crossed!!!

I already had It just said "This feature is not available". I have to admit, I didn't bother looking further into the logs, just changed it to a two digit one and it worked straight off. Should 3 digits be ok? I tried *001

Could we have 3 digit (or arbitary digit) speed-dials? Otherwise they're limited to 99...

PBXnSIP 2.1 comes with everything you need to provision the phones automatically - I've just done 50... All I've done is drop the 2.2 SIP app and version file in the tftp folder and make sure the phones are set to TFTP in the server options (and obviously set the TFTP option in DHCP).

Hmmm, ok, I can see that. Personally as a phone user, I'd prefer to use the pickup code and have the buttons work for dialing/transfering etc. Or for it to do both - users will understand if they press the button while it's flashing it'll steal the call, but 99% of phones and systems I've used have the buttons for calling extensions, not just monitoring them. Seems like a bit of a limitation to me, especially when setting the snom function key to extension makes it behave like that.

Thanks, that'll do nicely!

I've tried setting up a phone here with the buttons and the indicator lights work fine, but when set to extension, you can't press the buton and get it to dial that extension. Is there any way to have it monitor an extension AND work as a speed-dial button for that extension? You used to be able to do this on the snoms...

Hi, We've got a system where the customer would like the system to be able to give 3 prompts, and after the selection of the prompt say "Please note that your call may be recorded for training and monitoring purposes", then transfer them to the appropriate extention. I had thought I would just add an extra node, play the wav file and forward the call after x number of seconds... but there doesn't seem to be any way to do that. Also we'd like to be able to say "or please wait for an operator" after all the options, so that if they don't have a touch tone phone or DTMF isn't working the will still be able to get to talk to someone. Is there a way to set a timeout on the IVR nodes, or a way we can kludge this?

In a previous installation (2.0), we had a major issue with the following setup: 1 huntgroup with 5 phones each phone was watching each other's extension (so 4 buttons assigned as extensions) When a call came in, each phone was getting multiple notifies and the snoms couldn't cope and died. I have another installation where they have the same setup, a small office, a single hunt group with all the phones in, and they want to watch the status of each others phones. The new place has 2.1 and 7.1.24 firmware on the phones, or are we likely to still suffer the same problems using buttons or will it work?

Is it possible in the next version to be able to "name" an IVR node (same as you would a hunt group). Just makes it a bit more readable, so instead of just having 901 IVR Node 902 IVR Node 903 IVR Node 904 IVR Node you can have 901 IVR Node (Main) 902 IVR Node (Sales Menu) 903 IVR Node (Support Menu) 904 IVR Node (Other options menu) ta!

Oh well... I'd better get typing then!

Hi All, Is there a way I can import from CSV or something a list of extensions and names? I don't really want to be typing in 50 extensions... Thanks, Kristan

That looks excellent, thanks Fred, I will try it in the morning and let you know how I get on!

Hi all, Regarding the firmware upgrade options in the pnp for the snoms, what's the process for this? I have 10 360's on 6.5.8 I'd like to auto provision on a brand new PBX and thought great, I'll just let the PBX do it. Nope, when the phone subscribes to the sip mutlicast network it gets a user agent not supported back. Ok I thought, fair enough, going from 6->7 is probably a bit much to hope for, so upgraded the phone to 7.1.6 manually, reset it... and I can see it talks to the PBX via SSL, but not what happens. And the phone doesn't get upgraded any further, and it doesn't get auto-provisioned, despite me setting the MAC in the registration tab. What have I done wrong? Also, I wanted to put 7.1.24 on, so changed the pnp config setting for the 360 in the admin menu to the 7.1.24 file, and put the firmware file in the tftp folder. Is this the right place? Thanks, Kristan

Yeah, rebooting the PBX isn't great, but we need to do that occasionally to fix the hold music I'll put some logging on and see, it's not a huge issue at the moment as the customer who is using the polycom's isn't interested in BLF (thankfully!) but I'm sure there will be some in future.

Only thing is call forwarding doesn't integrate with the PBX.. But I'm sure they'll do that in the next version I'm having a bit of trouble working out the buttons, but I'll have play and make a separate post for that if necassary.

I'm assuming the PBX sends NOTIFY's or something to tell the phones what extensions to watch? I ask because suddenly after rebooting the PBX, the BLF on our bigger polycoms have started working again (without them pulling a new config etc. from the server). Is this correct? In which case, if we see BLF failing at a client, is there a way to push the NOTIFY's back out to the phone, as simply re-registering doesn't seem to do it. Thanks

We're still seeing this not working I'm afraid in even in 2.1 - single entry in the address book and it doesn't match the number on incoming calls at all, as per the rest of the thread above. More strangeness is that if I try to edit the number after adding the entry, it doesn't take the change - if I created it with 07624491xxx, then try deleting the area code 07624, save it, it works - but then if I try putting it back in again, it doesn't save, and just shows me the 491xxx. Any ideas? Sounds like the addressbook really isn't happy!

Sorry guys, this still appears to be broken - 3 PBX's, all different hardware, all 2.1, all work fine for a little while (aside from initial screeching after startup), then we just get horrible screechy noises after a few days or so. Any ideas? I notice the PBX supports streaming from RTP, can you recommend anything that will allow us to read MP3's, convert to G711 and stream via RTP to the PBX instead? Note that this only seems to happen for the wave input, the default moh is fine.