i have a softswitch capable of routing traffic as I have multiple styles of PBXs and ATAs in the field that I'm supporting and not all traffic will be going to the thirdlane server.
my softswitch is also capable of giving me reports for billing, and keeping track of usage for each client.
what are your experiences with the best way to setup trunks, 1 per tenant, 1 global inbound outbound trunk, and handle traffic to the thirdlane server by dialing rules in the softswitch.
looking for feedback
thanks
What kind of softswitch are you using
Hello.
We are in search of a good softswitch, If I may ask what are you both using ?
Thanks!
Cameron
current softswitch
I'm currently using VoipSwitch, and have been pretty happy with the options and ease of configuration. I'm only running about 65,000 minutes a month currently so I might not be the best opinion.
I've also been pretty happy with the support response on fixing issues. http://www.voipswitch.com
just my 2 cents, as it appears from other forum comments Erik has a lot more experience at this than I.
Sean
I am using a vanilla
I am using a vanilla installation of asterisk for now, until I get enough volume to justify a Sonus switch.
depends on your switch. its best to do 1 trunk per hardware server and not per tenant because multiple trunks to the exact same ip will cause identity issues like you wouldnt believe. If your switch can track different customers for billing by something other than ip address then you definitely want a single trunk. I use a method of adding an account code to the front end of the dialing string to identify the customer, then my switch dials everything after the fixed length account code.