11 Jun
2013
11 Jun
'13
3:57 p.m.
This is fixed now. It was a Level3 specific routing issue - I worked with them and it's resolved. Thanks all.