update transfer call to pass in the TN to transfer to

[rjheeta]

All TransferCall action to accept to_phone as a parameter so the LLM can feed the TN to transfer to at runtime.

[rjheeta]

@ajar98 Do you agree with this? Slight modification to allow LLM to pass in the phone number.

[arpagon]

LGTM!

[ajar98]

@rjheeta actually, I think the user should be able to configure whether or not the LLM can choose the transfer number. Couple of ways to approach this:

• Make a separate vocode action with this config change (poor DRY)
• Make the configuration value optional (which would translate to sending GPT a schema where it is not required) - imo too much control to the LLM when this is something that is easily configurable pre call
• [preferred] somehow making TransferCallParameters only get the property if to_phone is None - likely requires a deeper change to the actions system

[rjheeta]

@ajar98 Thanks for the feedback! If you're open to giving a bit of guidance / direction on your indicated preferred route, I'm happy to take a stab at it.

[ajar98]

@rjheeta awesome! Really excited to work with you on this -

BaseAction has a parameters_type method[0] that is usually implemented statically like this: https://github.com/vocodedev/vocode-python/blob/main/vocode/streaming/action/transfer_call.py#L37

We can override this for TransferCall to point to a TransferCallParameters that has a to_phone or not depending on self.action_config - i.e. if self.action_config.to_phone is None, then use the TransferCallParameters where to_phone is required.

[0] https://github.com/vocodedev/vocode-python/blob/main/vocode/streaming/action/base_action.py#L44-L46

[rjheeta]

@ajar98 Ajay, I just pushed an update. Could you have a look and advise if this is what you had in mind? Or let me know where/how I can improve it.

[ajar98]

hey @rjheeta , this is exactly what I had in mind 🎉

mind fixing the merge conflict? then should be g2g :)

[rjheeta]

my history got mangled. Will re-do this on new branch