Option 11C -External Call Forward Issue

[hcmbmt]

I got an issue with External Call Forward All Call of Option 11C
Customer requirement:
- External Call Forward All Call is activated on Extension 1111.
- Incoming call to Analog Trunk -> Auto Attendant -> Dial to Extension 1111-> call is forwarded to an external number.

I did many test calls with Extension 1111:
- External Call Forward All Call works if making internal call to extension 1111
- External Call Forward All Call doesn't work for incoming calls.
- 3 parties (2 external number) conference works
- Trunk to trunk transfer 1- successful: Make 1st external call -> Press Transfer key-> make 2nd call -> wait for the called answer -> hang up handset
- Trunk to trunk transfer 2 - unsuccessful: Make 1st external call -> Press Transfer key-> make 2nd call -> hang up handset

Setting:
LD 20: Extension 1111: CLS CFXA FTTU
LD 15 RDR_DATA: OPT CFF, CFTA YES
LD 15 NET_DATA: TRXN YES, EXTT YES, FTOP FTLY
LD 14 COT, SUPN YES, STYP BTS

Anyone know how to fix this issue?
Please note that all the trunks are anlog trunk

Thanks.

 

[bluebells11]

Is the NCOS of the 2008s used to interface CallPilot high enough to make this call? Does your RPL in CallPilot allow this call?

 

[NortelMelo]

HCMBMT,
Checking the agents NCOS and the Call Pilots RPL to see if the call is allowed is the proper step to take. However if you find this to be the case, you may want to try and set up a dummy ACD Cue and in the NCFW place the DN of 1111. Then put the ACD Cue number in the Auto Attendant and try it.

This may work and allow you to keep the systems security intact.

Good luck and let us know how it goes

Nortelmelo

 

[hcmbmt]

Thanks all for your advise.
Bluebells 11:
- The CLS of Auto Attendant Voiceport is UNR.
- I forward extension 111 to my cellphone and make the test call. My cell phone show there is a incoming call but immediately it is disconnected. Then the original call fallback to extension 1111.

NortelMello:
I tried create ACDN and forward to External number but the result still same. Internal call to Extension 111 works.Trunk to trunk doesn't work.

 

[Firebird Scrambler]

If you plan to dial out on the same route that your incoming trunk uses then check in LD 16 under RDB that TRMB = YES.

Firebird Scrambler
Nortel and Avaya Meridian 1 / Succession and BCM / Norstar Programmer

Very advance high level knowledge on the Linux BCM phone system.

Website

http://somertel.com

 

[hcmbmt]

It already activated for all routes but still not work

TRMB YES
NEDC ETH
FEDC ETH

Any other idea?

 

[Firebird Scrambler]

What sort of Auto Attendant do you have?. Is it Call Pilot or Meridian Mail etc?. Is the outgoing number long distance?.

In cases where I have customers who have wanted specific outgoing calls to take place via voicemail, I've used a Phantom DN or ACD queue where the DN is within the same range that the extensions use on the phone system and that the outgoing number is also entered in the call barring tables because it's usually barred to prevent dial through fraud.

Are all your analogue trunks in the same route?. Are they loop or Ground start calling?.

You could try creating another route with one member in it so that the incoming call comes in on one route and dials out on another route.
This way, you can rule out trunk to trunk barring.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

 

[hcmbmt]

We use 3rd Auto Attendant (EVM 2006) which connected to Option 11C via Analog Extensions. I changed CLS of those analog extension ports to UNR.
2 routes 0 and 3 for out going and incoming calls. All trunks are Loop start.
I also tried to configure ACDN and use NCFW for the external forwarding but It doesn't work.

And not only the External Call Forward no working, same problem with the trunk to trunk transfer. A call I transfer immediately fallback to my extension if I don't wait the destination extension answers before hangup my handset.
It's ok if I inform the destination extension before finish the transferring.

 

[NortelMelo]

Sir,

This sounds like a trunk to trunk transfer block or may be a TARG / TGAR issue. You may have to check and see if JNT is programmed for your routes and the agents TARG / TGAR. Check in your BARS Load 87 to see if TARG / TGAR checking is turned on.

The other thing that just may be a bit of a stretch is that this can be related to your loop start trunks / sets as there is no disconnection supervision and could be hold up your trunks causing a busy. Do you get a fast busy... just curious about that. The fast busy can be caused by all of the above.

Good luck! Let us know!

Nortelmelo

 

[Firebird Scrambler]

Download the

