Skip to content
  • There are no suggestions because the search field is empty.

Mastodon 

The Mastodon Call Routing Plugin is a Taalk Certified integration designed to facilitate real-time voice call routing through Mastodon’s infrastructure, using a lightweight and secure proxy endpoint. This plugin enables AI Agents within the Taalk ecosystem to dynamically route voice engagements—both inbound and outbound—based on customer, campaign, or agent-specific criteria.

This integration is ideal for businesses using Mastodon for telecom orchestration, carrier-level control, or lead delivery compliance workflows.

Use Case

With AI Agents handling millions of customer conversations monthly, Taalk supports complex engagement orchestration across voice, SMS, and email channels. For customers leveraging Mastodon for telecom routing, this plugin enables:

•Real-time call forwarding based on call direction (inbound vs. outbound)

•Precise lead-to-call correlation using unique identifiers

•Custom routing via agency_name or carrier flags

•Secure and auditable delivery via Taalk’s proxy infrastructure

 

Endpoint

POST https://post.xxxx.net/xmlPosts/mastodon-proxy.php

Required Query Parameters

Parameter

Type

Description

api_key

string

The API key used to authenticate the request (provided by Mastodon or intermediary service)

leadtype

string

Type or classification of the lead (e.g., “auto”, “health”, “home”)

source_token

string

Token identifying the lead source, assigned by the campaign or partner

leadid

string

Unique lead ID from the Taalk system (<Taalk_lead_id>)

lendor_id

int

ID used to tag and attribute the carrier/lender involved (typically 1 unless otherwise instructed)

carrier

string

Agency name or carrier reference (e.g., Other, AgencyABC)

call_type

string

Specifies the direction of the call: "inbound" or "outbound"

 

 

 

Dynamic Value Generation

 

Within Taalk’s runtime, these fields are often dynamically populated based on the AI Agent’s context or engagement metadata:

call_type = callDirection === "OUT" ? "outbound" : "inbound";

This ensures the right routing context is applied for AI-driven conversations that either initiate calls (e.g., proactive outreach) or receive inbound callbacks.

 

 

Example Request

POST https://post.xxxxx.net/xmlPosts/mastodon-proxy.php?api_key=ABC123KEY&leadtype=auto&source_token=tok123abc&leadid=&_lendor_id=1&carrier=Other&call_type=outbound

 

 

 

Response Format

 

Responses from this proxy typically return XML or status codes indicating:

•Success (200 OK with routing confirmation)

•Auth failure (401 Unauthorized)

•Invalid payload or field (400 Bad Request)

•System error (500 Internal Server Error)

If needed, responses can be transformed internally within Taalk for JSON consumption.

 

 

Integration Best Practices

•API Key Security: Store and rotate api_key values securely; avoid hardcoding them into public environments.

•Field Mapping: Ensure consistent lead metadata mappings between Taalk and Mastodon to avoid mismatches.

•Monitoring: Track proxy responses and use Taalk dashboards or logs to monitor failure rates or call drops.

•Fallback Logic: Implement retry or escalation paths if Mastodon proxy responses fail or exceed latency thresholds.

 

 

Troubleshooting

Issue

Possible Cause

Resolution

401 Unauthorized

Incorrect or expired api_key

Check key validity with your Mastodon or intermediary admin

400 Bad Request

Missing or malformed parameter

Validate all fields, especially leadid and call_type

No Response / Timeout

Mastodon endpoint down or unreachable

Retry after 30s or contact infrastructure support

 

 

 

Support

 

For setup assistance, parameter mapping help, or escalation of plugin issues, reach out to your assigned Taalk Solutions Engineer or email us at support@taalk.ai.