RUDELESS · VOIP 3.0

Different networks. One Conversation.

An assistant, four people, one shared interface.

Experimental UCTP profile · connect for build details.

Not connected
The Conversation ID stays with every interaction.

One Conversation, across the connections

Control / signalingAudio bridgeMessaging
Waiting for a Conversation.Connection IDs reveal continuity across the handoff.

Control, bridge and delivery states come from events. The SIP endpoint is visible; carrier and PSTN internals are not observed.

Waiting for Jonathan’s task
Arrangements still being gathered
0/4 final updates sent · 0/4 deliveredFinal updates wait for owner approval.

People and their connections

AI assistant · UCTP · RvoipWaiting for a provisioned Conversation
Task and follow-up

Attributed replies and final voice transcripts will appear here as context arrives.

Travel decisions are sandbox examples. Communication states below come from actual server events. SMS acceptance is distinct from delivery and a person's confirmation.

The Conversation, as it happens

Connect to see attributed messages, delivery receipts, voice connections, and approvals. Select an event to reveal its UCTP evidence.

The next connection could be yours.

Build a connector. Build a UCTP application. Share what you connect.

Where this goes next

Rvoip connects the systems. UCTP gives people and agents a shared interface.

Bring a system

Contribute a connector for a network or service your community uses. Describe what it supports and show it working with the reference client.

Bring an application

Connect a human interface or an agent through UCTP. Reuse the available connectors and share your example.

Future community integrations could include team messaging, email, radio, and additional carriers. These are contribution ideas, not capabilities demonstrated here. The experimental profile and local quickstart are in this demo repository; a public sharing destination will be added when verified.