External Transfers

[LBGeist]

Hi all,

I'm having issues with my Option 11 not being able to transfer externally. I can Forward externally, but when someone tries to transfer the call, one of 2 things happens, either the call gets a fast busy or you cannot press the transfer key a second time to complete the connection. . .

Has anyone seen this before and if so any suggestions? I know there's security things to deal with, but I just can't figure out why it won't work. TGAR and TARG aren't the issue, Class of SErvice doesn't appear to be the issue, i've checked all the settings in the Feature guides and they seem to be correct. . . but still the call won't transfer.

 

[johnpoole]

do you have transfer allowed on the trunks? might be a network issue.. when you don't get a chance to complete the transfer, does that change when the xfer to party answers?

john poole
bellsouth business
columbia,sc

 

[Firebird Scrambler]

Check in the RDB for "TRMB". If the same route is used for incoming & outgoing, then it must be set as "YES". Also check in LD 56 for RART & TBARS.

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.orange.co.uk/firebird_scrambler

Useful Nortel forum at

http://www.tspforum.com

If it's working, then leave it alone!.

 

[LBGeist]

TRMB is set to yes. There are no RART or TBAR tables. I have checked the trunks but don't see anything that would specify transfer or not, where would I see that?

Is it possible that the NCOS is the issue. My trunks have it set at 7 but my phoneset has an NCOS of 5. Now I will say the trunks on my LD circuit are set to NCOS 0 and it doesn't work there either.

I've tried to stare and compare with a site that it DOES work at and I can't see anything. Anyplace else I should be looking?

 

[johnpoole]

make sure the provider and the trunks accept a transfer.. the ncos 0 on the ld can block cfxa from that trunk at times but transfer follows a unique set of rules

john poole
bellsouth business
columbia,sc

 

[TAnselm]

It probably in ld 56. Look in your documentation for "Trunk Barring" where it talks about access restriction tables. Default is for consultation only. In other words you can conference to a restricted route or use the transfer key on a consultation basis, but as soon as you hang up the call is dropped.

 

[Eitsalo]

Is DID number assigned to the set that you're trying to transfer from. If so you may want to make sure that the RDB DID route have NCOS = 4.

 

[acewarlock]

Ncos =4 doesn't mean a thing. What FRL is the NCOS.

I could have an NCOS =0 and a FRL of 7.

You need to print out the NCTL's in LD 87 to see what NCOS/FRL conbo'you have.

 

[johnpoole]

it should not mater after the 9 ncos of the trunk is relaced with ncos of the station.. opt cff still takes control.. there is a cdb that allows or denies forward to an acod.. that may be blocking.. some of nortels cdb entries effect more then just the stated reason..

your right about ld 56, with default data i could conf to external, if i left the 2 way dies... remove that rest in 56 and i could leave the call... conf external call, conf ext call and hang up... sounds like a transfer to external...

john poole
bellsouth business
columbia,sc

 

[lexer]

Put en LD 15 FTOP --> FTLY and in the stations CLS FTTU