Jump to content

Pending snomONE Blue migrations "On-Hold"


VoiceA
 Share

Recommended Posts

Hi Guys,

 

Currently we have a “High Priority” inquiry regarding the snomOne Blue PBX System which requires the urgent assistance of Snom Technical.

We have a large number of Resellers prospecting the viability for a migration from their existing PBXNSIP environments over to snomOne Blue PBX Solutions.

Over the last few years we are aware there have been restructures and changes both within PBXNSIP and snomOne BLUE which may have affected the supported feature set of the snom One Blue PBX system.

The deciding factor is if a customer’s prior and existing investments into other non-SNOM VOIP handsets will be supported with the migration over to snom One Blue in 2012.

 

Can you provide us with an information sheet detailing the compatibility and feature set available for 3rd party NON-snom handsets on the SnomOne Blue PBX?

We would also like to have confirmation on the exact differences between PBXNSIP and snomONE Blue as of how it is currently available in the market today?

 

We have done some research regarding the support of 3rd Party handsets by snomOne BLUE and I want to confirm if the below statements are still relevant to the 2012 distribution of snomOne Blue?

 

ARE THE BELOW STATEMETNS STILL RELAVENT TO THE CURRENT RELEASE OF “SNOM ONE BLUE”?

 

-Blue will allow up to 40 non-snom devices to register. (snom ONE looks at the user-agent string in SIP and if it doesn't contain "snom" it will limit it to 5 in snom ONE Free, 10 in Yellow and 40 in Blue respectively)

 

-Note that I used the word "allow" instead of "supported". This was intentional as you will need to do the interop testing yourself. Which usually is not a big hurdle for basic functionality.

 

-Remember that these allowed non snom devices will have a limitation that they will not support a SIP REFER. In the real world this means that, for one, the Transfer button on software and hard phone will likely not work. This is not the end of the world though as with snom ONE you can put the call on hold and use the built in star code to transfer as a work around.

 

-Also note that snom ONE Blue only allow 5 domains (tenants) is not meant (licensing/eula) for reselling hosted service to other customers. I'm not sure how this is enforced and I suppose it can get grey? if a company owns a building and rents to tenants.

 

-snom ONE blue does not automatically auto-provision brands other than snom handsets.

 

Any assistance in this area would be greatly appreciated so we can provide the confidence to our resellers when recommending and rolling out pending installation projects of Snom One Blue solutions to their customer base.

 

Awaiting your reply.

Link to comment
Share on other sites

Hi Snom,

 

Is there an ETA on when a final solution might be available to the public?

Would you be able to provide us with an idea of what the draft solution might be for 3rd party support of VOIP non-Snom handsets?

What are the proposed differences between PBXNSIP and the newest iteration of the snomOne Blue PBX solution in 2012?

 

What are we meant to tell our customer base if they are contemplating the a migration from PBXNSIP with their existing non-Snom handsets over to snomONE Blue system?

 

This is not only going to cost project sales for us but also Snom as well.

We cannot continue to have this kind of uncertainty when we are trying to promote the superiorirty snomOne Blue bussiness PBX Solutions.

 

Please advise.

Link to comment
Share on other sites

Hi Snom,

 

Is there an ETA on when a final solution might be available to the public?

Would you be able to provide us with an idea of what the draft solution might be for 3rd party support of VOIP non-Snom handsets?

What are the proposed differences between PBXNSIP and the newest iteration of the snomOne Blue PBX solution in 2012?

 

What are we meant to tell our customer base if they are contemplating the a migration from PBXNSIP with their existing non-Snom handsets over to snomONE Blue system?

 

This is not only going to cost project sales for us but also Snom as well.

We cannot continue to have this kind of uncertainty when we are trying to promote the superiorirty snomOne Blue bussiness PBX Solutions.

 

Please advise.

 

There hasn't been any response to my questions yet.

Can Snom give us any indication on the future of the Snom One PBX Solutions?

 

Even if someone is not a member of the Snom Technical team...could they provide any guidance or assistance on the questions I have posed in the quotation above?

 

The Questions we are seeking answers for:

 

What are the proposed differences between PBXNSIP and the newest iteration of the snomOne Blue PBX solution in 2012?

 

What are we meant to tell our customer base if they are contemplating the a migration from PBXNSIP with their existing non-Snom handsets over to snomONE Blue system?

 

 

Thanks

Link to comment
Share on other sites

Well, there are not too many differences between the pbxnsip and snomONE versions, even though we had few differences at some point.

 

One main difference that still exists is the license, i.e., 3rd party phone plug and play support is now controlled by the license key. The transfers, registration restrictions on 3rd party phones have been already lifted.

Link to comment
Share on other sites

When you say registration restrictions on third party have been lifted, does this mean we can rigister 20 3rd party on yellow and unlimited on blue? The main snom website and wiki still has 10 on yellow and 40 on blue. I would like an answer from snom personel in regards to this, IMHO arguing with another member that doesn't work for snom doesn't answer anything :)

Link to comment
Share on other sites

This is the part where "snom is discussing internally how to proceed. There is a solution on the table, but not available yet" comes in handy ;)

 

Jokes apart, we want to support everything that the pbxnsip version did, but make it a license option.

 

I would be one happy customer if you did this. Some jobs I have to bid a lesser system in because it will match the phones the customer wants. I for one hate this because, like today, I had a service call to change two phones around on another brand pbx when I had a long trip out of my main service area already scheduled for a different job. If it were a snom system I could have easily walked them through the process over the phone or done it remotely because of the ease of use. This was proven by walking a customer through a setting up a service flag over the phone late this afternoon. 5 minutes later a happy customer.

 

Steve

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...