mkabbas

Its very interesting question
Were the system location? Country
Yes It’s related to trunk to trunk connection did u check that programming trunk to trunk connection?
Any how just change this CMD 3505 > route >1
But make shore after call end u can access that same Trunk if its not
Please check is there line reversal in that trunk? If its not there system will not release that Trunk line automatically line reversal is must shut for this feature

mkabbas

Its very interesting question
Were the system location? Country
Yes It’s related to trunk to trunk connection did u check that programming trunk to trunk connection?
Any how just change this CMD 3505 > route >1
But make shore after call end u can access that same Trunk if its not
Please check is there line reversal in that trunk? If its not there system will not release that Trunk line automatically line reversal is must shut for this feature

R4+Z

Ok lets look at the original post....

So we can say once and for all that trunk to trunk is enabled and works. It even works from the console but you can't do a "Dirty" transfer (transfer before answer).

commands 3504, 3505 & 08>206 have been suggested so lets look at what they cover.

3505 = Release signal from distant office for outgoing connection or incoming connection.

Now as this is a release signal it comes when one of the parties terminates the call so has nothing whatever to do with setting the call up in the first place. If no release signal arrives you can still set up trunk to trunk calls. They just won't clear down and sooner or later you will have to manually release the circuits. This pretty much rules out this command in these circumstances as the original poster, Bill, wasn't complaining of locked up trunks.

3504 = Answer signal from distant office for outgoing connection

Now at first look this seems reasonable but the problem is that as stated in the original post "it works good from any phone within the office with an immediate release" and the operator can transfer the call if she waits for an answer. The fact that she can transfer on answer implies that something is changing when the called party answers. You don't think that could be an answer signal do you?

Finally 08>206 = Trunk to trunk transfer by an attendant before answer on the outgoing trunk.

There are two options available or not available. Now since this command if set to available allows the operator to transfer before a release signal is recieved it kind of negates the consideration of CMD 3504.

I stand to be corrected but the logic seems pretty good to me that 08>206 is the culprit. It would be nice if the original poster could tell us what the cure eventually was.

Over to you Bill.

whbaxter

Sorry - been very busy. I appreciate all you guys are doing. 08>206 is set to 0 (Available). I changed 08>206 to 1 (Not available) and was able to do a dirty transer. However, the next attempt to transer a call (no matter where it is going) after a transfer to a virtual extension always produces a busy signal. The operator must then hit cancel and re-transfer that call. Hence, I change 08>206 back to 0, and I am right back where I started.....

AbuSuhail

whbaxter, you wrote:
(....the next attempt to transer a call (no matter where it is going) after a transfer to a virtual extension always produces a busy signal. The operator must then hit cancel and re-transfer that call. Hence, I change 08>206 back to 0, and I am right back where I started.....)
Did you verify that the first call was relaesed.. I guess it was not and that is why the operator gets a busy signal....and you have onll to force release the connection either by CM EB0 or extract the right card ..
Again I insist to check for polarity reversal on your CO lines.
Good LUCK