Ok lets look at the original post....
Quote:
| the procedure works good from any phone within the office with an immediate release, but my problem is that the operator cannot release the call right away from the console. |
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.