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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call forwarding off net not working

Status
Not open for further replies.

Phoneguy15

Vendor
Apr 23, 2002
458
US
I have a site that 2 users are having trouble with call forward off net.
CM4.0 S8700/G650

One extension is a 6408D+ and the other is a 2410.
I have done very little testing on the 2410 because of restricted access to the phone, but I have verified the 6408D+ will not forward to the users cell.

When using the FAC (*2) to forward (no console permissions) the user dials *2 9774XXXX but gets no confirmation tone.
I set up a call forward button on the phone and when they use that they get a confirmation tone but the forwarding does not work.
In both cases the calls follow the coverage path.

The 6408D+ user has an assistant with the same telephone set and her's works.
I have compared the station settings between them and they are the same except for the coverage path (same COR/COS and Feature Options).

I feel certain I am overlooking something simple, but for the life of me cannot think of what it may be...

I am hoping someone can point me in the right direction.

Thanks in advance!!

Todd
 
In the class of service is Restrict Call Fwd-off net set to N.

How is your System Parameter - Coverage Fowarding setup..?
 
I think mojo has you in the right direction. But to add a couple of things for you.

1. You can place bridged appearances of their set on your set for your testing. You are basically using their set then.

2. You can setup a "li trace station xxxx" (xxxx being their number) while you are testing it to see why it is getting waved off.

3. Something that i do to simplify this process here is set the users SAC buttons to activate a remote coverage path. This is setup under "next path". Just set the coverage path to "n" on sac/goto cover on the first path and allow it on the second. Have the second path go to coverage remote table 1 and add their cell number (including the 9).

This gives you a little more control on where those calls go out to. It may even lessen the chances of toll fraud.

Let me know if you need help setting this up. Its not that bad really.

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594


 
Thansk for the replies!

Mojo- The COS being used is the same as the station that works...

Here is the System Coverage Parameters:

change system-parameters coverage-forwarding Page 1 of 2
SYSTEM PARAMETERS CALL COVERAGE / CALL FORWARDING

CALL COVERAGE/FORWARDING PARAMETERS

Local Cvg Subsequent Redirection/CFWD No Ans Interval (rings): 2
Off-Net Cvg Subsequent Redirection/CFWD No Ans Interval (rings): 5
Coverage - Caller Response Interval (seconds): 4
Threshold for Blocking Off-Net Redirection of Incoming Trunk Calls: 1
Location for Covered and Forwarded Calls: called
COVERAGE
Keep Held SBA at Coverage Point? n
External Coverage Treatment for Transferred Incoming Trunk Calls? y
Immediate Redirection on Receipt of PROGRESS Inband Information? y
Maintain SBA At Principal? y
QSIG VALU Coverage Overrides QSIG Diversion with Rerouting? y
Station Hunt Before Coverage? y

FORWARDING
Call Forward Override? n
Coverage After Forwarding? y


change system-parameters coverage-forwarding Page 2 of 2
SYSTEM PARAMETERS CALL COVERAGE / CALL FORWARDING

COVERAGE OF CALLS REDIRECTED OFF-NET (CCRON)

Coverage Of Calls Redirected Off-Net Enabled? y
Activate Answer Detection (Preserves SBA) On Final CCRON Cvg Point? y
Ignore Network Answer Supervision? n
Disable call classifier for CCRON over ISDN trunks? n
Disable call classifier for CCRON over SIP trunks? n



Mikey,
I set up the SAC option as you described. the only difference I made was setting voicemail (h99) as the second point in coverage after the remote coverage point.
When we tested it, the call rand straight to voicemail.
The trace of the test shows no denial event. It's just like it tries the remote destination (cell) for 1 second and then coes to the next coverage point.


This is similar to what is happening using the manual forward method (*2 9XXXXXXX).
Calls would try the call forward destination and then almost immediatley go to the coverage path. Coverage after forward is active on the system.

I suppose I could just remove the VM point in the second coverage path that we are using for the SAC destination, but I would really like to know why it's not working.

Thanks again for the help,

Todd

 
Can you do a list trace and then post it, can you forward the call to a number other then a cell phone, I've seen in the past that there have been issues forwarding to certain cell companies..?

I think thats a good idea to remove the VM point just to see if can get to the cell phone.
 
