...other server messages from the Server URL? If so, why are they mutually exclusive, and why can't you then separate end of call and during call server messages so we can use both. Please clarify best practice around this issue when trying to send multiple server messages to different end points with only one Server URL slot available. Thanks!

@mindofman The server messages you receive are determined by the

serverMessages

enum array you configure. The options available, such as 'status-update', 'transcript', 'hang', 'function-call', 'tool-calls', 'end-of-call-report', 'conversation-update', 'phone-call-control', 'model-output', and 'voice-input', are not mutually exclusive. You can select multiple messages to be sent to your Server URL. However, if you need to send different messages to different endpoints, you would typically handle this on your server-side by routing the incoming messages to the appropriate internal endpoints based on the message type or content. Best practice in this scenario would be to set up a single Server URL endpoint that acts as a dispatcher. This endpoint would receive all server messages, parse them, and then forward them to the correct internal service or endpoint based on your routing logic. If you need to update your server message configuration to include both end-of-call and during-call messages, you can do so by specifying all the message types you need in the

serverMessages

array. If you need assistance with configuring this, please let me know the specific messages you want to include, and I can help you set that up.