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

Remote Call Forwarding with Simultaneous Internal Alert

Status
Not open for further replies.

jag62470

IS-IT--Management
Jun 17, 2002
81
US
I'm trying to get this to work. I was able to get Remote Call Forwarding setup but I cannot get the Simultaneous Internal Alert to work as well. Is there a special trick to this. All I am trying to do is setup an extension to both ring internally and externally to a cell phone. Is this possible?

Thanks,

Jacob Gomez
Technical Services
Faith Assembly of God
 
A PRI INFORMATION



A Slot 12 Switch: 5ESS

A System: By line

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 1 12 4073126092 CallbyCall By Dial Plan

A Channel ID: 23 22 21 20 19 18 17 16 15 14
A 13 12 11 10 9 8 7 6 5 4
A 3 2 1

A Line PhoneNumber NumberToSend
A 821
A 822
A 823
A 824
A 825
A 826
A 827
A 828
A 829
A 830
A 831
A 832
A 833
A 834
A 835
A 836
A 837
A 838
A 839
A 840
A 841
A 842
A 843

Looks like I have by Dial Plan.

Thanks,

Jacob Gomez
Technical Services
Faith Assembly of God
 
Like I said, I have a work around for this. You have a pull at least 2 lines from your PRI group and create another one with them routed by line appearance, then assign them to the pool you use for your Simul RCF. You can even assign ARS restrictions to prevent the pool from ever going busy, or only being utilized when the other 21 channels are used. Here again is a sample of what I worked out:
A PRI INFORMATION



A Slot 4 Switch: 5ESS

A System: By line

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 1 4 CallbyCall By Dial Plan

A Channel ID: 21 20 19 18 17 16 15 14 13 12
A 11 10 9 8 7 6 5 4 3 2
A 1

A Line PhoneNumber NumberToSend
A 805
A 806
A 807
A 808
A 809
A 810
A 811
A 812
A 813
A 814
A 815
A 816
A 817
A 818
A 819
A 820
A 821
A 822
A 823
A 824
A 825

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 2 4 By Line Appearance

A Channel ID: 23 22

A Line PhoneNumber NumberToSend
A 826
A 827


Hope this helps. Also remember ANY lines into pools may affect the operator consoles, so be aware!
bill
 
did you make sure that you put the extra # sign at the beginning of your dial string? I have made this work before without having to do all the aforementioned.
 
Everything said here is absolutely correct. Please note the additional # that FoneDude66 has brought up. The string will actually begin with a #33.

The part the manual forgets to mention is the most critical part to getting this damn feature working. For some reason, you've got to give this station dial access to 890.

I absolutely guarantee that once you put this missing piece in that it will work.

I have wracked and wracked my brains over this one a number of times until I figured it out. I dunno why the manual never mentions it, but it is a very serious oversight.
 
I have this working in a number of PBXs, and it will do exactly what you want it to do: ring the station AND the person's cell phone at the same time.

And if you keep your coverage timers at default, Merlin Messaging (or whatever the local VM is) will pick up BEFORE the cell phone's service provider.

Add outcalling to the mix and your guy will be unable to hide from the office.

I've gotta go right now. But if this somehow doesn't work, I'll post a print of a working config ASAP.
 
Sorry about the rambling, but I forgot to mention something. RCF with Simultaneous Alert only works on a PRI. I think that was mentioned earlier.

What wasn't mentioned is format of the forwarded number. In most cases, you DO NOT want to preface the phone number with a "1". Secondly, you will want to make sure you include the area code, even when forwarding to a local number.

Let's say you live in 209 Area Code. Your dial sequence might be *33#2095551212#. When you do a print of the station, the forward destination will show #2095551212#. If that's what your printout shows you...you're In Like Flynn. It's like you're riding the PRI directly: send the Area Code without the "1".

By the way, using Inspect to check your programming may lead to confusion! Even if you program this properly, this extension will be listed during an Inspect of "RCF Extensions" and NOT listed while inspecting "RCF Extensions with Simultaneous Alert". Very misleading. If there's any doubt about where your extension is really assigned, blindly go through the steps of pulling it out of the RCF group and adding it into the RCF w/Simul Alert group.
 
Hi dagwood,

When I deal *33 my phone will say forward to. As soon as I press # I get an error tone. What am I doing wrong? How can I check to make sure the extension has dial access to 890?

Thanks for your input.


Thanks,

Jacob Gomez
Technical Services
Faith Assembly of God
 
I may have some haze on the dial string...you have a switch that's a little older than the one's I've been doing this with.

Please try touching the [FEATURE] button, then dialing 33. It would seem that *33 is the same thing, but there are little weirdnesses with those kind of things.

