Remote call forward not working

[pmcook]

Version 5.0, full PRI. SO I set an extension for enable redirect. Since I only have PRI-A as a pool I just created a button, feature 4. Then I press the button, dial 9xxxxxxx. I call in using the DID but the set will not call forward. If I dial in on an iPhone it never rings then hangs up. On my Android I dial in and then I get "call cannot be completed as dialed." I hear the set beep rather than ring.

 

[curlycord]

*External Forward

You say you call the DID, did you mean the users DID or the main number/DID?
Did you try to Intercom the phone from another internal set? this may tell if it partially works....i.e outbound not an issue but rather the inbound caller to the DID.
Check any restrictions.
Beep once or describe better

Refresher/example:

4.1 or up
Allow Redirect
Dest Code 9 to use Route 001
Route 001 told to use PRI-A

Set - Feature 4, 9XXX-XXX-XXXX, OK




________________________________________

Add me to LinkedIN

**New Allworx Forum**

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[pmcook]

I called in using the set DID. I hear an abbreviated beep for every ring I should hear. Its as if the system is not sending all the digits as there is a delay between when the last beep is heard and when the dialing error message is heard from the CO.

 

[telcodog]

Caller ID issue? Some carriers will not allow an outbound clid that is not "owned" by the customer. If you are passing the original caller's number, the carrier is likely blocking your call. If you are set up the way Curly indicates, this is the most likely cause.

 

[curlycord]

Could be indeed.
The set beeping is a new one on me though.




________________________________________

Add me to LinkedIN

**New Allworx Forum**

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[pmcook]

I cannot say if the system is sending the caller id or the DID. I k now any calls from that site send the main trunk DID. I could find nothing in the config regarding this fopr CFWD. Does the outbound forward number have to be formatted as 10 digits? I am doing a GF4 91XXXXXXXXXX.

 

[curlycord]

91?
is 1 restricted?
The string should be the same as if you pressed Intercom to dial out.

Best to ask carrier if forwarding CLID


________________________________________

Add me to LinkedIN

**New Allworx Forum**

=----(((((((((()----=

http://www.curlycord.com

Toronto, CAN

 

[pmcook]

It does not work with 7 digit local numbers, either. I tried 9XXX-XXXX and it fails as well. SO it must be the CLID issue.

 

[telcodog]

This may be a stupid question but is your carrier using long distance codes? It may just be waiting for you to enter an authorization code.

By your description, you are instructing the system to dial the outbound number as a long distance call. If it isn't, remove the 1 as your carrier might not process a local call if it is dialed as LD.

Where are you located? I didn't think there was anyplace left that uses 7 digits for local calls.

 

[pmcook]

I am in the US. 10 digit dialing is still not the norm. We have a great many, in fact most, 7 digit areas. If I can dial a 7 digit number why cannot I use a 7 digit number for CFWD?

 

[telcodog]

You can use 7 digit numbers for cfwd if you can dial 7 digits directly.

 

[cook1082]

Like Curley said dial the extension from another phone to see if the call goes out if it does then it's the CO not recognize the CLID as the BTN number. it is passing the inbound CLID number.

 

[pmcook]

So the fix was that the extension had no line assigned to it. Now it works.