Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

After Hours Call Forwarding

Status
Not open for further replies.

JustAMan

IS-IT--Management
May 3, 2012
9
US
Hello all,

I have an IP Office 406 4.2(23) and I am trying to setup a model for after hours forwarding to a cell phone. I have followed many instructions for this and had it working fine. I then upgraded to version 5 and it quit functioning. I downgraded the software, but it still does not work. As far as I can tell, I have everything configured properly. Here is a brief overview of configs and tests I've run.

General Configuration:
- 3 Analog lines coming in
- 3 hunt groups (Electric 1, Electric 2, AfterHours)
- Electric 1 (2 users) is primary, overflows to Electric 2 (3 users)
- Electric 1 Fallback uses Time profile of BusinessHours (set 7:30-4:30 M-F), with Night Service Group of AfterHours, and is always In Service
- AfterHours group is always In Service, has a single user named AfterHour Forwa, Ring Mode of Sequential
- AfterHour Forwa has unconditional forwarding enabled, with Hunt Group and Internal checked, to the cell phone number, including prefix
- No auto attendant or voicemail is currently configured in the system

Tests I've performed:
- Dial AfterHour Forwa extension from internal results in the call being forwarded to the cell
- Dial AfterHours group extension from internal results in the call being forwarded to the cell
- During time profile, calls ring properly and overflow properly through primary groups
- Outside of time profile, calls are not handled at all - they continue to ring

I have spent days trying to solve this. I'm hoping someone may have some ideas to find a resolution.

Thanks!!
 
What does your time-profile controlling, Hunt groups or incoming call routes? These work differently and has to be setup differently?

Mitel, Avaya, NEC, INDEX
 
Time profile is only being referenced by the Hunt group. The incoming call route is a single line, with Default Value for timeprofile, Electric 1 for Destiation, and nothing for Fallback
 
You need to activate the "allow trunk to trunk transfer" setting on the analog trunks :)

 
Check he following threads


1. Time profile for hunt group
thread940-1430395
2. IPO 500 - 4.1.15 - HuntGroup Time Profile override
thread940-1500087

Seems you did not tell the system what to do with the call out of the Time profile periods

Mitel, Avaya, NEC, INDEX
 
amriddle01 - THANK YOU!!
I can't test it right now, but I can see where that is a problem. I did not have it enabled for any of my lines. Weird that it worked before, this isn't a new feature/requirement is it? Would moving to v5 have dropped that config? Just curious.
 
7deetz - Thanks for those links. I was not aware of the difference in the time profiles, and I can see where that will be vital as I expand this configuration.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top