Inbound routes that include brackets create invalid context

Hi,

I have a couple of inbound routes that have brackets for pattern matching eg:

_12123123[89]X

which TL creates a context such as:

/etc/asterisk/inbound_actions.include:[from-outside-_12123123[89]X-tl-allhours]

but because it contains the brackets, is invalid and asterisk shows it in the dialplan as:

from-outside-_12123123[89

Regards
Allister