COT PRI call forward

[pawels02]

Hi All,
I have following problem:
A COT analogue copper line is terminated on 2008 telephone (through ATDN on COT). A 2008 has an active call forward and should redirect the call over PRI trunk, but it fails.
But when I call that 2008 over PRI trunk, redirection is working fine
A 2008 has its own public number defined by CLID (it's defined only for PRI, not for COT)

COT------>2008------>PRI-out call rejected by PRI
PRI-in------->the same 2008------>PRI-out working fine

The message I receive from PRI-out in case of COT--->2008-->PRI-out:

DCH 9 UIPE_OMSG CC_SETUP_REQ REF 0000010C CH 9 1 TOD 11:24:58
PROGRESS: INTERWORKING WITH A PUBLIC NETWORK
PROGRESS: CALL IS NOT END TO END ISDN
CALLED #:0225942052 NUM PLAN: E164 ----> the number I'm redirecting the calls

DCH 9 UIPE_IMSG CC_REJECT_IND REF 0000010C CH 9 1 TOD 11:24:58
CAUSE: #21 - CALL REJECTED


The messages I receive from PRI-out in case of PRI in--->2008--->PRI-out:

DCH 9 UIPE_IMSG CC_SETUP_IND REF 00000700 CH 9 1 TOD 11:32:20
CALLING #:401833563 NUM PLAN: E164 ----> a calling number from outside world
CALLED #:225942112 NUM PLAN: E164 ----> a 2008 tel number defined by CLID

DCH 9 UIPE_OMSG CC_SETUP_REQ REF 0000010E CH 9 14 TOD 11:32:20
CALLING #:225942112 NUM PLAN: E164 ---->a 2008 tel number defined by CLID
CALLED #:0225942052 NUM PLAN: E164 ----> the number I'm redirecting the calls

DCH 9 UIPE_IMSG CC_ALERT_IND REF 0000010E CH 9 14 TOD 11:32:20
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

The problem is that there is no CALLING number of 2008 in case of redirection COT--->2008-->PRI-out and the PRI provider rejects the call with unknown originating number
Is there any way to insert 2008's number during redirection originating on COT line?

A 2008 is only example and all remaining tel sets working the same way.

I appreciated your help

Pawel

 

[acewarlock]

Post the TNB of the Copper trunk and the 2008 phone.

 

[pawels02]

Here it is:

TN 006 0 00 00
TYPE COT
CDEN 8D
CUST 0
XTRK XCOT
FWTM NO
BIMP 3COM
TRK ANLG
NCOS 0
RTMB 2 1
NITE 2112
SIGL LOP
SUPN YES
STYP BTS
AST NO
IAPG 0
SEIZ NO
PPID 0
BTID 0
S UNR DTN WTA LPR APN THFD BARD
P10 LOL
TKID 8460101
DATE 13 MAY 2007

DES OFFICE
TN 007 0 00 10
TYPE 2008
CDEN 8D
CUST 0
FDN
TGAR 0
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST 0
SCPW 1111
SFLT NO
CAC 3
CLS UNR FBD WTA LPR MTD FND HTD TDD HFD
MWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD TENA SWD LNA CNDD
CFTD SFD MRD DDV CNIA CDCA
ICDD CDMD MCTD CLBD AUTU
GPUD DPUD DNDD CFXA ARHD CLTA ASCD
CPFA CPTA ABDD CFHA FICD NAID DNAA BUZZ
UDI RCC HBTD AHD DDGA NAMA MIND PRSD NRWD NRCD NROD
EXR0
USRD ULAD RTDD PGND OCBD FLXD FTTC DNDY DNO3
CPND_LANG ROM
HUNT
TEN 2
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 2112 2 MARP
CPND
CPND_LANG ROMAN
NAME MDF
XPLN 27
DISPLAY_FMT FIRST,LAST
01 MCR 2110 0
CPND
CPND_LANG ROMAN
NAME AP TECH. ROOM
XPLN 27
DISPLAY_FMT FIRST,LAST
02 MCR 362110 0
03 MCR 362111 0
04 MCR 362112 0
05 TRN
06 CFW 20 00225942052
07
DATE 12 MAY 2007

 

[johnpoole]

that is blocked by the cdb opt, cfo.. the originating tn, (the analog cot) has an ncos that does not allow that call.. i would increase the ncos of that trunk or change the cdb opt to cff.. that can cause problems, depending on the cfxa sets.. cff allows the forwarding station control

john poole
bellsouth business
columbia,sc

 

[pawels02]

Hi john poole,
Call forward within my system works, it's not blocked by ncos, trunk, etc. The call is leaving my system and rejection is coming from PRI provider because it doesn't see originating number.
The situation is following:

incoming call ---> COT ----> 2008 (nbr 225942112) ---->PRI ---> no calling number ---> DCH CAUSE: #21 - CALL REJECTED --> this message is sent by PTT exchange where PRI is connected
incoming call ---> PRI -----> 2008 (nbr 225942112) ---> PRI---> DCH 9 CALLING #:225942112 NUM PLAN: E164 -------> call successful

So the problem is why forwarding station 2008 (nbr 25942112) doesn't show its number when the call comes from COT.
I set OCLI ALL in the NET_DATA so the last forwarding station should show its CLID. And this happens when the call comes from PRI, but not from COT

And this concerns all of my stations, phantoms.

 

[johnpoole]

reread that post OR maybe i need to re-type it..

for cfxa, the ncos of the inbound trunk has to be high enough to make the call if cdb opt cfo is used..

so if the call is coming in on a cot, ncos 1 and it takes a ncos 3 in your switch to make the call... either change the ncos of the cot or change the cdb opt to cff..

very common problem.. i can call internal, cfxa works.. but from external, it will not forward...


cdb opt cfo... the originating ncos controls
cdb opt cff.... the forwarding station controls

john poole
bellsouth business
columbia,sc

 

[pawels02]

Hi john poole,

Definitely this is not caused by ncos or the cdb opt to cff.
Besides the message CAUSE: #21 - CALL REJECTED has been sending by the provider's exchange, not by my trunk or system in general
I asked today my provider not to ignore my calls without unknown originating number (or dummy, fake, where behaviour was the same). In that case provider puts the leading number from the range assigned to my PRI (usually this is the first number from the range). And it works. So:

COT-->2008 (generally any station)--->no calling number--->PRI ---> provider inserts the leading number ---> call established, it's working now

But still I'm curious, why forwarding station (2008, 2616, phantom, etc) doesn't show its number when the call comes from COT, and for the call coming from a digital trunk does?

 

[johnpoole]

ok, what is the ncos of the inbound trunk? if that is high enough to make the call..then

does the targ of the two routes match? that can be a block..

CAUSE: #21 - CALL REJECTED


?? did you get that code as an error or did you enl msgo x on the d in 96.. your pri can reject the call and send that as well

john poole
bellsouth business
columbia,sc

 

[pawels02]

Yes, I did enl msgo x on the d in 96 and then I could see CAUSE: #21 - CALL REJECTED.
I agree that pri can reject the call and send that as well. But probably it would't be dch message. In my oppinion ncos, targ has nothing to do with dch message exchange. If targ, cos don't match you will never see dch messages
If it was ncos or targ the change did by the provider wouldn't help and I would still have a problem.
I removed targ from my routes and ncos is high enough.

Besides this message shows that the call had been made (I mean left my system)
B-channel #1 on card 9 had been used for the call

DCH 9 UIPE_IMSG CC_REJECT_IND REF 0000010C CH 9 1 TOD 11:24:58
CAUSE: #21 - CALL REJECTED

 

[acewarlock]

See The 2 after the SCR 2112, change it to a 0

KEY 00 SCR 2112 2 MARP
CPND
CPND_LANG ROMAN
NAME MDF
XPLN 27
DISPLAY_FMT FIRST,LAST
01 MCR 2110 0

 

[pawels02]

Hi acewarlock,

I changed but no impact. Actually there shouldn't be any impact because this is another CLID entry (properly configured. So If I don't see the previous one I will not see another one as well.

 

[johnpoole]

because you see the call reject on the d, your right.. if you had mentioned that 4 days ago it may have been a little faster to find a fix..

try this as a test, build a dsc for one of your inbound cot's that sends the call back out on the pri.. that will let you modify call type.. might not be the cure but maybe it will help find a work around

john poole
bellsouth business
columbia,sc