metwest

Would it be possible to get the option in each park orbit to turn off the "your call has been parked on orbit number" announcement? When using park orbit buttons there is no need for the announcement. On 7 series handsets it is annoying but you can just ignore it and continue mid announcement your next task, which is usually hit an intercom button or page key to alert another party of the parked call on that key ( I usually name the park orbits Park 1, Park 2, Park 3 so the announced orbit number never matches anyway) But when using an 870 it becomes a pain. I provision my 870's up so virtual keys are on idle and stay up (even when handset is lifted). The only time they go off is if your in a call or dialing. Problem is instead of a going straight back to virtual keys after a park button is pressed you have to either wait for the announcement finishes or you have to hit the cancel key before the virtual keys re appear. I know its not a huge problem but would make using 870's a little less cumbersome , and also make smaller installs a little user friendly when there is no need for the orbit to be announced.

Thanks, sent a pm for a fix build.

Spoke to soon Unsupported Media Type Errors cutting off customers coming off park and it is coming up every so often on outbound calls

Full day in the office system and 0 issues If all goes well this is going out into the real world for a customer waiting for park recall

I am currently waiting for this dnd issue and a CID issue that shows address book entries instead of e correct CID to be fixed for a large amount of 870s. Also using shared line buttons on 870s is useless as monitoring light hangs in some cases. I played around with the new beta but it seems to bring just as many bugs as it does new features. (Park key monitor light not working being a big one) As much as I love some of the new features Snom are throwing in I really think there should have been a better stable release after 8.7.3.19 before adding so much new stuff. At present my only option at the moment might be downgrading my 870s to 8.4.35 and hoping no other features break in the downgrade...

Try 5.08. And see if you have the same issue

What version of Snom One are you using? Try 5.08. (5.09 has some issues with pnp) Also maybe first try a simple softphone to start with and just enter the username, password and server address (ip address of system) and see if you have success. If not post log errors.

Just To add to this topic. The address book does carry over in a backup being loaded but will only appear after a restart of the system.

It's all good I will wait until 5.10. A pubic Beta before final would be a good way to get around this issue =)

Any chance of a re-release like when 5.08 was first released?

Hi Guys Sorry I stopped posting on this because I assumed you guys are working on a fix. 5.08 is stable, no problems provisioning handsets. 5.09 tried 3 different systems, 2 new ones on networks with nothing but the Snom products and our office system. Also on the already provisioned handsets in our office with 5.09 when we reboot handsets we get cannot find provisioning server in info. As stated before I enter the ip address of the Snom One System just as we always have in the handsets update settings url. And open mac based provisioning on the snom one of the desired account. Exact same way that works fine in 5.08 but 5.09 just flat out refuses to work. We are using 870 handsets and we use Debian 64 bit for my systems. Have been sticking with 5.08 on customers systems until we get a fix. Hopefully soon so I can implement the new park callback feature our customer wanted that you guys kindly added :-) Thanks.

Very nice. A great addition in the future would be click on another extension to call it. Also down the track maybe 30 button keys that can be programmed in the extensions button profile. Example say on an 870 button profile the user makes it 45 buttons the 1st 15 will appear on the handset and the 2nd 30 are just for the WAC.

I posted here.... I meant to post in 5.09.... sorry

No problem Timers are tricky since 5.0. That's what we use for Engin but Internode must be different, you may need to fine tune them a little more if you get random 408 errors. I'm guessing it was the :5060 that fixed the 401 registration problem.

Thanks for the reply. That is exactly how I do it. Server setting is IP address of the Snom One and I open the accounts for mac provisioning for 10 minutes... no luck. Exactly the same way I did the 60+ 870s on 5.08 with the multisite job Im on now ... 5.09 just does not like it

Try the following: # Trunk 2 in domain pbx.company.com Name: Internode Type: register To: sip RegPass: Direction: Disabled: false Global: false Display: MCBizman RegAccount: RegRegistrar: sip.internode.on.net:5060 RegKeep: RegUser: Icid: Require: OutboundProxy: sip.internode.on.net:5060 Ani: DialExtension: 40 Trusted: false AcceptRedirect: false RfcRtp: false Analog: false RtpBegin: RtpEnd: Prack: false SendEmail: UseUuid: false Ring180: false Failover: never HeaderRequestUri: {request-uri} HeaderFrom: {trunk} HeaderTo: {request-uri} HeaderPai: HeaderPpi: HeaderRpi: HeaderPrivacy: HeaderRpiCharging: BlockCidPrefix: Glob: RequestTimeout: Codecs: CodecLock: true DtmfMode: Expires: 120 Fraction: 230 Minimum: 30 FromUser: Tel: true TranscodeDtmf: false AssociatedAddresses: InterOffice: false DialPlan: UseEpid: false CidUpdate: Ignore18xSDP: false UserHdr: Diversion: CoBusy: 500 Line Unavailable Colines: DialogPermission:

Need a bit more info mate. Edit your trunk, at the top switch to text based editing and copy what you have (obviously remove your number and username/password) and paste it here so I can see what you have setup.

Confirmed fixed in 5.09. Thank you :-) Add it to 5.09 bugfixes Note (few little bugs, nothing major) 1) If an entry has nothing in the number field only in the cell, that entry will not import. so if you are creating a csv with entries with just cell numbers you will need to put a number in the number field then delete once imported. 2) If you do delete a number from an entry in the domain address book, you can no longer go back to edit that entry.

Try checking the codecs in the Snom gateway match the A200 . Also try checking the lock codec during conversation is on in the gateway settings.

This was a bug in 5.08. I am running 5.09 debian64 and I no longer have this bug.

The only file changed is the snom3xx_phone.xml file with a couple of simple variations such as US date format off, missed calls off and an altered springboard. I change this on all my installs with 870 handsets and have never had any issues until 5.09.

5.09 provisioning broken .... spent 2 1/2 hours trying to provision 4 new handsets up to a new system. Went back to 5.08 and provisioned fine. I am using manual provisioning as the system and handsets I am setting up are on 2 different sites over a VPN (In the 870 handsets I enter the direct IP address of the Snom to get its provisioning file ) I have not tried any of the new features as of yet but I do have it up and running on our office system. (handsets are already provisioned so It was not a hassle)

Hi guys Did anyone have any ideas what Im doing wrong with this?

Thanks for the replies guys. I need to sell it if a customer asks for it, so not buying it is not really an option ;-) I can't really give an opinion if its worth the money as Im yet to use it. It just seems strange telling a customer " Yes you can record calls, but if you want them to automatically record that will be $995" To be honest I never knew it was missing until asked by a customer today. Might put a trial on the office system to see how it all works.

No! Thanks for that. I was not aware it was an off the menu product! Anyone tried it yet? Is it a lot better than 4.5? For 995.00 I would hope so.