nitzan
Premium,VIP
join:2008-02-27
 ·ViaTalk
 ·Comcast
| vendor rating system
To be perfectly fair, the vendor rating system is based on DIDx's vendor rating. The entire DID selection tool is just a front-end to DIDx's API. 
...which is actually pretty neat, I've been considering writing a similar selection tool for FN. Might take a while though since we're busy with other stuff at the moment.
Funny though, we're using the same billing software, same DID vendor, and share at least one termination vendor.
--
Nitzan Kon, CEO
Future Nine Corporation |
|
gbh2o
join:2000-12-18
Greenville, NC
·Future Nine Corpor..
·callwithus
·MyPhoneCompany
·VBUZZER
·Voxee
 ·Embarq
·VOIPo
·STANAPHONE
·Axvoice
·Packet8
| You might also want to think about the flexibility other vendors [see voip.ms also] offer on user-selectable risk/quality or whatever on the outgoing/termination provider circuits. That is also reflected in a selectable rate structure with the quality-guaranteed termination circuits offered at a premium.
Some of us old Fogies with too much exposure to either artillery rounds or loud music don't really appreciate having more quality than we can hear; it justifies our miserly choice of cheap routes.  The young wife, however, may want to hear the full spectrum without the clicks, hums and other distractions that we can't even hear anymore. Businesses also seem to prefer 'clean' circuits!
Good luck, it will take you a while to implement all the goodies without the bugs. Take the time to fix it and test it properly before launch and you will enjoy high marks like these providers. |
|
nitzan
Premium,VIP
join:2008-02-27
·ViaTalk
·Comcast
| reply to nitzan
Very true. 
We try to provide the best quality routes we can to all customers though. Nowhere to go higher for most of them.
Although companies like Betamax (voicetrading) give you different rates for grey, standard, and premium termination.. I'm not sure there actually is much of a difference between standard and premium. grey I wouldn't use normally.
I guess this is where user input is valuable.. we obviously can't test all routes by ourselves, and some providers while promising great quality to a certain destination, sometime don't deliver on this promise, and there's no way for us to know unless users complain. I'm still thinking of how to do this, but probably a standard form with number called, date and time, and what happened.. so we can find the bad routes and replace them.
This by itself will probably be a ton of work.. |
|
