Guest

Preview Tool

Cisco Bug: CSCur68075 - ISR 4451-X : Add codec pass-through support to SCCP transcode dspfarm

Last Modified

Sep 17, 2019

Products (20)

  • Cisco IOS
  • Cisco ASR 901-6CZ-F-D Router
  • Cisco ASR 901-6CZ-FS-D Router
  • Cisco ASR 901-4C-FT-D Router
  • Cisco ME 3600X-24TS-M Switch
  • Cisco ASR 901S-4SG-F-D Router
  • Cisco ASR 901S-2SG-F-AH Router
  • Cisco ASR 901S-2SG-F-D Router
  • Cisco ASR 901-6CZ-F-A Router
  • Cisco ASR 901-6CZ-FT-A Router
View all products in Bug Search Tool Login Required

Known Affected Releases

15.4(3)S

Description (partial)

Symptom:
ISR 4451-X : Ehibits Transcoding failures and Core dumps.

Conditions:
2 IOS Versions tested:   
isr4400-universalk9.03.10.03.S.153-3.S3-ext.SPA.bin
isr4400-universalk9.03.13.01.S.154-3.S1-ext.SPA.bin


Platform ISR-4451 configured as DSP resources (Conference & Transcoder resources for CUCM 10.5)  fails to transcode pass-through streams (IPv4 <--> IPv6) and if failures continues over extended period of time the box Cores and reloads itself.

SCCP debug Error messages when Pass-through transcodeing Invokes:
----------------------------------------------------------------------------------------
requestedAddrType = 0, source_ip_addr.ipAddrType = 0, source_ip_addr = 10.10.2.15, source_port_number = 4000, 
audio_level_adjustment = 0
Nov 11 07:38:21.916 EST: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
   Bad argument: vdbPtr != NULL

Nov 11 07:38:21.916 EST: sym_xapp_calleg_setup_req: MSPSPI setup request failed for sess_id 51790975, conn_id 151001451, conn_id_tx 0, stream_passthr_id 16777216, call_ref 158670892, rc -1

-------------------------------------------------------------------------------------------------------------
Core BackTrace
#0  genmc_aborting_core () at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/hardware/genmc/hw-oct/hw_uart_macros.h:25
#1  0x10a66604 in exception_spin_wait () at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/hardware/genmc/hw-oct/oct_exception.c:249
#2  0x10a668e8 in oct_exception_handler (registers=<optimized out>) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/hardware/genmc/hw-oct/oct_exception.c:412
#3  0x1007cde0 in cvmx_interrupt_do_irq (registers=0x1c005d20) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/vendor/crankshaft/oct/2.2.0/executive/cvmx-interrupt.c:578
#4  0x10000560 in cvmx_interrupt_stage2 () at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/vendor/crankshaft/oct/2.2.0/executive/cvmx-interrupt-handler.S:116
#5  0x1089eef8 in pkt_get_packet_start (pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/infra/pkt_manip.c:146
#6  dsp_ingress_processing (pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/dplane/feature/dsp/dsp_ingress.c:424
#7  0x10a8e3bc in _invoke_features (perf_cnt_this_fia=0, trace_this_fia=0, pt_fia_trace=0, pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/hardware/genmc/common/hal_feature_invoke.c:230
#8  hal_invoke_features (fia_trace=0, pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/hardware/genmc/common/hal_feature_invoke.c:151
#9  invoke_features (pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/infra/feature_invoke.c:203
#10 pf_rx_process (pkt_state=0x1207faf0, rx_channel=<optimized out>) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/platform/ffp/pf-oct/pf_oct.c:731
#11 0x109dfb90 in pal_rx_process (rx_channel=<optimized out>, pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/platform/ffp/ffp_pal_rx.c:20
#12 infra_main (pkt_state=0x1207faf0) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/infra/packet.c:347
#13 0x10c22874 in main (argc=<optimized out>, argv=<optimized out>) at /auto/mcpbuilds15/release/03.10.03.S/BLD-V03_10_03_S_FC1/cpp/dp/platform/ffp/ffp.c:547
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.