Forum Discussion
Direct Routing
Hi, I often see posts on here asking for assistance configuring or troubleshooting Direct Routing. This makes me wonder what benefits organisations are seeing and why they choose to use their own S...
It can entirely depend on the organizations involved. Several I've worked with have a lot of analog equipment that they still need to support on premises. Taking these to third party SBC providers isn't always easy compared to hosting your own SBC.
Third party integrations, such as call center, that might have dedicated hardware that the hosting provider won't/cannot connect to.
Number portability, and retaining the control over their number pools.
One of the bigger ones I've seen has been cost. The cost to host the infrastructure and SIP trunks, has been less than having somebody else host it. That doesn't include things like the cost built into the number of users that the provider may charger by as well.
Thanks for your feedback, I really appreciate it. It seems there is quite a misconception around carrier hosted direct routing. We are a sip trunk provider who offers carrier hosted model and I have seen other vendors are charging per user but we only charge per sip channel/concurrent call which is much more cost effective. That is good to know as maybe sometimes customers aren't knocking on our door as they assume it will be cost prohibitive before they make the enquiry.
Not sure what the concern is over number portability? As the numbers will be hosted by the sip trunk provider either way?
We've done quite a few deployments, particularly universities in the UK where they needed to retain legacy analogue equipment or sip endpoints. All done successfully.
We haven't done many deployments which required third party integrations i.e. call centre (if customer requires call centre solution we have partnered with Mida and deploy their solution) but I'm not sure why this would be solved by an organisation using their own on prem or vSBC? If it can be done using their own SBC it can also be done carrier hosted.
Not sure what the concern is over number portability? As the numbers will be hosted by the sip trunk provider either way?
We've done quite a few deployments, particularly universities in the UK where they needed to retain legacy analogue equipment or sip endpoints. All done successfully.
We haven't done many deployments which required third party integrations i.e. call centre (if customer requires call centre solution we have partnered with Mida and deploy their solution) but I'm not sure why this would be solved by an organisation using their own on prem or vSBC? If it can be done using their own SBC it can also be done carrier hosted.