Forward phones in hunt list

no, great deal went into programming to prevent that. Allowing it creates very angry customers when the ring groups get hijacked by one forwarded phone. why not alter 'other numbers to dial' ?

The reason:

This simple client that has two lines in a hunt group. one is the roll over. At night she wants to forward her calls to the west coast branch.

this should be done in the inbound route section for the DID, not the extensions of a hunt list.

Is this the off hours part?

How would they toggle this on and off? I know the off hours time schedule can be set but I dont want a concrete time, some times they are there late, etc.

Does the Day/Night feature code apply to the phone that set it, or does it apply to the whole tenant and is this the right feature?

Thanks E

learn how to use the operator managed route system and you can dial into a feature code and toggle day/night/temp modes.

OK i see how this works. I will test this out tonight.

Thanks E

So this is the set up.

I will have the First line to have call forwarding always enabled with a number.

I will have an operator base schedule.

Inbound route during day time goes to Hunt List and night time goes to feature codes.

The receptionist dials *22 and activates Night Time.

Night time is configured to go to Feature Code which is a User Extension which is the first of the Hunt List.

Since this is a dial extension code, the call forwarding should take and the call with transfer to the west coast office.

I don't see any other way to forward a call.

I will test this set up tonight.

What are your thoughts?

??????? no.. #1 separate the DID from lines in your head...

extensions
line#1 SIP/11111111
line#2 SIP/22222222

Did's

DID #1 5025551212 <- main number
DID #1 7365551212 <- roll over #

hontlist main_huntlist

ring 11111111 for 90 seconds
ring 22222222 for 90 seconds
go to voicemail box xyz

inbound routes
inbound route 5025551212 operator managed :
day mode - go to hunt list main_huntlist
night mode - forward to did 2127775555

inbound route 7365551212 scheduled route:
all hours - go to user extension 22222222

feature codes
*22 - set day/night macro

Thats along the lines I was thinking originally. But let me clarify and explain.

DID: 2125551212

extensions: 888
777

Hunt list: ring 888 for 10 seconds then ring 777 for 10 seconds then go to voicemail.

Now this is where the issue came up for me before:

the inbound route is operator based.
Day Mode: goes to Hunt List
for the night mode, there is no 'forward to did'. this is where i want to go to say another office or someone's cell phone.

well theres one built into TL thats a little confusing and then theres one you can write yourself.

The one included into TL is called tl-reroute

its confusing becaues it asks how many digits to strip and how many digits to prepend.. which would work like

2125551212 forwards to 2127362212

in that case you would strip 10 digits, and prepend 2127362212

it was written to do something like

2125551212 strip 3 digits and prepend 502 in order to turn 2125551212 into 5025551212

then theres one I wrote that is easy...

[bgnv-forward-did]
exten => s,1,Goto(outgoing${TL_DASH}${tenant},${ARG1},1)

and the argument is type text where you would input what number you wanted to forward the call to.

I am not at the level yet of knowing how to write the code and having it pop into thirdlane yet.

since I dont know how to write the scripts or where to put them I found a work around.

for my set up, this is what I did:

I have extension 888 with a forward always to 13455551212 enabled.

I set the night mode of the inbound route to go to user extension with the forwarding on.

So when *22 activates night mode, the call forwarding works.