Alas, no... however you might not need a sound if you can use tonal inflections and pauses to express the boundary instead. Particularly when chunks are short and when the receiver (or the software they're typing into) knows the format already... Although with a tech-illiterate relative you'll have bigger problems, like explaining what an underscore even looks like and where it is on their keyboard.
Obviously I can't fully express it in text here, but try to imagine this as a coworker speaking to you: "Hey, write down this IP address. It's ten, seventy, one twentyyyyyTWO, five."
They didn't actually say "period" or even "dot", but I bet you'd type 10.70.122.5 .
I've worked in IT (support, network mgmt and development roles) for 20 years, with colleagues, customers and clients from dozens of countries.
I've never once heard anyone drop out the dots in an IP. Non technical users aren't confident enough to do anything but read it exactly as it appears (one zero dot seven zero dot...) and technical users who are generally experienced enough to know what an IP address is, know that the dots are meaningful.
If it's something like 56.7.23.231, I'm definitely going to disambiguate it by deliberately saying each one of of those three dots.
But if it's more like 192.168.0.1, I'm probably not going to bother with speaking any delimiters in conversation with another person who has at least reasonable familiarity with common IP networking layouts.
Bringing it back to the topic: UUIDs should not ever follow familiar content patterns (if they do, then that's an issue in and of itself), so I'm always going to speak the delimiters of a UUID -- whatever they consist of.
(If nothing else, doing so breaks up the pattern into human-digestible chunks -- which is probably the sole reason we have those delimiters in UUIDs to begin with.)
