Trunk to trunk transfer

[Schlickieboy]

Can a NON- lsp gateway do a trunk to trunk transfer. I have a 350 non- lsp gateway that canot do a TTT transfer. Phone are set with the proper COS. System Features are "restricted" switch is a 5.0. What am I missing.

 

[Behind8ball]

What do you see when you trace the call..?

 

[steeltown89]

Its probably your answer supervision on your trunk you are dialing out on. Out is probably set to no on the trunk form. Keep in mind this will allow users to transfer calls to where ever their COR allows and ties up 2 trunk ports. One on each trunk.

 

[AvayaTier3]

Disconnect Supervision - In? y  Out? y

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

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com