We are using HiPath 4000 V5 with 4,900+ subscribers including DECT, Digital, Analog, HFA & SIP.
All extensions frequently encounter a congestion tone when trying to access an outside line (e.g. dialing 9 to call a mobile phone). The problem goes out when we restart the system using "exec-rest:system, restart;" command. But this is too obvious for the subscribers to notice coz all lines goes offline for 6 minutes (even at night coz we're a manufacturing company).
Siemens & Unify is currently finding a way to create a patch to resolve it for more than a year now!!! They're turning ON some tracers but the process is too tedious and delayed!
So we're thinking maybe there's a way to restart the system without turning off the stations. I was assuming that maybe during the restart process, some cache memory is being cleared that is why the congestion tone is not coming up not until a few days (3 min or 2 weeks max) again.
Hi,
I presume that you are getting this congestion at around 12 noon and 3 pm - the busy office times where everyone is on the phone ?
Are there enough outside lines to cater for all your subscribers ?
What type of connections do you have to your providers / ISDN or Analogue lines ?
We experience the congestion at any time, but most usually during peak hours. And sometimes it goes congested all the way! So I need to restart one of the DIUN cards.
We actually have 2 systems. One is a slave system (also on HiPath 4000 V5) that derives external calling access to the first one. The primary system (called Hadeed-1) has the access for outside calls using E1 and analog lines, and the second system (Hadeed-2) gains access to external calls to Hadeed-1. Below is the dis-bcsu output. I duno if it is because we only have 3 SIUX cards installed.
LTG 1 LTU 9 SRCGRP 1 ALARMNO-LTU 0
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
19 | AVAILABLE 0| | AVAILABLE | |
25 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
31 | AVAILABLE 0| | AVAILABLE | |
37 | AVAILABLE 0| | AVAILABLE | |
43 | AVAILABLE 0| | AVAILABLE | |
49 | AVAILABLE 0| | AVAILABLE | |
55 | AVAILABLE 0| | AVAILABLE | |
61 | Q2196-X DIU-N2 1 A 0| | Q2196-X | 1 -07 - | READY
67 | AVAILABLE 0| | AVAILABLE | |
73 | Q2266-X LTUCA 0| | Q2266-X | 1 -14 - | READY
79 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
85 | AVAILABLE 0| | AVAILABLE | |
91 | AVAILABLE 0| | AVAILABLE | |
97 | AVAILABLE 0| | AVAILABLE | |
103 | AVAILABLE 0| | AVAILABLE | |
109 | Q2196-X DIU-N2 1 A 0| | Q2196-X | 1 -06 - | READY
115 | Q2168-X SLMO24 1 A 0| | Q2168-X | 1 -07 - | READY
121 | Q2168-X SLMO24 1 A 0| | Q2168-X | 1 -11 - | READY
LTG 1 LTU 10 SRCGRP 1 ALARMNO-LTU 0
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
19 | AVAILABLE 0| | AVAILABLE | |
25 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
31 | AVAILABLE 0| | AVAILABLE | |
37 | AVAILABLE 0| | AVAILABLE | |
43 | AVAILABLE 0| | AVAILABLE | |
49 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
55 | AVAILABLE 0| | AVAILABLE | |
61 | AVAILABLE 0| | AVAILABLE | |
67 | AVAILABLE 0| | AVAILABLE | |
73 | Q2266-X LTUCA 0| | Q2266-X | 1 -14 - | READY
79 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
85 | AVAILABLE 0| | AVAILABLE | |
91 | AVAILABLE 0| | AVAILABLE | |
97 | AVAILABLE 0| | AVAILABLE | |
103 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
109 | AVAILABLE 0| | AVAILABLE | |
115 | AVAILABLE 0| | AVAILABLE | |
121 | AVAILABLE 0| | AVAILABLE | |
LTG 1 LTU 11 SRCGRP 1 ALARMNO-LTU 0
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
19 | AVAILABLE 0| | AVAILABLE | |
25 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
31 | AVAILABLE 0| | AVAILABLE | |
37 | Q2324-X500 STMI4 1 A 0| | Q2324-X500 | 1 -G1 - | READY
+--------------------------------+-+------------+------------+------------
| IP ADDRESS : 144.111. 68. 55 B-CHANNELS : 10 BCHLCNT : 10
| BLOCK NO : 3 PRERESERVED LINES ASSIGNED : NO
| 1. FUNCT : SIP 120 LINES B-CHANNELS : 10 BCHLCNT : 10
+--------------------------------+-+------------+------------+------------
43 | AVAILABLE 0| | AVAILABLE | |
49 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -20 - | READY
55 | AVAILABLE 0| | AVAILABLE | |
61 | AVAILABLE 0| | AVAILABLE | |
67 | AVAILABLE 0| | AVAILABLE | |
73 | Q2266-X LTUCA 0| | Q2266-X | 1 -13 - | READY
79 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -09 - | READY
85 | AVAILABLE 0| | AVAILABLE | |
91 | AVAILABLE 0| | AVAILABLE | |
97 | AVAILABLE 0| | AVAILABLE | |
103 | Q2193-X200 SLC24 A 0| | Q2193-X200 | 1 -20 - | READY
109 | AVAILABLE 0| | AVAILABLE | |
115 | AVAILABLE 0| | AVAILABLE | |
121 | AVAILABLE 0| | AVAILABLE | |
LTG 1 LTU 12 SRCGRP 1 ALARMNO-LTU 0
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
| | | |S|H|AL-| | | |
| ASSIGNED | MODULE |FCT|E|W|ARM| | INSERTED | HW- | MODULE
PEN | MODULE | TYPE |ID |C|Y|NO | | MODULE |STATE INFO | STATUS
-----+-----------+--------+---+-+-+---+-+------------+------------+------------
19 | AVAILABLE 0| | AVAILABLE | |
25 | AVAILABLE 0| | AVAILABLE | |
31 | AVAILABLE 0| | AVAILABLE | |
37 | Q2324-X500 STMI4 1 A 0| | Q2324-X500 | 1 -11 - | READY
+--------------------------------+-+------------+------------+------------
| IP ADDRESS : 144.111. 57.131 B-CHANNELS : 60 BCHLCNT : 60
| BLOCK NO : 1 PRERESERVED LINES ASSIGNED : NO
| 1. FUNCT : HG3530 240 LINES B-CHANNELS : 60 BCHLCNT : 60
+--------------------------------+-+------------+------------+------------
43 | AVAILABLE 0| | AVAILABLE | |
49 | AVAILABLE 0| | AVAILABLE | |
55 | AVAILABLE 0| | AVAILABLE | |
61 | Q2168-X SLMO24 1 A 0| | Q2168-X | 1 -11 - | READY
67 | Q2168-X SLMO24 1 A 0| | Q2168-X | 1 -11 - | READY
73 | Q2266-X LTUCA 0| | Q2266-X | 1 -14 - | READY
79 | AVAILABLE 0| | AVAILABLE | |
85 | AVAILABLE 0| | AVAILABLE | |
91 | AVAILABLE 0| | AVAILABLE | |
97 | AVAILABLE 0| | AVAILABLE | |
103 | Q2196-X DIU-N2 2 A 0| | Q2196-X | 1 -07 - | READY
109 | AVAILABLE 0| | AVAILABLE | |
115 | AVAILABLE 0| | AVAILABLE | |
121 | AVAILABLE 0| | AVAILABLE | |
+----+----+---------------------------+-+------------+------------+--------+
| NO SECURITY STATUS AVAILABLE, SINCE FEATURE SPE IS NOT ACTIVATED |
+---------+----------------------------------------------------------------+
AMO-BCSU -111 BOARD CONFIGURATION, SWITCHING UNIT
DISPLAY COMPLETED;
Hi,
The routing would need to be looked at if you are dialling out over Analogue lines and ISDN.
Does your carrier provide a 'clear down signal' after a call is hung up? - if not then those analogue lines could be locking up.
However a few other things could be done in the meantime.
To see the amount of calls going out/coming in
To turn on
DIS-ZAUSL:,Y;
To See the amount of calls:
DIS-ZAUSL;
Add that in to CRON - Every night at midnight the counters are cleared
ADD-CRON:7,P,0,0,*,*,*,"DIS-ZAUSL:,Y;";
T-DIMSU;
H500: AMO DIMSU STARTED
H01: CC: 78 % OF THE TOTAL STATIC MEMORY AREAS AND 72 % OF THE
TOTAL DYNAMIC MEMORY AREAS RESERVED FOR THE FLEXAMA ARE USED.
H01: LTG: 68 % OF THE TOTAL STATIC MEMORY AREAS AND 55 % OF THE
TOTAL DYNAMIC MEMORY AREAS RESERVED FOR THE FLEXAMA ARE USED.
AMO-DIMSU-111 DIMENSIONING OF FEATURES, SWITCHING UNIT
TEST COMPLETED;
I believe we have quite a lot of unused trunk group in there.
I previously overheard that there is an "ID-4" signaling error or tag coming from the external line provider... I duno what it means.
Now my primary concern is what the system does during a restart that could temporarily resolve the congestion for 2 days or so. What memory does it clear? I would like to re-submit the "clear memory" command, if any, on a regular basis so I would not be experiencing the congestion problem.
Just have a look at
DIS-LDAT;
to see if that error shows up.
Any signalling error from a carrier will result in circuits not clearing down properly.
Can you also do a STA-HISTA:SEARCH;
and see if any errors are there that are relevant to the trunks not clearing, like that ID-4 error you mention.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.