Troubleshooting DIDWW MCP#
Use the following guidance to resolve common DIDWW MCP connection, authorization, account, upload, export, and request issues.
Accounts, permissions, and limits#
The wrong DIDWW account is active
Ask the MCP client:
Which DIDWW account is currently active?
If you can access multiple accounts, ask it to list them and switch to the required account. Confirm the active account before retrying the request.
An action is not permitted
The MCP client uses the roles and permissions of the DIDWW user who authorized the connection. Check:
the active DIDWW account
your role for that account
whether the record belongs to the active account
whether the required service is enabled
Connecting an MCP client does not grant additional roles or permissions.
A service or account limit was reached
The requested action cannot be completed because a limit applies to the active account or service. Review the response to identify the affected limit and any available next steps.
Contact DIDWW Customer Support if the limit needs to be reviewed or changed.
The account balance is insufficient
DIDWW does not complete a purchase when the active account has insufficient funds.
Add funds using a payment method in the DIDWW User Panel.
Return to the MCP client.
Review the updated balance.
Request a new purchase preview.
Too many requests were sent
DIDWW returns a waiting period when the connected MCP client exceeds its
request rate. Wait for the number of seconds identified by the MCP client or
the Retry-After value before sending another request.
Uploads and exports#
A secure upload link expired
A secure upload link cannot be used after it expires or after an upload is completed. Ask the MCP client to create a new secure upload link.
Do not send documents in the MCP client conversation.
An export is still processing
Ask the MCP client to check the export status. Do not create another export unless the original request failed.
An export link does not open the file
An export offers two links. The direct link opens the file without a DIDWW User Panel sign-in. The User Panel link requires a signed-in DIDWW user that can access the account associated with the export.
If the direct link does not open, ask the MCP client for the link again. Chat clients sometimes append punctuation to a link and break it.
Completed export files remain available for one month, and both links stop working when the file is deleted. Create a new export when the previous file is no longer available.
Requests and actions#
A confirmed action has an unclear result
Do not immediately repeat a purchase, termination, restoration, invitation, or deletion.
Ask the MCP client to check the relevant phone numbers, capacity, orders, trunks, groups, identities, addresses, or invitations. Start another request only when the account records show that the original action did not complete.
A newly released action is missing
An MCP client can cache the available DIDWW actions for up to one hour. Reconnect the client when a newly released action is missing or a previously valid setting is no longer recognized.
An action is not available through MCP
Use the DIDWW User Panel when an action is not supported through MCP. Current examples include:
number porting
A2P SMS campaigns
CNAM configuration
outbound trunks (Voice OUT)
shopping-cart actions
phone.systems™ subscription management
company details
Reconnect DIDWW MCP#
Open the connection or connector settings in the MCP client.
Select or add DIDWW.
Complete the DIDWW browser authorization process.
Ask the MCP client to identify the active DIDWW account.
Contact support#
If the problem continues, contact DIDWW Customer Support by email. To speak with a 24/7 live support agent, open the DIDWW contact page and use the live-chat widget.
Include the affected DIDWW account, MCP client name, approximate time of the problem, and the error message.
Note
Do not include passwords, API keys, two-factor authentication codes, or documents.