CLID Issue on Nortel Option 11C 1

[meinida]

Trying to get outgoing caller ID to work on PRI trunks. PSTN claims I need to set screening indicator to SCREENED.
Here is a copy of the current message.
From the signalling trace

24 01101100 6c Calling Party Number Tag (6c)
25 00001100 0c Calling Party length=12 octet(s)
26 -100---- 41 Type of number=Subscriber number
----0001 Numbering plan=ISDN/telephony plan
0------- Extension Indicator=Extension
27 ------00 80 Screening indicator=User provided,not screened
-00----- Presentation indicator=Presentation allowed
1------- Extension Indicator=No extension
28 00111001 39 Calling Party Number=9705423603

_____________________________________________

Anyone have any ideas?

 

[TAnselm]

LD 15
REQ: chg
TYPE: net_data
CUST: 0
OPT: <enter>
AC2 <enter>
FNP yes
ISDN yes
PNI <enter>
CLID yes
SIZE <enter>
INTL <enter>
ENTRY 0
HNTN <enter>
HLCL NPANXX (your NPA and NXX)
DIDN yes
<enter> to the end

 

[meinida]

This is already built using entry 1. that entry is assigned to the DN.

 

[1phonetech]

Can you paste an outgoing msg form ld 96 set at level 2 monitoring?

 

[meinida]

.set msgo 10 mon 2

.enl msgo 10
.
DCH 10 UIPE_OMSG CC_SETUP_REQ REF 00000044 CH 3 23 TOD 12:56:34 CK F6D0FD66
PRIM HDR: 01 00 01 00 53 00
MSG HDR: 08 02 44 00 0E 00
BCAP: 01 0D 13 00 01 10 00 00 22 00 00 00 00 00 00
CHID: 09 09 0D 00 29 00 03 00 01 00 17
PROGI: 1E 04 03 00 01 83
CLG#: 05 0A 07 00 02 00 04 00 03 06 0A 06
CAD#: 03 10 03 00 02 00 0A 00 09 07 0A 07 06 08 0A 0A
0A 06
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

DCH 10 UIPE_OMSG CC_SETUP_REQ REF 00000045 CH 3 22 TOD 12:56:34 CK F6D10224
PRIM HDR: 01 00 01 00 47 00
MSG HDR: 08 02 45 00 0E 00
BCAP: 01 0D 13 00 01 10 00 00 22 00 00 00 00 00 00
CHID: 09 09 0D 00 29 00 03 00 01 00 16
PROGI: 1E 04 03 00 01 83
CAD#: 03 10 03 00 41 00 0A 00 09 07 0A 07 06 08 05 08
07 08
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

DCH 10 UIPE_OMSG CC_PROCEED_REQ REF 00009CE6 CH 3 16 TOD 12:56:36 CK F6D109CF
PRIM HDR: 01 00 01 00 18 00
MSG HDR: 08 02 E6 39 09 00
CHID: 09 09 0D 00 29 00 03 00 01 00 10
UCAP: 2D 04 01 00 00 80

DCH 10 UIPE_OMSG CC_ALERT_REQ REF 00009CE6 CH 3 16 TOD 12:56:36 CK F6D109EA
PRIM HDR: 01 00 01 00 0C 00
MSG HDR: 08 02 E6 39 01 00
PROGI: 1E 04 03 00 01 88

DCH 10 UIPE_OMSG CC_DISC_REQ REF 000097E6 CH 3 5 TOD 12:56:42 CK F6D13AA2
PRIM HDR: 01 00 01 00 0D 00
MSG HDR: 08 02 E6 2F 02 00
CAUSE: 07 05 05 00 01 00 10

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 000097E6 CH 3 5 TOD 12:56:42 CK F6D13B6E
PRIM HDR: 01 00 01 00 06 00
MSG HDR: 08 02 E6 2F 1A 00

DCH 10 UIPE_OMSG CC_DISC_REQ REF 00000044 CH 3 23 TOD 12:56:46 CK F6D15809
PRIM HDR: 01 00 01 00 0D 00
MSG HDR: 08 02 44 00 02 00
CAUSE: 07 05 05 00 01 00 10

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 00000044 CH 3 23 TOD 12:56:46 CK F6D158D3
PRIM HDR: 01 00 01 00 06 00
MSG HDR: 08 02 44 00 1A 00

TIM000 12:56 23/2/2007 CPU 0

VAS008 ADMIN VSID 9 CUST -- TIME & DATE 12:56:50 23/02/2007

AUD370 VSID 9 CUST --
di
DCH 10 UIPE_OMSG CC_SETUP_RESP REF 00009CE6 CH 3 16 TOD 12:56:54 CK F6D19920
PRIM HDR: 01 00 01 00 11 00
MSG HDR: 08 02 E6 39 0F 00
PROGI: 1E 04 03 00 01 82
PCATG: 1D 03 01 00 01
s msgo 1
DCH 10 UIPE_OMSG CC_SETUP_REQ REF 00000046 CH 3 23 TOD 12:56:58 CK F6D1B246
PRIM HDR: 01 00 01 00 47 00
MSG HDR0: 08 02 46 00 0E 00
BCAP: 01 0D 13 00 01 10 00 00 22 00 00 00 00 00 00
CHID: 09 09 0D 00 29 00 03 00 01 00 17
PROGI: 1E 04 03 00 01 83
CAD#: 03 10 03 00 41 00 0A 00 09 07 0A 07 06 08 01 05
06 07
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

.
DCH000
.
There may be more than the one outgoing call, but I'm not sure how to tell. The first msg is for sure the start of the call.

 

