FIG. 4 is a diagram illustrating an exemplary telephone number verification process. When a trixNet user (e.g., subscriber to trixNet services) opts to enroll an existing carrier-issued telephone number, the user may enter the telephone number in a web interface provide by the management interface module 202. In order to avoid abuse, the verification module 208 will initiate the verification process. Initially, a membership request is sent from the call management system 112 to the data center system 104. The membership request may comprise, at least, a telephone number which the user wants to register for trixNet service.

Upon receipt of the membership request, the verification module 208 initiates a PSTN call to the entered carrier-issued telephone number being registered. The PSTN call may request a user at the telephone number to provide a response to the verification module 208. In one embodiment, the response may be a DTMF entry of a validation code given via verbal instructions. Only if the code is entered correctly is the number entered into the relational database and registered for trixNet service. Should the number be re-assigned via the PSTN to another user, the number may be re-validated at any time by request of the owner of the telephone number in accordance with one embodiment.

In some embodiments, trixNet service may be used on an “opt-in” (e.g., users must register phone numbers) or opt-out basis. As such, trixNet may be used in a partial manner on a PBX, whereby some phone numbers (e.g., DIDs) participate in trixNet services and some phone numbers do not.