Brent, The best way to handle forwarded calls from CUCM back out to the Vz IP trunk service is by utilizing Diversion Headers in the CUBE router. On the CUBE we can add the SIP Diversion header by adding the following configuration to the router config. 1.(add sip-profile) Here you will need to replace the phone number(2145551212) with the customer billing TN. Next you will need to change the IP address (10.10.10.10) with the VZ facing IP address or FQDN that the network is expecting.                              voice class sip-profiles 100   request INVITE sip-header Diversion add " Diversion: 2145551212@10.10.10.10) > < 2145551212@10.10.10.10)> " 2.(apply the SIP Profiles to the outgoing dialpeer towards the Vz network) dial-peer voice XXX   voice-class sip profiles 100 ... View more

Yes the Redirecting Diversion Header Delivery - Outbound needs to be checked on the SIP trunk configuration in CUCM. Are you certain that you are sending PAI? Can you get a wireshark trace of what is being sent from your CUBE to the VzB network? This should show you what is actually being sent. If PAI is not being sent then there maybe a CUBE configuration problem. If you are sending the appropriate PAI with the diversion header, then this maybe a porblem witht he VzB VoIP provisioning. We have this working in our lab. -Charles ... View more

What version of CUCM are you running? You need to enable the outbound diversion header delivery on the SIP Trunk configuration in CUCM. Starting with CUCM Release 6.1(4) adds the Redirected Dialed Number Identification Service (RDNIS) and diversion header capability for certain calls that use the Cisco Unified Mobility Mobile Connect feature. http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_1_4/cucm-rel_note-614.html#wp854592 -Charles ... View more