Ticket Navigation

Ticket #1182 (closed Bugs: fixed)

Opened 2 years ago

Last modified 2 years ago

can't use # transfer when call is outside number

Reported by:	fidalgonet	Assigned to:
Priority:	minor	Milestone:	2.2
Component:	Queues	Version:	2.2beta1
Keywords:	# transfer broken	Cc:
Confirmation:		SVN Revision (if applicable):
Backend Engine:	All	Backend Engine Version:

Description

Hi,

I have been trying to use the # transfer feature when the queue or ring group is an outside routing number, every extension I try says invalid extension. The only extensions that seem to work is the Phone extensions, but they just transfer and hang up on the caller. I want to be able to transfer to different ring groups or queue groups using the # transfer feature, I used to be able to do this just fine a few svn's ago. (Month or two?)

Change History

11/02/06 09:16:47 changed by fidalgonet

Anybody else having this issue, or is it just me? Would be nice to have someone confirm this as a bug.

(follow-up: ↓ 3 ) 11/13/06 09:40:08 changed by p_lindheimer

priority changed from 9 to minor.
status changed from new to closed.
resolution set to invalid.

set you 'asterisk outbound dial command options' on the 'General' tab with the approproiate options and it should work. If not, reopen this bug and provide more details. That is what controls dial options for anything that goes out a trunk vs. internal extensions and by default # transfer is disabled because it messes with internal people calling things like external IVRs

(in reply to: ↑ 2 ; follow-up: ↓ 4 ) 12/16/06 13:49:56 changed by m.ramaker

status changed from closed to reopened.
resolution deleted.

Replying to p_lindheimer:

set you 'asterisk outbound dial command options' on the 'General' tab with the approproiate options and it should work.

Checked the setting on the 'General'tab > tTw

It seems you can only transfer to extensions that are in the same ring group. Trying to transfer to a station outside the ring group results in an invalid extension.

Is this a bug or working as designed?

(in reply to: ↑ 3 ; follow-up: ↓ 5 ) 12/16/06 20:10:27 changed by strobes

you can see that that dial string has two

Executing Dial("SIP/203-098e4028", "SIP/205tr") in new stack I think it's a bug

(in reply to: ↑ 4 ) 12/16/06 20:13:31 changed by strobes

Replying to strobes:

you can see that that dial string has two

Executing Dial("SIP/203-098e4028", "SIP/205tr") in new stack I think it's a bug

Unfortunately this page does not display special characters so here is one with some editing:

Executing Dial("SIP/203-098e4028", "SIP/205IItr") in new stack

12/17/06 05:30:06 changed by vgster

Shouldn't there be a comma before the dial options to seperate it from the SIP/205?

12/17/06 17:23:28 changed by RobThomas

status changed from reopened to closed.
resolution set to fixed.

I think you'll find that philippe's changes have fixed this. Marking it as closed, try the latest trunk - see http://aussievoip.com.au/wiki/freePBX-Upgrading for instructions on downloading from SVN

01/08/07 11:46:44 changed by

milestone deleted.

Milestone 2.2 deleted

01/08/07 13:18:43 changed by vgster

milestone set to 2.2.

Download in other formats:

Comma-delimited Text
Tab-delimited Text
RSS Feed

Development - Get Connected