Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

robotic soung on ipcc recorded call

Hello everyone.

I have the following problem:

I have a CCM 4.1(3)sr7 and IPCC 3.5(2).

The calls are recorded using a workflow and everything was working fine.

Some day ago the voice quality is very poor and robotic.

Can anyone help?

Thank you

Gleidson CCVP

Nexa - Brazil


Re: robotic soung on ipcc recorded call

Hi Gleidson,

Could you please check your network switches if something has changed. Check for any network errors and LAN Card.



New Member

Re: robotic soung on ipcc recorded call

Hello mikram.

This is the port status

SW01#sh run | b sess

monitor session 2 source interface Gi0/2 rx

monitor session 2 source vlan 34 rx

monitor session 2 destination interface Fa0/16 ingress vlan 34


SW01#sh inter fas 0/16

FastEthernet0/16 is up, line protocol is down (monitoring)

Hardware is Fast Ethernet, address is 0011.5c3e.1010 (bia 0011.5c3e.1010)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 3/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, media type is 100BaseTX

input flow-control is off, output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:15, output 23:06:11, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 1445000 bits/sec, 829 packets/sec

2125410 packets input, 168098794 bytes, 0 no buffer

Received 40242 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

1 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 27139 multicast, 0 pause input

0 input packets with dribble condition detected

2101432444 packets output, 3905105117 bytes, 11334531 underruns

0 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

11334531 output buffer failures, 0 output buffers swapped out

CreatePlease login to create content