Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

COT Trunk to COT trunk transfer

Status
Not open for further replies.

motox2

Programmer
Jun 21, 2007
426
GY
Hello everybody, after scouring through tek-tips and reading over everything i could find in regards to the type of transfer im looking to do, i still havnt found anything that works. Apparently COT analog incoming trunk to COT analog outgoing trunk is kind of pain to configure. The place im working on has no DID, so they are using their COTs for everything. So when a call comes in across the COT, the user from the console (2250), attempts to transfer the call, but then it just disconnects moments later. However incoming calls across the COT can transfer to internal extensions with no problem. Trying to send the call back out another COT is where the issue is. Any help would be great. Thanks
 
let me add that calls that originate internally can transfer out across the COT's with no problem. the issue is calls that come in on a COT, and then try to go back out on a COT.
 
Make sure that any RARTS and TBARS aren't set in LD 56. It's rare to have this set up, but it can exist.

Against your COT route, check that you have TRMB = YES. You might want to consider have more than one COT route with a couple of COT members in it and give them a different access code to see if this allows outgoing access OK.

Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer

Very advance high level knowledge on the Linux BCM phone system.

Website
 
Check this also

LD 15 REQ: CHG
TYPE: NET_DATA
DITI = YES
EXTT = YES
FTOP = FTLY
 
Also check your trunks and route for Disconnect Supervision
 
An unsupervised trunk cannot be transferred to anorher unsupervised trunk. Allowing it to happen would result in two trunks which cannot be disconnected.
 
hi KCFLHRC, I noticed you mentioned.....
LD 15 REQ: CHG
TYPE: NET_DATA
DITI = YES
EXTT = YES
FTOP = FTLY

My FTOP setting is FRES. Would this be the cause of the transfer issue? I read in previous posts that FRES (fully restricted) was the correct setting, but at this point I guess it can't hurt to test it out with FTLY.
 
FRES is Fully Restricted and would cause the issue
 
Hi moxtox2,
Was your problem fixed?
I have same issue with you - COT Trunk to Trunk transfer. Follow all the suggestion but still not work
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top