Hello:
If you are using a node with duplex=3, then you won't be heard on the context that RepeaterPhone uses. Essentially, RepeaterPhone connects to a node more or less as if it's a local radio on that node, meaning any telemetry on your node will pass through. Courtesy tones, ID's, etc. Likewise, many radio-less nodes are configured using duplex=3, such that you have full duplex capability without hearing yourself. But, if you're running such a configuration, you have now discovered that works fine except for WT connections. Since your audio isn't being repeated, and the WT connection is essentially connected as if it's plugged directly into the node, that means it won't get audio from you, since it isn't being repeated.
This is not an issue which has affected me, personally, since I pretty much always use my radio-less nodes connected to other hubs, which handle the connection from RepeaterPHone, not my node directly, but I'm certainly aware of it.
The only thing I can really suggest is to use an intermediate node, even if it's just a second node on the same box. Connect your node to that one, and then have others connect RepeaterPhone to that node instead of the one associated with your interface directly.
The only other option I can think of without doing something drastic would be to set your duplex to either 0 or 1, which would disable full duplex, or set it to 2, which would probably be annoying for you, as you would hear yourself own audio back with a delay, but in all these cases, you would be heard over RepeaterPHone and any other node using WT.
I have a radioless node that I connect to via RepeaterPhone and can make calls while my node is connected to other nodes.