can't xfer calls from G3siV6 to Cisco

[Phoneguy15]

Have a customer that is running a Definity R6 system that is networked via PRI to a Cisco system.
The definity does not have UDP enabled on the system, so they are using phantom extensions that are remote forwarded to stations on the Cisco system. The remote forward dials the TAC and the extension number on the Cisco side to send the calls.
The problem is when someone places an outbound call from the Definity and then tries to transfer that call to a Cisco station, the transfer is not allowed to complete.
However, if a someone calls INTO the Definity and they try to transfer to the Cisco it works just fine.
I may be wrong, but I believe that it has something to do with COR and/or FRL levels. I just have not been able to isolate it.
I REALLY wish there was List Trace Station on the V6!


Thanks in advance for your help

Todd

 

[DontDeleteMeAgain]

make sure trunk to trunk transfer is turned on

 

[Phoneguy15]

trunk to trunk transfer is on in System Parameters and it is enabled in COS for the stations attempting it.

 

[Phoneguy15]

Anybody have any other ideas?

 

[2wire]

Make sure you have the extensions in the Cisco identified in the Avaya UDP (uniform-dialplan). At one of my locations we had it going to node 999 which our route-pattern took that and went to the trunk connected to Cisco.

I hope this makes sense and helps.

Good Luck,

2wire

 

[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

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[Phoneguy15]

@ 2wire
UDP is not being used on the Definity. They are using remote coverage to go over to the Cisco.

@ AvayaTier3,
The disconnect supervision is set to yes (in and out)for all trunk groups involved in the transfer attempts. the strange part (to me, at least) is the fact that someone can call into the definity and be xfered just fine. But if they call out of the definity and then try to xfer that call it is not allowed.

 

[Phoneguy15]

Any more ideas anyone?