2nd caller hears no ringtone?

[bartfliet]

Hello everybody,

So we've got this setup that people come into a choice menu. If they don't find their choice, they can choose 9 to be connected to the receptionist.
When somebody does this, they get connected. However, when a there's a second caller, who also chooses 9 and tries to get connected, they hear nothing, no ringtone, nothing. It's not that the call doesn't get through, it's just that there is no feedback, how can I fix this so that the second caller hears a ringtone untill he/she is connected to the receptionist?

Thanks in advance!

 

[kyle555]

What's the result of the route-to number in step 48? a station? a hunt? an attendant?

Maybe 48 should route to VDN/vector with "queue to" a hunt and a play music or ringback step while waiting.

 

[bartfliet]

Could I make step 47 "hear ringback" and would that continue on for the second caller untill he's patched through in step 48?
In step 47 they get routed to the receptionist at the desk. Just a station extention.

 

[kyle555]

No. 47 is a commented out line because of the # in front. You go to step 48 if the person presses 9. Whatever happens in 48 is what you need to work on to get ringback.

Personally, I would use a hunt group. 48 routes to a VDN/vector that queues to a hunt group of which reception is a member, and that vector would play ringback while queued.

 

[bartfliet]

I know 47 is a comment, but I could insert a line before 48 and put "hear ringback" on that line, making the next line with is now line 48 (route-to), or wouldn't that work?

 

[kyle555]

It would play ringback for a second or 2, but stop as soon as it routes to whatever 48 goes to. I'm saying I think you need to configure things so you get ringback during the route-to step otherwise it'll ring, then have dead air until answered and perhaps be even more confusing.

 

[bartfliet]

Ah...I see, so I'd need to setup a queue system of sorts...which only works with a vector...or VDN?