Free Erlang traffic calculators

The world's first online Erlang traffic calculators

Telecom Traffic Online
  Home | Free calculators | Products | Tech. papers | Forum | About us
A-Z termination - click here
A-Z termination - CLICK HERE
VoIP bandwidth calculator
  • VoIP softswitch

    DUAL Softswitch is a complete Voice over IP switching and billing solution.  Flat monthly rate.

    Web control panels; Least Cost Routing; Excel tariff uploads; SIP and H323 support.

    H323 SIP softswitch >>

  • VoIP calling

    Premium quality termination for wholesale carriers with their own VoIP switch.

    44Direct >>


    Our lowest rates for wholesale carriers with their own VoIP switch.

    44Mobile >>


    Our unique online callshop billing system.

    Bill My Calls >>

Recovery on timer expiry

Rogerio - 25th September 2017  (16:42 GMT)

Cause i = 0x80E6 - Recovery on timer expiry

Nitin Saini - 29th September 2014  (01:42 GMT)

Hello All,

Could you help me to answer below questions.

T313 = 30sAn application parameter determines the time supervision period between sending of CONNECT message and receiving of CONNECT ACKNOWLEDGE message using the T313 timer. Value range = 1s-255s
We need to check on the following: - Is there any another timer on the BSC/RNC that is linked to this timer? - In MIC1 network, the timer is set to default (30s), what are the risks of decreasing / increasing this timer? - What could be the advantages of changing this timer value? - what are the possible impact on the call flow? (Delay on call connection....) - What is the particular impact of this timer during an IRAT handover from 3G to 2G? Does this timer has any impact on call drops? - Does the expiry of this timer impact

Mania - 11th January 2012  (05:59 GMT)

Two scenarios are possible,
1. A Faulty handset.
2. RF UL Quality issues causing no reception at the MSC Level.
Probably you should check if the issue is being generated from one IMEI or IMEIs of same vendor if its a faulty handset or a chinees company's phone then its best to contact the customer and ask him to change his handset. Else you can improce the RF Quality of try increasing the T313 timmer.

Ayman - 8th January 2012  (20:31 GMT)

Dears,

we've faced exactly the same problem. call setup --> dedicated mode --> call drop --> disconnect and the call continue in dedicated mode then idle mode.

cause reason of drop call is "recovery on timer expiry" which is due to the expiry of T313.

Any suggestions to solve such issue?

Amit Yadav - 29th June 2011  (10:39 GMT)

It is T313 timer which MSC start after sending the Connect and wait connect ack. If T313 expire before ack then MSC will release the call.

Mania - 9th June 2010  (08:36 GMT)

Hi,
Have you guys tried having a trace on the Test cell phone at the MSC end and running them in parallel to trace weather the message is lost on the way or MSC receives the messages from MS or not.
Work with NSS assistance should be fruitful.

Cveloz - 8th June 2010  (19:55 GMT)

i have the same problem with a Ericsson network. Did you solve this?

aziz - 29th January 2010  (14:57 GMT)

"i am currently investigating a problem were calls on GSM are dropped with cause reason "recovery on timer expiry". An initial investigation of the core network timer shows no evident problems with the timer settings however i from K15 traces of the A interface, i noticed that in most cases, the call drop occurs when NO connect ACK is recived from the MS. The call is connected normally however after some time, it drops with reason "recovery on timer expiry". It seems that a timer is started when the msc sends the CONNECT message and it is stopped when CONNECT ACK is received. If no CONNECT ACK is received before expiry of this timer, the call is released. Did anyone see this type of behaviour before? Why is the connect ACK not being sent by MS (possible poor radio conditions?) Any help on this would be greatly apreciated. Network here is Siemens BR9.0"
I have the same problem , but im my case I see that the ms send connect ack but I don't know if the MSC receive this message

CellOpt - 5th February 2009  (08:11 GMT)

I am currently investigating a problem were calls on GSM are dropped with cause reason "recovery on timer expiry". An initial investigation of the core network timer shows no evident problems with the timer settings however i from K15 traces of the A interface, i noticed that in most cases, the call drop occurs when NO connect ACK is recived from the MS. The call is connected normally however after some time, it drops with reason "recovery on timer expiry". It seems that a timer is started when the msc sends the CONNECT message and it is stopped when CONNECT ACK is received. If no CONNECT ACK is received before expiry of this timer, the call is released. Did anyone see this type of behaviour before? Why is the connect ACK not being sent by MS (possible poor radio conditions?) Any help on this would be greatly apreciated. Network here is Siemens BR9.0

Post a reply to this article

Name Enter your name.
Message Enter your message.
Email Optional -  If you enter your email address in this box, then you will automatically be notified if anyone replies to your message.  Your email address will only be published if you pay to post this message.
Verification
Please confirm you are human.
Press the button to post your message.
Home | Free online calculators | Products | Technical papers | Forum | Contact us | About us

Last modified: 17 May 2017

Copyright 2017. All rights reserved.