CCS Trace is rarely usable in this case... If we are talking about a PRI, then the relevant information would be in "EDT TRACE TSP L2L3 <PLID>" (remember this is a toggle on/off command, do not leave it on for extended periods, it won't hurt anything but can get very annoying later)
If the COR is correct and you believe the carrier is blocking your call, this will show it instantly.
Just got around to running the command, here's the result from a traced call:
HDLC CC on link 1 trace enable .
HDLC VERBOSE on link 1 trace enable .
10:28:12 RIL DPN PEER NIL_PEER_ 867 2C ISRM_I
;10;*1#*19*Z#*58*Ca*1*Z#*100*Hangar 2 Breakro#
10:28:12 RIL DPN PEER NIL_PEER_ 867 2B SSRM_C
*58*CW*s]@s@@@@DndbCp#*50*8225#9<masked for privacy>
10:28:12 RO116 DPN 1F ISRM_I ;10;*1*1#*50*8225#*58A*Cc*4*8225#
10:28:12 RO116 DPN 18 SSRM_I *100*H.Breakroom#*19*Z#
10:28:12 RO116 DPN 2D SSRM_I *58*CW*s]@s@@@@DndbCp#*58*C6*001#*58*C4*4*1#
10:28:12 RO116 DPN B SSRM_C <masked for privacy>
10:28:12 RI116 DPN 23 CRM/CIM ;29;*100*ACCESS BARRED ACCESS BARRED#
10:28:12 ROL DPN PEER NIL_PEER_ 867 23 CRM/CIM
;29;*100*ACCESS BARRED ACCESS BARRED#
HDLC CC on link 1 trace disable .
HDLC VERBOSE on link 1 trace disable .
the error (to me at least) looks very similar to the other trace i attempted to do, would i be correct in presuming the carrier is blocking this device from making a call over the PRI?