cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1529
Views
0
Helpful
1
Replies

call drop after 2 min 45 sec - CISCO(29xx series) Router /Nortel11c Meredian E1 Connectivity

Humayun.sami_2
Level 1
Level 1

I have following setup configured: Nortel PBX---E1-->CISCO  Router----->CISCO Router (FXO/FXX Port) --- Having problem of dropping call  exactly after 2 minutes and 45 second. Analog set located at remote site use 9  to access PSTN trunk installed at Nortel PBX and then it dials out. These calls  are dropping after 2 min. 45 seconds...

The CISCO logs and the Nortel 11C  capture shows following error
Cause No. 102 - recovery on timer  expiry. This cause indicates that a procedure has  been initiated by the expiration of a timer in association with error handling  procedures.
What it means: This is seen in situations where ACO (Alternate  Call Offering) is being used. With this type of call pre-emption, the Telco  switch operates a timer. For example, when an analog call is placed to a Netopia  router that has two B Data Channels in place, the router relinquishes the second  channel, but if it doesn't happen in the time allotted by the switch  programming, the call will not ring through and will be discarded by the  switch.



   ISDN Serial0/3/1:15 Timers (dsl 0) Switchtype =  primary-qsig
       ISDN Layer 2 values
        K     =   7 outstanding  I-frames
        N200  =   3 max number of retransmits
        T200  =    1.000 seconds
        T203  =  10.000 seconds
       ISDN Layer 3  values
        T302  =  15.000 seconds
        T301  = 300.000  seconds
        T303  =   6.000 seconds
        T304  = 120.000  seconds
        T305  =  30.000 seconds
        T306  =  30.000  seconds
        T307  = 180.000 seconds
        T308  =   6.000  seconds
        T309    Disabled
        T310  = 120.000  seconds
        T313  =   6.000 seconds
        T314  =   6.000  seconds
        T316  = 120.000 seconds
        T318  =   4.000  seconds
        T319  =   4.000 seconds
        T322  =   4.000  seconds
        T3OOS =   5.000 seconds

Regarding the Dial-peers when I  use the below dial peers:

No  dial tone but call does not drop

dial-peer voice 82  pots

description ** PTCL Dialing  **

destination-pattern  82

incoming called-number  .

direct-inward-dial

port  0/3/1:15

forward-digits  all

Dial  Tone but call Drops in 2 min 45 sec

dial-peer voice 82  pots

description ** PTCL Dialing  **

destination-pattern  82T

incoming called-number  .

direct-inward-dial

port  0/3/1:15

forward-digits  all

Kindly  help…

1 Reply 1

Bryan Deaver
Cisco Employee
Cisco Employee

Hi Humayun,

That this does not match any of the likely timers (like T310), I would guess that this is something going on with the cisco to cisco connection.

You don't include the voip dial-peer or mention the voip signaling protocol, but I am guessing that this is H323.  You may be seeing an issue on the H245 connection or update.

Good to generally troubleshoot this would be debug isdn q931, isdn event, cch323 session, h245 asn.  Generally on IOS gateways, voip ccapi inout is also a good debug to have but lets focus on the signaling first to see what is going on.  When turning on any debugs, turn off console logging.  Also, recommend you setup logging buffered to something like 100000 and setup timestamps out to msec level (service timestamp debug date msec) to make reviewing debug logs easier.

A simple test may be to change the voip signaling protocol to sip to see if that makes a difference as well.

Normally sending this debug output may contain information that you may not want on a public forum.  If this is the case with what you have, please open up a tac case to help troubleshoot.