Canary release removed features

[mtjas...@gmail.com]

I'm trying to understand the feature sets that were removed from the Canary release.

Top of the list is the removal of sipxbridge.  It seems this means that canary will require a 3rd party B2BUA (sangoma listed in the press release).  I can't imagine having to upgrade all of my customer and require them to purchase a new Sangoma.  I release sipxbridge has a bad rep, but it has actually been running very well for dozens of our customers over the years with almost no issues.  To require them to buy a replacement with little perceived value will be hard to swallow.

Call parking will also be a no go for our customer.  Nearly all of them use it and have come to rely on it.  Not sure I'll be able to get anyone to upgrade with this feature removed.  Here's hoping for a replacement.

With the goal to completely replace the SIP core with Kamailio, what will be the upgrade/migration path for current sipx users?

-M

[Matt white]

This post shows as deleted....I guess thats why I haven't seen any responses.

Reposted - We really need to understand how the canary release will fit with our customers either short term or long term.

[Joegen E. Baclor]

On 28/03/2016 10:27 PM, Matt white wrote:

This post shows as deleted....I guess thats why I haven't seen any responses.

Reposted - We really need to understand how the canary release will fit with our customers either short term or long term.

On Thursday, February 18, 2016 at 8:15:30 AM UTC-5, Matt white wrote:

I'm trying to understand the feature sets that were removed from the Canary release.

Top of the list is the removal of sipxbridge.  It seems this means that canary will require a 3rd party B2BUA (sangoma listed in the press release).

We are in the process of replacing SIP trunking feature using Freeswitch trunk dialplans.   For remote workers, it has been replaced by oss_core B2BUA. 

I can't imagine having to upgrade all of my customer and require them to purchase a new Sangoma.  I release sipxbridge has a bad rep, but it has actually been running very well for dozens of our customers over the years with almost no issues.  To require them to buy a replacement with little perceived value will be hard to swallow.

Call parking will also be a no go for our customer. 

Also being replaced by an FS based orbit

Nearly all of them use it and have come to rely on it.  Not sure I'll be able to get anyone to upgrade with this feature removed.  Here's hoping for a replacement.

With the goal to completely replace the SIP core with Kamailio, what will be the upgrade/migration path for current sipx users?

15.06 is the base tag for Canary.  You should be able to do backup and restore your <= 15.06 to canary.

-M

--
You received this message because you are subscribed to a topic in the Google Groups "SIPfoundry users and developers group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipfoundry-users-and-developers-group/hzJX7wnu7cQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipfoundry-users-and-dev...@googlegroups.com.
To post to this group, send email to sipfoundry-users-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipfoundry-users-and-developers-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipfoundry-users-and-developers-group/4c634083-a83e-4a9e-8eb2-a9f8543da264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.