I sent you a PM. the tug logs will show *why* MBG isn't forwarding.
I sent you the logs, not sure if you got it though... I looked in the tug logs, guess I don't look at them enough, it shows an unauthorized RTP stream but I can't really see why it's not authorized. I added packet captures and tug logs to ticket with Mitel, will see what they say.
Going to have to look through the SIP CoE document tonight, see if I can find a backup to my backup plan to help this customer get NYC numbers into Minneapolis data center with an approved carrier, but I am not sure that will help since we tried once with an tested and certified carrier but apparently their "eSIP" product is not the same as SIP trunking so the approved method doesn't apply.
Don't suppose you can recommend a good cloud SIP provider than can terminate international calls reasonably and get numbers for most US markets? Worst part is we were testing this carrier for Hong Kong numbers and in all our tests this issue never came up, but something else did and we needed 20 NYC DID's in a hurry and they got us a block in 5 minutes.