I do use star codes, such as *96 (ie *9644 to bargein on extension 44)
But right now I only need max of 4 (most likely 2) codes, so if we can exclude those from OBi, that would be fine.
10 or 11 digits (leading 1 or not) after *xx code (which is always 2 digits from what I see on Anveo). I have attached a screenshot so it makes more sense.
We don't always spoof the ID, or call the same number all the time. I don't know if there can be a programmable key on 2182 or 1062 that sends the (example) *02 code and then allow dialing the number to be called.
If so, I'd label it (4321 CID) where 4321 is the last 4 digits of the spoofed ID. It would feel to the customer as if they are selecting an outside line on that number (like POTS PBX), even though that isn't what it is actually doing.
Right now, without any changes to the OBi's * handling, I can't send any *xx codes to the provider, they are intercepted by the OBi.
Is it possible to add a dialing digit map to allow just 4 of the codes to pass through without the Obi intercepting them? I'm not very good with digit maps yet, just starting to get used to some InboundCallRoute stuff.
Thank you for your help.