OPERATIONAL DEFECT DATABASE
...
...
platform: 4451 IOS XE isr4400-universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bin customer is running CDR accounting and sending them to syslog server router was upgraded to 16.6.4 isr4400-universalk9.16.06.04.SPA.bin after the upgrade there is an ambiguity with respect to the VOIP CALL HISTORY parameters "ConnectionID" and "fcid" they were identical before the upgrade and became unidentical after upgrade.
router upgraded to 16.6.4 isr4400-universalk9.16.06.04.SPA.bin
downgrade to isr4400-universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bin
Troubleshooting Performed with the previous version both these params were identical. However after upgrade the ConnectionId and "fcid" look different for eg here we can see that the ConnectionID and fcid are different 006593: *Mar 1 09:14:49.777: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 4AB82D4E3B3911E9FFFFFFFF811098F0FFFFFFFFC0DC6672, SetupTime *09:14:46.427 UTC Fri Mar 1 2019, PeerAddress 2626, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *09:14:47.977 UTC Fri Mar 1 2019, DisconnectTime *09:14:49.777 UTC Fri Mar 1 2019, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0 006594: *Mar 1 09:14:49.777: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:03/01/2019 09:14:46.427,cgn:2626,cdn:,frs:0,fid:8,fcid:4AB82D4E3B3911E9811098F0C0DC6672,legID:11B,bguid:4AB82D4E3B3911E9811098F0C0DC6672 006595: *Mar 1 09:14:49.779: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 4AB82D4E3B3911E9FFFFFFFF811098F0FFFFFFFFC0DC6672, SetupTime *09:14:47.229 UTC Fri Mar 1 2019, PeerAddress 2005, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *09:14:47.979 UTC Fri Mar 1 2019, DisconnectTime *09:14:49.779 UTC Fri Mar 1 2019, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 83, TransmitBytes 16600, ReceivePackets 85, ReceiveBytes 16841 006596: *Mar 1 09:14:49.779: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:03/01/2019 09:14:47.229,cgn:2626,cdn:2005,frs:0,fid:9,fcid:4AB82D4E3B3911E9811098F0C0DC6672,legID:11C,bguid:4AB82D4E3B3911E9811098F0C0DC6672 before the upgrade they were identical: for eg: 1690: CHS2VG33: *Feb 26 02:58:43.331: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 42CE364538A911E9FFFFFFFF8011C7D026CB7523, SetupTime *10:58:43.301 CST Tue Feb 26 2019, PeerAddress 15714, PeerSubAddress , DisconnectCause 1 , DisconnectText unassigned number (1), ConnectTime *10:58:43.331 CST Tue Feb 26 2019, DisconnectTime *10:58:43.331 CST Tue Feb 26 2019, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0 1691: CHS2VG33: *Feb 26 02:58:43.332: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/26/2019 10:58:43.297,cgn:15714,cdn:913920946977,frs:0,fid:4,fcid:42CE364538A911E9FFFFFFFF8011C7D026CB7523,legID:4,bguid:42CE364538A911E98011C7D026CB7523 I am able to reproduce this behavior in lab on IOS 16.3.7 on platform 4351 as well. as soon as i downgrade to isr4400-universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bin, the connectionID and fcid become identical.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
