Further to yesterday’s announcement regarding Advanced Inbound Routing, you can now configure the same set of features as a default configuration for your account. In this way, any numbers on your account, including those added in the future or ported in, will inherit the default configuration where no specific configuration is present. This is also especially handy for Virtual Interconnect customers who may have many hundreds of thousands of numbers; the default can be set and only the exceptions (if any) specifically configured.
Whilst discussing inbound routing, we’d like to remind all customers of a few low level differences between Simwood’s routing and our competitors. They have been there so long, we have not mentioned them in many years:
- if a SIP end-point is unavailable we will fail-over to the next route in a few seconds. Certain competitors rely on a SIP error code to fail over which is pretty useless when your equipment is down. Try it!
- if a SIP end-point is available but we do not obtain some kind of call state by a few seconds later, we’ll similarly fail over. This is important where customers use a proxy that may return, for example, a “100 Trying” message but due to configuration or other issue return nothing else.
- We support SRV, and always have done enabling your own failover or load-balancing to be configured within each SIP leg we forward to.
Of course, we’re still about the only wholesale provider offering TLS/SRTP, PSTN forwarding with cost/fraud controls, control over what codecs we offer you per number (useful for Asterisk users wanting G729), Freephone origin filtering, HD voice, channel/rate limits including per number and much more. All this controlled through our great API – no telnet required, and 100% of call routing handled in RAM.