Well it's like this.
One of the most significant resource hungry requirements of voxalot is the registration of VSP accounts for users; if users are able to lessen the load on voxalot by not registering accounts just because they can, then it has got to help voxalot cope better with resource requirements.
This could be a problem if:
- your provider requires the account to be registered for you to make calls or
- your provider does not offer any form of SIP URI forwarding.
Outgoing calls are setup with the credentials of your provider (as supplied by you) at the time of making the
authenticated call; this is far more efficient that doing constant registrations and the renewals required to remain registered.
Another potential issue, and this has caused problems with at least one provider, is having too many registrations come from the same IP address. In such cases, the VSP may block voxalot either via flood control mechanisms which makes it's use with voxalot less reliable or they may choose to ban voxalot's IPs completely thus making the VSP fail to work with voxalot at all.