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

Call forward on PRI or T1 not working

Status
Not open for further replies.

adc110

Vendor
Jul 26, 2007
373
US
I am attempting to setup a user (IP500 version 5.0 on both systems) to unconditionally forward their calls to an outside number using a PRI or a T1 (I have 2 systems one which has a full t1 and another has a partial PRI). When I call inbound on the either circuit and transfer to the extension the fowarding does not work. Is there something special that you need to configure to allow trunk to trunk transfer like you do on analog lines? My in-house test system which only has POTS lines with trunk transfer allowed works perfectly.
 
Does the telco require that you send outbound caller ID?
Like:

Short code 9N;
Feature Dial
telephone number Ns1234567890
line group 0 (or whatever your PRI/T1 Line group is)

I have seen this in the past and my solution was the outbound caller ID
 
I tried this but no luck. I modified all of my ARS entries to force caller id with your suggestion but did not make any difference. I am looking at the monitor trace but don't really see anything too suspicious. Just does not work. Do you know if you can force VMPRO to select a specific line to dial out on?
 
system - telephony - inhibit off switch transfer
there is a checkmark

Joe W.

FHandw., ACS

I don't suffer from insanity
I enjoy every moment of it :)
 
You cannot FWD calls that come in on a group set to "Collective" or "Collective Call Waiting"

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
It wasn't the inhibit switch as I had checked all of those parameters at the system level, user level as well as templates. I rebooted the system and it works. I was trying all sorts of options and now both systems work. I have no idea what the exact culprit was but it is now working great. I appreciate all of your help and assistance with this issue. I will keep an eye out to see if call forwarding mysteriously fails at any point and post if it happens again. I have many many system using call forwarding but never really had this type of issue where I couldn't trace the issue. Also - MikeGillespie the T1 does not accept any CLID information as it is all cloaked by AT&T with their main# and is not necessary to pass outbound but I would like to know - based on your post - if I do run into this issue and I want to allow each users CLID to pass out - how can you directly associate a specific CLID for VMPRO? Do you know how the IP Office sees the VMPRO as it dials out? Is it the NoUser? RAS? as I would need to create the appropriate CLID information for this information to pass out.
 
When VM Pro dials out it goes straight to system shortcodes, it isn't associated with any user :)

ACS - IP Office Implement

"What the Crocodile Hat....was that?
 
I've found that if you create a phantom ext it will not call forward unless you save the ext with a reboot not a merge.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top