ISDN Trunk member error

[telecomadmin12]

I have three tie ISDN-PRI trunks, all of which have a non-working B-channel on port 1. All other channels are good. Strange to me. This is a list trace with a failed call.

18:09:42 dial 5314 route:UDP|AAR
18:09:42 term trunk-group 8 cid 0x2d46
18:09:42 dial 5314 route:UDP|AAR
18:09:42 route-pattern 11 preference 1 cid 0x2d46
18:09:42 seize trunk-group 8 member 1 cid 0x2d46
18:09:42 Calling Number & Name 5318 Johann Mobil
18:09:42 denial event 1175: ISDN channel unacceptable D1=0x830007 D2=0x6
18:09:42 idle trunk-group 8 member 1 cid 0x2d46

TN464HP, CM3.0

 

[AvayaTier3]

failed call shows denial for 0x830007 which is trunk-group 7



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[telecomadmin12]

Trunk Group 7 is the trunk group the call came in (also an ISDN trunk) to an automated attendant and was forwarded to trunk group 8. Don't understand why I am getting an error on trunk group 7 then. Below is a similar example. However the call came in on trunk group 6, which is an IP trunk.

list trace tac 789 Page 1

LIST TRACE

time data

10:33:46 dial 5202 route:UDP|AAR
10:33:46 term trunk-group 8 cid 0x3316
10:33:46 dial 5202 route:UDP|AAR
10:33:46 route-pattern 11 preference 1 cid 0x3316
10:33:46 seize trunk-group 8 member 1 cid 0x3316
10:33:46 Calling Number & Name 5313 Johann Remote
10:33:46 denial event 1175: ISDN channel unacceptable D1=0x830006 D2=0x6
10:33:46 idle trunk-group 8 member 1 cid 0x3316

 

[AvayaTier3]

Are you setup to allow trunk to trunk transfer?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AvayaTier3]

Make sure you have port 1 not busied on each t1 circuit
what does Command: status trunk 8/1
show you?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[telecomadmin12]

display system-parameters features Page 1 of 16
FEATURE-RELATED SYSTEM PARAMETERS
Self Station Display Enabled? n
Trunk-to-Trunk Transfer: all

 

[telecomadmin12]

status trunk 8

TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports
Busy

0008/001 03A1601 in-service/idle no

 

[AvayaTier3]

Do you have Disconnect Supervision - In? y Out? y set on all trunk-groups?

In the Disconnect Supervision-In field, perform one of the following actions:

Type y if you want:

Trunk-to-trunk transfers that involve this trunk group

If you want trunk-to-trunk transfer in your system, you must also set the
Transfer field on the Feature-Related System Parameters screen to y.

To make the far end server or switch responsible for releasing the trunk, when
the far end server sends a release signal as the calling party releases an
incoming call.

To enhance Network Call Redirection

Type n if:

- You do not want trunk-to-trunk transfers that involve this trunk group.

- The far end server does not provide a release signal.

- The hardware in your system cannot recognize a release signal.

- You prefer to use timers for disconnect supervision on incoming calls.

The system displays the Disconnect Supervision-In field if the Direction field
is set to incoming or two-way.

If the Direction field is set to outgoing, the system sets the Disconnect
Supervision-In field to n.

The value in the Disconnect Supervision-In field determines whether the system
receives disconnect supervision for incoming calls over this trunk group.

CAUTION: The system does not allow trunk-to-trunk transfers unless at least one
party on the call can provide disconnect supervision. If you administer the
Disconnect Supervision-In field incorrectly, you can cause trunks to become
unusable until the problem is detected and the trunks are reset.

For example, if a user connects two trunks through the use of the Conference
feature or the Transfer feature, and a far end Avaya S8XXX server on the
resulting connection does not provide disconnect supervision, the trunks are not
released. The trunks are not released because the system cannot detect the end
of the call.

Usually, the COs in the United States provide disconnect supervision for
incoming calls, but do not provide disconnect supervision for outgoing calls.

Public networks in most other countries do not provide disconnect supervision
for incoming calls or outgoing calls. Talk with your network services provider
to determine if the public networks in your area provide disconnect supervision.

If a trunk without disconnect supervision goes to Night Service, the system
drops the trunk after a period of time to avoid locking up the trunk. The call
is not routed to the DID-LDN night extension.

When a user places a trunk call, Service Observing starts when the user finishes
dialing the call. For calls on central office (CO) trunks, the system considers
dialing to be complete when the answer supervision is returned, or when the
answer supervision timeout occurs. The system denies any attempt to use Service
Observing over trunks that do not have disconnect supervision.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[telecomadmin12]

Thanks for the very informative description.
On all trunks I have:
Disconnect Supervision - In? y Out? y

 

[AvayaTier3]

Need to work with your provider to troubleshoot.
May want to use MST trace on d-channel in CM.

You should make sure you have the whole t-1 available and not having circuit
run through a mux or csu/dsu defining channel 1 for data.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[telecomadmin12]

It is a tie trunk connecting two PBXs.
I am using a CSU 120A4 and D-channel is on port 24. The others should all be Bearer.

 

[kyle555]

Have you tried resetting the boards or checked for slips? I've only dealt with 1 channel off on a PRI once as a provider issue I had to gripe quite a bit to get diagnosed.
Also, side note, I've seen something similar when someone was a touch sloppy and omitted to define every port on the card in the trunk group form. Every call the provider selected to send on that channel inward got fast busy.

 

[AvayaTier3]

b-channels 1 to 23 of one trunk-group in switch A should be mapped to switch B b-channels 1 to 23
of one trunk-group. If trunk-groups are defined this way and you have not mapped or defined them in mux or csu/dsu separately, there is no way the CM trunk software will single out one trunk channel not to work.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]