If your PBX still doesn't like it, then I'm sure that the extension is assigned as a "straight" RCF. You'll have to pull it out of that group and assign it to the "RCF w/Simult Alert" group. Please let me know if you need assistance with that. I've left that piece out for the moment, because I tend to be long-winded as it is.

We're almost there, Jacob. Thanks for hanging in! And thanks again to everyone who takes the time to help.
 
If it doesn't already exist, I'll take the time to write a FAQ on this feature.

More importantly, has this problem been resolved? Please write back.
 
RCF with Simultaneous page works on T-1 as well because you can actually assign the lines to a pool, and are "seen" as lines - PRI needs to be set up as "by line appearance", but 99% of customers have it set up by dial plan to utilize DID's
 
I was unaware of the ability to pull this off with a T1. I appreciate you throwing that into the mix, bassbill. Avaya's documentation leads you believe that this is a feature of PRI only. Cool beans.

Every site where I have this working has their PRI set up by dial plan, due to their need to support DID service. My little trick with the DIALOUT CD (allowing the extension permission to directly dial the PRI trunk) overcomes the "by line appearance" mandate.

The only reason I forgive Avaya for offering incomplete documentation is that I get such a kick out of seeing clever techs figure out a work-around. I've learned something here myself, and I really appreciate everyone's input. I'm hoping we'll hear from Jacob as to whether this thing is cooking for him or not.
 
Ahh, I see. IF you want RCF w/SA on a straight T1, THEN you must be set up to route by line appearance. I get it, I get it, I get it. I just need more sleep. Arghh.

So really then, I don't understand why the DIALOUT CD parameter makes this thing work...but it does.

Sorry about asking here, but is there any chance we could correspond privately, bassbill? We can't post email addresses on this forum, but perhaps you could slap a dot com on the end of my "handle" or forum name in your browser. You'll find my contact info there. I could stand to bounce a few things off 'ya.
 
Hi Dagwoodsystems,

According to the Magix Feature Reference 3.0 on page 378, it states that RCFw/SIA starting with version 2.2, requires 1 pool per station and any of the following: PRI, DS1 emulating TIE, or analogue TIE, and the pool cannot contain any lines used for private networking. But like you mentioned the instructions for using the feature are flawed in this document!

Now further perusing has revealed a more complete explanation of the feature in the Magix Pocket Ref 3.0 on page 11 which is part of the 2.2 update of features/changes when version 2.2 was introduced. This statement is the one that should be in the Feature Reference! (Who knows what the tech writers were "on" when that document was composed!)

I would have posted it in this posting, but could not get the item from my clipboard to paste here.

The reason I think a pool is required is because of certain timing and access issues in software if using ARS. So using a pool access code gives direct facility access, only one search to get out. This is just an educated guess on my part.

Hope this clears up some of the confusion with the RCF w/SIA feature.

....JIM....


 
Hey Guys,

I'm back. Sorry about that. I took a few days off and then took a few days to catch up.

I looked over the last few posts. I found out that the extension I am trying to do the Simultaneous Internal Alert was in the Remote Call Forward list. I went in and deleted it. I then went in and added the extension to RCF with Simul Int Alrt and chose Pool 893 (that's our PRI pool). The system took it but also added it back to the Remote Call Forward section as well.

When I press the forward button I then have to put in a 9 and then my cell phone number. When someone calls it rings in my office for 2 or 3 rings and then rings on my cell phone. I think I turned on the Delay Forwarding to make this work because the Simultaneous won't work.

Any thoughts?


Thanks,

Jacob Gomez
Technical Services
Faith Assembly of God
 
One caveat about this feature is that when you Inspect the RCF w/SA group, you won't see any members. Members added to this group appear in the "straight" RCF group. This is a bug.

Even so, I'm glad you went through the exercise of removing the extension from the RCF group and then adding back to the RCF w/SA group. This assures me that you've got the extension assigned correctly.

Did you also give this extension the ability to directly dial the 893 pool? If not, go to System Programming, Start, Extensions, Dial OutCd. Enter the extension in question, and pool code 893 when prompted.

Once this is done, walk back over to the assigned extension. Press [FEATURE] and dial 33#, followed by the area code and number, then # again. Don't use a "9" or a "1" in front of the area code. The "9" tells the PBX to send the digits through the ARS table, and we don't want to do that.

When this works correctly, BOTH desk and cell phone WILL ring simultaneously. What you are doing currently is still ordinary remote call forwarding, only you've added a delay to the forwarding. Unless what you've done actually satisfies your needs, please try what I've suggested here.
 
That worked. The problem was that the extension was set to directly dial 890 instead of 893. As soon as I changed it to 893 I was able to press feature 33# without the error code.

It's now ringing simultaneously.

Thank you, Thank you, Thank you for your help!


Thanks,

Jacob Gomez
Technical Services
Faith Assembly of God
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top