Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Phones are freezing

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
  • #62332

    Hi Pix

    1. Someone is calling to me, I want to reject the call. But when I press NO button phone freezes about 10 seconds. It happens in all Huawei areas. Not everytime, most time.

    2. MS1 is speaking with MS2, MS3 is calling to MS1 and see it is busy. And presses NO button, but it freezes immediately 10-15 seconds. It happens everytime in all Huawei areas.

    Do you know about this problem???

    Thanks in advance



    Have you done a drive test ? Could extract the layer 3 messages that are occuring when the phone “freezes” ?
    Does it happen only with a certain type of phones, or all phones ?

    I’d rather say it is a phone issue than a huawei issue, but who knows…



    Maybe you can check this
    This timer is on mobile and assigned

    T3110:This timer is used to delay the channel deactivation after the receipt of a (full) CHANNEL RELEASE. Its purpose is to let some time for disconnection of the main signalling link. Its value is set to such that the DISC frame is sent twice in case of no answer from the network. (It should be chosen to obtain a good probability of normal termination (i.e. no time out of T3109) of the channel release procedure.)

    T3111:This timer is used to delay the channel deactivation after disconnection of the main signalling link. Its purpose is to let some time for possible repetition of the disconnection. Its value is equal to the value of T3110.


    Thanks, i will check timers. What value should be normally in Huawei?

    Dear Pix
    it is happing in all phones. What can i see in layer 3 about this?


    In layer 3, you could see at which message the phone is freezing.
    and you could check that huawei is actually following the 3GPP standards in these scenarios you described.
    Perhaps a weird message is sent, or a message with a weird field value, causing phones to freeze (???)

    Brother : good ideas !


    This is an interesting topic and i also faced this problem lets see some more definition…

    Actually i missed one thing in my last message

    t3110 is a mobile side timer
    t3111 is a network side timer

    you can define t3111 in parameters you can find and according to that value t3110 is defined same value. Siemens default is 0.5 second.

    Here is the siemens definition about t3111 and it says if you put high value call release will take more time

    T3111: This timer is used to delay the radio channel deactivation in
    the BSC after release of the main signalling link on the Um. During
    the call release procedure the BSC sends the CHANNEL RELEASE
    message. After receipt of the CHANNEL RELEASE message the MS
    sends a DISCONNECT message to the BTS to disconnect the
    FACCH. Subsequently the BTS acknowledges the DISCONNECT
    message towards the MS by an UA and informs the BSC by sending
    the RELEASE INDICATION message. On receipt of the RELEASE
    INDICATION the BSC stops timer T3109 and starts timer T3111. On
    expiry of T3111 the BSC deactivates the radio channels by sending
    the RF CHANNEL RELEASE message to the BTS. The sole purpose
    of timer T3111 is to let some time for the acknowledgement of the
    disconnection (by an UA) and to protect the channel in case of loss of
    the acknowledge frame.

    Note: The higher the value of T3111 is the longer the call release
    procedure takes. Thus T3111 has an impact on the feature ‘Queuing’
    (see also parameters EQ (SET BTS [OPTIONS]) and BSCT11PUB
    (SET BSC [TIMER])): the longer the release procedure for an existing
    call takes, the later a queued TCH request can be served. A released
    TCH is ‘available’ for a queued TCH request if the BSC has received
    the RF CHANNEL RELEASE ACKNOWLEDGE for the released
    TCH. As a higher value of T3111 leads to a delay of the RF
    CHANNEL RELEASE message it simultaneously leads to an
    extension of the queuing time. Therefore it is recommended to set
    T3111 to the default value (HLFSEC-1).


    Dear Pix/Brother

    I have investigated both cases:

    1. In Huawei BSC T3111 is 1 second, but could not find T3110.

    2. We are using sony ericsson with TEMS, but it is not happening in sony ericcson, it happens in only Nokia phones. I have just found out it, this problem seems on the Nokias.

    Do you have any idea about this?
    For remind, I’m repeating the case:

    MS1 is callining to MS2 and MS2 is ringing. Also MS3 is callining to MS2. But I see MS2 is busy, and want to reject but in this case the phone is freezing about 10-15 sec.

    Please your helps:
    Thanks in advance


    Hi Pix
    Any comments?



    I already said you should trace your scenarios with TEMS… very easy to do, and at least you’d understand where the problem lies.

    The problem is not in the phones, otherwise that would affect the rest of the world too.

    It’s perhaps a misunderstanding between BSS and NSS ?


Viewing 9 posts - 1 through 9 (of 9 total)
  • The forum ‘Telecom Design’ is closed to new topics and replies.