Here is the list trace I ran when testing the SAC option.

The first part is where they deactivated the manual forwarding first (#2) from 9:58:53 thru 9:58:55
The test call using the SAC option starts at 9:59:27

list trace previous Page 1

LIST TRACE

time data

09:58:53 tone-receiver 01B0904 cid 0xa6f
09:58:53 active station 57294 cid 0xa6f
09:58:55 idle station 57294 cid 0xa6f
09:59:27 Calling party station 57372 cid 0xa7d
09:59:27 Calling Number & Name 57372 Tina Gillispi
09:59:27 dial 57294
09:59:27 redirect station 57294 cid 0xa7d
09:59:31 coverage-path 32 point 1 cid 0xa7d
09:59:31 dial 9774 route:HNPA|ARS
09:59:31 redirect trunk-group 4 cid 0xa7d
09:59:31 xoip: fax:Relay modem:eek:ff tty:US 10.37.31.19:2492 (igc)
09:59:31 xoip: fax:Relay modem:eek:ff tty:US 10.37.31.21:2088 (igc)
09:59:31 G711MU ss:eek:ff ps:20 rn:1/1 10.37.31.19:2492 10.37.31.21:2088
09:59:31 dial 97747294 route:HNPA|ARS
09:59:31 route-pattern 2 preference 1 cid 0xa7d

press CANCEL to quit -- press NEXT PAGE to continue


list trace previous

LIST TRACE

time data
09:59:31 seize trunk-group 4 member 4 cid 0xa7d
09:59:31 Calling Number & Name 7707372 NO-CPName
09:59:31 Proceed trunk-group 4 member 4 cid 0xa7d
09:59:32 no answer station 57372 cid 0xa7d
09:59:32 coverage-path 32 point 2 cid 0xa7d
09:59:34 active station 58851 cid 0xa7d
09:59:37 idle station 57372 cid 0xa7d
10:04:42 TRACE COMPLETE station 57294 cid 0x0









Command successfully completed
Command:



I will remove VM from the coverage path and run a trace on the SAC option, but if I recall when we tested the manual forward (*2) before, it would work if I removed the coverage path from the station...


Todd
 
Ok,
I removed the VM from the SAC destination coverage path (32).
They had deactivated the SAC feature button to activate the 2nd coverage path already. I placed a test call with a trace running.
The call still followed the 2nd coverage path and immediatly got a busy tone.

Here is the trace from it:

list trace previous Page 1

LIST TRACE

time data

10:58:16 Calling party trunk-group 1 member 3 cid 0x1036
10:58:16 Calling Number & Name 8507840101 NO-CPName
10:58:16 dial
10:58:16 ring station 57294 cid 0x1036
10:58:16 dial 9774 route:HNPA|ARS
10:58:16 ring trunk-group 4 cid 0x1036
10:58:16 xoip: fax:Relay modem:eek:ff tty:US 10.37.31.19:2204 (igc)
10:58:16 xoip: fax:Relay modem:eek:ff tty:US 10.37.31.23:2928 (igc)
10:58:16 G711MU ss:eek:ff ps:20 rn:1/1 10.37.31.19:2204 10.37.31.23:2928
10:58:16 dial 97747294 route:HNPA|ARS
10:58:16 route-pattern 2 preference 1 cid 0x1036
10:58:16 seize trunk-group 4 member 11 cid 0x1036
10:58:16 Calling Number & Name 8507840101 NO-CPName
10:58:16 Proceed trunk-group 4 member 11 cid 0x1036
10:58:17 no answer trunk-group 1 cid 0x1036

press CANCEL to quit -- press NEXT PAGE to continue



list trace previous

LIST TRACE

time data
10:58:17 coverage-path 32 point 1 cid 0x1036
11:00:31 TRACE COMPLETE station 57294 cid 0x1036















Command successfully completed
Command:



I had to go in and remove the Next Path Number in the 1st coverage path in order for it to go back to using the 1st coverage path.

So, with the voicemail removed from the coverage path it just go a busy signal.

 
Finally managed to get back to this.
I did another test using Enhanced call forwarding.
We activated the Enh CF unconditionally and placed a test call.
The calls continue to follow the coverage path instead of the to the forward destination.

WTF!! This is driving me crazy.
Why would call forwarding on a station be ignored?
The system acts like call forward is not active on this particular station and just sends calls down the coverage path.

 
I think I would find a set there that could forward off-net and duplicate the cos. Also have you tried to set this up using the remote coverage? I would like to see if that makes it work. This would be the easiest on the user anyway. They can use the SAC button to activate the second path and away they go.



When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594


 
The trouble extension is already using the same cos as one that can succesfully forward off net.

I have also dialed in remotely and activated call forward (off net). When I placed a test call the call forwards AND follows the coverage path.

Here is the call trace on the test call I just performed.
It's like it immediatlly jumps from forward to coverage path.

list trace previous Page 1

LIST TRACE

time data

16:40:27 Calling party trunk-group 1 member 4 cid 0x28a5
16:40:27 Calling Number & Name 8507840101 NO-CPName
16:40:27 term station 57294 cid 0x28a5
16:40:27 call-forwarding 9774
16:40:27 term trunk-group 4 cid 0x28a5
16:40:27 xoip: fax:Relay modem:eek:ff tty:US 10.37.31.19:2296 (igc)
16:40:27 xoip: fax:Relay modem:eek:ff tty:US 10.37.31.23:2448 (igc)
16:40:27 G711MU ss:eek:ff ps:20 rn:1/1 10.37.31.19:2296 10.37.31.23:2448
16:40:27 call-forwarding 97747294
16:40:27 route-pattern 2 preference 1 cid 0x28a5
16:40:27 seize trunk-group 4 member 12 cid 0x28a5
16:40:27 Calling Number & Name 8507840101 NO-CPName
16:40:27 Proceed trunk-group 4 member 12 cid 0x28a5
16:40:28 no answer trunk-group 1 cid 0x28a5
16:40:28 coverage-path 31 point 1 cid 0x28a5

press CANCEL to quit -- press NEXT PAGE to continue

list trace previous

LIST TRACE

time data
16:40:28 ring station 57871 cid 0x28a5
16:40:38 no answer station 57871 cid 0x28a5
16:40:38 coverage-path 31 point 2 cid 0x28a5
16:40:38 ring station 57372 cid 0x28a5
16:40:48 no answer station 57372 cid 0x28a5
16:40:48 coverage-path 31 point 3 cid 0x28a5
16:40:49 active station 58852 cid 0x28a5
16:40:56 idle trunk-group 1 member 4 cid 0x28a5
16:41:23 TRACE COMPLETE station 57294 cid 0x0








Command successfully completed
Command:



 
Todd try tearing it down and programming it back again. It's starting to sound like this has something in software not liking it. Or It has something else built up with it preventing it from working. Use the same port everything.. This may get it (new technical term for ya) "Unhosed"... :)

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594


 
The latest tests are:

I changed the coverage path to a new one (cov pa 32) with a remote coverage destination of my cell phone as the only coverage point.
When I placed a test call to the extension, I get an immediate busy signal.

I removed all coverage paths from the extension and activated Enhanced Call Forwarding (Internal and External to my cell phone) and placed a test call.
The call connected just fine.

So the calls will forward without a coverage path assigned to the station but not if there IS a coverage path assigned.

Why would a coverage path be interfering with forward off net?

 
Sorry, Mikey. I didnt see your post before I updated with mine.


I have removed the station and rebuilt it again using the same port already.

 
Have you tried just setting up a coverage path and have a second one to remote coverage ??. I usually use sac to make the calls go to the second path.

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594


 
Thanks Mikey!
I did try that earlier and it did not work. It "tried rining" the cell for a second then goes to the next point in the (second) coverage path (in this case, voicemail).
 
Thinking out loud, is this a double coverage issue?
 
Jumbo,
It's not. There is only one coverage path assigned to the phone. When the phone is forwarded it follows the coverage path instead of to the forwarding destination.
If I remove the coverage path from the station, the calls will go to the forward destination.
 
In your coverage path...how many rings do you have it set? try upping the number of rings to 6.

Scott
________________________________________
When Life Gives You Questions, Google has Answers - AJ Carpio

 
Hi Scott,
The coverage path is set for 3 rings. I can give it a try with higher rings, though.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top