Remote Call Forward

[guybuzz]

Our Merlin Legend 3.1 customer has a Remote Call Forward problem. When an extension is set to Remote Call Forward, internal, ext-to-ext calls are successfully forwarded. When the customer transfers a call to the forwarded extension, the call is not forwarded. It simply rings on the local extension. Has anyone encountered and remedied this problem? Barring that, does a later version offer this feature successfully?

 

[Pepperz]

Set the Trunk transfer options to "enabled" for the extension in question.

Pepperz at newper dot net

 

[guybuzz]

Thanks so much for the fast reply. Unfortunately, that's a step we already took: trunk-to-trunk transfering is already enabled for that extension! I'd welcome any other thoughts!!

 

[Pepperz]

Well, then I don't know. It may be an issue with that particular release, but it works on the later LEgends and Magix releases.

Pepperz at newper dot net

 

[TouchToneTommy]

Check that the loop start reliable disconnect is set to ON

 

[Pepperz]

Yep, the LS Disconnect has always been there as a changup.

Pepperz at newper dot net

 

[fonetek]

Hello,
Im the technician that is doing the work.
Ive done this a million times on newer switches.
remote call fwd is on, Ls disc. is yes, trk to trk is on,
all stations are unrestricted, ARS restrict is 3.
Anything I missed?

FRANK C
CONSOLIDATED TECHNOLOGIES
AVAYA GOLD BUSINESS PARTNER
ACA CERTIFIED

 

[Pepperz]

One other little oolie, I was told by Lucent one day that only calls that arrive on an SA-Ring key could be forwarded offsite. Try setting all the SA keys to SA ring and then try again.

Pepperz at newper dot net

 

[merlinman]

Well, not exactly, HOWEVER the CALL MUST RING at the EXTENSION to be eligible to be forwarded.

IF it don't ring, it don't go!

 

[Pepperz]

Yep, EXACTLY. That's what I was told. When I changed it, the RCF happened.

Pepperz at newper dot net