![]() |
|
|
#1 (permalink) |
![]() Join Date: Nov 2004
Posts: 1
![]() |
'double' call-forward problem
hi all!
I've got a problem with call-forward. When one extension (e.g. 500) has activated a call-fwd to extension 510, and 510 has activated a call-fwd to another number (extension or outside), only first call-fwd will work. Example: a call to 500 will be forwarded to 510 and will stop there. Call-fwd on the extension 510 won't work. It's a little bit confusing, because users don't have to know, who has activated the call-fwd. my system's software: SOFTWARE VERSION Memory Resident: R011x.03.2.536.1 Disk Resident: R011x.03.2.536.1 Thanks in advance for help! |
|
|
|
|
|
#4 (permalink) |
|
PBXtech GOLD 100+ posts
![]() Join Date: Dec 2003
Posts: 143
![]() |
Re: 'double' call-forward problem
It has always worked like this and probably always will, so dearly called the "double coverage" rule. Once a call has forwarded or covered within the switch, it won't do it again (yes you can do it by leaving the switch to an adjunct, etc.) and it applies to vectors (if you have a station cover to a VDN then the vector does a route-to with coverage...the coverage won't workie) and all that. It actually makes sense, otherwise you would have no idea where calls would end up in a complex coverage and forwarding setup.
__________________
"There are only 10 types of people in the world, those who can read binary and those that cannot." |
|
|
|
|
|
#5 (permalink) |
|
PBXtech PLATINUM 300+ posts
![]() Join Date: Nov 2004
Posts: 354
![]() |
Re: 'double' call-forward problem
Koelemon is correct. If this wasn't true you could create a loop by forwarding ext 5000 to 6000 and 6000 to 5000. Then if call came into 5000 in would forward to 6000 which would forward to 5000 which would forward to 6000 which would forward to 5000 which would forward to 6000, etc....This would not be a good thing. I am sure it would eat up a lot of processor cycles and probably crash a system.
|
|
|
|
|
|
#6 (permalink) |
|
PBXtech SILVER 25+ posts
![]() Join Date: Mar 2004
Posts: 68
![]() |
Re: 'double' call-forward problem
How about setting up a coverage path remote. Have it as the first point of cover. The call gets routed to the 2nd extension and then the call will follow her coverage path. The down side would be it would be like an outside call coming in. I set it up here and it works great.
The steps 1. change coverage remote 9xxxxxxx 2. Change the coverage path of the manager’s extension to r? for the remote coverage path number. Lee |
|
|
|
|
Advertisement
|
Sponsored links
|
|
|
#7 (permalink) | |
|
PBXtech GOLD 100+ posts
![]() Join Date: Dec 2003
Posts: 143
![]() |
Re: 'double' call-forward problem
Quote:
great example ISA_Flee!
__________________
"There are only 10 types of people in the world, those who can read binary and those that cannot." |
|
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Call Forward External | mwade | Meridian systems | 0 | July 18th, 2005 09:34 AM |
| ACD call problem | STRSG3r | Definity Servers | 7 | April 18th, 2005 01:50 PM |
| Problem with forward to VM. | mtfs | Norstar systems | 4 | December 6th, 2003 08:59 AM |
| Call Forward on Busy overrides CLID | Andrew | Norstar systems | 0 | July 18th, 2003 08:31 AM |
| Setting up Call Forward remotely | Andrew | Norstar systems | 0 | July 18th, 2003 08:27 AM |