Hello all,<div><br></div><div>After nearly a year of active development on building our own voice platform, we&#39;ve adopted some cool tricks to speed up the workflow and make testing less tedious.</div><div><br></div><div>
Over the next few months I&#39;ll be posting more articles on the tricks we have used and the lessons we have learnt.</div><div><br></div><div>Here is part 1 - a write up about a neat hack we used to virtualize phone testing;</div>
<div><a href="http://blog.simplicitymedialtd.co.uk/533/quick-and-easy-approach-for-multi-tenant-sip-testing">http://blog.simplicitymedialtd.co.uk/533/quick-and-easy-approach-for-multi-tenant-sip-testing</a></div><div><br>
</div><div>For those that don&#39;t have time to read, here is a screenshot;</div><div><a href="http://i.imgur.com/e9kUdxg.jpg">http://i.imgur.com/e9kUdxg.jpg</a></div><div><br></div><div>This trick, which we&#39;ve used in development for approx 6 months, has saved countless hours in development overheads, with one-click start/stop functionality and all the necessary modules right there in one place.</div>
<div><br></div><div>Of course, this should never be used as a full replacement as nothing beats a proper hardware test to catch those weird edge cases, but it does allow you to do the majority of your testing (95%) from a single screen rather than a desk full of phones. It also makes attaching wireshark a lot easier, without having to use span ports and the alike.</div>
<div><br></div><div>Hope this helps someone else!</div><div><br></div><div>Cal</div>