[net.dcom] call -foward and -transfer behavior

hes@ecsvax.UUCP (Henry Schaffer) (05/10/86)

<>The Northern-Telecom DL100 at UCLA has both call-fowarding and 
call-transfer, and dgc@LOCUS.UCLA.EDU had set his office phone to
transfer when a departmental secretary transfered a call to his
office phone.  When she was on the line everything worked, but 
when she hung up to complete the transfer dgc and the calling
party were disconnected.  dgc was told that call-transfer
required that at least one of the parties be on a line local to
the exchange.
  dgc asked about whether this was a bug - or was it required by
regulation.  I asked our knowledgeable telecommunications 
director, and she sen me the following (more or less):

  "There are two different features, call foward and call transfer.  
For call transfer a party on the system *is* needed, but not for
call foward.  If call foward had been allowed to operate, the call
would have gone on through to him at home without the transfer
problem which resulted when his secretary was involved.  This is
the way the switch (most switches in fact) operate(s) and is not
a function of any regulation!"

--henry schaffer  n c state univ    ...mcnc!ecsvax!hes