Getting "busy" on external forward 7

[ivtrook]

Extension 6333 was an existing ext. with a physical phone. i renumbered the ext. to 5333 and made x6333 an adjunct (because the DID needs to forward without a physical phone)
Made the auth code the same as the adj. 6333 and then finally enabled remote forwarding for 6333.

Since i'm not out on site i had the customer input the code from an SA Key..

"#80 (6333) # *33 9 (1-847-xxx-xxxx) #"

Upon testing, dialing either internally or externally the 6333 DID, the caller gets busy tone.

Anyone have any ideas to why i have busy tone???

 

[memphisribs]

My testing indicates TouchTone Tommy was exactly correct,
glg01 strangely enough both #33 or *33 activate call-forwarding on-site with MLX sets, of course Feature 33 works also. You are correct about remote call forwarding having nothing to do with call transfer. This is a call redirection not a transfer.
From the Feature Reference document:
Telephone Differences
You can activate or deactivate Forward or Remote Call Forwarding from a local system telephone by first entering your authorization code. When you hear an inside dial tone, you press the Feature button and dial 33, or dial #33 or *33, depending on the type of telephone at the extension you are using. Activating the feature using an authorization code follows the same rules as other activations of Forward.
Syquest seems to have veered off on the wrong track; RCF is a WAD (works as designed). No feature interaction with Trunk to Trunk transfer.
Back to assisting ivtrook, for testing purposes use a real extension, for best results a display set. Program a forward button on a blank key. Enable remote call forwarding for the test phone.
Place a call from this set, to the location where you wish to forward to. ( You should’t have to touch any buttons just pick-up the handset and dial, now you know the extension can get to where you trying to send it.
Now press the forward button and enter the number just exactly as dialed in previous step. Remember to end dialing with a # sign (you should get confirmation tone and the forward light will come on)
Place a test call from any extension to the forwarding extension. Results should be the remote number rings.
Now you can add the authorization code business and test again.
This should work exactly the same for an adjunct port. Just make sure the adjunct auto-line selection, and restrictions are the same as the real test station.
My motto: KISS

42 years in the business and counting.

 

[glg01]

First off I want spit a feather and apologize to TTT for saying he was wrong with his post....I found the info memphisribs posted about both codes working on page 391 of the Magix Feature Reference manual...and after he posted his test results with the Magix R4 and Intuity I retested with my R2.0 Magix and the *33 did work as both of you had posted. I had already proven the trunk to trunk and voice mail ports transferring without trunk to trunk permissions.

Prior to us having the auth code/RCF capability introduced in R6.0 Legend (that allowed us to use the adjuncts) we had to use a physical T/R for RCF for a person that was not there and it had to be done obviously with a single line phone. To RCF from the single line phone you #33 plus the outside number and I can assure you #33 had to be used. Now if the auth code feature allows you to act like you are using your phone and an adjunct is considered a T/R device then why wouldn't you use the #33 as I originally posted? I haven't found the phone that actually uses or requires the *33 yet...in other words #33 worked on every type of phone I tried. Enough on this though.

Why is ivtrook not able to RCF? He has posted he has a Mgx 2.2. In 2.2 RCF with simultaneous ringing was introduced which allowed you have a pool button on your set and worked like a cheap EC500 on Definity. Maybe he has his adjunct programmed with RCF with simultaneous ringing. If he does then this could cause the problem. Just a thought.

I also want to thank memphisribs for his valuable posting, TTT, SYQUEST and merlinman for making this a stop and think challenge. I know this wasn't what you meant by KISS...Ha

Come on ivtrook let us know what's happening. lg

 

[TouchToneTommy]

It's always been #33 (or Feature 33) when setting Call Forwarding for the phone you're on, but *33 when setting it via an authorization code.

If you are earlier than R6, and don't have Auth Codes available to set forwarding for adjuncts, but have S/L and line ports, loop an extension to a trunk, make it remote access. Dial the extension, wait for the trunk to answer, put in the Barrier Code, and then #33, the adjunct extension, and the destination number.

Now that all us pundits have weighed in on this one, I'd really likle to hear from ivtrook about what is happening!!!

 

[ivtrook]

WOW, i'm overwhelmed with all the replies! I can't thank you guys enough!

Here's what i found though:

This code: (Hint: Make the Authorization Code be the same as the Extension Number)

It turns out that you CANNOT make the Auth Code the same as the adjunct ext. (at least in this release..)

Perhaps from now on when I'm in SPM I should make sure to have the SOUND ON when I'm programming, so i know for sure if something takes or doesn't!!

Other than that, calling the full DID works good but when calling 6333 internally, it does NOT forward out. This needs to be done if possible.

Thank you all, hope everyone's Thanksgiving was good! I had a satifying trip to the casino!

 

[TouchToneTommy]

This code: (Hint: Make the Authorization Code be the same as the Extension Number)

It turns out that you CANNOT make the Auth Code the same as the adjunct ext. (at least in this release..)

This may have revealed the underlying problem.

You most certainly can have the Authorization Code the same as the Extension Number. But the Authorization Code must be unique from all other Auth Codes.

I'll bet a nickle that it you did a print of Ext. 5333 (the port that used to be 6333), you will find that it had an Auth Code of 6333 when it was actually Ext. 6333.

So when you went to a phone, and put in the Auth Code, you were forwarding what is now Ext. 5333, not the Adjunct that got renumbered to 6333.

 

[glg01]

TTT what you're saying makes sense I haven't found anything in writing that states the auth code can't be the same as the extension. The auth code won't show up on the ext info but it would show if he prints the auth codes list. I didn't get that he was using the auth code(s) prior to trying to forward this adjunct. He says it still doesn't forward on internal??? ivtrook what do you hear on internal calls...busy signal? Denial sound (NOnoNOno)? Dead air..nothing? If it forwards with DID it should forward on internal calls. lg

 

[SYQUEST]

Ivtrook,

Why don't you post a print of the adjunct and station that have the problems per the posts above. That way we can all see what you have programmed, and offer better suggestions to solve the problem.

....JIM....

 

[ivtrook]

I believe the customer is getting a busy signal when she dials internally 6333, but i will confirm that...



A EXTENSION INFORMATION


A Extn SS/PP Type
A 6333 7/38 UNEQUIPPED

A CTI Link : No Alarms: ACTIVE
A Pool Access :
A Page Group :
A Primary Coverage :
A Secondary Coverage :
A Coverage Group :
A Call Screening : OFF
A Group Coverers :
A NS Groups :
A Auxiliary Work Time : NOT ACTIVE
A Group Calling Member:
A Group Calling Log In:
A Pickup Groups :
A Allowed Lists :
A Disallowed Lists :
A Restrictions : UNRESTRICTED
A ESS Sup. Status : NOT ACTIVE
A ESS Restrictions : ESS-0 - NO RESTRICTION
A Auto Callback : OFF
A Call Waiting : OFF
A Abbreviated Ring : ON
A Line Preference : ON
A Shared SA Ring : ON
A Receive Voice Calls : ON
A Coverage Inside : ON
A Forwarding to : 918474860282#
A Delay Forwarding : 0
A Rmt Call Frwd Pool :
A ARS Restriction : 3
A Forced Account Code : No
A Microphone Disable : No
A Rotary Enable : No
A Remote Forward Allow: Yes
A Trunk Transfer Allow: No
A NS Exclusion : No
A Voice Announce Pair : No
A Voice/Data Pair : No
A BIS/HFAI : No
A Language : English
A Authorization Code : 1357
A 2B Data Port : No
A Primary Ring Delay : 2
A Secondary Ring Delay: 2
A Group Cover Delay : 3
A HotLine Extension : No
A Networking and ISDN Display Preference: NUMBER
A Service Observer:
A Service Observing Group:
A EXTENSION INFORMATION


A Extn SS/PP Type
A 6333 7/38 UNEQUIPPED

A Button 34 *21 Blank Status None
A Button 33 *21 Blank Status None
A Button 32 *21 Blank Status None
A Button 31 *21 Blank Status None
A Button 30 *21 Blank Status None
A Button 29 *21 Blank Status None
A Button 28 *21 Blank Status None
A Button 27 *21 Blank Status None
A Button 26 *21 Blank Status None
A Button 25 *21 Blank Status None
A Button 24 *21 Blank Status None
A Button 23 *21 Blank Status None
A Button 22 *21 Blank Status None
A Button 21 *21 Blank Status None
A Button 20 *21 Blank Status None
A Button 19 *21 Blank Status None
A Button 18 *21 Blank Status None
A Button 17 *21 Blank Status None
A Button 16 *21 Blank Status None
A Button 15 *21 Blank Status None
A Button 14 *21 Blank Status None
A Button 13 *21 Blank Status None
A Button 12 *21 Blank Status None
A Button 11 *21 Blank Status None
A Button 10 *21 Blank Status None
A Button 9 *21 Blank Status None
A Button 8 *21 Blank Status None
A Button 7 *21 Blank Status None
A Button 6 *21 Blank Status None
A Button 5 *21 Blank Status None
A Button 4 *21 Blank Status None
A Button 3 *18 SysAcc-OO Ring Status None
A Shared System Access:
A
A Button 2 *16 SysAcc Voice -I Status None
A Shared System Access:
A
A Button 1 *16 SysAcc Ring -I Status None
A Shared System Access:
A

 

[merlinman]

Forward only works on a ringing phone.

You will need to set up coverage on a "REAL" phone to make this work. I use unused VM T&R Ports for stuff like that.

Or, you could use a Vacant T&R Extension port as your phone to forward.

I set one up like this just the other day.

http://home.comcast.net/~merlinman

 

[memphisribs]

Adjunt will work just fine, all calls inside and out should follow the fowarding just as you proved with the DID call. Suspect miss-dialing on the users part. I have made tests calls to a forwarded adjunt, to verify this works.

Good luck

42 years in the business and counting.

 

[SYQUEST]

I was rereading the original post and the reason you are getting a busy tone is quite simple. Unless the adjunct port is terminated with an MFM module in an MLX phone, or Covered on a phone, or has an SSA line appearance it is considered "busy" by the system! So one of those options needs to be assigned, then it will ring. Now with the SSA, you could program it on a non existant button with NO RING to satisfy the physical phone requirement. You might try that. One other item of note, if you remove the physical phone in the case of an MLX, it will revert to "busy" by the system, that being the only set in service with that SSA or Cover.

I ran into this situation a couple of years ago when setting up a "multiline" group using SSAs on MLX phones and trying to make the system work for the client. After much reading and rereading of the Features Document and testing I figured it out. If you Cover it, it goes there and rings. If not and there is no other place to go, you get a busy tone! From the system point, it is logical for this operation and makes sense (one of the few for the Legend/Magix).

Here is a sample print of the one I used:

A STATION INFORMATION 12JAN2007
A Stn SS/PP Type
A 541 3/26 UNEQUIPPED
A CTI Link : No Alarms: ACTIVE
A Pool Access :
A Page Group :
A Primary Coverage : 533
A Secondary Coverage :
A Coverage Group : 30
A Group Coverers : 770
A NS Groups :
A Group Calling Member:
A Pickup Groups :
A Allowed Lists :
A Disallowed Lists : 6 7
A Restrictions : UNRESTRICTED
A ESS Sup. Status : NOT ACTIVE
A ESS Restrictions : ESS-0 - NO RESTRICTION
A Auto Callback : OFF
A Call Waiting : OFF
A Abbreviated Ring : ON
A Line Preference : ON
A Shared SA Ring : ON
A Receive Voice Calls : ON
A Coverage Inside : OFF
A Forwarding to :
A Delay Forwarding : 0
A ARS Restriction : 3
A Forced Account Code : No
A Microphone Disable : No
A Remote Forward Allow: Yes
A Trunk Transfer Allow: Yes
A NS Exclusion : No
A Voice Announce Pair : No
A Voice/Data Pair : No
A BIS/HFAI : No
A Language : English
A Authorization Code : 8541
A 2B Data Port : No
A Primary Ring Delay : 1
A Secondary Ring Delay: 2
A Group Cover Delay : 3
A HotLine Extension : No
A Display Preference : NUMBER

A Stn SS/PP Type
A 541 3/26 UNEQUIPPED
A Button 34 *21 Blank Status None
A Button 33 *21 Blank Status None
A Button 32 *21 Blank Status None
A Button 31 *21 Blank Status None
A Button 30 *21 Blank Status None
A Button 29 *21 Blank Status None
A Button 28 *21 Blank Status None
A Button 27 *21 Blank Status None
A Button 26 *21 Blank Status None
A Button 25 *21 Blank Status None
A Button 24 *21 Blank Status None
A Button 23 *21 Blank Status None
A Button 22 *21 Blank Status None
A Button 21 *21 Blank Status None
A Button 20 *21 Blank Status None
A Button 19 *21 Blank Status None
A Button 18 *21 Blank Status None
A Button 17 *21 Blank Status None
A Button 16 *33 Forward Status Off
A Button 15 *46 Coverage VMS Status On
A Button 14 *21 Blank Status None
A Button 13 *21 Blank Status None
A Button 12 *21 Blank Status None
A Button 11 *21 Blank Status None
A Button 10 *21 Blank Status None
A Button 9 *21 Blank Status None
A Button 8 *21 Blank Status None
A Button 7 *21 Blank Status None
A Button 6 *16 SysAcc Ring -I Status None
A Shared System Access: 532 535 575 519 550 507 503 506
A 504 502 505 501 533
A Button 5 *16 SysAcc Ring -I Status None
A Shared System Access: 532 535 575 519 550 507 503 506
A 504 502 505 501 533
A Button 4 *16 SysAcc Ring -I Status None
A Shared System Access: 532 535 575 519 550 507 503 506
A 504 502 505 501 533
A Button 3 *16 SysAcc Ring -I Status None
A Shared System Access: 532 535 575 519 550 507 503 506
A 504 502 505 501 533
A Button 2 *16 SysAcc Ring -I Status None
A Shared System Access: 532 535 575 519 550 507 503 506
A 504 502 505 501 533
A Button 1 *16 SysAcc Ring -I Status None
A Shared System Access: 532 535 575 519 550 507 503 506
A 504 502 505 501 533


....JIM....

 

[merlinman]

I feel really confident that I said that same thing.

 

[glg01]

The answer in on page 387 of feature reference manual. lg

 

[ivtrook]

OMG! Sorry guys, i thought i had responded!

The customer tried dialing the internal number again, and it worked! Apparently the customer fat fingered it. I should have done it myself DUH! Once again I appreciate everyones responses!