CEN
Operator support

Get connected. Stay connected.

For application review, community portals or integration help, email [email protected]. Support is handled by the CEN operator; no response-time guarantee is provided.

Requests and replies are tracked in your support inbox. You can also email [email protected]; reply in the same thread from the same address to continue a ticket. Email is checked every minute while the service is healthy. Attachments are not imported; paste redacted text instead. For community-specific service, use Support tickets inside your community portal.

What to include

Your community/area code, PBX and Asterisk versions, timestamp and timezone, the action attempted, HTTP status or CEN_STATUS, and redacted error text. For portal help, include your published portal URL. Never send account passwords, API keys, IAX secrets, access tokens or unredacted configuration files.

SymptomCheck next
Verification email missingCheck spam, confirm your email, then resend from Account verification.
Portal address taken or rejectedUse 3–40 lowercase letters, numbers or single hyphens, starting with a letter. Some names are reserved for CEN.
Portal returns 404Check that a portal address is saved, visibility is set to Published, and the community is not suspended or retired.
Custom domain TLS errorDNS alone is insufficient. Support must attach the hostname and install a matching certificate.
401 / 403 / 422 / 429Check key, origin status, exactly ten digits, or request rate respectively.
unmapped_destinationAdd the approved response host/port and a matching local IAX peer to the JSON configuration.
interceptThe destination is intentionally unavailable. Check maintenance, suspension or inbound permissions.
Route resolves but no audioTest the IAX trunk directly; check authentication, firewall/NAT, codecs and the remote dialplan.