Connectivity and authorisation answer different questions
A dialler may connect successfully while the business has not completed the permissions relevant to its configuration. Conversely, legitimate internet calling should not be labelled cybercrime solely because it uses software rather than a conventional telephone handset. The review must distinguish technical function from regulatory authority and actual conduct. [1] [3]
PSEB’s published facilitation framework links call centre voice operations with registration and the relevant IP-whitelisting process involving PTA. Begin there, then examine whether the configuration includes other telecommunications activities requiring separate consideration.
Do not describe a vendor’s ability to make calls as an official approval. The person selling a service may be able to explain its setup, but that explanation must be checked against the competent authority’s requirements.
Build a plain-language map of the voice operation
Management should be able to identify the operating entity, approved premises, internet provider, relevant IP addresses, dialler or platform provider, number provider and the party controlling routing. This is an internal governance recommendation: it makes the real arrangement understandable to counsel and the technical team.
The map should distinguish inbound support, outbound sales and any handling of traffic for other entities. Different activities may raise different regulatory questions. Do not assume that approval for a call centre also authorises operating as a public telecommunications service or undertaking unrelated traffic-routing activity. [1]
Record who is responsible for changes. A network administrator should not silently alter a production arrangement whose legal approval depends on details recorded with an authority.
What IP whitelisting does, and what it does not do
PSEB’s guidance describes a route for the relevant registered or provisionally approved call centre to have its IP information processed for legal voice operations. The status, address and application details must correspond to the actual business. [1]
Whitelisting is not a certificate that every lead is lawfully sourced, every sales claim is truthful or every foreign campaign meets destination-market law. It also should not be interpreted as permission for unrelated or unauthorised telecommunications activity.
Keep the approval and technical record together. When an address or IP changes, review the applicable update process before assuming the old entry covers the new connection. Where the authority’s instructions are unclear, seek clarification instead of trying to bypass a restriction.
SIP, hosted diallers and virtual numbers require due diligence
SIP describes a communications protocol; a hosted dialler is a service configuration. Neither label tells you whether the parties, routes and use are authorised. Ask the supplier to identify the contracting entity, service scope, responsibility for numbering and the basis on which it provides the relevant service.
A foreign virtual number may serve a genuine customer-support purpose. Its presentation becomes a different issue where the caller falsely claims to be an unrelated institution or deliberately creates a counterfeit source. PECA’s spoofing provision has specific elements and should be applied to the actual conduct rather than to every overseas number. [3]
Keep supplier agreements and authorised-use restrictions. Vendor assurances do not excuse a business from examining an obviously deceptive instruction or a configuration it cannot explain.
Operational changes should trigger legal review
Common change events include moving premises, adding a branch, changing the internet service, introducing remote agents, replacing the dialler or permitting another company to use the same infrastructure. None should be treated as a purely technical decision where it affects recorded approvals. [1]
Use a change ticket that records the old arrangement, proposed change, operational reason, regulatory check, client-security implications and approval to proceed. The level of detail should match the risk rather than creating paperwork for its own sake.
For remote working, examine access security and the authority’s treatment of the actual voice configuration. Do not publish a universal statement that all home-based calling is either authorised or prohibited without checking the relevant circumstances.
A lawful response to blocked or disrupted voice service
If voice traffic stops working, first establish whether the cause is technical, contractual or regulatory. Review the service provider’s explanation, the current approval status and recent configuration changes. Preserve relevant logs and correspondence.
Do not respond by concealing the business, misrepresenting traffic or implementing a route designed to evade an applicable restriction. Request correction, clarification or restoration through the appropriate provider and authority process. Where a formal adverse decision exists, obtain advice on the available remedy. [1]
A hypothetical office move illustrates the point: if a new connection is not reflected in the whitelisting record, the solution is to reconcile the approval and technical facts. A temporary workaround that creates a second undisclosed configuration can make the original problem harder to resolve.
Give management evidence it can actually understand
Maintain a concise approved-configuration sheet with the supporting contracts, authority records and responsible contacts. Keep technical passwords and secrets in a secure access system, not in a public compliance folder or marketing document.
Periodically compare the documented arrangement with the production environment. A signed policy is weak protection where the actual system has changed several times without review. Ask the administrator to demonstrate the configuration safely and preserve any required audit record without exposing customer information unnecessarily.
Lawful voice operation is a joint legal and technical responsibility. Registration advice cannot replace competent network administration, and technical competence cannot replace the required legal permissions.
Legal assistance for this issue
Legal Bridge LLP can review the Pakistan-law and contractual side of a proposed voice arrangement. A competent telecommunications or network specialist should separately validate technical implementation and provider claims.
