Call Forwarding from client device to Local blocked

Hi folks,

I have a perfectly working Asterisk, AVM C2, chan_capi 1.1.5, Asterisk Addons, FreePBX on a Debian Lenny with Snom370 SIPs.

All the little features work just great.

Since I am using Snom370s I now wanted to use their F_REDIRECT function on the shortcut keys. This does a 302 redirect to the specific extension which is in my case a voicemail. My intention is to switch Voicemails for “holidays” or “out of office”. I don’t want to set this up using a timeplan.

Basically it is working, but the local redirect is being blocked and the call gets redirected into the block-cf context so that the call can not be forwarded to the voicemail. Instead it stays in the local queue and follows that dialplan.

Here’s my debug output:

[Jan 18 13:09:18] VERBOSE[8824] netsock.c: == Using SIP RTP TOS bits 184
[Jan 18 13:09:18] VERBOSE[8824] netsock.c: == Using SIP RTP CoS mark 5
[Jan 18 13:09:18] VERBOSE[8824] app_dial.c: – Called 101
[Jan 18 13:09:18] VERBOSE[8822] app_queue.c: – Local/[email protected];1 is ringing
[Jan 18 13:09:18] VERBOSE[2664] chan_sip.c: – Got SIP response 302 “Moved Temporarily” back from
[Jan 18 13:09:18] VERBOSE[8824] app_dial.c: – Now forwarding Local/[email protected];2 to ‘Local/[email protected]’ (thanks to SIP/101-000000c6)
[Jan 18 13:09:18] VERBOSE[8825] pbx.c: – Executing [[email protected]:1] NoOp(“Local/[email protected];2”, “Blocking callforward to 104 because CF is blocked”) in new stack
[Jan 18 13:09:18] VERBOSE[8825] pbx.c: – Executing [[email protected]:2] Hangup(“Local/[email protected];2”, “”) in new stack
[Jan 18 13:09:18] VERBOSE[8825] pbx.c: == Spawn extension (block-cf, 104, 2) exited non-zero on ‘Local/[email protected];2’
[Jan 18 13:09:18] VERBOSE[8824] app_dial.c: – No one is available to answer at this time (1:0/0/0)

I left the [block-cf] context as it was by default.

Any help is appreciated.

Best regards Oliver

I am having an identical issue using Snom 720/760s. The problem was that the queue that the call was in prior to being transferred to the phone with the forward on it was disallowing call forward. Removing this restriction fixed the issue. As the CF phone is not in the queue, why is it behaving as if it were? In my case, this manifested itself by just hanging up on the caller.