Analog GSM GW ACCESS not released when routed to IAAtendant

[mkrustev]

I have 2 Analog GSM GWs.

Each of them has 2 analog interfaces, connected to APA8 board which is at position 7 in shelf 2.

I also have Integrated Automated Attendant.

The gates are in trunk group 81 and 82 respectively and in the CDT there is routing to the IAA.

I have tested all and it works fine.

Currently I have problem. The first access of gate 82 is busy all the time. Nobody is using it for conversation, but it is busy.
>trkstat -r 82 outputs the following all the time:

Code: Select all

+==============================================================================+
|           T R U N K    S T A T E     Trunk group number : 82                 |
|                                      Trunk group name   : MTEL2              |
|                                      Number of Trunks   : 2                  |
+------------------------------------------------------------------------------+
|   Index :     1    2                                                         |
|    Neqt  :   455  456                                                        |
|   State :     B    F                                                         |
+------------------------------------------------------------------------------+
|  F:  Free   |    B: Busy   |   Ct: busy Comp trunk   |  Cl: busy Comp link   |
|  WB: Busy Without B Channel|   Cr: busy Comp trunk for RLIO inter-ACT link   |
|  WBD: Data Transparency without chan.| WBM: Modem transparency without chan. |
|  D: Data Transparency      |   M: Modem transparency                         |
+------------------------------------------------------------------------------+

I checked with the command listincall and it returns the following:

Code: Select all

(1)xa000001> listincall 2 7 

Fri Oct 30 12:37:42 EET 2009

 +-----------------------------------------------------------------------------+
 |  :  :  :   |     |            |           |ST|         partner one info     |
 | C:cp:ac:ter| neqt| typ term   | dir_nb    |AT|------------------------------|
 |  :  :  :   |     |            |           |US| link name  | neqt  | dir nb  |
 |-----------------------------------------------------------------------------|
 | 2: 7: 0:  2| 0455|      JONCT |           |IS|         RCL|    541|         |
 +-----------------------------------------------------------------------------+
 +-----------------------------------------------------------------------------+
 |         Nombre total de terminaux en com hors service :        0            |
 |         Nombre total de terminaux en com en service   :        1            |
 +-----------------------------------------------------------------------------+


(1)xa000001> listincall 2 27

Fri Oct 30 12:38:14 EET 2009

 |Coupler:  2 27 Logic type: CPL_GPA   Board: GPA FI State: IN SERVICE     |
 +-----------------------------------------------------------------------------+
 |  :  :  :   |     |            |           |ST|         partner one info     |
 | C:cp:ac:ter| neqt| typ term   | dir_nb    |AT|------------------------------|
 |  :  :  :   |     |            |           |US| link name  | neqt  | dir nb  |
 |-----------------------------------------------------------------------------|
 | 2:27: 0:  1| 0494|    VG_CHAN |           |IS|    MOI     |    494|         |
 | 2:27: 0: 64| 0541|   DSP_CHAN |           |IS|         RCL|    455|         |
 +-----------------------------------------------------------------------------+
 +-----------------------------------------------------------------------------+
 |         Nombre total de terminaux en com hors service :        0            |
 |         Nombre total de terminaux en com en service   :        2            |
 +-----------------------------------------------------------------------------+

As a conclusion I thin that what might happen is one of the following:
1. When there is external call to some GSM GW and it routes to the IAA, the call is not released after the external party hangs up.
2. Someone has forwarded his phone to his GSM and again the call is not released after the external party hangsup.

I believe it is most likely my first guess, for IAA is all about voiceguides, which I guess 541 is - a neqt number of voiceguide.


Have someone had such issues? What does MOI and RCL mean under the link name column?

[mkrustev]

I also tried vgemis command a couple of times with interval of a second between each try:

Code: Select all

(1)xa000001> vgemis

Fri Oct 30 12:55:05 EET 2009


+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name      | cr | cpl| term| neqt |lng|     listeners neqt      |
+------+-----------------+----+----+-----+------+---+-------------------------+
|  702 | VG_MULT_702     |  2 | 27 |   1 |  494 | 1 |  454                    |
+------+-----------------+----+----+-----+------+---+-------------------------+
|  702 | VG_MULT_702     |  2 | 27 |   3 |  496 | 1 |  455                    |
+------+-----------------+----+----+-----+------+---+-------------------------+

(1)xa000001>




(1)xa000001> vgemis

Fri Oct 30 12:55:39 EET 2009


+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name      | cr | cpl| term| neqt |lng|     listeners neqt      |
+------+-----------------+----+----+-----+------+---+-------------------------+
|                   there  is   no   message   broadcasted                    |
+-----------------------------------------------------------------------------+


(1)xa000001> vgemis

Fri Oct 30 12:56:15 EET 2009


+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name      | cr | cpl| term| neqt |lng|     listeners neqt      |
+------+-----------------+----+----+-----+------+---+-------------------------+
|  702 | VG_MULT_702     |  2 | 27 |   1 |  494 | 1 |  454                    |
+------+-----------------+----+----+-----+------+---+-------------------------+
|  702 | VG_MULT_702     |  2 | 27 |   2 |  495 | 1 |  455                    |
+------+-----------------+----+----+-----+------+---+-------------------------+


 

(1)xa000001> vgemis

Fri Oct 30 12:56:51 EET 2009


+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name      | cr | cpl| term| neqt |lng|     listeners neqt      |
+------+-----------------+----+----+-----+------+---+-------------------------+
|                   there  is   no   message   broadcasted                    |
+-----------------------------------------------------------------------------+





(1)xa000001> vgemis

Fri Oct 30 12:57:16 EET 2009


+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name      | cr | cpl| term| neqt |lng|     listeners neqt      |
+------+-----------------+----+----+-----+------+---+-------------------------+
|  702 | VG_MULT_702     |  2 | 27 |   2 |  495 | 1 |  455                    |
+------+-----------------+----+----+-----+------+---+-------------------------+






(1)xa000001> vgemis

Fri Oct 30 12:57:33 EET 2009


+------+-----------------+----+----+-----+------+---+-------------------------+
| guid | guide name      | cr | cpl| term| neqt |lng|     listeners neqt      |
+------+-----------------+----+----+-----+------+---+-------------------------+
|                   there  is   no   message   broadcasted                    |
+-----------------------------------------------------------------------------+




...  And if I continue it keeps on showing randomly that eqt 455 is connected to voiceguide 702

So in general I believe that this issue is due to the incoming calls from the GSM GW being routed to the IAA and the inability to stop the conversation and disconnect.

[tot3nkopf]

Try to use polarity reversal, busy tone detection or timed disconnection for these trunks in order to avoid these kind of problems.

[mkrustev]

Thanks a lot! I will check out these topics but I am not quite familiar with them.
I will be very thankful for any hints and details:).