You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It will be allow convinient way for communication between SIP server and LiveKit agent handling call.
Ir should allow specyfing Content Type and INFO payload (transfered as body)
Thank you.
The text was updated successfully, but these errors were encountered:
Hi @dennwc ,
Our solution uses a media server to handle user interactions. We control the media server via MSML (https://datatracker.ietf.org/doc/html/rfc5707), which uses bidirectional SIP INFO both to send requests and to receive events. Currently, we are transitioning to Livekit, but we intend to continue using SIP INFO as our transport mechanism—not only to receive events from the voice agent but also to influence its logic. We believe that the scenario in which a product migrates from a traditional media server to Livekit is quite common, and enabling INFO support will be instrumental in accelerating the transition.
It will be allow convinient way for communication between SIP server and LiveKit agent handling call.
Ir should allow specyfing Content Type and INFO payload (transfered as body)
Thank you.
The text was updated successfully, but these errors were encountered: