Xenek Stoehr

[Xenek Stoehr @xeneks]

@ThorTorrens For a person drinking 3-6 cups of tea a day, would the small amount of milk in them offset the calcium loss?

[Xenek Stoehr @xeneks]

@fchollet People. You also need people.

[Xenek Stoehr @xeneks]

@steipete What I’ve realised recently is that YouTube and AI together are absolutely brilliant if you’re trying to fix something. I think all generations will benefit from that.

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I'll have to try that. But re: The voice agent builder - I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!

[Xenek Stoehr @xeneks]

I've tested it from Australia, using an Australian Telnyx DID. Answering & the voice is very fast. Problems: It has a tool section. I setup an API call there to contact my Openclaw via /responses. But the tool times out after only 10 seconds. It reaches out and rarely gets a response in less than 10 seconds. So we need a configurable timeout, eg. 600 seconds (10 minutes), for long running tasks on the openclaw to respond. Also, while it has a tool builder for API calls, it doesn't support MCP, which would be the better tool. Another thing is, if I was to use my local Australian DIDs & sip trunks (instead of the Telnyx ones) sip voice traffic is carried only in PCMU or Ulaw or G711u, and that has no handling for packet loss/disordered packets/jitter/latency. So presently, it's unworkable for me. Nice trick though!