http://www.ghtrout.com/files/ConversionUtility(BARS-TNB-More)_by_DB.zip

The data compiled will help you get a list of the TN's and DN's with relation to the trunks barring details being the important part. Also print off the barring tables in LD 49 and also the RDB and LTM information in LD 21.

Once you have all this, it should be possible to work out what you currently have set up.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

 

[hcmbmt]

NortelMelo:
1. TGAR of Extension 1111 (for transfer/forward) is 2
2. TAGR of Route 0 (for in/out call) is BLANK
I think no issue with restriction as I can do the supervision trunk to trunk transfer.
Maybe the system doesn't allow the un-supervision transfer. How to fix it?

Firebird Scrambler: Thanks for your file but it shows "runtime error"

I attached here capture some configuration of RDB, TNB, RDR_DATA, NET_DATA

 

[NortelMelo]

Sir,
FTOP options. Review the choices and see if you have the correct one in place. You also may want to see if changing the FEDC options in the route to JNT. Its been years since I had to deal with such an issue but something is rattling around in my old head that keeps saying JNT is the possible answer.

Hurts nothing to try it. Also I saw your trunks NCOS is a 1. You may want to check on the FRL associated with that NCOS in load 87. You never know until you look at all of the restriction possibilities.

Please let us all know the outcome!

Nortelmelo

 

[hcmbmt]

Hi NortelMelo,
I tried all options of FTOP (NET_DATA) but It doesn't work either FEDC of trunk route is JNT or ETH.
And also I'm sure that NCOS of trunks, extension are not restriction.
Any other idea for this case?

The tracing I did for Trunk (port 041 0 00 2) which is in used for Call forwarding.
Note: I make incoming call --> Auto Attendant (Extension 1042) --> Dial Extension 1111 (is forwarding to 600201278898666)

16:14:54 01/12/2016
IDLE TN 041 0 00 02


.
TIM000 16:15 1/12/2016 CPU 0
16:15:14 01/12/2016
ACTIVE TN 041 0 00 02 INDIRECT MW_CALL
ORIGDN 1111

ORIG 003 0 00 00 MARP 0 1042 L500
TERM 041 0 00 02 COT RMBR 3 2
TTR 000 0 00 07
DIAL 40 26 TTR 60
RCVR 62 SET 26

DIAL DN 600201278898666
MAIN_PM DIAL AUX_PM DDL
TALKSLOT ORIG 28 TERM 28
QUEU 128
CALL ID 0 395





.16:15:14 01/12/2016
ACTIVE TN 041 0 00 02 INDIRECT MW_CALL
ORIGDN 1111

ORIG 003 0 00 00 MARP 0 1042 L500
TERM 041 0 00 02 COT RMBR 3 2
TTR 000 0 00 07
DIAL 40 26 TTR 60
RCVR 62 SET 26

DIAL DN 600201278898666
MAIN_PM DIAL AUX_PM TEMPPATH
TALKSLOT ORIG 28 TERM 28
QUEU 128
CALL ID 0 395





.16:15:16 01/12/2016
ACTIVE TN 041 0 00 02 INDIRECT MW_CALL
ORIGDN 1111

ORIG 003 0 00 00 MARP 0 1042 L500
TERM 041 0 00 02 COT RMBR 3 2
TDTN 0 SLOT 14 PTY SLOT 14
TTR 000 0 00 07
DIAL 40 26 TTR 60
RCVR 62 SET 26

DIAL DN 600201278898666
MAIN_PM DIAL AUX_PM OUTPULSE
TALKSLOT ORIG 28 TERM 28
QUEU 128
CALL ID 0 395





.16:15:16 01/12/2016
ACTIVE TN 041 0 00 02
ORIG 041 0 00 02 COT RMBR 3 2
TERM NONE
DIAL DN NONE
MAIN_PM READY
TALKSLOT NONE
QUEU 2S
CALL ID 0 491





.16:15:24 01/12/2016
IDLE TN 041 0 00 02

 

[kstaff22]

I had somewhat similar issue with our system a couple weeks ago------------------it's the loop start trunks----they can't be forwarded off the system.Try changing the incoming trunk to ground--it will answer but will give you a trk error,

 

[Medo Shafik]

I have had the same issue with CS1K different releases 4.5 and 7 multi group and solved Avaya expert after created a new patch .

 

[joe2938]

Just a guess but do you suppose that the line provider is blocking this as from looking over all the post it should allow this, maybe as a security measure the line provider is blocking this