#Well the voice-call module thats in

1 messages · Page 1 of 1 (latest)

thick zinc
#

actually i guess it makes sense, you want any agent in any channel to be able to place a phone call. Maybe it can call you to talk or you can call it, but you can also just ask your agent via any channel to "call my wife and tell her ill be late" or something like that - which makes more sense for it not to be a dedicated channel itself

warm bridge
#

A phone call can be seen as a skill/action ; But perhaps it can also be seen as a channel. So you could implement it both ways is my guess. Before the recent changes, it was a pain to create such a channel though, because of the last of plugin surface area to plug into.

thick zinc
#

yeah i could see both as well i guess, but since the skill/action implemetnation is kind of whats already there and i think is useful - thats what i was thinking might plug into what you have done well

warm bridge
#

If you have an Alexa-like/OpenHome-like "always-on-microphone+speaker" device, that would probably be better represented as a channel.

thick zinc
#

yeah for sure

warm bridge
#

my PR is focused on allowing to add additional AI model providers which have different capabilities/modalities. Two of which are ASR and TTS, including telephony codecs.

thick zinc
#

ah yes i see

#

now i see the divergence, but this pattern still i think is great. something like this could be applied more generally to any extension providing a common "function" so that when its exposed to the core agent model they get a common tool interface