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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Openscape 4k - problem with fwd

Namber

Technical User
Jul 29, 2021
6
IT
I'm doing some tests with the forward on openscape 4k v22

ADD-ACTDA:STN,1234,FWD,STATIONV,CFU,GEN,VCE,0339xxxxx;

(in ZAND the field EXCOCO is set to YES)

if an external or internal calls the extension 1234, the FWD works correctly and the call arrive to the 339xxxxx.

if a colleague in office receive an external call and he tries to pass to the extension 1234, the call arrives on the 339xxxxx number but the communication is only with the person forwarding the call and if he hangs up, the original call returns.

I hope I explained myself clearly.
 
You don't have a problem with a forward, you have a problem with a transfer.

There are lots of things that can cause this but two commons reasons are TTT (trunk to trunk transfer) not in the COS of the trunk/phone, and mismatched node numbers where the incoming node number (TDCSU), station number node number (KNDEF), system node number (ZAND ALLDATA) and outgoing node number (from dialled RICHT) are mismatched. Example, some might be single level NNO 100. Others could be triple level 1-1-100. They all need to to be the same level, doesn't usually matter if all single or triple, but they must be the same.

Or it could be you are transferring the outgoing call to the same trunk as the incoming, in which case setting DESTNO=0 on that trunk can help (turn off loop check).
 

Part and Inventory Search

Sponsor

Back
Top