Call forwarding to external lines (seems to work but then "line in use") 1

[TheHYPO]

I followed various instructions to get call forwarding set up on our system.

I created a "Route" (318) with a dialout to the desired external number, and a "Destcode" (also 318) tied to the 318 Route.

Most instructions suggested that the route should be left blank and then you put in the external number when you do the feature+4, but I found the Destcode would not let me selection route 318 (or any other) because it just says "route undefined" and doesn't let me select it.

The workaround seemed to work; I Feature+4 and select "318" and press "ok" and when I dial in to my extension, it forwards the line to my cell phone. So far so good, except ever since I programmed it this morning, I have found that lines are now showing as in use (with the note "line in use" when you hit a line button, rather than the usual
"In Use:[user]". (to clarify, forwardning isn't even turned on on any phones right now and the lines are still locked - I have to go reset the system)

Two questions are - can anyone tell me why I am unable to programmed a blank Route so I can just key in the phone number to forward to?

And more importantly, can anyone help me figure out why the forwarding appears to be locking up lines (this is the more important issue, as I won't be able to use the system if it's locking up lines).

Thanks.

 

[Multimedium]

can anyone help me figure out why the forwarding appears to be locking up lines (this is the more important issue, as I won't be able to use the system if it's locking up lines).

The lines should be released when the call is over (as soon as the caller or the callee hangs up).

Make sure that disconnect supervision is enabled on all lines: Lines > Trunk/Line Data > Trunk Mode: Supervised.

can anyone tell me why I am unable to programmed a blank Route so I can just key in the phone number to forward to?

I believe the system will tell that a route is invalid when it does not use any line pool.

You can try to clear the Dial Out for Route 318. Make sure a line pool is still selected, though.

 

[allworxguy]

Line supervision must be turned on for call forwarding to work. The system will give an error if it isn't. I suspect you are not receiving the disconnect signal from the CO.

Marv ccna

http://www.telemarv.ca

 

[Multimedium]

Line supervision must be turned on for call forwarding to work. The system will give an error if it isn't.

I don't think so.

Call Forwarding applies to both external and internal calls, and so does External Call Forwarding. There is no need for disconnect supervision when forwarding internal calls. The system simply forwards an internal call using an external line. When the internal party releases the call, the system releases the line.

Unlike External Transfer and Line Redirection, External Call Forwarding doesn't require disconnect supervision to be turned on. In fact, the system doesn't even check for disconnect supervision before forwarding a call. If it would, external calls coming in on an unsupervised line would be routed to the prime set.

Also, when programming Line Redirection, there is an error message when disconnect supervision is turned off: "Line unequipped". There is no such message when programming Call Forwarding because the system can't know in advance if a call will be coming in on an unsupervised line.

 

[TheHYPO]

Thanks for the feedback. It's not a line pool issue. The route definately uses pool A (that was one of the steps required in the instructions), so that's not why it's invalid, and as soon as I program in an external number, it doesn't give me the error, so it's clearly not allowing me to select a route with no number programmed. I'll see if the disconnect is 'yes' or 'no' tomorrow.

 

[SupportDude]

Forwarding is very simple to setup, but the first question is does your current release of software support external call forward? The software must be 4.1 or better.

You also have some confusion about routing.
You must first build a route, then build a destination code and assign it to a route.

A route is a path out of the Norstar using a defined trunk or group of trunks.
You can define a "dial out", which is a number that will be pre-pended to what the user dialed, or not define a dial out.
The route means nothing without the destination code.

A destination code can be a single digit, like 9, or a group of digits like 91800.
You can configure the Norstar to "absorb" part, or all, of the destination code.
For example, if my destination code was 91800 and I set the absorb length to 1, the system would strip out the 9 and send 1800 plus whatever else the user dialed to the route.
Destination codes are used to point specific dialed digits to routes.

Here's and example of configuration for external call forward.
1) I configure route 001 to use pool A with no dial out
2) I configure a destination code of 8, absorb all, use route 001
3) I go to capabilities for the DN I want to forward calls from and enable "Allow Redirect".
That's it!

To use External Call Forward:
Go to the DN and press F4.
Input 8 and the destination number.

And the Supervision setting should not matter, but it's always best to set Supervision to Yes for all your trunks and insure the Telco is using OSI disconnect supervision to keep the trunks from getting locked up.

Hope this helps!







-SD-

http://www.mysupportguy.net

 

[Multimedium]

[…] as soon as I program in an external number, it doesn't give me the error, so it's clearly not allowing me to select a route with no number programmed.

Give it another try, you may find it works as advertised.

Besides, Route 000 already has no dial out and uses Pool A. You could tie Destination 318 to Route 000.

I'll see if the disconnect is 'yes' or 'no' tomorrow.

Actually, you will see either "Supervised" or "Unsupervised".

 

[Multimedium]

the first question is does your current release of software support external call forward?

It does. TheHYPO already has it working.

If the software did not support External Call Forwarding, the display would read "Invalid number" when dialing the destination code.

And the Supervision setting should not matter

As I said, if disconnect supervision is off, it doesn't prevent the calls from being forwarded. However, it will prevent the system from releasing the lines when the calls are over.

Having that said, there is a case in which it matters: if disconnect supervision is off and a call is transferred to a set that is externally forwarded, the system will deny the transfer.

 

[TheHYPO]

Thanks to all so far.

Here's what I can tell you:

1. Trunk mode is "Unspr" for all four lines we have here.

If I turn that one, it will then solve the problem? Will turning this on have any other impact to the system? I don't want to affect other features/functions that are already working the way we want them. I can advise that once in a while we actually do have lines lock up like this (not using forwarding) and have to reset the system. We have never known why it happens once every few months.

2. Notwithstanding SupportDude and Multimedium's insistance that it will work (and I agree it must work on some systems because the instructions I read online on more than one site suggested it should work), when I try to set destcode 318 (or other ones I tried) to Route 001 (no number, pool A), I get "Route undefined" as the return display, and it doesn't take the route. I MUST hardcode the external phone number into the Route before the DestCode will accept the route.

The only thing I can note is that I followed instructions that look like this:
[URL unfurl="true"]http://pbxbook.com/norstar/ext_cf.html[/url]
Under the "build a route" instructions (part 1), I note that it says:

Dialout: No Numbr – Leave alone – Next
Use: ( ) – Change to Pool you want it to use. (Pool A)
DN Type: Public

On our system, There is no attribute for DN Type. I have Dialout: and Use: and that's in under the route menu. Perhaps this is a clue as to why my system is working differently and doesn't allow me to leave the Dialout blank?

 

[Multimedium]

If I turn that one, it will then solve the problem?

Yes. Change it to "Supervised".

As you saw, the default value is "Unsupervised".

Will turning this on have any other impact to the system?

No. It doesn't affect anything else.

Disconnect supervision is a signal (called Open Switch Interval) sent by the CO when the calling or the called party hangs up. When the system receives this signal, it releases the line.

I MUST hardcode the external phone number into the Route before the DestCode will accept the route.

As I said before, you can try to use Route 000, which has no dial out and uses Pool A.

You can also try a pause (Feature 78) as the dial out instead of a number.

On our system, There is no attribute for DN Type.

The DN Type setting only appears when there is a PRI trunk on the system.

You are using analog lines. It is normal that you don't see the DN Type.

 

[TheHYPO]

I tried using Route 7 and it SEEMS like it is working (feat+4+7+[number]) - I will test it out and see how it goes. Thanks for all the help!

 

[Multimedium]

I tried using Route 7 and it SEEMS like it is working (feat+4+7+[number])

You meant destination code 7.