in-service/active but connected ports are blank

[gany]

Hi,



I'm having a problem with one of my trunk. It seems that the trunk members are seized but there were no connected ports on it. This consumes all the trunk channels and will not allow me to use the trunk later. Here's the status.



status trunk 27 Page 1

TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports
Busy

0027/001 T00365 in-service/idle no
0027/002 T00366 in-service/idle no
0027/003 T00367 in-service/idle no
0027/004 T00368 in-service/idle no
0027/005 T00369 in-service/idle no
0027/006 T00370 in-service/active no
0027/007 T00371 in-service/active no
0027/008 T00372 in-service/active no
0027/009 T00373 in-service/active no
0027/010 T00374 in-service/active no
0027/011 T00375 in-service/active no
0027/012 T00376 in-service/active no
0027/013 T00377 in-service/active no
0027/014 T00378 in-service/active no
0027/015 T00379 in-service/active no
0027/016 T00380 in-service/active no
0027/017 T00381 in-service/active no
0027/018 T00382 in-service/active no
0027/019 T00383 in-service/active no
0027/020 T00384 in-service/active no
0027/021 T00385 in-service/active no
0027/022 T00386 in-service/active no
0027/023 T00387 in-service/active no
0027/024 T00388 in-service/idle no
0027/025 T00389 in-service/active no
0027/026 T00390 in-service/active no
0027/027 T00391 in-service/active no
0027/028 T00392 in-service/active no
0027/029 T00393 in-service/active no
0027/030 T00394 in-service/active no
0027/031 T00395 in-service/active no





I have included the configuration of my trunk: See below..





-------------


display trunk-group 27 Page 1 of 22
TRUNK GROUP

Group Number: 27 Group Type: isdn CDR Reports: y
Group Name: IP Trunk COR: 10 TN: 1 TAC: 333
Direction: two-way Outgoing Display? n Carrier Medium: IP
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical QSIG Value-Added? n
Digital Loss Group: 18
Incoming Calling Number - Delete: Insert: Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0


-------------

display trunk-group 27 Page 2 of 22
TRUNK FEATURES
ACA Assignment? n Measured: internal Wideband Support? n
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: y Send Calling Number: y
Used for DCS? y PBX ID: 8
Suppress # Outpulsing? n Format: public DCS Signaling: d-chan
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y
Network Call Redirection: none Hold/Unhold Notifications? y
Send UUI IE? y Modify Tandem Calling Number? n
Send UCID? y
Send Codeset 6/7 LAI IE? y



SBS? n Network (Japan) Needs Connect Before Disconnect? n



---------





Can anyone please help me on this? Thank you.

 

[Gielo]

Are you using any UDP (uniform dial plan extensions) that works across the trunk to another pabx. If this is the case and somebody phones and extension that is transfered to the adjacent pabx where that extension does not exist it will come back to the avaya and the process will start again filling up your trunk in no time as the call "ping pong" between the pabxes. To stop this you should fix the problem and also put a hop limit in the route pattern of the avaya.

Hope you come right!

 

[ewaaijenberg]

Hi,

this is a known issue. We had this also with IP Dect trunks and have loaded a patch for release CM 3.1.4