Vance

It is not a good partnership when you withdraw all support for your product in an attempt to force your clients to pay you for upgrades.

I think it is much worse than the issue of charging more and/or additional for the same product bought under a clear agreement and understanding. For those of us choosing to maintain version 4, there would, at this time anyway, seem to be zero support. I have a number of issues some of which are extremely serious and damaging to my business that are being ignored. In fact one of the statements from a so called 'support engineer' was "This looks like a defect on this version, please backup your system and roll to 4.5.1 or version 5, unfortunately I cannot test 4.6 since that was an overlap version to 4.5. , our development team are only working on V5 today." So, the question is, even if we bought into the very expensive upgrade, why would we be inclined to believe that the next major move on this prouduct would not leave us as high and dry as this one. Version 6 could as easily come with the same kind of price hike, and be forced due to no version 5 support. A class action springs to mind folks?

Have the same issue myself. I wonder at the reality of the 'check your license' facility. Either these guys know what their licenses are and where they are or they have serious issues regarding what licenses they have out there and what licenses they dont. An odd facility - check your license!

Let us all know how you got on with that?

Could I invite you to read your original post in this thread!!!!!!!!!! The topic is only about the move from version 4 to version 5 and the change in model. Are you suggesting that you start a thread with a subject and now want to stop everyone from discussing it?

Well, yes you did. We purchased Snom One products at a promulgated one-off price and subsequently, certainly in my case, a lot of Snom phones. This was the stated model. The PBX was at a price that encouraged the purchase of the associated phones. In fact, third-party phones were restricted. Now, the model has completely changed. The cost of the PBX is vastly higher so anyone who was working under the original model can no longer justify the upfront costs against their original business plan. What might be considered 'class' is a company that spent some time working communication with their loyal clients before rushing into a completely different model illustrated by the constant changes in pricing since you first went into this. If you were that sorry you would fix it.

I think it is worse than 'confusing'. For those of us who commited to this company and built our businesses based on the model that was promulgated, the change this time is fatal. Worse, the statement that 'you dont have to change to 5.x we are still supporting 4.x' has proved to be somewhat untrue. Every request for a bug fix is replied with 'move to 5'. I wonder if in fact Vodia even have the code base running for the previous version based on some of the support I am getting.

Hi A problem with this release is that the CDR report only shows 100 calls regardless of how many are actually made. This is the report sent via the command "send daily CDR report to' in the extension used as 'assume thta caller comes from'. Vance

Hi That is a fix! I have put through a few hundred calls and they all terminated correctly. Best regards Vance

Hi Could really do with a solution to this even if it is only a test version. Anyone getting this? Vance

Any joy lads. Got lots of calls I can testthis with

Any chance of a 32bit version?

Sorry! My test system is 32bit.

Hi Need 64bit Windows? Best regards Vance

That is not the issue. This issue we are talking about here is where a call comes in on a trunk and uses the account (Assume that the call comes from user) to terminate the call which in turns sends the call out of another trunk. If the B-End hangs up the A-End does not receive the BYE so it stays holding that end up. Big problem and means, for me anyway, that at least one client cannot use anything greater than 4.2. Log trace of at least one call is attached. Document.rtf

I have a trace. The information there is live so I cant just post it on a public site. How do I get this to you?

I have the same problem. Rather than the 'crude' method, how do we get the system back to showing the form correctly? I did not upgrade from a particularly old version; most recent to latest all the way in fact.

Sorry! Too many calls going through to stop the system - waited until after midnight but I need my beauty sleep so abandoned. Sunday is quiet so I can go again that night. Again, this is easily recreated so maybe the Snom lads could simply set this scenario up in the lab no?

I can have a go at this tonight. Not easy as I would need to update the platform to 4.5, wait for a couple of calls and then downgrade it again. The call detail will have private infomation, how do I get the PCAP to you privately? BTW, you could easily test this yourself. Simply set it up as semistatic has detailed and you will see the leg hanging there on the 'calls' display if you hang up the B-End.

Hi I have exactly the same problem. It is OK in version 4.2.x but the latest versions do not pass the BYE on if the B-Party hangs up. Eventually, after a long time, the leg does 'go away' but not before the call is sitting there for all this time racking up the billing. I have tried to get this through to support but it is a difficult problem to describe and get the logging straight on. At one point the lads indicated there was a known problem so I was expecting something to change in a later version but I can confirm the same issue exists on the latest release. I got a PCAp and as you rightly say, teh BYE is simply not sent through.

Hello there On the recordings page under 'call history' (a fantastic addition by the way) I can only see one page of recordings. Is there a way we could have multiple pages so we can go back further in history? Regards