I posted this in the general questions and it did not seem to get noticed, I have noticed other issues posted in features wanted so thought I would try here?
I have a couple of inbound routes that have brackets for pattern matching eg:
which TL creates a context such as:
but because it contains the brackets, is invalid and asterisk shows it in the dialplan as:
Is there anyway to get TL to escape them for the context but use the expression for the extension?