PSTN OUTGOING CALL DISCONNECTION IN CISCO ISR G2 (C2951-CME-SRST)

[djibrilcamara]

Hi all members and contributors,

We recently receive a Cisco CME ISR G2 CISCO2951-CCME with the following IOS c2951-universalk9-mz.SPA.151-3.T.bin. After the configuration of the voice equipment, we start using it in our company before deploying it on the customer network. However, we were surprise to have call disconnection on PSTN call after a ramdom time of communication. We use the same configuration that we used in the past for Cisco ISR G1 and which worked fine.

We change the IOS at three times but we encoureted the same problem.

Does someone have an idea about the issue. We are really blocked. All licence are bought for the Cisco CallManager Express.

Here are Information about the E1 car configuration:

----------------------------------------------------------------------------------

license udi pid CISCO2951/K9 sn FCZ1450200D
hw-module ism 0
!
hw-module pvdm 0/0

!

controller E1 0/0/0
framing NO-CRC4
clock source internal
pri-group timeslots 1-31
!

interface Serial0/0/0:15
description ***** E1 INTERFACE *****
no ip address
encapsulation ppp
isdn switch-type primary-net5
isdn incoming-voice voice
isdn bchan-number-order ascending round-robin
isdn sending-complete
isdn outgoing-voice info-transfer-capability 3.1kHz-audio
keepalive 10 3
no cdp enable
!

[Roman Rodichev]

Hi, you shouldn't need "clock source internal", as clocking should be provided by the provider's phone switch, change it to "clock source line" and "shut" then "no shut".

[djibrilcamara]

Hi Roman,

Thanks for your response. But we already test with this configuration with no success. Currently the system is connected to a BRI interface and we notice the same problem. Here are information about our BRI configuratation

isdn switch-type basic-net3
isdn voice-call-failure 0
isdn tei-negotiation first-call
!
!
voice call send-alert
voice call convert-discpi-to-prog
voice rtp send-recv
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
no supplementary-service sip moved-temporarily
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none
modem passthrough nse codec g711alaw
sip
  registrar server expires max 1200 min 300
  no update-callerid
!

voice-card 0
dspfarm
dsp services dspfarm
!

interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
!
interface BRI0/0/1
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn send-alerting
isdn sending-complete
!

Sincerly  I check since now one month and I can't understand the problem.

Many thanks in advance for your support.

[paolo bevilacqua]

You should capture a q931 or whatever applicable trace when the disconnection occours.

[djibrilcamara]

You will see in attached file q931 & q921 debug. Many thanks for your contribution.

[paolo bevilacqua]

Fri Mar 11 09:52:06 2011: <187>18886: WVI_CME: *Mar 11 09:51:06.106: %DSPRM-3-DSPALARM: Received alarm indication from dsp (0/1). Resetting the DSP.
Fri Mar 11 09:52:06 2011: <187>18887: WVI_CME: *Mar 11 09:51:06.106: %DSPRM-3-DSPALARMINFO: 002A 0000 0080 0000 0008 0004 5761 7463 6844 6F67 2054 696D 656F 7574 2C20 5043 3D30 3030 6539 3663 3400 6D59 00FD 0000 0000
Fri Mar 11 09:52:06 2011: <187>18888: WVI_CME: *Mar 11 09:51:06.106: %DSPRM-3-DSPALARMINFO: WatchDog Timeout, PC=000e96c4

Seems like HW failure, replace PVDM module.

[djibrilcamara]

Thanks but the problem is that we have this problem with two ISR G2 (CISCO2951) of two different customers.  All equipments are newly shipped from our Cisco distributor. I think that it can be a problem with our operator public switch but what configuration must run in case of we never have information about operator equipments.

Thanks!

[paolo bevilacqua]

I can only comment on what I see from the trace you posted.

I do not see any problem with telco.

I do see an hardware failure requiring (at least) the PVDM module to be replaced.

And that you have to open a TAC case for further support.

Then if you want to think differently, feel free and good luck.

[djibrilcamara]

Man thanks Paolo for your support. I will do your recommendations and hope that the problem will be solved after.

Thanks again

[paolo bevilacqua · Accepted solution]

Thanks for the nice rating and good luck!