Hopefully an easy one here. 2801 router with 4 FXO trunks. Customer insists that callerid and number should show up inbound. Is there a debug I can run on an incoming call that can verify that telco is sending this info down the trunk. "caller-id enable" is configured on the voice ports and I didn't think there was much else to do. This is a 2801 CME with a mix of 7975, 7962, and 7911 phones. Of course, I could go onsite with an old analog display phone, but that involves a 2 hour drive--a nice debug would be a good start. Thanks.
The debug you would really want to look at is 'debug vpm signal'.
You should be able to skim through the debugs for 'FSK', as this is the name of the protocol that is responsible for the caller id. We occasionally see instances where the FSK is being distorted and fails. This is almost always a provider issue.
If you have caller-id enabled, and you're not getting caller id, it's probably a provider issue. You can check the ccapi debug, and you'll want to check this part of the debug:
----- ccCallInfo IE subfields -----
The ani there should have some value if you're getting caller id.
Note that this is what I've seen in my experience - normally the cases where the analog phone works but the router doesn't is still a problem with the provider.
The way it normally comes down is that the provider is sending a slightly-out-of-spec CLID, and the phone is more lenient in what it will take than the router. This then becomes a problem because if the router was to be more lenient, then there would be another phone somewhere else that wouldn't receive the right caller id from a provider that was in spec.
Some insight into the less fun nitpicking that goes on with providers.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...