Trunks staying out of service

[tsturg]

Hi All

We have a new office in Dublin set up as an LSP gateway off a S8710 (CM3.1.4) in the UK. Over the past few weeks, it has been reported to us that the local ISDN30 trunk is out of service. When investigating this, the trunk shows as out of service far end and in the error logs, we get an error type 769 (and this actually corresponds to a short network outage)on the WAN.

To resolve the problem, we just reset the media module in the G350 gateway and the trunk come back into service. The question is, why do the trunks not come back into service themselves? There is a WAN outage that is not long enough to put the location into LSP mode, but the trunks go out of service and stay out of service. Any ideas?

 

[colby007]

Check to see if the syncronization source is set correctly in the G350. Log into the gateway and type show sync timing. See if the syncronzation is set to the local DS1 module.

 

[tsturg]

The G350 sync source is the Primary circuit as per below with switching enabled.

Gateway-019(super)# show sync timing

SOURCE MM STATUS FAILURE
--------- ------------------- ----------------------- ---------------
Primary v5 Active None
Secondary Not Configured
Local v0 Standby None

Active Source: v5 Sync Source Switching: Enabled

Done!
Gateway-019(super)#

 

[inerguard]

Provide a screen print of the trunk set up, pages 1 - 3 and we'll check the setup for you.


[Started on Version 3 software 15 years a go]

 

[tsturg]

Here you go.

change trunk-group 19 Page 1 of 21
TRUNK GROUP

Group Number: 19 Group Type: isdn CDR Reports: y
Group Name: Gateway 19 COR: 59 TN: 19 TAC: 819
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4

Group Type: isdn

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: 13
Incoming Calling Number - Delete: Insert: Format: pub-unk
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n

TRUNK FEATURES
ACA Assignment? n Measured: both Wideband Support? n
Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: n Send Calling Number: n
Used for DCS? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: public
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? n
Send UUI IE? y
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

Apply Local Ringback? n US NI Delayed Calling Name Update? n

Network (Japan) Needs Connect Before Disconnect? n

QSIG TRUNK GROUP OPTIONS








SBS? n


TRUNK GROUP
Administered Members (min/max): 1/20
GROUP MEMBER ASSIGNMENTS Total Administered Members: 20

Port Code Sfx Name Night Sig Grp
1: 019V501 MM710 B 19
2: 019V502 MM710 B 19
3: 019V503 MM710 B 19
4: 019V504 MM710 B 19
5: 019V505 MM710 B 19
6: 019V506 MM710 B 19
7: 019V507 MM710 B 19
8: 019V508 MM710 B 19
9: 019V509 MM710 B 19
10: 019V510 MM710 B 19
11: 019V511 MM710 B 19
12: 019V512 MM710 B 19
13: 019V513 MM710 B 19
14: 019V514 MM710 B 19
15: 019V515 MM710 B 19
16: 019V517 MM710 B 19
17: 019V518 MM710 B 19
18: 019V519 MM710 B 19
19: 019V520 MM710 B 19
20: 019V521 MM710 B 19
21:
22:
23:
24:

 

[inerguard]

The only difference I can find is: -

Dial access set to n rather than y
Format I have blank

Disconnect Supervision Out I have Y

Send Calling Name and Number I have as Y

None of these have any effect on the trunk coming into service.

What it sounds like is the Telco has a setting that takes the circuit out of service if it sees alarms on all channels for a length of time. Have a chat to your Telco around this area. They should let the circuit alarm for long enough before marking it as OOS.




[Started on Version 3 software 15 years a go]

 

[tsturg]

This was logged out to Avaya and it looks like they have this issue fixed with a patch:

Description:

After a WAN outage, several media gateways are registered with LSP. After WAN connections re-establish, and media gateways register back to the primary media server, ISDN-PRI trunk group's status is still out-of-service. A manual reset on the ISDN-DS1 board is required to have the ISDN-PRI service status back in-service. Temporary Solution: Perform busyout or reset or release on the affected ISDN-DS1 board from Communication Manager (CM) platform: System Administration Terminal (SAT).



It is fixed in MRdefsw070259 and is included in the latest incremental build of the CM service pack #2: 16570