re: Juniper Kills Its Session Controllers My answer to the integrated sbc model is based on completly different perspective.
I agree that the cration of the SBC market is just because softswitch and other systems vendors were too lazy to implement few features in their products. So integrating SBC functionality to another system sounds like a good idea.
However integrating it into the edge router is not such a good idea. This has nothing to do with technical reasons, it's rather a political reason: it's a totally different set of people operating the voice services than the one operating the data services (routers). Even in my former company which was basically an ISP there were distinct teams for those functions, so imagine how it would look in an incumbent provider. No way the bell heads will let the net heads to get to involved with their services, and god forbid that a net head will allow a bell head cli access to it's precious router.
Integrating SBC into a softswitch sounds much better.
re: Juniper Kills Its Session Controllers"it may seem like social service in retrospect but maybe the M&A team at Juniper just wasn't so good at picking. "
They have as good a runrate as any and better than most. That doesn't mean I am a fan of buying technology all the time. Seems to me it is usually more expensive than organic growth, and M&A activity very rarely increases overall shareholder value.
re: Juniper Kills Its Session ControllersLike computers don't know how to control sessions by theselves and we actually *need* this stuff in a network. Companies like Microsoft, HP, Sony, and Dell will lay over and die for Juniper on an already crowded bus. Sounds like somebody is spending too much time with the branding ingredients.
Make everything as simple as possible, but not simpler. - Albert Einstein
I think you meant number one for the session control mechanism and a choice few others for the companies who make the specialized products and actually persuade folks to buy them.
My answer to the integrated sbc model is based on completly different perspective.
I agree that the cration of the SBC market is just because softswitch and other systems vendors were too lazy to implement few features in their products.
So integrating SBC functionality to another system sounds like a good idea.
However integrating it into the edge router is not such a good idea. This has nothing to do with technical reasons, it's rather a political reason:
it's a totally different set of people operating the voice services than the one operating the data services (routers).
Even in my former company which was basically an ISP there were distinct teams for those functions, so imagine how it would look in an incumbent provider.
No way the bell heads will let the net heads to get to involved with their services, and god forbid that a net head will allow a bell head cli access to it's precious router.
Integrating SBC into a softswitch sounds much better.
Just my two cents.