[1phonetech]

It looks like the number is being sent out as private and presenting only the 4 digit extension number 3603. It should be presented as e.164. You might try to modify the ctyp in ld 86 for the rlb by using a dgt. Try npa first.

 

[meinida]

We changed this and it did not have any effect. We have a Cisco VOIP system connected to the same PSTN as the Nortel and it works. We traped the messages with a protocol anylyzer and the
Screening indicator=User provided,not screened
is the only difference that we can see. Is there anyway that you have ever heard to turn Screening on?

 

[1phonetech]

I don't think that is what is stopping it. Here ia a call made from a pbx with NI2 it is from the CLG# line. I left out the calling number at the end below but the set being called displays the calling number.

CLG#: 05 10 07 00 21 00 0A 00

The 21 indicates it's a "National number" and it's "ISDN/Telephony numbering plan E.164".

You had 02 which is "unknown type of number" and "private numbering plan".

The following 00 indicates "presentation allowed" and "user provided, not screened" which is what yours has.

What did you do to try and change the number to an NPA?

 

[meinida]

MEM AVAIL: (U/P): 883221 USED U P: 192695 103731 TOT: 1179647
DISK RECS AVAIL: 398
REQ chg
CUST 0
FEAT dgt
DMI 1
DEL
INST
CTYP npa

 

[meinida]

.enl msgo 10
.
DCH 10 UIPE_OMSG CC_SETUP_REQ REF 00000113 CH 3 23 TOD 17:17:24 CK F8AE917C
PRIM HDR: 01 00 01 00 53 00
MSG HDR: 08 02 13 02 0E 00
BCAP: 01 0D 13 00 01 10 00 00 22 00 00 00 00 00 00
CHID: 09 09 0D 00 29 00 03 00 01 00 17
PROGI: 1E 04 03 00 01 83
CLG#: 05 0A 07 00 21 00 04 00 03 06 0A 06
CAD#: 03 10 03 00 21 00 0A 00 09 07 0A 07 06 08 0A 0A
0A 06
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

DCH 10 UIPE_OMSG CC_PROCEED_REQ REF 0000BD67 CH 3 9 TOD 17:17:34 CK F8AED7D1
PRIM HDR: 01 00 01 00 18 00
MSG HDR: 08 02 E7 7A 09 00
CHID: 09 09 0D 00 29 00 03 00 01 00 09
UCAP: 2D 04 01 00 00 80

DCH 10 UIPE_OMSG CC_ALERT_REQ REF 0000BD67 CH 3 9 TOD 17:17:34 CK F8AED891
PRIM HDR: 01 00 01 00 0C 00
MSG HDR: 08 02 E7 7A 01 00
PROGI: 1E 04 03 00 01 88

DCH 10 UIPE_OMSG CC_DISC_REQ REF 00000113 CH 3 23 TOD 17:17:34 CK F8AEE0BF
PRIM HDR: 01 00 01 00 0D 00
MSG HDR: 08 02 13 02 02 00
CAUSE: 07 05 05 00 01 00 10

DCH 10 UIPE_OMSG CC_RELEASE_RESP REF 00000113 CH 3 23 TOD 17:17:34 CK F8AEE16A
PRIM HDR: 01 00 01 00 06 00
MSG HDR: 08 02 13 02 1A 00
dis msgo 10
.
Still had the same result I see the 21 now

 

[1phonetech]

yes but is still only sending out 4 digits. Can you paste your clid table from ld 21?

 

[meinida]

The other end wants 4 digits, they prefix NPA/NXX

 

[1phonetech]

If you set up the npa/nxx for a test call what happens?

Something else to try would be to change the ctyp fron npa to unkn

 

[meinida]

When I send them 10 digits, they ignore it and show a preset CLID #. So Basically I am asking them to show the CLID of the DN if I send them 4 digits (prefixing NPA/NXX) and show the pre-defined # if I don't send them any digits in the CLID field. This is the same setup that we have with the Cisco system, and it works. I think that is why they said we need to change the screening indicator to screened. Do you know if that can be done? We traped messages from both systems and that seems to be the only difference.

 

[1phonetech]

I don't know of a way to change the screening indicator. The pbx I made the test call from had the same screening indicator as yours does, and it presented the number to the far end.
Is the other end of the circuit the telco?
The 10 digit number that you send out, is it part of your DID range that the telco assigned you?

 

[HarrisD1200]

If you are sending the call to a CO, I've never heard of a CO Switch that will append NPA/NXX for calling ID. Find someone with a PRI test set to come out and terminate into the Smart Jack and test. Have them send different Calling Numbers, and map the results. In the absense of more evidence, I'd suggest this is a CO issue. My CO switches will only replace caller ID if I recieve 10 digits, and am programmed to replace it. Now, I will only replace the Caller ID with a DN that you own, so if you are sending a number you don't own, I will replace it with the default number you do own (which sounds like what is happening when you send 10 digits, and it gets changed).

 

[1phonetech]

Thats what I was trying to find out.

 

[meinida]

We are also the PSTN in this senario. That is why I kept bringing up the Cisco Platform. The vendor of the switch said that the screening ind. was the problem. The Cicso techs were able to change it on their platform and it worked. I will go back to the switch vendor and tell them that we can't change it on the Nortel. Maybe they will come up with a different solution. Thanks for all of you input!

 

[jjfuertesrico]

vdan,

I don't really know is this thread can help you:

http://www.tek-tips.com/viewthread.cfm?qid=1179068

I found to send different CLIDs through different PRIs.

Regards,
JJF.