Set the default number (E.164) and Telnyx signature verification
Set the default outbound number in E.164 format and, optionally, add the Ed25519 public key so Omnifox verifies the signature of Telnyx webhooks.
Once your Telnyx Programmable Voice channel is connected, it's worth tuning two settings: the default number calls go out from and, optionally, signature verification for webhooks. This guide is intermediate level.
The E.164 format
Telnyx (and telephony in general) uses the E.164 format: a + sign, the country code and the number, with no spaces or dashes. Examples:
- United States:
+15125551234 - Ecuador:
+5939XXXXXXXX - Spain:
+34XXXXXXXXX
If the number isn't in E.164, outbound calls may fail or go out with the wrong caller ID.
Step 1: Set the default number
- In Omnifox go to Channels and open your Telnyx Programmable Voice channel (or connect it from Connect channel if it doesn't exist yet).
- In the Default From Number (E.164) field, enter your Telnyx number in E.164 format, e.g.
+15125551234. - Save. From then on, outbound calls without an explicit number will use this one as the sender.
This number must be one you actually own in Telnyx and that is tied to the channel's connection.
Step 2 (optional): Ed25519 signature verification
Telnyx signs every webhook with Ed25519 and sends the signature in the telnyx-signature-ed25519 header. If you give Omnifox the public key, we'll verify that signature and reject any webhook that didn't truly come from Telnyx. It's an extra security layer, recommended for production.
- In Telnyx, go to your connection: Connection -> Webhook -> Signing Key and copy the public key (base64 format).
- In Omnifox, on the Telnyx channel, paste that value into the Public Key (Ed25519, base64) field.
- Save.
If you leave this field empty, Omnifox will accept webhooks without verifying the signature (it still works, just without that protection).
How to verify
- Default number: place a test outbound call and confirm the caller ID the recipient sees is your E.164 number.
- Signatures: with the public key set, place a real inbound call. If it comes through normally, the signature is being validated. If calls suddenly stop arriving after pasting the key, the public key doesn't match.
If it doesn't work
- Outbound calls show a wrong number or fail: check the number is in E.164 (with
+and country code) and belongs to your Telnyx connection. - Calls stopped arriving after setting the signature: you copied the wrong key or one from another connection. Go back to Telnyx, copy the correct public key from Connection -> Webhook -> Signing Key, or clear the field to accept without verification while you sort it out.
Tips
- Start without a public key to confirm calls come in, then add signature verification; that isolates any problem.
- Always store the default number in E.164 across the platform to avoid inconsistencies.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.