Outbound call transfer off net

[hcphere]

We have a G3r v.11. We are doing an outbound campaign, and need to transfer the call we make to a toll free number. we have 3 trunks, and all outbound calls go out on TR3. The transfers off net work fine (with the proper Cor/Cos) for inbound calls that need to be transferred. I have tried all of the following and it is still not working for outbound to outbound.
Can anybody tell what I am missing?

1. sys features trk-trk transfer is restricted.
2. set up vdn/vector with route to command to the toll free number. VDN was set with the same cor we use to enable other inbound to outbound route-to commands to work.
3. set up ch cover remote coverage path to the tollfree for a station that has the same cor that allows other stations to transfer incoming calls out. COS has "n" in "restrict call fwd-off net", and "y" in "trk-to-trk transfer override"
4. Changed the ars for toll free numbers to go out on trunk 2 instead of 3. The originating outbound goes out tr 3, and then the transfer went out tr2 but it still wouldn't work.

5.I even changed the trk-trk transfer in sys features to all, and tried it and still couldn't make the transfer work.

What am I missing???

Thanks,
Patricia

 

[RGarcia87]

I have the same problem. Check out this thread..

http://www.tek-tips.com/viewthread.cfm?qid=1012074&page=6

 

[telcomwork]

Did anyone ever get this to work? If so what did you do?

Thanks!

 

[hcphere]

I have not gotten it to work.

Avaya is in the process of building a patch for our switch right now because whenever we are service observing a line that gets transferred off net (it was originally an inbound call-so we can transfer it), the call gets disconnected.

Maybe it will effect the outbound issue???

 

[eclemente]

Have you tried changing the disconnect supervision, in your trunk form, to y and y instead of y and n?

Edgar Clemente

 

[4merAvaya]

At least one of the trunk groups must be digital (T1 or PRI). The outbound trunk must have Disconnect Supervision Out set to 'y'.

Kevin

 

[alberton]

Is that parch only for your swith or is global parch?
I got the same problem with the service observing and the system has the Disconnect Supervision to y in both ways.
I think it is R.11 bug.

 

[hcphere]

I will ask them when they get around to installing it!!!!

 

[alberton]

You know the Definity R.11 what is the corresponding version as Comunication Manager. I think it is 1.1 but not sure.
Thanks

 

[alberton]

hcphere, Do you know what is the parch version? I think it should be 03.1.531.0 but can you confirm it?
Thanks

 

[hcphere]

They haven't installed it yet, but have escalated it to Tier 4 (whatever that means!)

I will call them today to get a status.

 

[alberton]

When it will be installed the software system will change from R11.03.0.526.5 (I suppose it is the current software system)to other version. What I am interested is in this new version.
Regards.