Elegance is nice, but converting from one system (multiple registrations for a single AoR) to the other (using Shared Call Appearance / Shared Line Appearance) is certainly achievable. The first step can be done in the weeks leading to a migration. You must get your devices under CPE Management, so that you've got your SIP phone configurations on a server, so you can manipulate them. If you don't already have this, there are ways to recover the configuration from devices. The most difficult is Polycom, but fortunately the Polycom's web interface HTML code can map nicely to the key provisioning details of the phone. Aastra, Linksys, and Cisco give more direct ways to retrieve the config from the phone. Once you've got the phone config on a CPEM server, it's straightforward to discover which phones are registering using the same SIP URI AoR. Then, if you're migrating to BroadWorks, you can create new devices, and new users, and configure Shared Call Appearance using OCI-P (BroadWorks's XML-over-TCP provisioning interface). Then you modify the phone configs appropriately, and ask them to re-download their configs. All of this can be automated. It's not a trivial change, but it's certainly achievable. And it wouldn't be the largest part of a migration from one softswitch platform to another. On Aug 7, 2009, at 7:20 PM, anorexicpoodle wrote:
Supporting forked registrations was a big consideration in our platform decision as well, and once you have designed product around something like that, there is no elegant way to backpedal.
On Fri, 2009-08-07 at 17:57 -0500, Brandon Buckner wrote:
Another issue I?ve seen with Broadworks is that it doesn?t allow multiple registrations to a single DID. Broadsoft confirmed that. We have a large amount of customers using that feature on our Sylantro platform instead of one number/one phone, whichever happened to register last. As we already support a Broadworks installation for a big customer of ours via Taqua, we?ve got experience managing and configuring the system. It was just when we started looking ourselves that we didn?t want to do business like that. A big selling point on the Metaswitch solution right now (and we?ve not signed anything) is consolidating all the different portals for users and admins and support along with troubleshooting. Especially with the Service Assurance Server, there?s much less things to look at and 3rd party tools to utilize for the same or better diagnostic information, meaning faster resolution and better customer support.
---- Brandon Buckner Switching Technician / VoIP Admin Iowa Network Services 515-830-0440 opt 1 brandonb at netins.com
______________________________________________________________________ From:voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia Sent: Friday, August 07, 2009 4:44 PM To: voiceops at voiceops.org Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
unfortunately some of the legacy Sylantro Synergy folks will never learn about the BroadWorks product if they get turned off by the sales folks though.
i completely agree that their product is solid, as a long term broadworks user myself it is just a constant decision around if the product is *so* good that the lack of account management isn't an issue.
I really like the feedback i've been hearing about metaswitch on this list so it seems like certainly a good solution to thoroughly investigate.
On Fri, Aug 7, 2009 at 1:28 PM, Hiers, David <David_Hiers at adp.com> wrote:
Charm school dropouts are certainly not underrepresented there; but their stuff works.
David
______________________________________________________________________ From: voiceops-bounces at voiceops.org [voiceops-bounces at voiceops.org] On Behalf Of Brandon Buckner [BrandonB at netins.com] Sent: Friday, August 07, 2009 9:12 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Sylantro users
We are still running Sylantro. We looked into Broadsoft as we manage a BW installation for a customer of ours, but pretty much everyone we talked to was an arrogant #^@& that acted like we owed them our business and really turned us off to them. We already have a Metaswitch for a PSTN gateway so we're looking heavily into their offerings.
----
Brandon Buckner
Switching Technician / VoIP Admin
IowaNetwork Services
______________________________________________________________________ From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia Sent: Friday, August 07, 2009 10:50 AM To: voiceops at voiceops.org Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
Hi
Guess since no one else responded i can rep the Synergy platform :)
We've got the Synergy platform. Haven't moved to another platform yet, still have a bunch of things to consider...
a) we have yet to receive an EOL/EOS notice from BroadSoft. We're told it will be ~2 years but waiting for something official.
b) BroadSoft is working on an ability to migrate the base from the Synergy platform to the BroadWorks platform so will need to see how that works out. I think if you have SIP Trunk customers or SIP Hosted customers you'll be OK but anyone that might be running MGCP the advance features just don't seem to be present on the BroadWorks platform.
c) There aren't a lot of other carrier grade platforms out there... Metaswitch, Sonus ASX, BroadSoft Broadworks are the big ones i can think of -- anyone have any other major vendors they would recommend? -- We are familiar with the BroadWorks platform but we're waiting for release 16 to come out with Sol10/x86 hardware support.
On top of all that, it is extremely costly to move customers from one platform to another so it will take several months to continue the evaluation and if a migration is required probably a couple years past that.
When you factor in ongoing M&S and licensing costs and the need to reduce network costs all the time... sometimes I wonder if building your own soft switch isn't the best route...
Are you still running the Synergy platform or have you already migrated to something new?
-katia
On Thu, Aug 6, 2009 at 1:32 AM, anorexicpoodle <anorexicpoodle at gmail.com> wrote:
I see this list has a lot of Broadsoft users, anyone left running Sylantro? If you were a Sylantro shop until the buyout etc what platform did you move to and what steered the decision?
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
______________________________________________________________________ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Mark R Lindsey lindsey at e-c-group.com http://e-c-group.com/~lindsey +12293160013