CUCM 7.1(3) with 2811 ISR 12.4(13r)T11 .We opened a ticket with Verizon recently because all calls originating from CUCM were showing as having a caller ID of the main number instead of their DIDs. When testing we found out that this was not always the case. Outbound calls being triggered from MobileConnect were showing up with the correct caller ID. From the 2811 isdn q931 debug we confirmed that we are sending 10 digits but there was a difference in the ISDN "Plan" and "Type" information:
Call triggered by MobileConnect (correct caller ID '8575559971' is displayed on called device)
Calling Party Number i = 0x2183, '8575559971'
Call originated by user at ext 3838 (incorrect caller ID '4105553000' is displayed on called device)
Calling Party Number i = 0x0081, '4105553838'
Why would the calls be set up differently? Where does this get configured and would it affect Caller ID?
If this is H.323 you can control Plan and Type on the Gateway for all calls. If this is MGCP, you can check the plan and type for Calling Party on Gateway page.
n some cases if a carrier does not see a type and plan of their liking they will automatically mask the outgoing calling number to the billing number or pilot number of the carrier hunt group. It sounds that is what you are up against. If you will always be sending 10 digits NANP for the CLID out you might try setting the plan and type to match the successful situation at the route list, or the gateway (if there is only one gateway and you are running a recent CCM version) to Verizon. Also, once this change is in place you will need to reset the route list and/or the gateway, whether it is H323 or MGCP.