Phone Call Forwarding : 302 Moved Temporarily

[alloy]

Is there a reason why I cannot call forward from the IP Phone ?

Example:
IP Phone Ext 11 , dials Ext 12.
12 is either Aastra or Snom (both do the same) and is set to forward to external destination. (which is logical and often done - say to a mobile/cell)

Forwarding pattern matches the correct route pattern rules.

Both Aastra and snom send back to the PBX a 302 diversion :
SIP/2.0 302 Moved Temporarily
....
Contact: <sip:00xxxxxxxx@192.168.15.208;user=phone>
Diversion: <sip:44@192.168.15.44:1046;line=owejz3u6>;reason=" unconditional"

The QuodroPBX - gives and error response back to Ext 11 (cannot recall the error)

Why can this not be supported ?

[davrays]

A counter-question: why not to use the call forwarding on Quadro
We are trying to be as independant from phones and their specifics as possible. Thats why we don't encourage using neither DND nor CallForward on the phones, and we have pretty good replacement for that: both services are implemented on the PBX. So why to ignore the PBX feature and use the one on phone?

[alloy]

I understand that you have more controll by enforcing PBX only Call forwarding, but in general the call forwarding is easier for the user to implement on the Phone.
(they get visual feedback on the forwarding destination selected for example)

Perhaps you need a "Quadro Tools" application.
A windows GUI that user can enable / disable call forwarding rules via.
Could you then push an XML message to the phone "Call forward Busy : 12334324"

ie Aastra - Call Forward options
Prompts
1. All (destination)
2. Busy (destination)
3. No Answer (destination)

[davrays]

We will add the button indication first for the PBX CFWD. This will work for unconditional CFWD only however. This is done for 5.0.
In parallel we are working on XML implementation for forwarding indication, and we'll take into account your suggestion. Tough I am not sure when this work will be completed.

[alliancesoftware]

I'm trying to get this working on Yealink handsets.

The problem I have with using the *4 system is that the handset doesn't have any visual indication that forwarding is in effect. This means that users forget it's enabled and don't receive any calls to their desk phone.

Has anyone else come up with a solution for this (since forwarding from the handset isn't respected by the Quadro)?

[Harutyun]

For Yealink T28,T26 models you can auto-configure programmable buttons on the right from Quadro, and set one of the to "call forwarding". In that case you will have visual indication if forwarding is enabled or not. Pressing that button will toggle forwarding.

[KSComs]

For Yealink T28,T26 models you can auto-configure programmable buttons on the right from Quadro, and set one of the to "call forwarding". In that case you will have visual indication if forwarding is enabled or not. Pressing that button will toggle forwarding.

When using Auto Deployment and the above method for T22 handsets you will have to log in to the handset to remedy the line parameter from line 3 if you are using the line key.

Otherwise the feature that you have programmed will fail.

[lunacom]

Hrant,
Any update on this request?
I also have the same problem. I am using Snom 760

SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 192.168.10.160:5060;rport=5060;branch=z9hG4bKEPSVB US87ee371a-cf30-4a6d-8113-5b444d6c5f33
From: "Michele" <sip:616@192.168.10.160>;tag=143132859269ecc863-4d6e-4c07-9f82-67ed5e2ae2d7
To: <sip:LunInt620@192.168.10.160:5060>;tag=0kp4lu4m py
Call-ID: 22659809367934167_092abafa-e16e-4652....lunacom.local
CSeq: 153 INVITE
Contact: <sip:3351025289@192.168.10.160:5060;user=phone>
Diversion: <sip:LunInt620@192.168.10.170:1024>;reason="uncond itional"
Why can this not be supported ?
Thanks
Michele