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

CLID from outside POTS *72 fwd line causing issues with CFNA to Call Pilot

Status
Not open for further replies.

curtismo

MIS
Dec 4, 2006
699
US
We have a toll-free number delivered via ISDN-PRI trunk (along with other toll-frees), with DNIS routing to various endpoints. In this case I have a toll-free number that send the DNIS of a desk set primary DN, with that set CFNA to Call Pilot. When dialing the toll-free number directly, the DN rings, and rolls to voicemail as it should. Now we have set up a local POTS line with CLASS Call Forwarding (*72) set to this toll-free number as the endpoint. When we call this POTS number, it call forwards and rings the DN as it should; however, when the call no-answer forwards to Call Pilot, the system tells the caller: "You have been forwarded to a voicemail system. However, the person at..." 10-digit POTS number "...is not subscribed to this service." So basically, the POTS CLID of the CLASS-forwarded line is passed to Call Pilot, rather than the terminating

I have tried setting up an IDC entry to point to an ACD that points to the internal DN; same thing. Tried a phantom number DCFW to the internal DN; ring no answer (unsure where it was sending the call). Tried placing the 10-digit TN in Call Pilot as an additional Extension DN; didn't fix the issue. Tried both CLS SFA and SFD on the MARPd TN; no difference. Anyone know how to work around this?

System: CS1000E, 7.5, last deplist applied in June.
Call Pilot 5.0, patched to current patches in June.
IXC ISDN-PRI, DMS250 with 4-digit DNIS.
 
You wrote "Tried placing the 10-digit TN in Call Pilot as an additional Extension DN; didn't fix the issue". Don't ask why, but "enter 9, plus the 10 digit number"

So, rather than 4145551212, enter 94145551212

Find more at GHTROUT.com
 
That's kinda weird, but I bet it is a product of you being connected to a Nortel C.O. I bet you are set up Custom on your d-channel instead of NI2 and the Co_Type is probably D100 or D250. There use to be a setting in the Nortel C.O.'s in the LTDEF Table telling it that it was connected to an Sl-1, I wonder if that is your issue?
 
GHTROUT, tried both 84155551212 (we use 8 for AC1) and 94145551212 (where 414-555-1212 is changed to my POTS forwarded number). Same problem.

I think KCFLHRC may be on to something, as the PRI that my toll-free numbers come in on (along with outgoing LD) is setup as D250 DCH protocol. And of course the CO of the POTS line doing the CLASSS call forward is doing a database dip and handing it directly to my IXC - probably the same switch I'm connected to.

Anyhow, thanks for the suggestions. This may end up being a ticket opened with Avaya if I can't find a workaround.
 
I've worked around this in the past using a PCA instead of a phantom forwarded to Voicemail. However I realize not everyone has PCA licenses to burn.
 
Per a suggestion from our vendor, came up with a workaround. Yes, its a kludge.

Basically, set up in Call Pilot an SDN of the 10-digit forwarding number. Built a simple CP application consisting only of a Call Transfer block to the real extension DN, then pointed the SDN to this application. It works. Whatever.
 
Thanks, too, to guycable2 for the suggestion. I wish I had PCA at all to use.[surprise]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top